- Table of Contents
-
- 01-Fundamentals Command Reference
- 00-Preface
- 01-CLI commands
- 02-RBAC commands
- 03-Login management commands
- 04-FTP and TFTP commands
- 05-File system management commands
- 06-Configuration file management commands
- 07-Software upgrade commands
- 08-Automatic configuration commands
- 09-Tcl commands
- 10-Python commands
- 11-License management commands
- 12-Device management commands
- Related Documents
-
Title | Size | Download |
---|---|---|
12-Device management commands | 489.34 KB |
display cpu-usage configuration
display diagnostic-information
display transceiver eyediagram-diagnosis
monitor cpu-usage logging interval
monitor memory-usage logging interval
monitor resend memory-threshold
Device management commands
bootrom-access enable
Use bootrom-access enable to allow access to the BootWare menu during device startup.
Use undo bootrom-access enable to disable access to the BootWare menu during device startup.
Syntax
bootrom-access enable
undo bootrom-access enable
Default
A login user can press Ctrl+B during device startup to access the BootWare menu.
Views
User view
Predefined user roles
network-admin
Usage guidelines
By default, anyone can press Ctrl+B during startup to access the BootWare menu, load software, and manage storage media. To prevent unauthorized BootWare menu access, set a BootWare menu password or disable BootWare menu access.
Examples
# Disable access to the BootWare menu during device startup.
<Sysname> undo bootrom-access enable
Related commands
display bootrom-access
clock datetime
Use clock datetime to set the system time.
Syntax
clock datetime time date
Default
The system time is UTC time 00:00:00 01/01/2011.
Views
User view
Predefined user roles
network-admin
Parameters
time: Specifies a time in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.
date: Specifies a date in the MM/DD/YYYY or YYYY/MM/DD format. The value range for YYYY is 2000 to 2035. The value range for MM is 1 to 12. The value range for DD varies by month.
Usage guidelines
CAUTION: Change of the system time affects execution of system time-related features (such as scheduled tasks) and cooperative operation with other devices (such as log reporting and statistics collection). Before executing this command, make sure you understand its impact on the live network. |
Correct system time is essential to network management and communication. You must configure the system time correctly before you run the device on the network.
For the device to use the local system time, execute the clock protocol none command and this command in turn. The specified system time takes effect immediately. Then, the device uses the clock signals generated by its built-in crystal oscillator to maintain the system time.
A device power cycling operation restores the local system time to the default. After the device is power cycled, you must execute this command again to set the local system time.
Examples
# Set the system time to 08:08:08 01/01/2015.
<Sysname> clock datetime 8:8:8 1/1/2015
# Set the system time to 08:10:00 01/01/2015.
<Sysname> clock datetime 8:10 2015/1/1
Related commands
clock protocol
clock summer-time
clock timezone
display clock
clock protocol
Use clock protocol to specify the system time source.
Use undo clock protocol to restore the default.
Syntax
clock protocol { none | ntp }
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.
ntp: Uses NTP to obtain the UTC time. You must configure NTP correctly. For more information about NTP and NTP configuration, see Network Management and Monitoring Configuration Guide.
Usage guidelines
Correct system time is essential to network management and communication. You must configure the system time correctly before you run the device on the network.
The device can use the locally set system time, or obtain the UTC time from a time source on the network and calculate the system time.
If you execute the clock protocol none command, the device uses the locally set system time. The device then uses the clock signals generated by its built-in crystal oscillator to maintain the system time.
If you execute the clock protocol ntp command, the device obtains the UTC time through NTP and calculates the system time. The device then periodically synchronizes the UTC time and recalculates the system time.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Configure the device to use the local UTC time.
<Sysname> system-view
[Sysname] clock protocol none
clock summer-time
Use clock summer-time to set the daylight saving time.
Use undo clock summer-time to restore the default.
Syntax
clock summer-time name start-time start-date end-time end-date add-time
undo clock summer-time
Default
The daylight saving time is not set.
Views
System view
Predefined user roles
network-admin
Parameters
name: Specifies a name for the daylight saving time schedule, a case-sensitive string of 1 to 32 characters.
start-time: Specifies the start time in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.
start-date: Specifies the start date in one of the following formats:
· MM/DD. The value range for MM is 1 to 12. The value range for DD varies by month.
· month week day, where:
¡ month—Takes January, February, March, April, May, June, July, August, September, October, November or December.
¡ week—Represents week of the month. It takes first, second, third, fourth, fifth, or last.
¡ day—Takes Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.
end-time: Specifies the end time in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.
end-date: Specifies the end date in one of the following formats:
· MM/DD. The value range for MM is 1 to 12. The value range for DD varies by month.
· month week day, where:
¡ month—Takes January, February, March, April, May, June, July, August, September, October, November or December.
¡ week—Represents week of the month. It takes first, second, third, fourth, fifth, or last.
¡ day—Takes Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.
add-time: Specifies the time to be added to the standard time, in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.
Usage guidelines
Correct system time is essential to network management and communication. You must configure the system time correctly before you run the device on the network.
After you set the daylight saving time, the device recalculates the system time. To view the system time, use the display clock command.
Make sure all devices on the network are using the same daylight saving time as the local time.
Examples
# Set the system time ahead 1 hour for the period between 06:00:00 on 08/01 and 06:00:00 on 09/01.
<Sysname> system-view
[Sysname] clock summer-time PDT 6 08/01 6 09/01 1
Related commands
clock datetime
clock timezone
display clock
clock timezone
Use clock timezone to set the time zone.
Use undo clock timezone to restore the default.
Syntax
clock timezone zone-name { add | minus } zone-offset
undo clock timezone
Default
The UTC time zone is used.
Views
System view
Predefined user roles
network-admin
Parameters
zone-name: Specifies a time zone by its name, a case-sensitive string of 1 to 32 characters.
add: Adds an offset to the UTC time.
minus: Decreases the UTC time by an offset.
zone-offset: Specifies an offset to the UTC time, in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.
Usage guidelines
Correct system time is essential to network management and communication. You must configure the system time correctly before you run the device on the network.
After you set the time zone, the device recalculates the system time. To view the system time, use the display clock command.
Make sure all devices on the network are using the same time zone as the local time.
Examples
# Set the name of the time zone to Z5, and add 5 hours to the UTC time.
<Sysname> system-view
[Sysname] clock timezone Z5 add 5
Related commands
clock datetime
clock summer-time
display clock
command
Use command to assign a command to a job.
Use undo command to revoke a command.
Syntax
command id command
undo command id
Default
No command is assigned to a job.
Views
Job view
Predefined user roles
network-admin
Parameters
id: Specifies an ID for the command, in the range of 0 to 4294967295. A command ID uniquely identifies a command in a job. Commands in a job are executed in ascending order of their command IDs.
command: Specifies the command to be assigned to the job.
Usage guidelines
To assign a command (command A) to a job, you must first assign the job the command or commands for entering the view of command A.
If you specify the ID of an existing command for another command, the existing command is replaced.
Make sure all commands in a schedule are compliant to the command syntax. The system does not examine the syntax when you assign a command to a job.
If a command requires a yes or no answer, the system always assumes that a Y or Yes is entered. If a command requires a character string input, the system assumes that either the default character string (if any) or a null string is entered.
A job cannot contain the telnet, ftp, ssh2, or monitor process command.
Examples
# Assign commands to the backupconfig job to back up the startup.cfg file to the TFTP server at 192.168.100.11.
<Sysname> system-view
[Sysname] scheduler job backupconfig
[Sysname-job-backupconfig] command 2 tftp 192.168.100.11 put flash:/startup.cfg backup.cfg
# Assign commands to the shutdownGE job to shut down GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] scheduler job shutdownGE
[Sysname-job-shutdownGE] command 1 system-view
[Sysname-job-shutdownGE] command 2 interface gigabitethernet 1/0/1
[Sysname-job-shutdownGE] command 3 shutdown
Related commands
scheduler job
copyright-info enable
Use copyright-info enable to enable copyright statement display.
Use undo copyright-info enable to disable copyright statement display.
Syntax
copyright-info enable
undo copyright-info enable
Default
Copyright statement display is enabled.
Views
System view
Predefined user roles
network-admin
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 clock
Use display clock to display the system time, date, time zone, and daylight saving time.
Syntax
display clock
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display the system time and date when the time zone is not specified.
<Sysname> display clock
10:09:00.258 UTC Fri 03/16/2015
The time is in the hour:minute:second.milliseconds format.
# Display the system time and date when the time zone Z5 is specified.
<Sysname> display clock
15:10:00.152 Z5 Fri 03/16/2015
Time Zone : Z5 add 05:00:00
# Display the system time and date when the time zone Z5 and daylight saving time PDT are specified.
<Sysname> display clock
15:11:00.211 Z5 Fri 03/16/2015
Time Zone : Z5 add 05:00:00
Summer Time : PDT 06:00:00 08/01 06:00:00 09/01 01:00:00
Related commands
clock datetime
clock timezone
clock summer-time
display copyright
Use display copyright to display the copyright statement.
network-admin
network-operator
# Display the copyright statement.
...
display cpu-usage
Use display cpu-usage to display the current CPU usage statistics.
Syntax
display cpu-usage [ summary ] [ slot slot-number [ cpu cpu-number [ core { core-number| all } ] ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
summary: Displays CPU usage statistics in table form. If you do not specify this keyword, the command displays CPU usage statistics in text form.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays CPU usage statistics for all member devices.
cpu cpu-number: Specifies a CPU by its number.
core core-number: Specifies a CPU core by its number.
core all: Specifies all CPU cores.
Usage guidelines
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
Slot 1 CPU 0 CPU usage:
1% in last 5 seconds
1% in last 1 minute
1% in last 5 minutes
# Display the current CPU usage statistics in table form.
<Sysname> display cpu-usage
Slot CPU Last 5 sec Last 1 min Last 5 min
1 0 17% 29% 28%
Table 1 Command output
Field |
Description |
x% in last 5 seconds Last 5 sec |
Average CPU or CPU core usage during the most recent 5-second interval. |
y% in last 1 minute Last 1 min |
Average CPU or CPU core usage during the most recent 1-minute interval. |
z% in last 5 minutes Last 5 min |
Average CPU or CPU core usage during the most recent 5-minute interval. |
display cpu-usage configuration
Use display cpu-usage configuration to display CPU usage monitoring settings.
Syntax
display cpu-usage configuration [ slot slot-number [ cpu cpu-number ] ]
Views
Any view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays the CPU usage monitoring settings for the master device.
cpu cpu-number: Specifies a CPU by its number.
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 99%.
Current minor alarm threshold is 98%.
Current recovery-threshold is 50%.
Table 2 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 recovery threshold is xxx. |
CPU usage recovery threshold. |
Related commands
monitor cpu-usage enable
monitor cpu-usage interval
monitor cpu-usage threshold
display cpu-usage history
Use display cpu-usage history to display the historical CPU usage statistics in a coordinate system.
Syntax
display cpu-usage history [ job job-id ] [ slot slot-number [ cpu cpu-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
job job-id: Specifies a process by its ID. The value range for job-id is 1 to 2147483647. If you do not specify a process, this command displays the statistics for the entire system's CPU usage (the total CPU usage of all processes). To view the IDs and names of the running processes, use the display process command. For more information, see Network Management and Monitoring Configuration Guide.
slot slot-number: Specifies an IRF member device by its member ID. If you specify a process but do not specify a member device, this command displays the statistics for the process on the master device. If you do not specify any options, this command displays the statistics for all processes on all member devices.
cpu cpu-number: Specifies a CPU by its number. If you specify a process but do not specify a CPU, this command displays the statistics for the default CPU. If you do not specify a process or CPU, this command displays the historical statistics for all CPUs.
Usage guidelines
After CPU usage monitoring is enabled, the system regularly samples CPU usage and saves the samples to the history record buffer. This command displays the most recent 60 samples in a coordinate system as follows:
· The vertical axis represents the CPU usage. If a statistic is not a multiple of the usage step, it is rounded up or down to the closest multiple of the usage step. For example, if the CPU usage step is 5%, the statistic 53% is rounded up to 55%, and the statistic 52% is rounded down to 50%.
· The horizontal axis represents the time.
· Pound signs (#) indicate the CPU usage. The value on the vertical axis for the topmost pound sign at a specific time represents the CPU usage at that time.
Examples
# Display the historical CPU usage statistics.
<Sysname> display cpu-usage history
100%|
95%|
90%|
85%|
80%|
75%|
70%|
65%|
60%|
55%|
50%|
45%|
40%|
35%|
30%|
25%|
20%|
15%| #
10%| ### #
5%| ########
------------------------------------------------------------
10 20 30 40 50 60 (minutes)
cpu-usage (Slot 1 CPU 0) last 60 minutes (SYSTEM)
The output shows the following items:
· Process name. The name SYSTEM represents the entire system.
· CPU that is holding the process: CPU 0 in slot 1.
· Historical CPU usage statistics for the entire system during the last 60 minutes.
¡ 12 minutes ago—Approximately 5%.
¡ 13 minutes ago—Approximately 10%.
¡ 14 minutes ago—Approximately 15%.
¡ 15 minutes ago—Approximately 10%.
¡ 16 and 17 minutes ago—Approximately 5%.
¡ 18 minutes ago—Approximately 10%.
¡ 19 minutes ago—Approximately 5%.
¡ Other time—2% or lower.
monitor cpu-usage enable
monitor cpu-usage interval
display device
Use display device to display device information.
Syntax
display device [flash | usb ] [ slot slot-number [ subslot subslot-number ] | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
flash: Displays flash memory information.
usb: Displays USB interface information.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays information for all member devices.
subslot subslot-number: The value for the subslot-number argument is fixed at 0, which does not make any sense.
verbose: Displays detailed information. If you do not specify this keyword, this command displays brief information, and does not display firewall card information.
Usage guidelines
If you do not specify the flash and usb keywords, this command displays information about member devices.
Examples
# Display device information.
<Sysname> display device
Slot 1
Slot Type State Subslot Soft Ver Patch Ver
1 S5136S-8FP4XS-EI-Q Master 0 S5136S-8FP4XS-EI-Q-6653P None
02
Table 3 Command output
Field |
Description |
Type |
Device type. |
State |
Role of the device in an IRF fabric: · Master—The device is the master. · Standby—The device is a subordinate member. |
Soft Ver |
Software version of the device. |
Patch Ver |
Most recently released patch image version that is running on the device. If no patch image is installed, this field displays None. If both incremental and non-incremental patch images are running on the device, this field displays the most recently released incremental patch image version. For more information about patch image types, see "Upgrading software." |
display device manuinfo
Use display device manuinfo to display electronic label information for the device.
Syntax
display device manuinfo [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays electronic label information for all member devices.
Usage guidelines
An electronic label contains the permanent configuration information, including the hardware serial number, manufacturing date, MAC address, and vendor name. The data is written to the storage component during hardware debugging or testing. This command displays only part of the electronic label information.
Examples
# Display electronic label information for the device.
<Sysname> display device manuinfo
...
display diagnostic-information
Use display diagnostic-information to display or save operating information for features and hardware modules.
Syntax
display diagnostic-information [ hardware | ifmgr | infrastructure | l2 | l3 | service ] [ key-info ] [ filename ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
hardware: Specifies hardware-related operating information.
ifmgr: Specifies IFMGR-related operating information.
infrastructure: Specifies operating information for the fundamental features.
l2: Specifies operating information for the Layer 2 features.
l3: Specifies operating information for the Layer 3 features.
service: Specifies operating information for Layer 4 and upper-layer features.
key-info: Displays or saves only critical operating information. The device might have a large amount of operating information if an exception occurs or after the device runs for a long period of time. Specifying this keyword reduces the command execution time and helps you focus on critical operating information. If you do not specify this keyword, the command displays or saves both critical and non-critical operating information.
filename: Saves the information to a file. The filename argument must use the .tar.gz extension. If you do not specify this argument, the command prompts you to choose whether to save the information to a file or display the information.
Usage guidelines
You can use one of the following methods to collect operating statistics for diagnostics and troubleshooting:
· Use separate display commands to collect operating information feature by feature or module by module.
· Use the display diagnostic-information command to collect operating information for multiple or all features and hardware modules.
To save storage space, this command automatically compresses the information before saving the information to a file. To view the file content:
1. Use the tar extract command to extract the file.
2. Use the gunzip command to decompress the extracted file.
3. Use the more command to view the content of the decompressed file.
If you abort the display diagnostic-information command, the gunzip command might not be able to decompress the extracted file. To decompress the extracted file, export the extracted file to a PC that is running Linux, and use the gunzip -c command.
If you do not specify a file name for the command, the system prompts you to choose whether to display or save the information. If you choose to save the information, the system automatically assigns a file name and displays the file name in brackets. For file name uniqueness, the file name includes the device name and the current system time. If the device name contains any of the following special characters, the system uses an underscore (_) to replace each special character: forward slashes (/), backward slashes (\), colons (:), asterisks (*), question marks (?), less than signs (<), greater than signs (>), pipeline signs (|), and quotation marks ("). For example, device name A/B will change to A_B in the file name, as in flash:/diag_A_B_20160101-000438.tar.gz.
If you do not specify any feature parameters, this command displays or saves the operating information for all features and modules.
This command does not support the |, >, and >> options.
While the device is executing this command, do not execute any other commands. Executing other commands might affect the collected operating information.
Examples
# Display the operating information for all features and modules.
<Sysname> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N]:n
===============================================
===============display clock===============
14:03:55 UTC Thu 01/05/2015
=================================================
===============display version===============
...
# Save the operating information to the default file.
<Sysname> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N]:y
Please input the file name(*.tar.gz)[flash:/diag_Sysname_20160101-024601.tar.gz]:
Diagnostic information is outputting to flash:/diag_Sysname_20160101-024601.tar.gz.
Please wait...
Save successfully.
Press Enter when the system prompts you to enter the file name.
# Save the operating information for all features and modules to file test.tar.gz.
<Sysname> display diagnostic-information test.tar.gz
Diagnostic information is outputting to flash:/test.tar.gz.
Please wait...
Save successfully.
Related commands
gunzip
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 4 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 an IRF member device by its member ID. If you do not specify a member device, this command displays temperature information for all member devices.
Examples
# Display information about all temperature sensors on the device.
<Sysname> display environment
System temperature information (degree centigrade):
----------------------------------------------------------------------
Slot Sensor Temperature Lower Warning Alarm Shutdown
1 MAC 45 0 99 102 107
1 PHY0 36 0 112 117 NA
1 POE 38 0 112 117 NA
1 Optmod NA NA NA NA NA
Table 5 Command output
Field |
Description |
System Temperature information (degree centigrade) |
Temperature information (°C). |
sensor |
Temperature sensor: · MAC—MAC chip sensor. · PHY0—PHY chip sensor. · PoE—PoE chip sensor. · Optmod—Transceiver module sensor. |
Slot |
Sensor position. |
Temperature |
Current temperature. |
Lower |
Lower temperature limit. If the device does not support this field, this field displays NA. |
Warning |
Warning temperature threshold. If the device does not support this field, this field displays NA. |
Alarm |
Alarming temperature threshold. If the device does not support this field, this field displays NA. |
Shutdown |
Shutdown temperature threshold. When the sensor temperature reaches the limit, the system shuts down automatically. If the device does not support this field, this field displays NA. |
display fan
Use display fan to display fan tray operating status information.
Syntax
display fan [ slot slot-number [ fan-id ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays fan tray operating status information for all member devices.
fan-id: Specifies a fan tray by its ID. If you do not specify a fan tray, this command displays operating status information for all fan trays at the specified position.
Examples
# Display the operating states of all fan trays.
<Sysname> display fan
Slot 1:
Fan 1:
State : Normal
Table 6 Command output
Field |
Description |
Slot 1 |
Member device number. |
Fan 1 |
Fan tray number. |
State |
Fan tray status: · Absent—The slot is not installed with a fan tray. · Fault—The fan tray is faulty. · Normal—The fan tray is operating correctly. · FanDirectionFault—The actual airflow direction is not the preferred direction. |
display memory
Use display memory to display memory usage information.
Syntax
display memory [ summary ] [ slot slot-number [ cpu cpu-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
summary: Displays brief information about memory usage. If you do not specify this keyword, the command displays detailed information about memory usage.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays memory usage for all member devices.
cpu cpu-number: Specifies a CPU by its number.
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:
Slot 1:
Total Used Free Shared Buffers Cached FreeRatio
Mem: 984560 456128 528432 0 4 45616 53.7%
-/+ Buffers/Cache: 410508 574052
Swap: 0 0 0
LowMem: 739824 375552 364272 -- -- -- 49.2%
HighMem: 244736 80576 164160 -- -- -- 67.1%
# Display brief memory usage information.
<Sysname> display memory summary
Memory statistics are measured in KB:
Slot CPU Total Used Free Buffers Caches FreeRatio
1 0 984560 456128 528432 4 45616 53.7%
Low memory statistics are measured in KB:
Slot CPU Total Used Free Buffers Caches FreeRatio
1 0 739824 375552 364272 -- -- 49.2%
High memory statistics are measured in KB:
Slot CPU Total Used Free Buffers Caches FreeRatio
1 0 244736 80576 164160 -- -- 67.1%
Table 7 Command output
Field |
Description |
Mem |
Memory usage information. |
Total |
Total size of the physical memory space that can be allocated. The memory space is virtually divided into two parts. Part 1 is solely used for kernel code, kernel management, and ISSU functions. Part 2 can be allocated and used for such tasks as running service modules and storing files. The size of part 2 equals the total size minus the size of part 1. |
Used |
Used physical memory. |
Free |
Free physical memory. |
Shared |
Physical memory shared by processes. If this field is not supported, two hyphens (--) are displayed. |
Buffers |
Physical memory used for buffers. If this field is not supported, two hyphens (--) are displayed. |
Cached Caches |
Physical memory used for caches. If a memory threshold is reached, part of memory used for caches can be automatically released for other services. If this field is not supported, two hyphens (--) are displayed. |
FreeRatio |
Free memory ratio. The free memory includes the free physical memory and the part of memory used for caches that can be automatically released for other services when a memory threshold is reached. |
-/+ 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. |
LowMem |
Low-memory usage information. |
HighMem |
High-memory usage information. |
display memory-threshold
Use display memory-threshold to display memory alarm thresholds and statistics.
Syntax
display memory-threshold [ slot slot-number [ cpu cpu-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays the memory usage thresholds and statistics for the master device.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
For more information about memory usage notifications, see log information containing MEM_EXCEED_THRESHOLD or MEM_BELOW_THRESHOLD.
Examples
# Display memory alarm thresholds and statistics.
<Sysname> display memory-threshold
Memory usage threshold: 100%
Free-memory thresholds:
Minor: 60M
Severe: 56M
Critical: 52M
Normal: 64M
Current free-memory state: Normal (secure)
Free-memory event statistics:
[Back to secure state]
First notification: 0.0
Latest notification: 0.0
Total number of notifications sent: 0
[Entered early-warning state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Back to normal state]
First notification: 0.0
Latest notification: 0.0
Total number of notifications sent: 0
[Entered minor alarm state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Back to minor alarm state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Entered severe alarm state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Back to severe alarm state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Entered critical alarm state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
Table 8 Command output
Field |
Description |
Free-memory thresholds Minor Severe Critical Normal |
Free-memory thresholds: · Minor—Minor alarm threshold in MB. · Severe—Severe alarm threshold in MB. · Critical—Critical alarm threshold in MB. · Normal—Normal state threshold in MB. |
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. |
First notification at |
Time when the alarm notification was sent for the first time, in the format of yyyy-mm-dd hh:mm:ss.msec. |
Latest notification at |
Time when the alarm notification was sent most recently in the format of yyyy-mm-dd hh:mm:ss.msec. |
Total number of notification send |
Total number of the alarm notifications that were sent. |
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 an IRF member device by its member ID. 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 power module information.
<Sysname> display power
Slot 1:
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Normal AC -- -- --
Table 9 Command output
Field |
Description |
PowerID |
Power module ID. |
State |
Power module status. · Absent—The slot is not installed with a power module. · Fault—The power module is faulty. · Normal—The power module is operating correctly. |
Mode |
Mode of the power module: · AC—AC power module. · DC—DC power module. |
Current(A) |
Output current of the power module, in amperes. If this field is not supported, two hyphens (--) are displayed. |
Voltage(V) |
Output voltage of the power module, in volts. If this field is not supported, two hyphens (--) are displayed. |
Power(W) |
Output power of the power module, in watts. If this field is not supported, two hyphens (--) are displayed. |
display scheduler job
Use display scheduler job to display job configuration information.
Syntax
display scheduler job [ job-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
job-name: Specifies a job by its name, a case-sensitive string of 1 to 47 characters. If you do not specify a job, this command displays configuration information for all jobs.
Examples
# Display configuration information for all jobs.
<Sysname> display scheduler job
Job name: saveconfig
copy startup.cfg backup.cfg
Job name: backupconfig
Job name: creat-VLAN100
system-view
vlan 100
// The output shows that the device has three jobs: the first has one command, the second does not have any commands, and the third has two commands. Jobs are separated by blank lines.
display scheduler logfile
Use display scheduler logfile to display job execution log information.
Syntax
display scheduler logfile
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display job execution log information.
<Sysname> display scheduler logfile
Logfile Size: 1902 Bytes.
Job name : shutdown
Schedule name : shutdown
Execution time : Tue Dec 27 10:44:42 2015
Completion time : Tue Dec 27 10:44:47 2015
--------------------------------- Job output -----------------------------------
<Sysname>system-view
System View: return to User View with Ctrl+Z.
[Sysname]interface rang gigabitethernet 1/0/1 to gigabitethernet 1/0/3
[Sysname-if-range]shutdown
Table 10 Command output
Field |
Description |
Logfile Size |
Size of the log file, in bytes. |
Schedule name |
Schedule to which the job belongs. |
Execution time |
Time when the job was started. |
Completion time |
Time when the job was completed. If the job has never been executed or the job does not have any commands, this field is blank. |
Job output |
Commands in the job and their output. |
Related commands
reset scheduler logfile
display scheduler reboot
Use display scheduler reboot to display the automatic reboot schedule.
Syntax
display scheduler reboot
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display the automatic reboot schedule.
<Sysname> display scheduler reboot
System will reboot at 16:32:00 05/23/2015 (in 1 hours and 39 minutes).
scheduler reboot at
scheduler reboot delay
display scheduler schedule
Use display scheduler schedule to display schedule information.
Syntax
display scheduler schedule [ schedule-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
schedule-name: Specifies a schedule by its name, a case-sensitive string of 1 to 47 characters. If you do not specify a schedule, this command displays information about all schedules.
Examples
# Display information about all schedules.
<Sysname> display scheduler schedule
Schedule name : shutdown
Schedule type : Run once after 0 hours 2 minutes
Start time : Tue Dec 27 10:44:42 2015
Last execution time : Tue Dec 27 10:44:42 2015
Last completion time : Tue Dec 27 10:44:47 2015
Execution counts : 1
-----------------------------------------------------------------------
Job name Last execution status
shutdown Successful
Table 11 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 system stability and status information. If you do not specify this keyword, the command displays detailed information about CPU role and status.
Usage guidelines
The device startup process takes some time. If the values of the status fields do not change to Stable, execute this command multiple times to identify the devices that are not in Stable state. You can also use other commands to identify the faulty components. For example:
· Use the display device command to identify the device operating status.
· Use the display 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 system stability and status information.
<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
Redundancy state: No redundancy
Slot CPU Role State
1 0 Active Stable
Table 12 Command output
Field |
Description |
System state |
Operating status of all member devices: · Stable—All member devices are operating stably. · Not ready—The system is not operating stably. |
Redundancy state |
This field is not supported in the current software version. System redundancy status: · Stable—Member devices are operating stably. You can perform a switchover. · No redundancy—The system has only one member device. You cannot perform a switchover. · Not ready—The system is not operating stably. You cannot perform a switchover. |
Role |
Role of the device in the system. The value for this field is Active, which indicates the device. |
State |
This field is not supported in the current software version. Member device status: · Stable—The member device is operating stably. · Board inserted—The member device has just been installed. · Kernel initiating—Member device kernel is being initialized. · Service starting—Services are starting on the member device. · Service stopping—Services are stopping on the member device. · HA Batch backup—An HA batch backup is going on. · Interface data batch backup—An interface data batch backup is in progress. |
* |
The object is not operating stably. |
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 alarm information 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 13 Command output for 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 bias low warning |
Early warning on a low transmit bias current. |
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. |
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/1.
<Sysname> display transceiver alarm interface gigabitethernet 1/0/1
GigabitEthernet1/0/1 transceiver current alarm information:
RX signal loss
RX power low
Table 14 Command output
Field |
Description |
transceiver current alarm information |
Alarms present on the transceiver module. |
RX signal loss |
Receive signal loss. |
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/1.
<Sysname> display transceiver diagnosis interface gigabitethernet 1/0/1
GigabitEthernet1/0/1 transceiver diagnostic information:
Current diagnostic parameters:
Temp.(C) Voltage(V) Bias(mA) RX power(dBm) TX power(dBm)
36 3.31 6.13 -35.64 -5.19
Alarm thresholds:
Temp.(C) Voltage(V) Bias(mA) RX power(dBm) TX power(dBm)
High 50 3.55 1.44 -10.00 5.00
Low 30 3.01 1.01 -30.00 0.00
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 15 Command output
Field |
Description |
transceiver diagnostic information |
Digital diagnosis information for the transceiver module in the interface. |
Temp.(C) |
Temperature in °C, accurate to 1°C. |
Voltage(V) |
Voltage in V, accurate to 0.01 V. |
TEC Curr. (%) |
TEC current in percentage, accurate to 0.01%. |
Laser Temp.(C) |
Laser temperature in °C, accurate to 0.01°C. |
Bias(mA) |
Bias current in mA, accurate to 0.01 mA. |
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. |
RX power(dBm) |
Receive power in dBm, accurate to 0.01 dBm. |
TX power(dBm) |
Transmit power in dBm, accurate to 0.01 dBm. |
High |
High alarm threshold or high early warning threshold. |
Low |
Low alarm threshold or low early warning threshold. |
Warning threshold |
Early warning threshold. |
Total average launch power(dBm) |
Total average launch power on the multi-lane transceiver module in dBM, accurate to 0.01 dBm. |
display transceiver eyediagram-diagnosis
Use display transceiver eyediagram-diagnosis to diagnose transceiver modules and display diagnosis information in an eye diagram.
Syntax
display transceiver eyediagram-diagnosis interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
Parameters
interface [ interface-type interface-number ]: Specifies an interface by its type and number. If no interface is specified, this command displays the diagnostic results on every transceiver module.
Usage guidelines
This command is used to simulate the quality of data transmission from professional testing instruments. It obtains the sampling values of received data on chips and outputs the diagnostic results of transceiver modules in an eye diagram. This facilitates users in analyzing and evaluating the data transmission quality of transceiver modules.
You can analyze the data transmission quality of transceiver modules through eye diagrams as follows:
· A larger eye opening area with a clearer shape indicates more stable signal transmission and better quality. The eye opening area is the blank area above and below the central line (0mV line).
· No digits in the eye opening area indicate good data transmission quality. If the eye opening area has digits, the data transmission quality is poor.
Examples
# Diagnose the transceiver module in interface GigabitEthernet 1/0/1, and display the diagnostic results in an eye diagram.
<Sysname> display transceiver eyediagram-diagnosis interface gigabitethernet 1/0/1
This operation might consume a large amount of system resources. It might cause unknown risks and might take several minutes. Continue?[Y/N]:y
+--------------------------------------------------------------------+
| EYESCAN Phy: 0x0e1 lane_mask: 0x01 |
+--------------------------------------------------------------------+
Each character N represents approximate error rate 1e-N at that location
UI/64 : -30 -25 -20 -15 -10 -5 0 5 10 15 20 25 30
: -|----|----|----|----|----|----|----|----|----|----|----|----|-
128mV : 111111111111111111111111112222322222222211111111111111111111111
124mV : 111111111111111111111111122233332222222221111111111111111111111
120mV : 111111111111111111111111222333333332222222211111111111111111111
115mV : 111111111111111111111112223334443333222222221111111111111111111
111mV : 111111111111111111111122233344444333322222222111111111111111111
107mV : 111111111111111111111122233445544433332222222211111111111111111
103mV : 111111111111111111111222334456655544333332222222111111111111111
99mV : 111111111111111111112223344566665544433333222222211111111111111
95mV : 11111111111111111111222344556776655443333322222221111111111111
91mV : 11111111111111111112223345567 :766554443333222222111111111111
86mV : 11111111111111111122233455677 : 76655444333322222211111111111
82mV : 111111111111111111223344567----+---7665544433322222221111111111
78mV : 111111111111111112223345667 : :76655444333222222111111111
74mV : 11111111111111112223345677: : :77665544333322222111111111
70mV : 1111111111111111223344567 7 : : 76655443332222211111111
66mV : 1111111111111112223345677 : : : 7665444333222221111111
62mV : 111111111111112223345667--+----+----+----+776554433322222111111
57mV : 111111111111112223445677 : : : :76655443332222111111
53mV : 1111111111111222334566 : : : : 7765544333222211111
49mV : 1111111111112223345567 : : : : 76554333222221111
45mV : 111111111111222334567: : : : : :7655443322222111
41mV : 111111111112223345677+----+----+----+----+----+7765544332222211
37mV : 11111111112223344567 : : : : : :776544333222211
33mV : 11111111112223345667 : : : : : : 7654433322221
28mV : 1111111112223344567 : : : : : : 7765443322222
24mV : 111111111222334567 : : : : : : 765543332222
20mV : 111111112223345567---+----+----+----+----+----+----+76544333222
16mV : 11111112222344567 : : : : : : :7654433222
12mV : 1111111222334567: : : : : : : :77655433322
8mV : 1111112223344567: : : : : : : : 765543322
4mV : 111111222334566 : : : : : : : : 776544332
0mV : 111111222344567-+----+----+----+----+----+----+----+----6554332
-4mV : 111111222344567 : : : : : : : : 76544332
-8mV : 111111222334567 : : : : : : : : 765443332
-12mV : 1111112223344567: : : : : : : :7655433322
-16mV : 1111111222334567: : : : : : : :7654433222
-20mV : 11111112222344567----+----+----+----+----+----+----776544333222
-24mV : 111111112223345677 : : : : : : 765543332222
-28mV : 111111111222334567 : : : : : : 7665443332222
-33mV : 1111111111222344567 : : : : : : 77654433322221
-37mV : 1111111111222334567 : : : : : :766544333222211
-41mV : 11111111111223344567-+----+----+----+----+----+7765544332222211
-45mV : 11111111111222334566 : : : : : 77655443332222111
-49mV : 1111111111112223345677 : : : : 76554433322221111
-53mV : 1111111111111222344567 : : : : 7765544333222221111
-57mV :1111111111111222334567 : : : :77655443332222211111
-62mV : 111111111111112223445677--+----+----+----+776654433332222211111
-66mV : 111111111111111223345567 : : : 7765544333222222111111
-70mV : 1111111111111112223345667 : : : 7655443333222221111111
-74mV :11111111111111112223345667 : : : 766554433322222211111111
-78mV :111111111111111112233445677 : : 776554433322222211111111
-82mV : 111111111111111112223345567----+----766554443332222221111111111
-86mV : 1111111111111111112223345567 : 765544433322222221111111111
-91mV : 11111111111111111112233445667 : 7665444333322222211111111111
-95mV : 111111111111111111122233445667 :7766554433332222222111111111111
-99mV : 111111111111111111112223344566777665544333322222221111111111111
-103mV : 111111111111111111111223334556676655443333222222211111111111111
-107mV : 111111111111111111111222333445565544333322222222111111111111111
-111mV : 111111111111111111111122233444554443333222222221111111111111111
-115mV : 111111111111111111111112223334444433332222222211111111111111111
-120mV : 111111111111111111111111222333444333322222222111111111111111111
-124mV : 111111111111111111111111222233333332222222211111111111111111111
-128mV : 111111111111111111111111122223333322222222111111111111111111111
: -|----|----|----|----|----|----|----|----|----|----|----|----|-
UI/64 :-30 -25 -20 -15 -10 -5 0 5 10 15 20 25 30
display transceiver interface
Use display transceiver interface to display the key parameters of transceiver modules.
Syntax
display transceiver interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the key parameters of every transceiver module.
Examples
# Display the key parameters of the transceiver module in interface GigabitEthernet 1/0/1.
<Sysname> display transceiver interface gigabitethernet 1/0/1
...
display transceiver manuinfo
Use display transceiver manuinfo to display electronic label information for transceiver modules.
Syntax
display transceiver manuinfo interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface [ interface-type interface-number ]: Specifies an interface by its type and number. If no interface is specified, this command displays electronic label information for all transceiver modules.
Examples
# Display electronic label information for the transceiver module in interface GigabitEthernet 1/0/1.
<Sysname> display transceiver manuinfo interface gigabitethernet 1/0/1
...
display version
Use display version to display system version information.
Syntax
display version
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display system version information.
<Sysname> display version
H3C Comware Software, Version H01, Alpha 6653P02
Copyright (c) 2004-2023 New H3C Technologies Co., Ltd. All rights reserved.
H3C S5136S-8FP4XS-EI-Q uptime is 0 weeks, 0 days, 8 hours, 0 minutes
Last reboot reason : Cold reboot
Boot image: flash:/s5136s_ei-cmw710-boot-a6653p02.bin
Boot image version: H01, Alpha 6653P02
Compiled Aug 24 2023 11:00:00
...
Table 16 Command output
Field |
Description |
Last reboot reason |
Reason for the last reboot: · User reboot—The reboot was manually initiated from a user interface, such as the CLI or SNMP. · Cold reboot—The reboot was caused by a power cycle. · Kernel abnormality reboot—The reboot was caused by kernel exceptions. · DeadLoop reboot—The reboot was caused by a kernel thread dead loop. · DEV HandShake reboot—The reboot was caused by a device management handshake failure. · SlaveSwitch reboot—The reboot was caused by a master/subordinate switchover. · IRF Merge reboot—The reboot was caused by an IRF merge. · Auto Update reboot—The reboot was caused by an automatic software upgrade. · Memory exhaust reboot—The reboot was caused by a card-memory-exhausted event. · Double Master Reboot—The reboot was caused by a double master event. |
display version-update-record
Use display version-update-record to display startup software image upgrade records.
Syntax
display version-update-record
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
The device records its current startup software version information whenever it starts up, and records all software version update information. Such information can survive reboots.
Examples
# Display the startup software image upgrade records.
<Sysname> display version-update-record
Record 1 (updated on Jan 01 2013 at 00:00:33):
*Name : s5136s_ei-cmw710-boot-a6653p02.bin
Version : H01 Alpha 6653P02
Compile time: Aug 24 2023 11:00:00
*Name : s5136s_ei-cmw710-system-a6653p02.bin
Version : H01 Alpha 6653P02
Compile time: Aug 24 2023 11:00:00
*Name : s5136s_ei-cmw710-freeradius-a6653p02.bin
Version : H01 Alpha 6653P02
Compile time: Aug 24 2023 11:00:00
Table 17 Command output
Field |
Description |
Record n |
Number of the startup software image upgrade record. Record 1 is the most recent record. |
Name |
Software image file name. |
* |
The software image version changed during the upgrade. |
Related commands
reset version-update-record
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 | v3 [ authentication | privacy ] } 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.
· v3: Uses SNMPv3. If you do not specify the authentication or privacy keyword, no authentication or encryption is performed.
¡ authentication: Performs only authentication on packets.
¡ privacy: Performs both authentication and encryption on packets.
securityname security-string: Specifies an SNMPv1 or SNMPv2c community name, or SNMPv3 username, 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.
When you configure the device to send poweroff alarms in SNMP v3 traps to the NMS, execute the snmp-agent usm-user command to create an SNMP v3 user. Make sure the authentication mode for the group to which the SNMP v3 user belongs is the same as the authentication mode configured by the dying-gasp host command. In addition, the authentication and encryption parameters must match those configured on the NMS side. If you fail to do so, the device cannot send poweroff alarms in SNMP v3 traps to the NMS.
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
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: Specifies an interface by its type and number.
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
The device does not have banners.
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 job save-job to schedule saveconfig.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] job save-job
Related commands
scheduler job
scheduler schedule
memory-threshold
Use memory-threshold to set free-memory thresholds.
Use undo memory-threshold to restore the defaults.
Syntax
memory-threshold [ slot slot-number [ cpu cpu-number ] ] [ ratio ] minor minor-value severe severe-value critical critical-value normal normal-value
undo memory-threshold [ slot slot-number [ cpu cpu-number ] ]
Default
Minor alarm threshold: 60 MB.
Severe alarm threshold: 56 MB.
Critical alarm threshold: 52 MB.
Normal state threshold: 64 MB.
Views
System view
Predefined user roles
network-admin
Parameters
ratio: Specifies free-memory thresholds in percentage. If you do not specify this keyword, the command sets free-memory thresholds in MB.
minor minor-value: Specifies the minor alarm threshold. To view the value range for this threshold, enter a question mark (?) in the place of the minor-value argument. Setting this threshold to 0 disables the minor alarm feature.
severe severe-value: Specifies the severe alarm threshold. To view the value range for this threshold, enter a question mark (?) in the place of the severe-value argument. Setting this threshold to 0 disables the severe alarm feature.
critical critical-value: Specifies the critical alarm threshold. To view the value range for this threshold, enter a question mark (?) in the place of the critical-value argument. Setting this threshold to 0 disables the critical alarm feature.
normal normal-value: Specifies the normal state threshold. To view the value range for this threshold, enter a question mark (?) in the place of the normal-value argument.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command sets free-memory thresholds for the master device.
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.
You can use the display memory command to display memory usage information.
If a memory alarm occurs, delete unused configuration items or disable some features to increase the free memory space. Because the memory space is insufficient, some configuration items might not be able to be deleted.
For more information about the thresholds, see Fundamentals Configuration Guide.
After you execute this command, if the amount of the free memory space reaches an alarm threshold, the system does not support creating a segment or entering its view. However, an existing microsegment will not be affected by this command.
The system restarts the device if one of the following conditions is met:
· After a critical alarm occurs, the remaining free-memory value has been smaller than the critical alarm threshold for 30 seconds.
· The interval between two consecutive critical alarms is shorter than 30 seconds.
· The critical alarm has occurred three times within three minutes.
· After a critical alarm occurs, the system will periodically sample free memory space and predict if the free memory space will be exhausted within 30 seconds. If the prediction result indicates that the free memory space will be exhausted within 30 seconds, the system will restart the device.
Once the free memory space reaches the minor, severe, or critical alarm threshold, the device will display the current memory usage information when you log in to the device through console or Telnet login, or execute every command.
# Set the minor alarm, severe alarm, critical alarm, and normal state thresholds to 64 MB, 48 MB, 32 MB, and 96 MB, respectively.
<Sysname> system-view
[Sysname] memory-threshold minor 64 severe 48 critical 32 normal 96
# Set the minor alarm, severe alarm, critical alarm, and normal state thresholds to 3%, 2%, 1%, and 5% of the total memory size, respectively.
<Sysname> system-view
[Sysname] memory-threshold ratio minor 3 severe 2 critical 1 normal 5
Related commands
display memory-threshold
memory-threshold usage
Use memory-threshold usage to set the memory usage threshold.
Use undo memory-threshold usage to restore the default.
Syntax
memory-threshold [ slot slot-number [ cpu cpu-number ] ] usage memory-threshold
undo memory-threshold [ slot slot-number [ cpu cpu-number ] ] usage
Default
The memory usage threshold is 100%.
Views
System view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command sets the memory usage threshold for the master device.
cpu cpu-number: Specifies a CPU by its number.
memory-threshold: Specifies the memory usage threshold in percentage. The value range is 0 to 100.
Usage guidelines
The device samples memory usage at 1-minute intervals. If the sample is greater than the memory usage threshold, the device sends a trap.
Examples
# Set the memory usage threshold to 80%.
<Sysname> system-view
[Sysname] memory-threshold usage 80
Related commands
display memory-threshold
monitor cpu-usage enable
Use monitor cpu-usage enable to enable CPU usage monitoring.
Use undo monitor cpu-usage enable to disable CPU usage monitoring.
Syntax
monitor cpu-usage enable [ slot slot-number [ cpu cpu-number ] ]
undo monitor cpu-usage enable [ slot slot-number [ cpu cpu-number ] ]
Default
CPU usage monitoring is enabled.
Views
System view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command enables CPU usage monitoring for the master device.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
After CPU usage monitoring is enabled, the system samples and saves CPU usage at the interval specified by the monitor cpu-usage interval command. You can use the display cpu-usage history command to view recent CPU usage.
Examples
# Enable CPU usage monitoring.
<Sysname> system-view
[Sysname] monitor cpu-usage enable
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 [ slot slot-number [ cpu cpu-number ] ]
undo monitor cpu-usage interval [ slot slot-number [ cpu cpu-number ] ]
Default
The system samples CPU usage every 1 minute.
Views
System view
Predefined user roles
network-admin
Parameters
interval: Specifies the sampling interval for CPU usage monitoring. Valid values include 5Sec (5 seconds), 1Min (1 minute), and 5Min (5 minutes), case insensitive.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command sets the interval for the master device.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
After CPU usage monitoring is enabled, the system samples and saves CPU usage at the specified interval. You can use the display cpu-usage history command to view recent CPU usage.
Examples
# Set the sampling interval for CPU usage monitoring to 5 seconds.
<Sysname> system-view
[Sysname] monitor cpu-usage interval 5Sec
Related commands
display cpu-usage configuration
display cpu-usage history
monitor cpu-usage enable
monitor cpu-usage logging interval
Use monitor cpu-usage logging interval to enable periodic CPU usage logging.
Use undo monitor cpu-usage logging interval to disable periodic CPU usage logging.
Syntax
monitor cpu-usage logging interval interval-time
undo monitor cpu-usage logging interval
Default
Periodic CPU usage logging is disabled.
Views
System view
Predefined user roles
network-admin
Parameters
interval interval-time: Specifies the logging interval in seconds, a multiple of five in the range of 5 to 300.
Examples
# Enable periodic CPU usage logging and set the logging interval to 60 seconds.
<Sysname> system-view
[Sysname] monitor cpu-usage logging interval 60
monitor cpu-usage threshold
Use monitor cpu-usage threshold to set CPU usage alarm thresholds.
Use undo monitor cpu-usage threshold to restore the default.
Syntax
monitor cpu-usage threshold severe-threshold { minor-threshold minor-threshold recovery-threshold recovery-threshold [ slot slot-number [ cpu cpu-number ] ] | 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 ] ] | slot slot-number cpu cpu-number [ core core-id-list ] }
Default
Severe CPU usage alarm threshold: 99%.
Minor CPU usage alarm threshold: 98%.
CPU usage recovery threshold: 50%.
Views
System view
Predefined user roles
network-admin
Parameters
severe-threshold: Specifies the severe CPU usage alarm threshold in percentage. The value range for this argument is 2 to 100.
minor-threshold minor-threshold: Specifies the minor CPU usage alarm threshold in percentage. The value range for this argument is 1 to the severe CPU usage alarm threshold minus 1.
recovery-threshold recovery-threshold: Specifies the CPU usage recovery threshold in percentage. The value range for this argument is 0 to the minor CPU usage alarm threshold minus 1.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command sets the CPU usage threshold for the master device.
cpu cpu-number: Specifies a CPU by its 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
CAUTION: If you set the severe CPU usage alarm threshold to a too low value, the device will reach the threshold easily. Normal services will be affected. |
The device samples CPU usage and CPU core usage at 1-minute intervals. If the sample is greater than the CPU usage threshold, the device sends a trap.
Examples
# Set the severe CPU usage alarm threshold to 90%, minor CPU usage alarm threshold to 80%, and CPU usage recovery threshold to 70%.
<Sysname> system-view
[Sysname] monitor cpu-usage threshold 90 minor-threshold 80 recovery-threshold 70
Related commands
display cpu-usage configuration
monitor 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 [ slot slot-number ] disk disk-name threshold threshold-value
undo monitor disk-usage [ slot slot-number ] disk disk-name threshold
Default
The disk usage threshold is 95%.
Views
System view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify an IRF member device, the command applies to the master device.
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 configure 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 five in the range of 5 to 1800.
Usage guidelines
After you set the disk usage sampling interval, the device samples disk usages 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 memory-usage logging interval
Use monitor memory-usage logging interval to enable periodic memory usage logging.
Use undo monitor memory-usage logging interval to disable periodic memory usage logging.
Syntax
monitor memory-usage logging interval interval-time
undo monitor memory-usage logging interval
Default
Periodic memory usage logging is disabled.
Views
System view
Predefined user roles
network-admin
Parameters
interval interval-time: Specifies the logging interval in seconds, a multiple of five in the range of 5 to 300.
Examples
# Enable periodic memory usage logging and set the logging interval to 60 seconds.
<Sysname> system-view
[Sysname] monitor memory-usage logging interval 60
monitor resend cpu-usage
Use monitor resend cpu-usage to set CPU usage alarm resending intervals.
Use undo monitor resend cpu-usage to restore the default.
Syntax
monitor resend cpu-usage { minor-interval minor-interval | severe-interval severe-interval } * [ slot slot-number [ cpu cpu-number ] ]
undo monitor resend cpu-usage [ minor-interval | severe-interval ] [ slot slot-number [ cpu cpu-number ] ]
Default
The minor alarm resending interval is 300 seconds. The severe alarm resending interval is 60 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
minor-interval minor-interval: Specifies the minor alarm resending interval in seconds, a multiple of five in the range of 10 to 3600.
severe-interval severe-interval: Specifies the severe alarm resending interval in seconds, a multiple of five in the range of 10 to 3600.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command sets alarm resending intervals for the master device.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
The device samples CPU usage periodically and compares the sample with the CPU usage threshold. If the sample increases above an alarm threshold, the CPU usage enters an alarm state and the device sends an alarm.
While the CPU usage is in minor alarm state, the device sends minor alarms periodically until the CPU usage increases above the severe threshold or the minor alarm is removed.
While the CPU usage is in severe alarm state, the device sends severe alarms periodically until the severe alarm is removed.
You can use this command to change CPU usage alarm resending intervals.
If you do not specify the minor-interval or severe-interval keyword, the undo monitor resend cpu-usage command restores default settings for both the minor and severe alarm resending intervals.
Examples
# Set the CPU usage minor alarm resending interval to 60 seconds for CPU 0 in slot 1.
<Sysname> system-view
[Sysname] monitor resend cpu-usage minor-interval 60 slot 1 cpu 0
monitor resend memory-threshold
Use monitor resend memory-threshold to set memory depletion alarm resending intervals.
Use undo monitor resend memory-threshold to restore the default.
Syntax
monitor resend memory-threshold { critical-interval critical-interval | early-warning-interval early-warning-interval | minor-interval minor-interval | severe-interval severe-interval } * [ slot slot-number [ cpu cpu-number ] ]
undo monitor resend memory-threshold [ critical-interval | early-warning-interval | minor-interval | severe-interval ] * [ slot slot-number [ cpu cpu-number ] ]
Default
· Early warning resending interval: 1 hour.
· Minor alarm resending interval: 12 hours.
· Severe alarm resending interval: 3 hours.
· Critical alarm resending interval: 1 hour.
Views
System view
Predefined user roles
network-admin
Parameters
critical-interval critical-interval: Specifies the critical alarm resending interval in hours, in the range of 1 to 48.
early-warning-interval early-warning-interval: Specifies the early warning resending interval in hours, in the range of 1 to 48.
minor-interval minor-interval: Specifies the minor alarm resending interval in hours, in the range of 1 to 48.
severe-interval severe-interval: Specifies the severe alarm resending interval in hours, in the range of 1 to 48.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command sets alarm resending intervals for the master device.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
The device samples the amount of free memory space periodically and compares the sample with free-memory thresholds. If the sample decreases to or below a threshold, the device enters a memory depletion alarm state and sends an alarm.
In critical alarm state, the device sends critical alarm notifications periodically until the critical alarm is removed.
In a lower alarm state, the device sends notifications for the alarm state periodically until it enters a higher alarm state or the current alarm is removed.
You can use this command to change the alarm resending intervals.
If you do not specify any memory depletion alarm resending intervals, the undo monitor resend memory-threshold command restores default settings for all memory depletion alarm resending intervals.
Examples
# Set the minor memory depletion alarm resending interval to 12 hours for CPU 0 in slot 1.
<Sysname> system-view
[Sysname] monitor resend memory-threshold minor-interval 12 slot 1 cpu 0
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.
To access the device configuration without authentication, you must connect to the master device and access the BootWare menu while the master device is starting up.
Availability of BootWare menu options depends on the password recovery capability setting. For more information, see the release notes.
Examples
# Disable password recovery capability.
<Sysname> system-view
[Sysname] undo password-recovery enable
power sleep
Use power sleep to place a power module into sleeping state.
Use undo power sleep to wake up a sleeping power module.
Syntax
power sleep slot slot-number power-id
undo power sleep slot slot-number power-id
Default
Power modules are in operating state.
Views
System view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies an IRF member device by its member ID.
power-id: Specifies a power module by its ID.
Usage guidelines
Use this command with caution. This command does not identify whether or not the remaining power is greater than the rated power of the power module. Executing this command might cause power insufficiency on cards.
Before placing a power module into sleeping state, make sure the remaining power is greater than the rated power of the power module. To view the remaining power, execute the display power verbose command.
A sleeping power module cannot wake up automatically. To wake up a sleeping power module, use the undo power sleep command.
Examples
# Place power module 1 on member device 1 into sleeping state.
<Sysname> system-view
[Sysname] power sleep slot 1 1
Power module will enter sleep module, Confirm ?[Y/N]:y
push-button mode enable
Use push-button mode enable to enable MODE button press configuration.
Use undo push-button mode enable to restore the default.
Syntax
push-button mode enable
undo push-button mode enable
Default
MODE button press configuration is disabled.
Views
System view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
The MODE button on the front panel works in conjunction with the port LEDs to indicate the operating state of the ports from various angles and obtain more device information. Pressing the MODE button has different effects depending on the duration of the press as follows:
· 0 to 5 seconds: Change the type of port information that the port LEDs are showing.
· More than 5 seconds: Invalid operation.
After you execute the push-button mode enable command, pressing the MODE button has different effects depending on the duration of the press as follows:
· Less than 5 seconds: Same as the effect before the command is executed, used for changing the type of port information that the port LEDs are showing.
· 5 to 10 seconds: Deploys the device to Cloudnet. In this case, the device attempts to set up a connection with Cloudnet. If the Cloudnet management status LED flashes at 1Hz in blue, the connection is being set up. After the connection is set up, you can add the device to Cloudnet. When the device is managed by Cloudnet successfully, the Cloudnet management status LED changes to steady blue. After the device is managed by Cloudnet, pressing the MODE button for 5 to 10 seconds will disconnect the device from Cloudnet, which changes turns off the Cloudnet management status LED.
· More than 10 seconds: No operation will be performed. To indicate that you have pressed MODE button for 10 seconds, the Cloudnet management status LED flashes once at 3Hz in blue.
When the device connects to Cloudnet, the following settings are deployed:
· The minimum password length is 4 characters.
· The global password composition policy requires that a password must contain at least one character type and one character for each type.
· Disable username checking.
· Enable HTTP-based NETCONF over SOAP.
· Enable the HTTP service.
· Create local user clouduser and configure the following settings:
¡ Authorize the user to use the HTTP service.
¡ Assign the network-admin user role to the user.
¡ Set the password to admin in plaintext.
· Configure the IPv4 address for the DNS server as 114.114.114.114.
· Specify the domain name of the Cloudnet server as cloudnet.h3c.com.
· Save the configuration forcedly.
After the device disconnects from Cloudnet, the following settings are deployed:
· Restore the domain name of the Cloudnet server to the default.
· Save the configuration forcedly.
Examples
# Enable MODE button press configuration.
<Sysname> system-view
[Sysname] push-button mode 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 an IRF member device by its member ID. If you do not specify an IRF member device, the command reboots all IRF member devices.
force: Reboots the device immediately without performing software or hard disk check. If this keyword is not specified, the system first identifies whether the reboot might result in data loss or a system failure. For example, the system identifies whether the main system software image file exists and whether a write operation is in progress on a storage medium. If the reboot might cause problems, the system does not reboot the device.
Usage guidelines
CAUTION: · A reboot might interrupt network services. · Use the force keyword only when the device fails or a reboot command without the force keyword cannot perform a reboot correctly. A reboot command with the force keyword might result in file system corruption because it does not perform data protection. |
If the main startup software images are corrupt or missing, you must re-specify a set of main startup software images before executing the reboot command.
For data security, the device does not reboot if you reboot the device while the device is performing file operations.
If the IRF fabric has only one member device, rebooting the member device reboots the entire IRF fabric. If the IRF fabric has a subordinate member and the member is operating correctly, rebooting the master triggers a master/subordinate switchover.
To ensure correct operation of the IRF fabric and member devices, do not trigger a switchover by rebooting the master if no subordinate member devices are in Stable state. To view the status of subordinate member devices, execute the display system stable state command.
Examples
# Reboot the device. Save the running configuration at prompt.
<Sysname> reboot
Start to check configuration with next startup configuration file, please wait.........DONE!
Current configuration will be lost after the reboot, save current configuration? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Configuration is saved to mainboard device successfully.
This command will reboot the device. Continue? [Y/N]:y
Now rebooting, please wait...
# Reboot the device immediately without performing software check.
<Sysname> reboot force
A forced reboot might cause the storage medium to be corrupted. Continue? [Y/N]:y
Now rebooting, please wait...
display system stable state
reset scheduler logfile
Use reset scheduler logfile to clear job execution log information.
Syntax
reset scheduler logfile
Views
User view
Predefined user roles
network-admin
Examples
# Clear job execution log information.
<Sysname> reset scheduler logfile
Related commands
display scheduler logfile
reset version-update-record
Use reset version-update-record to clear startup software image upgrade records.
Syntax
reset version-update-record
Views
System view
Predefined user roles
network-admin
Examples
# Clear the startup software image upgrade records.
<Sysname> system-view
[Sysname] reset version-update-record
This command will delete all records of version update. Continue? [Y/N]:y
Related commands
display version-update-record
resource-monitor minor resend enable
Use resource-monitor minor resend enable to enable resending of minor resource depletion alarms.
Use undo resource-monitor minor resend enable to disable resending of minor resource depletion alarms.
Syntax
resource-monitor minor resend enable
undo resource-monitor minor resend enable
Default
Resending of minor resource depletion alarms is enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
When a resource type enters minor alarm state, the device issues a minor alarm. If the resource type stays in minor alarm state or changes from severe alarm state to minor alarm state, the device identifies whether resending of minor resource depletion alarms is enabled. If the feature is disabled, the device does not issue additional minor alarms. If the feature is enabled, the device resends minor alarms periodically.
The resending period is fixed at 24 hours for a severe alarm and is fixed at 7 * 24 hours for a minor alarm.
Examples
# Enable resending of minor resource depletion alarms.
<Sysname> system-view
[Sysname] resource-monitor minor resend enable
Related commands
display resource-monitor
resource-monitor output
resource-monitor resource
resource-monitor output
Use resource-monitor output to specify destinations for resource depletion alarms.
Use undo resource-monitor output to remove destinations for resource depletion alarms.
Syntax
resource-monitor output { netconf-event | snmp-notification | syslog } *
undo resource-monitor output [ netconf-event | snmp-notification | syslog ] *
Default
Resource depletion alarms are sent to NETCONF, SNMP, and the information center.
Views
System view
Predefined user roles
network-admin
Parameters
netconf-event: Sends resource depletion alarms to the NETCONF feature to encapsulate the alarms in NETCONF events. For more information, see NETCONF in Network Management and Monitoring Configuration Guide.
snmp-notification: Sends resource depletion alarms to the SNMP feature to encapsulate the alarms in SNMP traps and informs. For more information, see SNMP in Network Management and Monitoring Configuration Guide.
syslog: Sends resource depletion alarms to the information center to encapsulate the alarms in log messages. For more information, see information center in Network Management and Monitoring Configuration Guide.
Usage guidelines
If you do not specify any keywords for the undo resource-monitor output command, the command disables resource depletion alarm output.
Examples
# Specify the information center module as the output destination for resource depletion alarms.
<Sysname> system-view
[Sysname] resource-monitor output syslog
Related commands
resource-monitor minor resend enable
resource-monitor resource
restore factory-default
Use restore factory-default to restore the factory-default configuration for the device.
Syntax
restore factory-default
Views
User view
Predefined user roles
network-admin
Usage guidelines
CAUTION: This command restores the device to the factory default settings. Before executing this command, make sure you understand its impact on the live network. |
This command is disruptive. Use this command only when you cannot troubleshoot the device by using other methods, or you want to use the device in a different scenario.
Examples
# Restore the factory-default configuration for the device.
<Sysname> restore factory-default
This command will restore the system to the factory default configuration and clear the operation data. Continue [Y/N]:y
Restoring the factory default configuration. This process might take a few minutes. Please wait..........................................................................................................Done.
Please reboot the system to place the factory default configuration into effect.
Related commands
reboot
scheduler job
Use scheduler job to create a job and enter its view, or enter the view of an existing job.
Use undo scheduler job to delete a job.
Syntax
scheduler job job-name
undo scheduler job job-name
Default
No job exists.
Views
System view
Predefined user roles
network-admin
Parameters
job-name: Specifies the job name, a case-sensitive string of 1 to 47 characters.
Usage guidelines
A job can be referenced by multiple schedules. In job view, you can assign commands to the job.
Examples
# Create a job named backupconfig and enter job view.
<Sysname> system-view
[Sysname] scheduler job backupconfig
[Sysname-job-backupconfig]
Related commands
command
scheduler schedule
scheduler logfile size
Use scheduler logfile size to set the size of the job execution log file.
Syntax
scheduler logfile size value
Default
The size of the job execution log file is 16 KB.
Views
System view
Predefined user roles
network-admin
Parameters
value: Specifies the size of the job execution log file, in KB. The value range is 16 to 1024.
Usage guidelines
The job execution log file saves the execution information of jobs. If the file is full, old records are deleted to make room for new records. If the size of the log information to be written to the file is greater than the file size, the excessive information is not written to the file.
Examples
# Set the size of the job execution log file to 32 KB.
<Sysname> system-view
[Sysname] scheduler logfile size 32
Related commands
display scheduler logfile
scheduler reboot at
Use scheduler reboot at to specify the reboot date and time.
Use undo scheduler reboot to delete the reboot schedule configuration.
Syntax
scheduler reboot at time [ date ]
undo scheduler reboot
Default
No reboot date or time is specified.
Views
User view
Predefined user roles
network-admin
Parameters
time: Specifies the reboot time in the hh:mm format. The value range for hh is 0 to 23. The value range for mm is 0 to 59.
date: Specifies the reboot date in the MM/DD/YYYY or YYYY/MM/DD format. The value range for YYYY is 2000 to 2035. The value range for MM is 1 to 12. The value range for DD varies by month.
Usage guidelines
CAUTION: This command enables the device to reboot at a scheduled time, which causes service interruption. Before using this command, make sure you fully understand its impact on your live network. |
When the date argument is not specified, the system uses the following rules to determine the reboot time:
· If the reboot time is later than the current time, a reboot occurs at the reboot time of the current day.
· If the reboot time is earlier than the current time, a reboot occurs at the reboot time the next day.
The device supports only one device reboot schedule. If you execute both the scheduler reboot delay and scheduler reboot at commands or execute one of the commands multiple times, the most recent configuration takes effect.
For data security, the system does not reboot at the reboot time if a file operation is being performed.
Examples
# Configure the device to reboot at 12:00 p.m. This example assumes that the current time is 11:43 a.m. on June 6, 2015.
<Sysname> scheduler reboot at 12:00
Reboot system at 12:00:00 06/06/2015 (in 0 hours and 16 minutes). Confirm? [Y/N]:
Related commands
scheduler reboot delay
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, 2015.
<Sysname> scheduler reboot delay 88
Reboot system at 13:16 06/06/2015(in 1 hours and 28 minutes). Confirm? [Y/N]:
scheduler schedule
Use scheduler schedule to create a schedule and enter its view, or enter the view of an existing schedule.
Use undo scheduler schedule to delete a schedule.
Syntax
scheduler schedule schedule-name
undo scheduler schedule schedule-name
Default
No schedule exists.
Views
System view
Predefined user roles
network-admin
Parameters
schedule-name: Specifies the schedule name, a case-sensitive string of 1 to 47 characters.
Usage guidelines
You can configure a schedule to have the device automatically run a command or a set of commands without administrative interference.
To configure a schedule:
1. Use the scheduler job command to create a job and enter job view.
2. Use the command command to assign commands to the job.
3. Use the scheduler schedule command to create a schedule and enter schedule view.
4. Use the job command to assign the job to the schedule. You can assign multiple jobs to a schedule. The jobs must already exist.
5. Use the user-role command to assign user roles to the schedule. You can assign up to 64 user roles to a schedule.
6. Use the time at, time once, or time repeating command to specify an execution time for the schedule. You can specify only one execution time for a schedule.
Examples
# Create a schedule named saveconfig.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
Related commands
job
time at
time once
shutdown-interval
Use shutdown-interval to set the port status detection timer.
Use undo shutdown-interval to restore the default.
Syntax
shutdown-interval interval
undo shutdown-interval
Default
The port status detection timer setting is 30 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
interval: Specifies the port status detection timer value in seconds. The value range is 0 to 300. 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
On a network enabled with loopback detection or STP, the device starts a port status detection timer when a port is shut down by a protocol. 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
sysid
Use sysid to set the system ID.
Use undo sysid to restore the default.
Syntax
sysid system-id
undo sysid
Default
The device does not have a system ID.
Views
System view
Predefined user roles
network-admin
Parameters
system-id: Specifies the system ID for the device. You can use this argument to indicate the position or functionality of the device or any other information.
Examples
# Set the system ID of the device to position-hall.
<Sysname> system-view
[Sysname] sysid positon-hall
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
temperature-limit
Use temperature-limit to set the temperature alarm thresholds.
Use undo temperature-limit to restore the default.
Syntax
temperature-limit slot slot-number hotspot sensor-number lowlimit warninglimit [ alarmlimit ]
undo temperature-limit slot slot-number hotspot sensor-number
Default
The defaults vary by temperature sensor model. To view the defaults, execute the undo temperature-limit and display environment commands in turn.
Views
System view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies an IRF member device by its member ID.
hotspot: Configures temperature alarm thresholds for hotspot sensors. A hotspot sensor is typically located near a high-heat chip to monitor the chip temperature.
sensor-number: Specifies a sensor by its number. To view the value range, enter a question mark (?) in the place of this argument.
lowlimit: Specifies the low-temperature threshold in Celsius degrees. The value range varies by temperature sensor. To view the value range, enter a question mark (?) in the place of this argument.
warninglimit: Specifies the high-temperature warning threshold in Celsius degrees. This threshold must be greater than the low-temperature threshold. To view the value range, enter a question mark (?) in the place of this argument.
alarmlimit: Specifies the high-temperature alarming threshold in Celsius degrees. This threshold must be greater than the warning threshold. To view the value range, enter a question mark (?) in the place of this argument.
Usage guidelines
When the device temperature drops below the low-temperature threshold or reaches the high-temperature warning or alarming threshold, the device performs the following operations:
· Sends log messages and traps.
· Sets LEDs on the device panel.
Examples
# Set temperature alarm thresholds for hotspot sensor 1 in a slot.
<Sysname> system-view
[Sysname] temperature-limit slot 1 hotspot 1 -10 50 60
Related commands
display environment
time at
Use time at to specify an execution date and time for a non-periodic schedule.
Use undo time to delete the execution date and time configuration for a non-periodic schedule.
Syntax
time at time date
undo time
Default
No execution time or date is specified for a non-periodic schedule.
Views
Schedule view
Predefined user roles
network-admin
Parameters
time: Specifies the schedule execution time in the hh:mm format. The value range for hh is 0 to 23. The value range for mm is 0 to 59.
date: Specifies the schedule execution date in the MM/DD/YYYY or YYYY/MM/DD format. The value range for YYYY is 2000 to 2035. The value range for MM is 1 to 12. The value range for DD varies by month.
Usage guidelines
The specified time (date plus time) must be later than the current system time.
The time at command, the time once command, and the time repeating command overwrite one another. The most recently executed command takes effect.
Examples
# Configure the device to execute schedule saveconfig at 01:01 a.m. on May 11, 2015.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] time at 1:1 2015/05/11
Related commands
scheduler schedule
time once
Use time once to specify one or more execution days and the execution time for a non-periodic schedule.
Use undo time to delete the execution day and time configuration for a non-periodic schedule.
Syntax
time once at time [ month-date month-day | week-day week-day&<1-7> ]
time once delay time
undo time
Default
No execution time or day is specified for a non-periodic schedule.
Views
Schedule view
Predefined user roles
network-admin
Parameters
at time: Specifies the execution time in the hh:mm format. The value range for hh is 0 to 23. The value range for mm is 0 to 59.
month-date month-day: Specifies a day in the current month, in the range of 1 to 31. If you specify a day that does not exist in the current month, the configuration takes effect on that day in the next month.
week-day week-day&<1-7>: Specifies a space-separated list of up to seven week days for the schedule. Valid week day values include Mon, Tue, Wed, Thu, Fri, Sat, and Sun.
delay time: Specifies the delay time for executing the schedule, in the hh:mm or mm format. This argument can have up to six characters. When in the hh:mm format, mm must be in the range of 0 to 59.
Usage guidelines
If the specified time has already occurred, the schedule will be executed at the specified time the following day.
If the day in the month has already occurred, the schedule will be executed at the specified day in the following month.
If the specified day in a week has already occurred, the schedule will be executed at the specified day in the following week.
The time at command, the time once command, and the time repeating command overwrite one another. The most recently executed command takes effect.
Examples
# Configure the device to execute schedule saveconfig once at 15:00.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] time once at 15:00
Schedule starts at 15:00 5/11/2011.
# Configure the device to execute schedule saveconfig once at 15:00 on the coming 15th day in a month.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] time once at 15:00 month-date 15
# Configure the device to execute schedule saveconfig at 12:00 p.m. on the coming Monday and Friday.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] time once at 12:00 week-day mon fri
# Configure the device to execute schedule saveconfig after 10 minutes.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] time once delay 10
Related commands
scheduler schedule
time repeating
Use time repeating to specify an execution time table for a periodic schedule.
Use undo time to delete the execution time table configuration for a periodic schedule.
Syntax
time repeating [ at time [ date ] ] interval interval
time repeating at time [ month-date [ month-day | last ] | week-day week-day&<1-7> ]
undo time
Default
No execution time table is specified for a periodic schedule.
Views
Schedule view
Predefined user roles
network-admin
Parameters
at time: Specifies the execution time in the hh:mm format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. If you do not specify this option, the current system time is used as the execution time.
date: Specifies the start date for the periodic schedule, in the MM/DD/YYYY or YYYY/MM/DD format. The value range for YYYY is 2000 to 2035. The value range for MM is 1 to 12. The value range for DD varies by month. If you do not specify this argument, the execution start date is the first day when the specified time arrives.
interval interval: Specifies the execution time interval in the hh:mm or mm format. This argument can have up to six characters. When in the hh:mm format, mm must be in the range of 0 to 59. When in the mm format, this argument must be equal to or greater than 1 minute.
month-date [ month-day | last ]: Specifies a day in a month, in the range 1 to 31. The last keyword indicates the last day of a month. If you specify a day that does not exist in a month, the configuration takes effect on that day in the next month.
week-day week-day&<1-7>: Specifies a space-separated list of up to seven week days for the schedule. Valid week day values include Mon, Tue, Wed, Thu, Fri, Sat, and Sun.
Usage guidelines
The time repeating [ at time [ date ] ] interval interval command configures the device to execute a schedule at intervals from the specified time on.
The time repeating at time [ month-date [ month-day | last ] | week-day week-day&<1-7> ] command configures the device to execute a schedule at the specified time on every specified day in a month or week.
The time at command, the time once command, and the time repeating command overwrite one another, whichever is executed most recently takes effect.
Examples
# Configure the device to execute schedule saveconfig once an hour from 8:00 a.m. on.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] time repeating at 8:00 interval 60
# Configure the device to execute schedule saveconfig at 12:00 p.m. every day.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] time repeating at 12:00
# Configure the device to execute schedule saveconfig at 8:00 a.m. on the 5th of every month.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] time repeating at 8:00 month-date 5
# Configure the device to execute schedule saveconfig at 8:00 a.m. on the last day of every month.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] time repeating at 8:00 month-date last
# Configure the device to execute schedule saveconfig at 8:00 a.m. every Friday and Saturday.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] time repeating at 8:00 week-day fri sat
Related commands
scheduler schedule
transceiver monitor enable
Use transceiver monitor enable to enable transceiver monitoring.
Use undo transceiver monitor enable to restore the default.
Syntax
transceiver monitor enable
undo transceiver monitor enable
Default
Transceiver monitoring is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
After transceiver monitoring is enabled, the device samples the parameters of transceiver modules periodically, including the input power and output power of transceiver modules. If a sampled value reaches the alarm threshold, the device generates a log to notify users.
Examples
# Enable transceiver monitoring.
<Sysname> system-view
[Sysname] transceiver monitor enable
Related commands
transceiver monitor interval
transceiver monitor interval
Use transceiver monitor interval to set a transceiver monitoring interval.
Use undo transceiver monitor interval to restore the default.
Syntax
transceiver monitor interval interval
undo transceiver monitor interval
Default
The transceiver monitoring interval is 600 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
interval: Specifies the transceiver monitoring interval in seconds. The value range is 300 to 3600.
Usage guidelines
After transceiver monitoring is enabled, the device samples the parameters of transceiver modules periodically, including the input power and output power of transceiver modules. If a sampled value reaches the alarm threshold, the device generates a log entry to notify users.
This command takes effect only when the transceiver monitor enable command is used.
Examples
# Set the transceiver monitoring interval to 500 seconds.
<Sysname> system-view
[Sysname] transceiver monitor interval 500
Related commands
transceiver monitor enable
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.
Examples
# Assign user role rolename to schedule test.
<Sysname> system-view
[Sysname] scheduler schedule test
[Sysname-schedule-test] user-role rolename
Related commands
command
scheduler schedule