Non-default vSystems do not support some of the device management commands. For information about vSystem support for a command, see the usage guidelines on that command. For information about vSystem, see Virtual Technologies Configuration Guide.

archer high-priority to-cpu enable

Use archer high-priority to-cpu enable to enable the FPGA chips to send high-priority packets to the CPU.

Use undo archer high-priority to-cpu enable to disable the FPGA chips from sending high-priority packets to the CPU.

Syntax

In standalone mode:

archer high-priority to-cpu enable chip chip-number slot slot-number subslot-number cpu cpu-number

undo archer high-priority to-cpu enable chip chip-number slot slot-number subslot-number cpu cpu-number

In IRF mode:

archer high-priority to-cpu enable chip chip-number chassis chassis-number slot slot-number subslot-number cpu cpu-number

undo archer high-priority to-cpu enable chip chip-number chassis chassis-number slot slot-number subslot-number cpu cpu-number

Default

The FPGA chips send high-priority packets to the CPU.

Views

User view

Predefined user roles

network-admin

context-admin

Parameters

chip chip-number: Specifies a chip by its number, in the range of 0 to 1.

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

subslot-number: Specifies a subcard by its subslot number.

cpu cpu-number: Specifies a CPU by its number. This option is supported only if multiple CPUs are available on the specified slot.

Usage guidelines

This command is supported on only NSQM1FWEFGA0 modules.

The sending of high-priority packets from the FPGA chips to the CPU on the service module might cause packet loss on the FPGA chips. You need to disable the FPGA chips from sending high-priority packets to the CPU as needed.

Examples

# Enable the FPGA chips to send high-priority packets to the CPU.

<Sysname> archer high-priority to-cpu enable chip 0 slot 4 0 cpu 1

This might cause FPGA drop low priority packet. In addition, sure make enable fpga high priority ability. Continue? [Y/N]:y

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

This command is supported only on the default context.

Non-default vSystems do not support this command.

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 Coordinated Universal Time (UTC) 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:

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

This command is supported only on the default context.

Non-default vSystems do not support this command.

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.

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 method for obtaining the system time.

Use undo clock protocol to restore the default.

Syntax

clock protocol { none | ntp context context-id }

undo clock protocol

Default

The device uses NTP to obtain the UTC time on the default MDC.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

context context-id: Specifies a context. For more information about context and the value range for the context ID, see Virtual Technologies Command Reference.

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

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

· If you execute the clock protocol none command, you can use the clock datetime command to configure the 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 GNSS, NTP, or PTP periodically. After obtaining the UTC time, the device uses the UTC time, time zone, and daylight saving time to calculate the system time. If the GNSS, NTP, or PTP signals are lost, the device uses the clock signals generated by its built-in crystal oscillator to maintain the system time. After the GNSS, NTP, or PTP signals recover, the device obtains the UTC time again from the signals.

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

All contexts on the device use the same system time. After obtaining the system time from a context, the device automatically synchronizes the system time to the other contexts.

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

This command is supported only on the default context.

Non-default vSystems do not support this command.

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 time zone is GMT+08:00.

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

This command is supported only on the default context.

Non-default vSystems do not support this command.

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

context-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

Non-default vSystems do not support this command.

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

undo copyright-info enable

Default

Views

System view

Predefined user roles

network-admin

context-admin

Usage guidelines

Non-default vSystems do not support this command.

Examples

# Enable copyright statement display.

<Sysname> system-view

[Sysname] copyright-info enable

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

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

* Without the owner's prior written consent, *

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

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

display alarm

Use display alarm to display alarm information.

Syntax

In standalone mode:

display alarm [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

display alarm [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays alarm information for all cards. (In standalone mode.)

cpu cpu-number: Specifies a CPU by its number. This option is supported only if multiple CPUs are available on the specified slot.

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

Examples

# Display alarm information.

<Sysname> display alarm

Slot CPU Level Info

- - ERROR power 1 is faulty.

- - INFO power 2 is absent.

- - INFO power 3 is absent.

Table 1 Command output

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

‌

display bootrom-access

Use display bootrom-access to display the BootWare menu access authorization status.

Syntax

display bootrom-access

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

Examples

# Display the BootWare menu access authorization status.

<Sysname> display bootrom-access

Bootrom access: Enabled.

Related commands

bootrom-access enable

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

context-admin

context-operator

Usage guidelines

Non-default vSystems do not support this command.

Examples

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

<Sysname> display clock

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

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

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

<Sysname> display clock

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

Time Zone : Z5 add 05:00:00

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

<Sysname> display clock

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

Time Zone : Z5 add 05:00:00

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

Related commands

clock datetime

clock timezone

clock summer-time

display copyright

Use display copyright to display the copyright statement.

Syntax

display copyright

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Usage guidelines

Non-default vSystems do not support this command.

Examples

# Display the copyright statement.

<Sysname> display copyright

...

display cpu-usage

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

Syntax

In standalone mode:

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

display cpu-usage [ control-plane | data-plane ] [ summary ] [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

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

display cpu-usage [ control-plane | data-plane ] [ summary ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

control-plane: Displays CPU usage statistics for the control plane. If you do not specify this keyword or the data-plane keyword, the command displays the total CPU usage statistics.

data-plane: Displays CPU usage statistics for the data plane. If you do not specify this keyword or the control-plane keyword, the command displays the total CPU usage statistics.

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 a card by its slot number. If you do not specify a card, this command displays the CPU usage statistics for all cards. (In standalone mode.)

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

core { core-number | all }: Displays CPU core usage statistics. If you specify a CPU core by its number, this command displays usage statistics for the CPU core. If you specify the all keyword, this command displays average usage statistics for all CPU cores.

Usage guidelines

Executing this command on a context displays the current CPU usage statistics for the context.

Non-default vSystems do not support this command.

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

# (In standalone mode.) 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

# (In standalone mode.) Display the current CPU usage statistics in table form.

<Sysname> display cpu-usage

Slot CPU Last 5 sec Last 1 min Last 5 min

1 0 17% 29% 28%

Table 2 Command output

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

‌

display cpu-usage configuration

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

context-admin

vsys-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the CPU usage monitoring settings for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays the CPU usage monitoring settings for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. If you do not specify a CPU, this command displays the CPU usage monitoring settings for all CPUs on the specified slot.

Usage guidelines

Executing this command on a context displays CPU usage monitoring settings for the context.

Examples

# Display the CPU usage monitoring settings.

<Sysname> display cpu-usage configuration slot 4

Slot 0 CPU 0 CPU configuration:

CPU usage monitor is enabled.

Current monitor interval is 60 seconds.

Current monitor threshold is 70%.

Current monitor threshold is 100% for the following cores: 0 to 15.

Current monitor recovery threshold is 30%.

Current monitor recovery threshold is 80% for the following cores: 0 to 15.

Current statistics-interval is 60 seconds for the following cores: 0 to 15.

Slot 3 CPU 0 CPU configuration:

CPU usage monitor is enabled.

Current monitor interval is 60 seconds.

Current monitor threshold is 70%.

Current monitor threshold is 100% for the following cores: 0 to 7.

Current monitor recovery threshold is 30%.

Current monitor recovery threshold is 80% for the following cores: 0 to 7.

Current statistics-interval is 60 seconds for the following cores: 0 to 7.

Slot 3 CPU 1 CPU configuration:

CPU usage monitor is enabled.

Current monitor interval is 60 seconds.

Current monitor threshold is 85%.

Current monitor threshold is 95% for the following cores: 0 to 47.

Current monitor recovery threshold is 30%.

Current monitor recovery threshold is 76% for the following cores: 0 to 47.

Current statistics interval is 90 seconds for the following cores: 0 to 47.

Table 3 Command output

Field	Description
Slot n CPU m CPU configuration	Usage monitoring settings for a CPU.
CPU usage monitor is xxx.	Whether CPU usage tracking is enabled.
Current monitor interval is xxx.	Sampling interval for CPU usage tracking.
Current monitor threshold is xxx.	CPU usage threshold.
Current monitor recovery threshold is xxx.	CPU usage recovery threshold.
Current statistics-interval is xxx seconds for the following cores	CPU core usage statistics interval.

‌

Related commands

monitor cpu-usage enable

monitor cpu-usage interval

monitor cpu-usage threshold

display cpu-usage history

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-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 a card by its slot number. If you specify a process but do not specify a card, this command displays the statistics for the process on the active MPU. If you do not specify any options, this command displays the statistics for all processes on all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you specify a process but do not specify a card, this command displays the statistics for the process on the global active MPU. If you do not specify any options, this command displays the statistics for all processes on all cards. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. If you specify a process but do not specify a CPU, this command displays the statistics for the default CPU. If you do not specify a process or CPU, this command displays the historical statistics for all CPUs.

Usage guidelines

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

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

The horizontal axis represents the time.

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

Executing this command on a context displays the historical CPU usage statistics for the context.

Non-default vSystems do not support this command.

Examples

# (In standalone mode.) Display the historical CPU usage statistics.

<Sysname> display cpu-usage history

100%|

95%|

90%|

85%|

80%|

75%|

70%|

65%|

60%|

55%|

50%|

45%|

40%|

35%|

30%|

25%|

20%|

15%| #

10%| ### #

5%| ########

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

10 20 30 40 50 60 (minutes)

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

The output shows the following items:

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

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

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

¡ 12 minutes ago—Approximately 5%.

¡ 13 minutes ago—Approximately 10%.

¡ 14 minutes ago—Approximately 15%.

¡ 15 minutes ago—Approximately 10%.

¡ 16 and 17 minutes ago—Approximately 5%.

¡ 18 minutes ago—Approximately 10%.

¡ 19 minutes ago—Approximately 5%.

¡ Other time—2% or lower.

Related commands

monitor cpu-usage enable

monitor cpu-usage interval

display crc-error configuration

Use display crc-error { higig-port | xe-port } configuration to display CRC error configuration about inner ports.

Syntax

display crc-error { higig-port | xe-port } configuration

Views

User view

Predefined user roles

network-admin

network-operator

Parameters

higig-port: Specifies the HG port.

xe-port: Specifies the XE port. This keyword is available for Blade V security modules.

Usage guidelines

This command takes effect only on security modules that support FPGA.

Examples

# Display HG port configuration on the service module.

<Sysname> display crc-error higig-port configuration

HG Port Configuration:

Monitor times : 300

Monitor threshold : 50

Monitor action : reboot

# Display XE port configuration on the service module.

<Sysname> display crc-error xe-port configuration

XE Port Configuration:

Monitor times : 300

Monitor threshold : 50

Monitor action : reboot

Table 4 Command output

Field	Description
Monitor times	Maximum number of times that the number of CRC errors exceeds the threshold per second consecutively.
Monitor threshold	Threshold for the number of CRC errors per second.
Monitor action	Action to be taken by the service module when the number of CRC errors exceeds the threshold per second consecutively.

‌

Related commands

monitor archer action

monitor archer threshold

monitor archer times

display device

Use display device to display device information.

Syntax

In standalone mode:

display device[ slot slot-number [ cpu cpu-number ] [ subslot subslot-number ] | verbose ]

In IRF mode:

display device [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] [ subslot subslot-number ] ] | verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

chassis chassis-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. (In IRF mode.)

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.

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

verbose: Displays detailed information. If you do not specify this keyword, this command displays brief information.

cpu cpu-number: Specifies a CPU by its number. This option is supported only if multiple CPUs are available on the specified slot.

Examples

# Display device information.

<Sysname> display device

Slot No. Brd Type Brd Status Subslot Sft Ver Patch Ver

0 NSQM1SUPB0 Master 0 M9006-9141P04 None

1 NONE Absent 0 NONE None

2 NSQ1GT48EA0 Normal 0 M9006-9141P04 None

3 NONE Fault 0 NONE None

4 NSQM1FWDFGD1 Normal 0 M9006-9141P04 None

CPU 1 Normal 0 M9006-9141P04

5 NSQM1FWDFGD1 Normal 0 M9006-9141P04 None

CPU 1 Normal 0 M9006-9141P04 NONE

6 NSQ1FAB04B0 Normal 0 M9006-9141P04 None

7 NONE Absent 0 NONE None

8 NONE Absent 0 NONE None

9 NONE Absent 0 NONE None

Table 5 Command output

Field	Description
Brd Type	Hardware type of the card.
Brd Status	Card status: · Standby—The card is the standby MPU. · Master—The card is the active MPU. · Absent—The slot is not installed with a card. · Fault—The card is faulty and cannot start up. · Normal—The card is an interface module and is operating correctly. · Offline-OLO—The card is a switching fabric module and is isolated. · DDRError—The card failed the FPGA DDR test.
Soft Ver	Software version of the card.
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 software upgrade in Fundamentals Configuration Guide.

‌

display device manuinfo

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

chassis chassis-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. (In IRF mode.)

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays electronic label information of all cards.

cpu cpu-number: Specifies a CPU by its number. This option is supported only if multiple CPUs are available on the specified slot.

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

Usage guidelines

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

This command is supported only on the default context.

Non-default vSystems do not support this command.

Examples

# (In standalone mode.) Display electronic label information for the device.

<Sysname> display device manuinfo

Chassis self:

DEVICE_NAME : NS-SecPath M9006

DEVICE_SERIAL_NUMBER : 210235A1ABX13C000010

MAC_ADDRESS : 0CDA-41B6-4295

MANUFACTURING_DATE : 2013-12-10

VENDOR_NAME : H3C

Slot 0 CPU 0:

DEVICE_NAME : NSUM1SUPC0

DEVICE_SERIAL_NUMBER : 210231A4V40000000001

MAC_ADDRESS : 1231-2312-3123

MANUFACTURING_DATE : 2015-12-24

VENDOR_NAME : UNIS

Slot 2 CPU 0:

DEVICE_NAME : NSQM1GT48EA0

DEVICE_SERIAL_NUMBER : 210231A2HBB13B000016

MAC_ADDRESS : 5CDD-7086-9C33

MANUFACTURING_DATE : 2013-12-12

VENDOR_NAME : H3C

Slot 4 CPU 0:

DEVICE_NAME : NSQM1ADEDFGA0

DEVICE_SERIAL_NUMBER : 210231A5X2H164000022

MAC_ADDRESS : 3C8C-400E-3C96

MANUFACTURING_DATE : 2016-03-28

VENDOR_NAME : H3C

Slot 4 CPU 1:

DEVICE_NAME : NSQM1ADEDFGA0

DEVICE_SERIAL_NUMBER : 210231L010H164000022

MAC_ADDRESS : 3C8C-400E-3C96

MANUFACTURING_DATE : 2016-03-28

VENDOR_NAME : H3C

Slot 6 CPU 0:

DEVICE_NAME : NSQM1FAB04B0

DEVICE_SERIAL_NUMBER : 210231A2HFB151000056

MAC_ADDRESS : NONE

MANUFACTURING_DATE : 2015-02-04

VENDOR_NAME : H3C

Fan 0:

DEVICE_NAME : LSUM110504FAN

DEVICE_SERIAL_NUMBER : 210212A036X13C000018

MAC_ADDRESS : NONE

MANUFACTURING_DATE : 2013-12-10

VENDOR_NAME : H3C

Power 0:

DEVICE_NAME : POWER

DEVICE_SERIAL_NUMBER :

MAC_ADDRESS :

MANUFACTURING_DATE :

VENDOR_NAME :

display device manuinfo chassis-only

Use display device manuinfo chassis-only to display electronic label information for the backplane.

Syntax

In standalone mode:

display device manuinfo chassis-only

In IRF mode:

display device manuinfo chassis chassis-number chassis-only

The following compatibility matrix shows the support of hardware platforms for this command:

Hardware platform	Module type	Command compatibility
M9006 M9010 M9014	Blade IV firewall module	Yes
	Blade V firewall module	Yes
	NAT module	Yes
M9010-GM	Encryption module	Yes
M9016-V	Blade V firewall module	Yes
M9008-S M9012-S	Blade IV firewall module	Yes
	Intrusion prevention service (IPS) module	Yes
	Video network gateway module	Yes
M9008-S-V	Blade IV firewall module	Yes
M9000-AI-E4 M9000-AI-E8 M9000-AI-E16	Blade V firewall module	No
		Yes
		Yes
M9000-AK001	Blade V firewall module	No
M9000-X06 M9000-X06-B M9000-X06-B-G M9000-X06-G M9000-X10	Blade VI firewall module	Yes
M9000-AI-X06 M9000-AI-X10	Blade VI firewall module	Yes

‌

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID. (In IRF mode.)

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

Examples

# (In standalone mode.) Display electronic label information for the backplane.

<Sysname> display device manuinfo chassis-only

Chassis self:

DEVICE_NAME : XXXX

DEVICE_SERIAL_NUMBER : XXXXXXXXXXXXXXXXXXXX

MAC_ADDRESS : NONE

MANUFACTURING_DATE : XXXX-XX-XX

VENDOR_NAME : H3C

PRODUCT_ID : XX-XXXX-XX

display device manuinfo fan

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

Syntax

In standalone mode:

display device manuinfo fan fan-id

In IRF mode:

display device manuinfo chassis chassis-number fan fan-id

The following compatibility matrix shows the support of hardware platforms for this command:

‌

Hardware platform	Module type	Command compatibility
M9006 M9010 M9014	Blade IV firewall module	Yes
	Blade V firewall module	Yes
	NAT module	Yes
M9010-GM	Encryption module	Yes
M9016-V	Blade V firewall module	Yes
M9008-S M9012-S	Blade IV firewall module	No
	Intrusion prevention service (IPS) module	No
	Video network gateway module	No
M9008-S-V	Blade IV firewall module	No
M9000-AI-E4	Blade V firewall module	No
M9000-AI-E8		Yes
M9000-AI-E16		Yes
M9000-AK001	Blade V firewall module	No
M9000-X06 M9000-X06-B M9000-X06-B-G M9000-X06-G M9000-X10	Blade VI firewall module	Yes
M9000-AI-X06 M9000-AI-X10	Blade VI firewall module	Yes

‌

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID. (In IRF mode.)

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

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

Examples

# (In standalone mode.) Display electronic label information for a fan tray.

<Sysname> display device manuinfo fan 1

Fan 1:

DEVICE_NAME : XXXX

DEVICE_SERIAL_NUMBER : XXXXXXXXXXXXXXXXXXXX

MAC_ADDRESS : NONE

MANUFACTURING_DATE : XXXX-XX-XX

VENDOR_NAME : H3C

display device manuinfo power

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

Syntax

In standalone mode:

display device manuinfo power power-id

In IRF mode:

display device manuinfo chassis chassis-number power power-id

The following compatibility matrix shows the support of hardware platforms for this command:

‌

Hardware platform	Module type	Command compatibility
M9006 M9010 M9014	Blade IV firewall module	Yes
	Blade V firewall module	Yes
	NAT module	Yes
M9010-GM	Encryption module	Yes
M9016-V	Blade V firewall module	No
M9008-S M9012-S	Blade IV firewall module	No
	Intrusion prevention service (IPS) module	No
	Video network gateway module	No
M9008-S-V	Blade IV firewall module	No
M9000-AI-E4 M9000-AI-E8 M9000-AI-E16	Blade V firewall module	Yes
M9000-AK001	Blade V firewall module	Yes
M9000-X06 M9000-X06-B M9000-X06-B-G M9000-X06-G M9000-X10	Blade VI firewall module	Yes
M9000-AI-X06 M9000-AI-X10	Blade VI firewall module	Yes

‌

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID. (In IRF mode.)

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

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

Examples

# (In standalone mode.) Display electronic label information for a power module.

<Sysname> display device manuinfo power 1

Power 1:

DEVICE_NAME : XXXX

DEVICE_SERIAL_NUMBER : XXXXXXXXXXXXXXXXXXXX

MANUFACTURING_DATE : XXXX-XX-XX

VENDOR_NAME : H3C

display diagnostic-information

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

hardware: Specifies hardware-related operating information.

infrastructure: Specifies operating information for the fundamental features.

l2: Specifies operating information for the Layer 2 features.

l3: Specifies operating information for the Layer 3 features.

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

context context-name: Specifies a context by its name, a case-sensitive string of 1 to 15 characters. If you do not specify a context, this command display or save operating information for the default context.

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

Non-default vSystems do not support this command.

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.

To execute the display diagnostic-information command, make sure the CPU usage is less than 100% and the memory usage is equal to or less than 90%. To view the CPU usage and the memory usage, use the display cpu-usage and display memory commands.

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

Examples

# Display the operating information for all features and modules.

<Sysname> display diagnostic-information

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

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

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

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

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

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

...

# Save the operating information to the default file.

<Sysname> display diagnostic-information

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

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

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

Please wait...

Save successfully.

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

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

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

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

Please wait...

Save successfully.

Related commands

gunzip

tar extract

display environment

Use display environment to display temperature information.

Syntax

In standalone mode:

display environment [ slot slot-number ]

In IRF mode:

display environment [ chassis chassis-number [ slot slot-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

chassis chassis-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. (In IRF mode.)

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.

Usage guidelines

(In standalone mode.) This command displays information about all temperature sensors on the device if you do not specify a card.

(In IRF mode.) This command displays information about all temperature sensors in the IRF fabric if you do not specify an IRF member device. If you specify an IRF member device but do not specify a card, this command displays information about all sensors on the member device.

This command is supported only on the default context.

Non-default vSystems do not support this command.

Examples

# (In standalone mode.) Display information about all temperature sensors on the device.

<Sysname> display environment

System temperature information (degree centigrade):

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

Slot Sensor Temperature Lower Warning Alarm Shutdown

1 hotspot 1 38 10 40 50 100

1 hotspot 2 42 10 50 80 100

Table 6 Command output

Field	Description
System Temperature information (degree centigrade)	Temperature information (°C).
sensor	Temperature sensor: · hotspot—Hotspot sensor. · inflow—Air inlet sensor. · outflow—Air outlet sensor.
Slot	Sensor position.
Temperature	Current temperature.
Lower	Low-temperature threshold. If the device does not support this field, this field displays NA.
Warning	High-temperature warning threshold. If the device does not support this field, this field displays NA.
Alarm	High-temperature alarming threshold. If the device does not support this field, this field displays NA.
Shutdown	High-temperature 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

In standalone mode:

display fan [ fan-id ]

In IRF mode:

display fan [ chassis chassis-number [ fan-id ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

chassis chassis-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. (In IRF mode.)

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

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

Examples

# Display the operating status of all fan trays.

<Sysname> display fan

Fan Frame 0 State: Normal

Table 7 Command output

Field	Description
Fan Frame 0	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.

Field

Description

Fan Frame 0

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

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-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 a card by its slot number. If you do not specify a card, this command displays memory usage for all cards. (In standalone mode.)

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

Usage guidelines

Executing this command on a context displays memory usage information for the context.

Non-default vSystems do not support this command.

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

# (In standalone mode.) 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

# (In standalone mode.) Display brief memory usage information.

<Sysname> display memory summary

Memory statistics are measured in KB:

Slot CPU Total Used Free Buffers Caches FreeRatio

1 0 984560 456128 528432 4 45616 53.7%

Table 8 Command output

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

‌

display memory-threshold

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

vsys-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the memory usage thresholds and statistics for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays the memory usage thresholds and statistics for the global active MPU. (In IRF mode.)

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

Usage guidelines

This command is supported only on the default context.

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: 87%

Free memory threshold:

Minor: 512M

Severe: 384M

Critical: 256M

Normal: 768M

Current memory state: Normal

Event statistics:

[Back to normal state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Enter minor low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to minor low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Enter severe low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to severe low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Enter critical low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

display monitor fault

Use display monitor fault to display fault monitor configuration information.

Syntax

display monitor fault

Views

System view

Predefined user roles

network-admin

Examples

# Display fault monitor configuration information.

<Sysname> system-view

[Sysname] display monitor fault

Slot 0:

Fault monitor: Enabled

Reboot number: 3

Slot 1:

Fault monitor: Enabled

Reboot number: 3

Table 9 Command output

Field	Description
Slot x	Slot number of the card.
Fault monitor	Enabling status of fault monitor: · Enabled. · Disabled.
Reboot number	Number of reboots before the faulty card is isolated.

Related commands

monitor fault reboot-number

display monitor parity-error

Use display monitor parity-error to display parity error check configuration.

Syntax

display monitor parity-error

Views

System view

Predefined user roles

network-admin

Examples

# Display parity error check configuration.

<Sysname> system-view

[Sysname] display monitor parity-error

Period Threshold Status Chassis Slot

10 800 Disabled 1 1

10 800 Disabled 1 3

Table 10 Command output

Field	Description
Period	Interval of parity error check, in seconds.
Threshold	Threshold for parity errors in intervals, measured in the number of parity errors.
Status	Enabling status of parity check: · Enabled. · Disabled.
Chassis	Slot number of the chassis where the card resides.
Slot	Slot number of the card.

Related commands

montior parity-error

display power

Use display power to display power module information.

Syntax

In standalone mode:

display power [ power-id ]

In IRF mode:

display power [ chassis chassis-number [ power-id ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

chassis chassis-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. (In IRF mode.)

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.

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

Examples

# Display brief power supply information.

<Sysname> display power

Power 0 State: Normal Voltage:12.0 V Current:51.8 A Power:619.1 W

Power 1 State: Error

Power 2 State: Absent

Power 3 State: Absent

Table 11 Command output

Field	Description
Power xxx	Power supply ID.
State	Power supply status: · Absent—The slot is not installed with a power supply. · Fault/Error—The power supply is faulty. · Normal—The power supply is operating correctly.
Current(A)	Output current of the power supply, in amperes. If this field is not displayed if it is not supported. "-- A" is displayed if the device fails to read the current.
Voltage(V)	Output voltage of the power supply, in volts. If this field is not displayed if it is not supported. "-- A" is displayed if the device fails to read the voltage.
Power(W)	Output power of the power supply, in watts. If this field is not displayed if it is not supported. "-- A" is displayed if the device fails to read the power.

‌

display resource-monitor

Use display resource-monitor to display resource monitoring information.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

resource resource-name: Specifies a resource type by its name. See Table 25 for the resource types.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays resource monitoring information for all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays resource monitoring information for all cards. (In IRF mode.)

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

This command is supported only on the default context.

Examples

# (In standalone mode.) Display ARP resource monitoring information.

<Sysname> display resource-monitor resource arp

Minor alarms resending: Enabled

Slot 1:

Resource Minor Severe Free/Total

(%) (%) (absolute)

arp 50 20 90095/90098

Table 12 Command output

Field	Description
Minor alarms resending	Status of the minor resource depletion alarm resending feature: · Enabled. · Disabled.
Resource	Monitored resource type.
Minor (%)	Minor resource depletion threshold, in percentage.
Severe (%)	Severe resource depletion threshold, in percentage.
Free/Total (absolute)	Numbers of available resources and total resources, in absolute values.

‌

Related commands

resource-monitor minor resend enable

resource-monitor resource

display scheduler job

Use display scheduler job to display job configuration information.

Syntax

display scheduler job [ job-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-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.

Usage guidelines

Non-default vSystems do not support this command.

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

context-admin

context-operator

Usage guidelines

Non-default vSystems do not support this command.

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 13 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

context-admin

context-operator

Usage guidelines

Non-default vSystems do not support this command.

Examples

# Display the automatic reboot schedule.

<Sysname> display scheduler reboot

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

Related commands

scheduler reboot at

scheduler reboot delay

display scheduler schedule

Use display scheduler schedule to display schedule information.

Syntax

display scheduler schedule [ schedule-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-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.

Usage guidelines

Non-default vSystems do not support this command.

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 14 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 health

Use display system health to display system health status information.

Syntax

In standalone mode:

display system health

In IRF mode:

display system health [ chassis chassis-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays health status information about the master device. (In IRF mode.)

Usage guidelines

The device periodically performs a series of checks to identify the health status of the device. The check items are already defined in the factory-default configuration. The check results can be used by the internal service modules such as IRF in the device. You can execute this command to view these check results.

Examples

# Display system health status information.

<Sysname> display system health

Health: Normal(0)

HgPortDown check: Normal(0)

HgPacketLoss check: Normal(0)

ParityError check: Normal(0)

PortDrop check: Normal(0)

HgPacketDrop check: Normal(0)

HgPacketTamper check: Normal(0)

ChipError check: Normal(0)

BladeFmea check: Normal(0)

PortFmea check: Normal(0)

Table 15 Command output

Field	Description
Health: Normal(0)	System health status: · Normal(0)—The system is healthy. · Faulty(n)—The system is faulty. A greater value of n indicates a worse condition.
HgPortDown check	Port down check item detected by inner ports
HgPacketLoss check	Check item of packet drop caused by FCS or RERPKT error.
ParityError check	Check item of parity error.
PortDrop check	Check item of port packet drop.
HgPacketDrop check	Check item of HGMonitor probe packet drop on a HG port.
HgPacketTamper check	Check item of probe packet tampering.
ChipError check	Check item of chip error.
BladeFmea check	Check item of security engine error.
PortFmea check	Check item of port connection error between interface switch modules and subcards.

‌

Related commands

display system health history

Use display system health history to display historical system health status change information.

Syntax

In standalone mode:

display system health history

In IRF mode:

display system health history[ chassis chassis-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays historical health status change information about the master device. (In IRF mode.)

Examples

# Display historical system health status change information.

<Sysname> display system health history

Health: Faulty(1)

PortFmea check:

Faulty(1) 2019-10-10 18:00:00 on slot 1

Normal(0) 2019-10-08 17:00:00 on slot 1

Faulty(1) 2019-10-07 18:00:00 on slot 1

Table 16 Command output

Field

Description

Health: Normal(0)

System health status:

· Normal(0)—The system is healthy.

· Faulty(n)—The system is faulty. A greater value of n indicates a worse condition.

PortFmea check:

Faulty(1) 2019-10-10 18:00:00 on slot 1

Historical status change information of items. For more information about the supported check items on the device, see Table 15.

A maximum of 30 historical status change entries are supported for each item.

‌

Related commands

display system health

display system stable state

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

Syntax

display system stable state [ context { context-id | all } ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

context { context-id | all }: Specifies a context by its ID or specifies all contexts. For more information about context and the value range for the context ID, see Virtual Technologies Command Reference.

Usage guidelines

Non-default vSystems do not support this command.

If you do not specify a context, this command displays stability information for the system.

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

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

· Use the display ha service-group command to display the status of HA service groups and identify the groups in batch backup state.

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

Examples

# (In standalone mode.) Display system stability and status information.

<Sysname> display system stable state

System state : Stable

Redundancy state : Stable

Slot CPU Role State

0 0 Active Stable

1 0 Standby Stable

3 0 Other Stable

15 0 Other Stable

Table 17 Command output

Field	Description
System state	System status: · Stable—The system is operating stably. · Not ready.
Redundancy state	System redundancy status: · Stable—Both MPUs are operating stably. You can perform a switchover. · No redundance—The system has only one MPU. You cannot perform a switchover. · Not ready—The system is not operating stably. You cannot perform a switchover.
Role	Role of the card in the system: · Active—The card is the active MPU. · Standby—The card is the standby MPU. · Other—The card is a service card.
State	Card status: · Stable—The card is operating stably. · Board inserted—The card has just been installed. · Kernel initiating—Card kernel is being initialized. · Service starting—Services are starting. · Service stopping—Services are stopping. · HA Batch backup—An HA batch backup is going on. · Interface data batch backup—An interface data batch backup is in progress. · Context starting—Contexts are starting. · Context stopping—Contexts are stopping.
*	The object is not operating stably.

‌

Related commands

display context (Virtual Technologies Command Reference)

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

context-admin

context-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

Non-default vSystems do not support this command.

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

Table 18 Common transceiver alarm components

Field	Description
APD	Avalanche photo diode
PCS	Physical coding sublayer
PHY XS	PHY extended sublayer
PMA/PMD	Physical medium attachment/physical medium dependent
power	Optical power
REFCLK	Reference clock
RX	Receive
Temp	Temperature
TX	Transmit
WIS	WAN interface sublayer

‌

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 loss of signal

RX power low

Table 19 Command output

Field	Description
transceiver current alarm information	Alarms present on the transceiver module.
RX loss of signal	Received signals are lost.
RX power low	Received power is low.

‌

display transceiver diagnosis

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-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 all interfaces.

Usage guidelines

Non-default vSystems do not support this command.

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

Table 20 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.
Bias(mA)	Bias current in mA, accurate to 0.01 mA.
RX power(dBm)	Receive power in dBm, accurate to 0.01 dBm.
TX power(dBm)	Transmit power in dBm, accurate to 0.01 dBm.

‌

display transceiver interface

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

Syntax

display transceiver interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-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.

Usage guidelines

Non-default vSystems do not support this command.

Examples

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

<Sysname> display transceiver interface gigabitethernet 1/0/1

GigabitEthernet1/0/1 transceiver information:

Transceiver Type : 1000_BASE_SX_SFP

Connector Type : LC

Wavelength(nm) : 850

Transfer Distance(m) : 550(50um),270(62.5um)

Digital Diagnostic Monitoring : YES

Vendor Name : H3C

Ordering Name : SFP-GE-SX-MM850

Table 21 Command output

Field	Description
Wavelength(nm)	Central wavelength of the laser in nm. For a fiber transceiver module that supports multiple wavelengths, for example, the 10GBASE-LX4 transceiver module, this field displays all the wavelengths, separating the values by commas (,). For a copper module, this field displays N/A.
Transfer Distance(m)	Transmission distance, in km (for single-mode modules) or in m (for other modules). For a module that supports multiple transmission media, this field displays all the transmission distances, separating the values by commas (,). Each transmission distance is followed by the medium name in parentheses. · 9um—9/125um single-mode optical fiber. · 50um—50/125um OM2 multi-mode optical fiber. · 62.5um—62.5/125um OM1 multi-mode optical fiber. · CX4—CX4 cables. · OM3—50um OM3 multi-mode optical fiber. · OM4—50um OM4 multi-mode optical fiber. · OM5—50um OM5 multi-mode optical fiber. · STACK—Stack cable. · TP—Twisted pairs.
Digital Diagnostic Monitoring	Whether digital diagnosis is supported: · YES—Digital diagnosis is supported. · NO—Digital diagnosis is not supported.

‌

display transceiver manuinfo

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-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 the transceiver modules in all interfaces.

Usage guidelines

Non-default vSystems do not support this command.

Examples

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

<Sysname> display transceiver manuinfo interface gigabitethernet 1/0/1

GigabitEthernet1/0/1 transceiver manufacture information:

Manu. Serial Number : 213410A0000054000251

Manufacturing Date : 2017-09-01

Vendor Name : H3C

display version

Use display version to display system version information.

Syntax

display version

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Usage guidelines

Non-default vSystems do not support this command.

Examples

# Display system version information.

<Sysname> display version

H3C Comware Software, Version 7.1.064, Ess 9141P04

H3C SecPath M9006 uptime is 0 weeks, 0 days, 23 hours, 35 minutes

Last reboot reason : User reboot

Boot image: flash:/M9000-CMW710-BOOT-E9141P04.bin

Boot image version: 7.1.064, Ess 9141P04

Compiled Feb 24 2018 16:00:00

System image: flash:/M9000-CMW710-SYSTEM-E9141P04.bin

System image version: 7.1.064, Ess 9141P04

Compiled Feb 24 2018 16:00:00

...

Table 22 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.

· Power on—The reboot was caused by a power cycle.

· Exception reboot—The reboot was caused by kernel exceptions.

· Heart-beat timeout—The reboot was caused by a device management handshake failure.

· Switch to standby—The reboot was caused by a master/subordinate switchover.

· IRF Merge—The reboot was caused by an IRF merge.

· Auto reboot after updating—The reboot was caused by a software upgrade.

· Out of memory—The reboot was caused by a card-memory-exhausted event.

‌

display version-update-record

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

Syntax

display version-update-record

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

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

Examples

# Display the startup software image upgrade records.

<Sysname> display version-update-record

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

*Name : boot-test.bin

Version : 7.1.070 Test 0001

Compile time: Mar 25 2015 15:52:43

*Name : system-test.bin

Version : 7.1.070 Test 0001

Compile time: Mar 25 2015 15:52:43

Table 23 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

display voltage

Use display voltage to display voltage information.

Syntax

In standalone mode:

display voltage [ slot slot-number ]

In IRF mode:

display voltage [ chassis chassis-number [ slot slot-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID. (In IRF mode.)

slot slot-number: Specifies a card by its slot number.

Usage guidelines

This command is supported only on the default context.

(In standalone mode.) If you do not specify a card, this command displays voltage information for all cards.

(In IRF mode.) If you do not specify a member device, this command displays voltage information for all member devices. If you specify a member device but do not specify a card, this command displays voltage information for all cards on the member device.

If the voltage is lower than the lower limit or higher than the higher limit, the device sends a log message and a trap.

Examples

# (In standalone mode.) Display voltage information.

<Sysname> display voltage

System voltage information (volt):

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

Slot Sensor Voltage Status Required LowLimit HighLimit Description

1 0 0.763 Normal 0.750 0.675 0.825 0.75

1 1 1.051 Normal 1.050 0.945 1.155 1.05

Table 24 Command output

Field	Description
Slot	Chassis ID/slot ID. For a sensor on a slot, this field displays the slot number.
Sensor	ID of the sensor.
Voltage	Current voltage of the sensor.
Description	Description for the sensor. This field is generated by the device. It displays the rated voltage of the sensor. If another sensor has the same rated voltage value, a string is automatically inserted before the rated voltage value to uniquely identify the item.

‌

fabric load-sharing mode

Use fabric load-sharing mode to specify load sharing modes for an interface module or a switching fabric module.

Use undo fabric load-sharing mode to restore the default.

Syntax

In standalone mode:

fabric load-sharing mode { { destination-ip | destination-mac | ingress-port | source-ip | source-mac } * | flexible } slot slot-number

undo fabric load-sharing mode [ { destination-ip | destination-mac | ingress-port | source-ip | source-mac } * | flexible ] slot slot-number

In IRF mode:

fabric load-sharing mode { { destination-ip | destination-mac | ingress-port | source-ip | source-mac } * | flexible } chassis chassis-number slot slot-number

undo fabric load-sharing mode { destination-ip | destination-mac | ingress-port | source-ip | source-mac } * | flexible ] chassis chassis-number slot slot-number

Default

The default varies by card model. As a best practice, use the default. To change the default, contact H3C Support.

Views

System view

Predefined user roles

network-admin

Parameters

destination-ip: Balances load based on destination IP address.

destination-mac: Balances load based on destination MAC address.

ingress-port: Balances load based on ingress interface.

source-ip: Balances load based on source IP address.

source-mac: Balances load based on source MAC address.

flexible: Selects a balance mode based on the packet type (for example, Layer 2 packet or IPv4 packet).

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

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

Examples

# (In standalone mode.) Set the load sharing mode to destination-mac for a card.

<Sysname> system-view

[Sysname] fabric load-sharing mode destination-mac slot 2

Related commands

display xbar

hardware usb power-on

Use hardware usb power-on to enable USB interfaces on service modules to provide power.

Use undo hardware usb power-on to disable USB interfaces on service modules from providing power.

Syntax

hardware usb power-on

undo hardware usb power-on

Default

USB interfaces on service modules can provide power.

Views

System view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Examples

# Enable USB interfaces on service modules to provide power.

<Sysname> system-view

[Sysname] hardware usb power-on

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

context-admin

Parameters

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

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

shell: Configures the banner to be displayed before a 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 device management in Fundamentals Configuration Guide.

Usage guidelines

Non-default vSystems do not support this command.

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

context-admin

Parameters

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

Usage guidelines

Non-default vSystems do not support this command.

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

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

Examples

# Assign job save-job to schedule saveconfig.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] job save-job

Related commands

scheduler job

scheduler schedule

locator blink

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

Use locator blink stop to stop LED flashing.

Syntax

In standalone mode:

locator blink blink-time

locator blink stop

In IRF mode:

locator [ chassis chassis-number ] blink blink-time

locator [ chassis chassis-number ] blink stop

Views

User view

Predefined user roles

network-admin

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID. If you do not specify a member device, the command applies to all member devices. (In IRF mode.)

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

stop: Stops flashing.

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

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

Examples

# Start LED flashing to locate devices.

<Sysname> locator blink 30

# Stop LED flashing.

<Sysname> locator blink stop

memory-threshold

Use memory-threshold to set free-memory thresholds.

Use undo memory-threshold to restore the default.

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

The default settings vary by device model. To view the default settings, use the undo memory-threshold command to restore the default settings and then execute the display memory-threshold command.

Views

System view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command sets free-memory thresholds for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets free-memory thresholds for the global active MPU. (In IRF mode.)

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

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

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

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

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

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

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

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

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.

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

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

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

Examples

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

<Sysname> system-view

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

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

In standalone mode:

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

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

In IRF mode:

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

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

Default

The memory usage threshold is 90%.

Views

System view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command sets the memory usage threshold for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets the memory usage threshold for the global active MPU. (In IRF mode.)

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

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

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

The device samples memory usage at 1-minute intervals. If the sample is equal to or 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-pci-status

Use monitor cpu-pci-status to enable PCI bus status monitoring.

Use undo monitor cpu-rx-status to disable PCI bus status monitoring.

Syntax

monitor cpu-pci-status

undo monitor cpu-pci-status

Default

PCI bus status monitoring is disabled.

Views

System view

Predefined user roles

network-admin

context-admin

Usage guidelines

After you enable PCI bus status monitoring, the system monitors whether the PCI bus is operating correctly. If an error is found, the system generates a log message and issues an alarm.

Examples

# Enable PCI bus status monitoring.

<Sysname> system-view

[Sysname] monitor cpu-pci-status

Related commands

display monitor cpu-status

monitor cpu-rx-status

monitor cpu-tx-status

monitor cpu-rx-status

Use monitor cpu-rx-status to enable CPU forwarding status monitoring in the inbound direction.

Use undo monitor cpu-rx-status to disable CPU forwarding status monitoring in the inbound direction.

Syntax

monitor cpu-rx-status

undo monitor cpu-rx-status

Default

CPU forwarding status monitoring is disabled in the inbound direction.

Views

System view

Predefined user roles

network-admin

Usage guidelines

After you enable CPU forwarding status monitoring in the inbound direction, the system monitors whether the CPUs can receive packets correctly. If an error is found, the system generates a log message and issues an alarm.

Examples

# Enable CPU forwarding status monitoring in the inbound direction.

<Sysname> system-view

[Sysname] monitor cpu-rx-status

Related commands

display monitor cpu-status

monitor cpu-tx-status

Use monitor cpu-tx-status to enable CPU forwarding status monitoring in the outbound direction.

Use undo monitor cpu-tx-status to disable CPU forwarding status monitoring in the outbound direction.

Syntax

monitor cpu-tx-status

undo monitor cpu-tx-status

Default

CPU forwarding status monitoring is disabled in the outbound direction.

Views

System view

Predefined user roles

network-admin

Usage guidelines

After you enable CPU forwarding status monitoring in the outbound direction, the system monitors whether the CPUs are sending packets correctly. If an error is found, the system generates a log message and issues an alarm.

Examples

# Enable CPU forwarding status monitoring in the outbound direction.

<Sysname> system-view

[Sysname] monitor cpu-tx-status

Related commands

display monitor cpu-status

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

In standalone mode:

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

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

In IRF mode:

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

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

Default

CPU usage monitoring is enabled.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command enables CPU usage monitoring for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command enables CPU usage monitoring for the global active MPU. (In IRF mode.)

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

Usage guidelines

Non-default vSystems do not support this command.

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

Examples

# Enable CPU usage monitoring.

<Sysname> system-view

[Sysname] monitor cpu-usage enable

Related commands

display cpu-usage configuration

display cpu-usage history

monitor cpu-usage interval

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

Syntax

In standalone mode:

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

In IRF mode:

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

Default

The system samples CPU usage every 1 minute.

Views

System view

Predefined user roles

network-admin

context-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 a card by its slot number. If you do not specify a card, this command sets the interval for the active MPU. (In standalone mode.)

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

Usage guidelines

Non-default vSystems do not support this command.

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

Examples

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

<Sysname> system-view

[Sysname] monitor cpu-usage interval 5Sec

Related commands

display cpu-usage configuration

display cpu-usage history

monitor cpu-usage enable

monitor cpu-usage statistics-interval core

Use monitor cpu-usage statistics-interval core to set CPU core usage statistics intervals.

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

Syntax

In standalone mode:

monitor cpu-usage statistics-interval interval slot slot-number cpu cpu-number core core-id-list

undo monitor cpu-usage statistics-interval slot slot-number cpu cpu-number core core-id-list

In IRF mode:

monitor cpu-usage statistics-interval interval chassis chassis-number slot slot-number cpu cpu-number core core-id-list

undo monitor cpu-usage statistics-interval chassis chassis-number slot slot-number cpu cpu-number core core-id-list

Default

The CPU core usage statistics interval is 60 seconds.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

interval: Specifies the CPU core usage statistics interval in seconds. The value range for this argument is 10 to 3600. As a best practice, set this argument to a multiple of the sampling interval, which is fixed at 5 seconds. If you do not do so, the actual statistics interval is the biggest multiple of the sampling interval that is smaller than the setting. For example, if you set this argument to 12 seconds, the actual statistics interval is 10 seconds.

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

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 greater than or equal to the value for core-id1.

Usage guidelines

Non-default vSystems do not support this command.

The device samples CPU core usage at 5-second intervals and calculates the average value during each CPU core usage statistics interval. If the value during an interval is greater than the CPU core usage threshold, the device issues an alarm and logs the event.

Examples

# (In standalone mode.) Set the usage statistics interval to 60 seconds for a CPU core.

<Sysname> system-view

[Sysname] monitor cpu-usage statistics-interval 60 slot 1 cpu 0 core 0

Related commands

monitor cpu-usage threshold core

monitor resend cpu-usage core-interval

monitor cpu-usage threshold

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

The CPU usage alarm threshold is 70%. The CPU usage recovery threshold is 30%.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

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

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 a card by its slot number. If you do not specify a card, this command sets the CPU usage threshold for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets the CPU usage threshold for the global active MPU. (In IRF mode.)

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

Usage guidelines

CAUTION:

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

Non-default vSystems do not support this command.

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

Examples

# Set the CPU usage alarm threshold to 90% and the CPU usage recovery threshold to 70%.

<Sysname> system-view

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

Related commands

display cpu-usage configuration

monitor crc-error action

Use monitor crc-error { higig-port | xe-port } action to specify the action to be taken by the service module when the number of CRC errors exceeds the threshold per second for the specified times consecutively on inner ports.

Use undo monitor crc-error { higig-port | xe-port } action to restore the default.

Syntax

monitor crc-error { higig-port | xe-port } action { ignore | reboot | isolate }

undo monitor crc-error { higig-port | xe-port } action

Default

The service module reboots when the number of CRC errors exceeds the threshold per second for the specified times consecutively.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

higig-port: Specifies the HG port.

xe-port: Specifies the XE port. This keyword is available for Blade V security modules.

ignore: Specifies the ignore action.

reboot: Specifies the reboot action.

isolate: Specifies the power-off action. This action is not supported in the BladeVI security service module.

Usage guidelines

This command takes effect only on security modules that support FPGA.

You can execute this command together with the monitor crc-error threshold and monitor crc-error times commands. Then, the service module will perform the specified action when the number of CRC errors exceeds the threshold per second for the specified times consecutively on inner ports.

Examples

# Configure the service module to power off when the number of CRC errors exceeds the threshold per second for the specified times consecutively on HG ports.

<Sysname> system-view

[Sysname] monitor crc-error higig-port action isolate

Related commands

display crc-error configuration

monitor crc-error threshold

monitor crc-error times

monitor crc-error threshold

Use monitor crc-error { higig-port | xe-port } threshold to specify the threshold for the number of CRC errors per second on the inner ports of the service module.

Use undo monitor crc-error { higig-port | xe-port } threshold to restore the default.

Syntax

monitor crc-error { higig-port | xe-port } threshold threshold-value

undo monitor crc-error { higig-port | xe-port } threshold

Default

The threshold for the number of CRC errors per second on the inner ports of the service module is 50.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

higig-port: Specifies the HG port.

xe-port: Specifies the XE port. This keyword is available for Blade V security modules.

threshold-value: Specifies the threshold for the number of CRC errors, in the range of 10 to 10000.

Usage guidelines

This command takes effect only on security modules that support FPGA.

You can execute this command together with the monitor crc-error action and monitor crc-error times commands. Then, the service module will take the specified action when the number of CRC errors per second consecutively exceeds the threshold for the specified times.

Examples

# Specify the threshold for the number of CRC errors per second on the HG ports as 100.

<Sysname> system-view

[Sysname] monitor crc-error higig-port threshold 100

Related commands

display crc-error configuration

monitor crc-error action

monitor crc-error times

Use monitor crc-error { higig-port | xe-port } times to specify the maximum number of times that the number of CRC errors per second consecutively exceeds the threshold on inner ports of the service module.

Use undo monitor crc-error { higig-port | xe-port } times to restore the default.

Syntax

monitor crc-error { higig-port | xe-port } times times

undo monitor crc-error { higig-port | xe-port } times

Default

The maximum number of times that the number of CRC errors per second consecutively exceeds the threshold on inner ports of the service module is 300.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

higig-port: Specifies the HG port.

xe-port: Specifies the XE port. This keyword is available for Blade V security modules.

times: Specify the maximum number of times that the number of CRC errors per second consecutively exceeds the threshold, in the range of 10 to 10000.

Usage guidelines

This command takes effect only on security modules that support FPGA.

You can execute this command together with the monitor crc-error threshold and monitor crc-error action commands. Then, the service module will take the specified action when the number of CRC errors per second consecutively exceeds the threshold for the specified times.

Examples

# Specify the maximum number of times that the number of CRC errors per second consecutively exceeds the threshold on the HG ports as 600.

<Sysname> system-view

[Sysname] monitor crc-error higig-port times 600

Related commands

display crc-error configuration

monitor crc-error action

monitor crc-error threshold

monitor fault reboot-number

Use monitor fault reboot-number to specify the number of card reboots before the device isolates a faulty card detected by fault monitor.

Use undo monitor fault to disable fault monitor.

Syntax

monitor fault reboot-number reboot-number

undo monitor fault

Default

Fault monitor is enabled and a faulty card reboots three times before being isolated.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

reboot-number: Specifies the number of card reboots, in the range of 0 to 3. Value 0 indicates that a faulty card will be directly isolated without any reboot attempts.

Usage guidelines

The monitoring system monitors the health status of cards in the system. When a hardware fault occurs on a card, the system attempts to recover the card by rebooting it. By default, if a card fails to recover to normal after three consecutive reboots, the card will be isolated directly. A card will be considered to have failed to recover from consecutive reboots and then be isolated as configured only when the interval between each reboot is equal to or less than 30 minutes. Otherwise, isolation will not be triggered.

A faulty service subcard can only rebooted and cannot be isolated.

Examples

# Configure the device to isolate a card when the card fails to recover to normal after a reboot.

<Sysname> system-view

[Sysname] monitor fault reboot-number 1

Related commands

display monitor fault

monitor resend cpu-usage core-interval

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

monitor resend cpu-usage core-interval core-interval [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

undo monitor resend cpu-usage core-interval [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Default

The CPU core alarm resending interval is 300 seconds.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

core-interval: Specifies the CPU core alarm resending interval in seconds, a multiple of 5 in the range of 10 to 3600.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command sets the CPU core alarm resending interval for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets the CPU core alarm resending interval for the global active MPU. (In IRF mode.)

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

Usage guidelines

Non-default vSystems do not support this command.

Examples

# Set the CPU core alarm resending interval to 60 seconds.

<Sysname> system-view

[Sysname] monitor resend cpu-usage core-interval 60

monitor resource-usage { bridge-aggregation | route-aggregation } threshold

Use monitor resource-usage { bridge-aggregation | route-aggregation } threshold to set aggregate interface usage thresholds.

Use undo monitor resource-usage { bridge-aggregation | route-aggregation } threshold to restore the default.

Syntax

monitor resource-usage { bridge-aggregation | route-aggregation } threshold threshold-value

undo monitor resource-usage { bridge-aggregation | route-aggregation } threshold

Default

No aggregate interface usage thresholds are set. The aggregate interface usage alarm feature is disabled.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

bridge-aggregation: Sets the Layer 2 aggregate interface usage threshold.

route-aggregation: Sets the Layer 3 aggregate interface usage threshold.

threshold-value: Specifies the aggregate interface usage threshold, in the range of 1 to 4294967295.

Usage guidelines

Non-default vSystems do not support this command.

When the number of created Layer 2 or Layer 3 aggregate interfaces reaches the threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 3-hour intervals.

Examples

# Set the Layer 2 aggregate interface usage threshold to 100.

<Sysname> system-view

[Sysname] monitor resource-usage bridge-aggregation threshold 100

# Set the Layer 3 aggregate interface usage threshold to 150.

<Sysname> system-view

[Sysname] monitor resource-usage route-aggregation threshold 150

monitor resource-usage bandwidth inbound threshold

Use monitor resource-usage bandwidth inbound threshold to set the total inbound bandwidth usage threshold.

Use undo monitor resource-usage bandwidth inbound threshold to restore the default.

Syntax

monitor resource-usage bandwidth inbound threshold threshold-value [ duration duration-value ]

undo monitor resource-usage bandwidth inbound threshold

Default

The total inbound bandwidth usage threshold is not set. The bandwidth usage alarm feature is disabled.

Views

System view

Predefined user roles

network-admin

Parameters

threshold-value: Specify the total inbound bandwidth usage threshold in Mbps. The value range for this argument is 1 to 4294967295.

duration duration-value: Specify the high-usage duration criterion in seconds, a multiple of five in the range of 5 to 300. The default value is 300.

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

If the total inbound traffic remains greater than or equal to the total inbound bandwidth usage threshold for the specified duration, the device sends an alarm. If the alarm state persists, the device resends the alarm at 5-second intervals.

Examples

# Set the total inbound bandwidth usage threshold to 1024 Mbps and set the high-usage duration criterion to 60 seconds.

<Sysname> system-view

[Sysname] monitor resource-usage bandwidth inbound threshold 1024 duration 60

monitor resource-usage blade-controller-team context

Use monitor resource-usage blade-controller-team context to enable monitoring of the number of contexts in each security engine group.

Use undo monitor resource-usage blade-controller-team context to disable monitoring of the number of contexts in each security engine group.

Syntax

monitor resource-usage blade-controller-team context

undo monitor resource-usage blade-controller-team context

Default

Monitoring of the number of contexts in each security engine group is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

After you enable monitoring of the number of contexts in each security engine group, the device regularly monitors the number of contexts in each security engine group.

The device supports a minor alarm threshold and a severe alarm threshold.

· When the number of contexts in a security engine group increases to or above the minor alarm threshold, the team enters minor alarm state and issues a minor alarm.

· When the number of contexts in a security engine group increases to or above the severe alarm threshold, the team enters severe alarm state and issues a severe alarm.

· When the number of contexts in a security engine group decreases below the severe alarm threshold, the team enters minor alarm state and issues a severe-alarm-removed notification.

· When the number of contexts in a security engine group decreases below the minor alarm threshold, the team issues a minor-alarm-removed notification.

· If the security engine group stays in minor alarm state, the device resends minor alarms at 6-hour intervals. If the security engine group stays in severe alarm state, the device resends severe alarms at 6-hour intervals.

The alarm thresholds are fixed and cannot be changed. You can view the thresholds by reading alarm messages.

Examples

# Enable monitoring of the number of contexts in each security engine group.

<Sysname> system-view

[Sysname] monitor resource-usage blade-controller-team context

monitor resource-usage blade-throughput threshold

Use monitor resource-usage blade-throughput threshold to set the inner interface throughput threshold.

Use undo monitor resource-usage blade-throughput threshold to restore the default.

Syntax

monitor resource-usage blade-throughput threshold threshold-value

undo monitor resource-usage blade-throughput threshold

Default

The inner interface throughput threshold is not set. The inner interface throughput alarm feature is disabled.

Views

System view

Predefined user roles

network-admin

Parameters

threshold-value: Specifies the inner interface throughput threshold in Mbps. The value range for this argument is 1 to 4294967295.

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

When the inner interface throughput reaches the threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 10-minute intervals.

Examples

# Set the inner interface throughput threshold to 2000 Mbps.

<Sysname> system-view

[Sysname] monitor resource-usage blade-throughput threshold 2000

monitor resource-usage context threshold

Use monitor resource-usage context threshold to set the global context usage threshold.

Use undo monitor resource-usage context threshold to restore the default.

Syntax

monitor resource-usage context threshold threshold-value

undo monitor resource-usage context threshold

Default

The global context usage threshold is not set. The context usage alarm feature is disabled.

Views

System view

Predefined user roles

network-admin

Parameters

threshold-value: Specifies the global context usage threshold, in the range of 1 to 4294967295.

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

When the number of created contexts on the device reaches the threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 6-hour intervals.

Examples

# Set the global context usage threshold to 16.

<Sysname> system-view

[Sysname] monitor resource-usage context threshold 16

monitor resource-usage qacl threshold

Use monitor resource-usage qacl threshold to set the QACL resource usage threshold.

Use undo monitor resource-usage qacl threshold to restore the default.

Syntax

monitor resource-usage qacl threshold threshold-value

undo monitor resource-usage qacl threshold

Default

The QACL resource usage threshold is not set. The QACL resource usage alarm feature is disabled.

Views

System view

Predefined user roles

network-admin

Parameters

threshold-value: Specifies the QACL resource usage threshold in percentage. The value range for this argument is 1 to 100.

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

When the QACL resource usage reaches the threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 3-hour intervals.

Examples

# Set the QACL resource usage threshold to 70.

<Sysname> system-view

[Sysname] monitor resource-usage qacl threshold 70

monitor resource-usage security-policy threshold

Use monitor resource-usage security-policy { ip | ipv6 } threshold to set security policy rule usage thresholds.

Use undo monitor resource-usage security-policy { ip | ipv6 } threshold to restore the default.

Syntax

monitor resource-usage security-policy { ip | ipv6 } threshold threshold-value

undo monitor resource-usage security-policy { ip | ipv6 } threshold

Default

No security policy rule thresholds are set. The security policy rule alarm feature is disabled.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

ip: Sets the IPv4 security policy rule threshold.

ipv6: Sets the IPv6 security policy rule threshold.

threshold-value: Specifies the security policy rule threshold, in the range of 1 to 4294967295.

Usage guidelines

Non-default vSystems do not support this command.

When the number of created security policy rules reaches the threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 6-hour intervals.

Examples

# Set the IPv4 security policy rule threshold to 500.

<Sysname> system-view

[Sysname] monitor resource-usage security-policy ip threshold 500

# Set the IPv6 security policy rule threshold to 500.

<Sysname> system-view

[Sysname] monitor resource-usage security-policy ipv6 threshold 500

monitor resource-usage session-count threshold

Use monitor resource-usage session-count threshold to set session usage thresholds.

Use undo monitor resource-usage session-count threshold to restore the default.

Syntax

In standalone mode:

monitor resource-usage session-count [ slot slot-number cpu cpu-number ] threshold threshold-value

undo monitor resource-usage session-count [ slot slot-number cpu cpu-number ] threshold

In IRF mode:

monitor resource-usage session-count [ chassis chassis-number slot slot-number cpu cpu-number ] threshold threshold-value

undo monitor resource-usage session-count [ chassis chassis-number slot slot-number cpu cpu-number ] threshold

Default

No session usage thresholds are set. The session usage alarm feature is disabled.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command sets the session usage threshold for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets the session usage threshold for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. This option is supported only if multiple CPUs are available on the specified slot.

threshold-value: Specifies the session threshold, in the range of 1 to 4294967295.

Usage guidelines

Non-default vSystems do not support this command.

When the number of sessions reaches the threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 10-minute intervals.

Examples

# Set the session usage threshold to 100000.

<Sysname> system-view

[Sysname] monitor resource-usage session-count threshold 100000

monitor resource-usage session-rate threshold

Use monitor resource-usage session-rate threshold to set session establishment rate thresholds.

Use undo monitor resource-usage session-rate threshold to restore the default.

Syntax

In standalone mode:

monitor resource-usage session-rate [ slot slot-number cpu cpu-number ] threshold threshold-value

undo monitor resource-usage session-rate [ slot slot-number cpu cpu-number ] threshold

In IRF mode:

monitor resource-usage session-rate [ chassis chassis-number slot slot-number cpu cpu-number ] threshold threshold-value

undo monitor resource-usage session-rate [ chassis chassis-number slot slot-number cpu cpu-number ] threshold

Default

No session establishment rate thresholds are set. The session establishment rate alarm feature is disabled.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command sets the session establishment rate threshold for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets the session establishment rate threshold for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. This option is supported only if multiple CPUs are available on the specified slot.

threshold-value: Specifies the session establishment rate threshold, in the range of 1 to 4294967295.

Usage guidelines

Non-default vSystems do not support this command.

When the session establishment rate reaches the threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 10-minute intervals.

Examples

# Set the session establishment rate threshold to 500.

<Sysname> system-view

[Sysname] monitor resource-usage session-rate threshold 500

monitor parity-error

Use monitor parity-error to configure the parity error checking interval and parity error threshold.

Use undo monitor parity-error to disable parity error checking.

Syntax

monitor parity-error period period-value threshold threshold-value

undo monitor parity-error

Default

Parity error checking is enabled. The system checks for parity errors at 10-second intervals and the parity error threshold is 800.

Views

System view

Predefined user roles

network-admin

Parameters

period period-value: Specifies the parity checking interval, in seconds. The value value is 1 to 86400.

threshold threshold-value: Specifies the parity error threshold. The value range is 1 to 1000000.

Usage guidelines

The system monitors the health status of switch chip entries on the cards in real time. If the number of parity errors on a card exceeds the threshold within the checking interval, the system will generate logs and traps and flags the status as unhealthy.

Examples

# Set the parity error checking interval to 20 seconds and the parity error threshold to 1000.

<Sysname> system-view

[Sysname] montior parity-error period 20 threshold 1000

Related commands

display montior parity-error

password-recovery enable

Use password-recovery enable to enable password recovery capability.

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

Syntax

password-recovery enable

undo password-recovery enable

Default

Password recovery capability is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

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.

(In standalone mode.) (In IRF mode.) To access the device configuration without authentication, you must connect to the active MPU and access the BootWare menu while the MPU is starting up.

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

Examples

# Disable password recovery capability.

<Sysname> system-view

[Sysname] undo password-recovery enable

reboot

Use reboot to reboot the device.

Syntax

In standalone mode:

reboot [ slot slot-number ] [ force ]

In IRF mode:

reboot [ chassis chassis-number [ slot slot-number ] ] [ force ]

Views

User view

Predefined user roles

network-admin

context-admin

Parameters

chassis chassis-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. (In IRF mode.)

slot slot-number: Specifies a card by its slot number. If you do not specify a card, the command reboots the IRF member device. (In IRF mode.)

slot slot-number: Specifies a card by its slot number. If you do not specify a card, the command reboots the entire device. (In standalone mode.)

cpu cpu-number: Specifies a CPU by its number. If you do not specify this option or the subslot subslot-number option, the command reboots the specified slot.

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

Usage guidelines

CAUTION:

· A reboot might interrupt network services.

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

‌

Non-default vSystems do not support this command.

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.

In standalone mode:

If the device does not have a standby MPU, rebooting the active MPU reboots the entire device. If the device has a standby MPU and the standby MPU is operating correctly, rebooting the active MPU triggers a switchover.

To ensure correct operation of the system and cards, do not trigger a switchover by rebooting the active MPU if the standby MPU is not in Stable state. To view the status of the standby MPU, execute the display system stable state command.

In IRF mode:

If the IRF fabric has only one MPU, rebooting the MPU reboots the entire IRF fabric. If the IRF fabric has a global standby MPU and the MPU is operating correctly, rebooting the global active MPU triggers a switchover.

To ensure correct operation of the IRF fabric and cards, do not trigger a switchover by rebooting the global active MPU if no global standby MPUs are in Stable state. To view the status of global standby MPUs, execute the display system stable state command.

Examples

# (In standalone mode.) Reboot the device. Save the running configuration at prompt.

<Sysname> reboot

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

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

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

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

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

Validating file. Please wait...

Configuration is saved to mainboard device successfully.

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

Now rebooting, please wait...

# Reboot the device immediately without performing software check.

<Sysname> reboot force

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

Now rebooting, please wait...

Related commands

display system stable state

reset-health-value

Use reset-health-value to reset the health status of a card after occurrence of a specific error.

Syntax

In standalone mode:

reset-health-value { chip-error | fmea-blade | fmea-port | hg-packet-drop | hg-packet-loss | hg-packet-tamper | hg-port-down | parity-error | port-drop } slot slot-number [ cpu cpu-number ]

In IRF mode:

reset-health-value { chip-error | fmea-blade | fmea-port | hg-packet-drop | hg-packet-loss | hg-packet-tamper | hg-port-down | parity-error | port-drop } chassis chassis-number slot slot-number [ cpu cpu-number ]

Views

System view

Predefined user roles

network-admin

Parameters

chip-error: Specifies the chip error.

fmea-blade: Specifies the security engine error.

fmea-port: Specifies the port connection error between interface switch modules and subcards.

port-drop: Specifies the packet loss error.

hg-packet-drop: Specifies the HGMonitor detection packet drop error.

hg-packet-loss: Specifies the port hardware FCS packet error and RERPKT hardware drop error.

hg-packet-tamper: Specifies the detection packet tampering error.

hg-port-down: Specifies the inline port down error.

parity-error: Specifies the parity error.

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

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

Usage guidelines

After this command is executed, the card recovers from the specified error and is reset to the Normal(0) state.

Examples

# Reset the health status of a card when an inline port down error occurs.

<Sysname> system-view

[Sysname] reset-health-value hg-port-down chassis 1 slot 1

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

Non-default vSystems do not support this command.

Examples

# Clear job execution log information.

<Sysname> reset scheduler logfile

Related commands

display scheduler logfile

reset version-update-record

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

Syntax

reset version-update-record

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

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

This command is supported only on the default context.

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

This command is supported only on the default context.

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

Examples

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

<Sysname> system-view

[Sysname] resource-monitor output syslog

Related commands

resource-monitor minor resend enable

resource-monitor resource

Use resource-monitor resource to set resource depletion thresholds.

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

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

Views

System view

Predefined user roles

network-admin

Parameters

resource-name: Specifies a resource type by its name. The values for this argument are case insensitive and cannot be abbreviated.

Table 25 Resource types that can be monitored

Resource type	Description
mqcin	Inbound MQC resources.
openflow	OpenFlow resources.

‌

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

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

by-percent: Specifies resource depletion thresholds in percentage.

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

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

Usage guidelines

This command is supported only on the default context.

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

Examples

# (In standalone mode.) Set the minor resource depletion threshold to 30% and the severe resource depletion threshold to 10% for OpenFlow resources on slot 1.

<Sysname> system-view

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

Related commands

display resource-monitor

resource-monitor minor resend enable

resource-monitor output

restore factory-default

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

Syntax

restore factory-default

Views

User view

Predefined user roles

network-admin

Usage guidelines

CAUTION:

This command restores the device to the factory default. Make sure you understand its impact on the live network before executing the command.

This command is supported only on the default context.

Non-default vSystems do not support this command.

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, and forcibly reboot the system. Continue [Y/N]:y

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

The system is rebooting...

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

context-admin

Parameters

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

Usage guidelines

Non-default vSystems do not support this command.

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

context-admin

Parameters

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

Usage guidelines

Non-default vSystems do not support this command.

The job execution log file stores 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

context-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 reboots the device at the specified time and interrupts network services. Make sure you understand its impact on the live network before executing the command.

‌

Non-default vSystems do not support this command.

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

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

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

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

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

Examples

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

<Sysname> scheduler reboot at 12:00

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

Related commands

scheduler reboot delay

Use scheduler reboot delay to specify the reboot delay time.

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot delay time

undo scheduler reboot

Default

No reboot delay time is specified.

Views

User view

Predefined user roles

network-admin

context-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 reboots the device after the specified delay time and interrupts network services. Make sure you understand its impact on the live network before executing the command.

‌

Non-default vSystems do not support this command.

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

context-admin

Parameters

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

Usage guidelines

Non-default vSystems do not support this command.

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

context-admin

Parameters

interval: Specifies the port status detection timer value in seconds. The value range is 0 to 300. If the value is 0, the system does not detect the port status automatically, and you need to execute the undo shutdown command to restore the port status.

Usage guidelines

Non-default vSystems do not support this command.

On a network enabled with loop detection or STP, the device starts a port status detection timer when a port is shut down by a protocol. Once the timer expires, the system restores its 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

context-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.

Usage guidelines

Non-default vSystems do not support this command.

Examples

# Set the system ID of the device to position-hall.

<Sysname> system-view

[Sysname] sysid positon-hall

stack load-sharing fabric-slot-based

Use stack load-sharing fabric-slot-based to enable a switching fabric module to distribute traffic from a non-IRF interface module to multiple IRF interface modules.

Use undo stack load-sharing fabric-slot-based to restore the default.

Syntax

stack load-sharing fabric-slot-based chassis chassis-number slot slot-number

undo stack load-sharing fabric-slot-based chassis chassis-number slot slot-number

Default

A switching fabric module can distribute traffic from a non-IRF interface module to only one IRF interface module.

Views

System view

Predefined user roles

network-admin

Parameters

chassis chassis-number slot slot-number: Specifies a switching fabric module on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the switching fabric module.

Usage guidelines

This command takes effect only in IRF mode.

The term "IRF interface modules" refers to interface modules that have IRF physical interfaces. The term "non-IRF interface modules" refers to interface modules that do not have IRF physical interfaces.

By default, traffic from a non-IRF interface module can be forwarded to multiple switching fabric modules. However, the switching fabric modules forward the traffic to only one IRF interface module. After you execute this command for switching fabric modules, the switching fabric modules can forward the traffic to multiple IRF interface modules to implement load balancing.

Examples

# Enable a switching fabric module to distribute traffic from a non-IRF interface module to multiple IRF interface modules.

<Sysname> system-view

[Sysname] stack load-sharing fabric-slot-based chassis 1 slot 6

stack port split

Use stack port split to enable IRF physical interface splitting.

Use undo stack port split to restore the default.

Syntax

stack port split chassis chassis-number slot slot-number

undo stack port split chassis chassis-number slot slot-number

Default

IRF physical interface splitting is disabled.

Views

System view

Predefined user roles

network-admin

Parameters

Usage guidelines

Use this command in scenarios where an interface module has multiple types of IRF physical interfaces. You can enable IRF physical interface splitting on the interface module to improve the usage of high-speed physical interfaces.

Examples

# Enable IRF physical interface splitting.

<Sysname> system-view

[Sysname] stack port split chassis 1 slot 4

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

context-admin

Parameters

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

Usage guidelines

Non-default vSystems do not support this command.

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

Examples

# Set the name of the device to R2000.

<Sysname> system-view

[Sysname] sysname R2000

[R2000]

temperature-limit

Use temperature-limit to set the temperature alarm thresholds.

Use undo temperature-limit to restore the default.

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

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

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID. (In IRF mode.)

slot slot-number: Specifies a card by its slot number.

hotspot: Configures temperature alarm thresholds for hotspot sensors. A hotspot sensor is typically near the chip that generates a great amount of heat and used to monitor the chip.

inflow: Configures temperature alarm thresholds for inlet sensors. An inlet sensor is near the air inlet and used for monitoring ambient temperature.

outflow: Configures temperature alarm thresholds for outlet sensors. An outlet sensor is near the air outlet for monitoring device temperature.

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

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

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

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

Usage guidelines

This command is supported only on the default context.

Non-default vSystems do not support this command.

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

# (In standalone mode.) 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

context-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

Non-default vSystems do not support this command.

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

context-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

Non-default vSystems do not support this command.

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

context-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

Non-default vSystems do not support this command.

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

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

context-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, context-admin, context-operator, and level-0 to level-15.

Usage guidelines

Non-default vSystems do not support this command.

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

01-Fundamentals Command Reference

display copyright

display device manuinfo chassis-only

display fan

display memory

display resource-monitor

display scheduler job

display system stable state

display version-update-record

job

memory-threshold usage

monitor cpu-usage interval

monitor resource-usage { bridge-aggregation | route-aggregation } threshold

resource-monitor resource

restore factory-default

scheduler reboot at

stack load-sharing fabric-slot-based

sysname

temperature-limit

time once

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us