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

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

Usage guidelines

This command is supported only on the default MDC.

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

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

Examples

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

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

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

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

Related commands

clock protocol

clock summer-time

clock timezone

display clock

clock protocol

Use clock protocol to specify the system time source.

Use undo clock protocol to restore the default.

Syntax

clock protocol { none | { ntp | ptp } mdc mdc-id }

undo clock protocol

Default

The device obtains the UTC time from an NTP time source specified on the default MDC.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

mdc mdc-id: Specifies the MDC to be used for time synchronization. The value range is 1 to 9.

Usage guidelines

This command is supported only on the default MDC.

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

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

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

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

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

All MDCs on the device use the same system time. After obtaining the system time from an MDC, the device automatically synchronizes the system time to the other MDCs.

Examples

# Configure the device to use the local 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 MDC.

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

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

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

Examples

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

<Sysname> system-view

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

Related commands

clock datetime

clock timezone

display clock

clock timezone

Use clock timezone to set the time zone.

Use undo clock timezone to restore the default.

Syntax

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

undo clock timezone

Default

The UTC time zone is used.

Views

System view

Predefined user roles

network-admin

Parameters

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

add: Adds an offset to the UTC time.

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] clock timezone Z5 add 5

Related commands

clock datetime

clock summer-time

display clock

command

Use command to assign a command to a job.

Use undo command to revoke a command.

Syntax

command id command

undo command id

Default

No command is assigned to a job.

Views

Job view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] scheduler job backupconfig

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

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

<Sysname> system-view

[Sysname] scheduler job shutdownGE

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

[Sysname-job-shutdownGE] command 2 interface hundredgige 3/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

mdc-admin

Examples

# Enable copyright statement display.

<Sysname> system-view

[Sysname] copyright-info enable

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

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

* 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 ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Usage guidelines

This command is supported only on the default MDC.

Examples

# (In standalone mode.) Display alarm information.

<Sysname> display alarm

Slot CPU Level Info

1 0 ERROR faulty

Table 1 Command output

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

‌

display asset-info

Use display asset-info to display the asset profile for a physical component.

Syntax

In standalone mode:

display asset-info { chassis | fan fan-id | power power-id | slot slot-number } [ csn | custom| department | description | location | service-date | state ]

In IRF mode:

display asset-info chassis chassis-number { chassis | fan fan-id | power power-id | slot slot-number } [ csn | custom| department | description | location | service-date | state ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

chassis: Displays the asset profile for the frame.

fan fan-id: Displays the asset profile for the specified fan tray. The value range for the fan-id argument is 0 to 14.

power power-id: Displays the asset profile for the specified power module. The value range for the power-id argument is 0 to 16.

slot slot-number: Displays the asset profile for the card in the specified slot.

csn: Displays the asset ID for the asset.

custom: Displays the customized asset items.

department: Displays the department name.

description: Displays the asset description.

location: Displays the asset location.

service-date: Displays the service start date.

state: Displays the asset usage status.

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

Usage guidelines

To display an item in an asset profile, specify the corresponding keyword for the command. To display all items in an asset profile, do not specify the item keywords.

If an item is not configured, the system displays an empty field.

If you specify a fan tray or power module that does not exist, the system prompts that the fan tray or power module is absent.

Examples

# (In standalone mode.) Display the asset ID for fan tray 1.

<Sysname> system-view

[Sysname] display asset-info fan 1 csn

Type : Fan 1

csn : 123456

# (In standalone mode.) Display the asset information for fan tray 1.

<Sysname> system-view

[Sysname] display asset-info fan 1

Type : Fan 1

csn : 123456

description : FAN 1

location :

service-date:

department : MKT

state : Normal

custom : 1:789

Related commands

reset asset-info

set asset-info

display clock

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

Syntax

display clock

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

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

<Sysname> display clock

10:09:00.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

mdc-admin

mdc-operator

Examples

# Display the copyright statement.

<Sysname> display copyright

...

display cpu-usage

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

Syntax

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

mdc-admin

mdc-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: Specifies a CPU core by its number.

core all: Specifies all CPU cores.

Usage guidelines

Executing this command on an MDC displays the current CPU usage statistics for the MDC.

Examples

# (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 or CPU core usage during the most recent 5-second interval.
y% in last 1 minute Last 1 min	Average CPU or CPU core usage during the most recent 1-minute interval.
z% in last 5 minutes Last 5 min	Average CPU or CPU core usage during the most recent 5-minute interval.

‌

display cpu-usage configuration

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

Syntax

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

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

Usage guidelines

Executing this command on an MDC displays CPU usage monitoring settings for the MDC.

Examples

# Display the CPU usage monitoring settings.

<Sysname> display cpu-usage configuration

CPU usage monitor is enabled.

Current monitor interval is 60 seconds.

Current severe alarm threshold is 90%.

Current minor alarm threshold is 80%.

Current recovery-threshold is 40%.

Table 3 Command output

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

‌

Related commands

monitor cpu-usage enable

monitor cpu-usage interval

monitor cpu-usage threshold

display cpu-usage history

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

Syntax

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

mdc-admin

mdc-operator

Parameters

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

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 an MDC displays the historical CPU usage statistics for the MDC.

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 device

Use display device to display device information.

Syntax

In standalone mode:

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

In IRF mode:

display device[ flash ] [ chassis chassis-number [ slot slot-number ] | verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

flash: Displays flash memory information.

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.

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

Usage guidelines

If you do not specify the flash keyword, this command displays information about cards.

This command displays information about the physical device, whether you execute it on the default MDC or a non-default MDC.

Examples

# (In standalone mode.) Display device information.

<Sysname> display device

Slot Type State Subslot Soft Ver Patch Ver

0 LSXM2SUPT2 Master 0 S12500G-AF-759202 None

1 NONE Absent 0 NONE None

2 LSXM1TGS48C4TD2 Normal 0 S12500G-AF-759202 None

3 NONE Absent 0 NONE None

4 NONE Absent 0 NONE None

5 NONE Absent 0 NONE None

6 NONE Absent 0 NONE None

7 NONE Absent 0 NONE None

8 NONE Absent 0 NONE None

9 NONE Absent 0 NONE None

10 LSXM2SFT08E1 Normal 0 S12500G-AF-759202 None

11 NONE Absent 0 NONE None

12 NONE Absent 0 NONE None

13 NONE Absent 0 NONE None

14 NONE Absent 0 NONE None

15 NONE Absent 0 NONE None

Table 4 Command output

Field	Description
Type	Hardware type of the card.
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 card and is operating correctly. · Offline—The card is a switching fabric module and is isolated.
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 "Upgrading software."

‌

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 ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

chassis chassis-number: Specifies 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.

Usage guidelines

This command is supported only on the default MDC.

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

Examples

# Display electronic label information for the device.

<Sysname> display device manuinfo

...

display device manuinfo 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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-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 MDC.

Examples

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

<Sysname> display device manuinfo chassis-only

...

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

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

Examples

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

<Sysname> display device manuinfo fan 1

...

display device manuinfo power

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

Syntax

In standalone mode:

display device manuinfo power power-id

In IRF mode:

display device manuinfo chassis chassis-number power power-id

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

Usage guidelines

This command is supported only on the default MDC.

Examples

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

<Sysname> display device manuinfo power 1

...

display device uptime

Use display device uptime to display information about card uptime since the latest startup.

Syntax

display device uptime

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# (In standalone mode.) Display information about card uptime since the latest startup.

<Sysname> display device uptime

Slot No. Brd Type Brd Status Subslot UP time(DD:HH:MM)

0 LSUM1SUPXD0 Master 0 0000:03:03

1 LSUM1SUPXD0 Standby 0 0000:01:05

2 LSUM1TGS24EC0 Normal 0 0000:01:43

3 NONE Absent 0 None

4 NONE Absent 0 None

# (In IRF mode.) Display information about card uptime since the latest startup.

<Sysname> display device uptime

Slot Type State Subslot UP time(DD:HH:MM)

1/0 LSUM1SUPXD0 Master 0 0000:01:43

1/1 NONE Standby 0 None

1/2 LSUM2GT24PTSSE0 Normal 0 0000:01:41

1/3 NONE Absent 0 None

1/4 NONE Absent 0 None

1/5 NONE Absent 0 None

1/6 NONE Absent 0 None

1/7 NONE Absent 0 None

display diagnostic-information

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

hardware: Specifies hardware-related operating information.

infrastructure: Specifies operating information for the fundamental features.

l2: Specifies operating information for the Layer 2 features.

l3: Specifies operating information for the Layer 3 features.

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

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

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

Usage guidelines

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

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

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

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

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

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

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

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

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

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

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

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

mdc-admin

mdc-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 MDC.

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 inflow 1 26 0 48 60 NA

1 hotspot 1 34 0 80 95 NA

1 hotspot 2 33 0 62 76 NA

1 hotspot 3 45 0 75 88 NA

3 hotspot 1 37 0 80 97 110

3 hotspot 2 45 0 80 97 110

7 hotspot 1 39 0 68 80 NA

7 hotspot 2 54 0 88 100 110

Table 5 Command output

Field	Description
System Temperature information (degree centigrade)	Temperature information (°C).
sensor	Temperature sensor: · hotspot—Hotspot sensor. · inflow—Air inlet sensor. · outflow—Air outlet sensor.
Slot	Sensor position.
Temperature	Current temperature.
Lower	Lower temperature limit. If the device does not support this field, this field displays NA.
Warning	Warning temperature threshold. If the device does not support this field, this field displays NA.
Alarm	Alarming temperature threshold. If the device does not support this field, this field displays NA.
Shutdown	Shutdown temperature threshold. When the following conditions are met, the system shuts down automatically: · A fan has failed or is absent. · The sensor temperature is greater than this threshold for over 10 seconds. If the device does not support this field, this field displays NA.

‌

display environment history

Use display environment history to display historical temperature information in a coordinate system.

Syntax

In standalone mode:

display environment history slot slot-number { 30days | day | hour } [ { hotspot | inflow | outflow } sensor-number ]

In IRF mode:

display environment history chassis chassis-number slot slot-number { 30days | day | hour } [ { hotspot | inflow | outflow } sensor-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.

30days: Displays the historical temperature information during the past 30 days.

day: Displays the historical temperature information during the past 24 hours.

hour: Displays the historical temperature information during the past 60 minutes.

hotspot: Displays the historical temperature information of the hotspot sensors. A hotspot sensor is typically located near a high-heat chip to monitor the chip temperature.

inflow: Displays the historical temperature information of the inflow sensors. An inflow sensor is located near an air inlet to monitor the ambient temperature. Support for this keyword depends on the device model.

outflow: Displays the historical temperature information of the outflow sensors. An outflow sensor is located near an air outlet to monitor the device temperature. Support for this keyword depends on the device model.

sensor-number: Specifies a sensor by its number. 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 MDC.

The device periodically takes temperature readings from sensors and buffers the readings. When you execute this command, the device calculates and displays the most recent average temperature values as follows:

· For historical temperature information during the past 60 minutes, the device calculates the average temperature value during every 1-minute interval.

· For historical temperature information during the past 24 hours, the device calculates the average temperature value during every 1-hour interval.

· For historical temperature information during the past 30 days, the device calculates the average temperature value during every 1-day interval.

This command displays temperature values in a coordinate system.

· The vertical axis represents the temperature in degrees centigrade.

¡ If a value is not a multiple of the 5-degree step, it is rounded up or down to the closest multiple of the step. For example, value 23 is rounded up to 25, and value 22 is rounded down to 20.

¡ The default value range for the vertical axis is 0 to 100. If a temperature value is higher than 100 °C or lower than 0°C, the value range automatically expands.

· The horizontal axis represents the time. The unit varies by the specified time keyword.

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

If you do not a sensor for the command, the command displays the historical temperature information of all sensors on the specified component.

Examples

# (In standalone mode.) Display the historical temperature information of hotspot sensor 1 on a slot during the past 24 hours.

<Sysname> display environment history slot 1 day hotspot 1

Temperature readings of hotspot sensor 1 (in slot 1) during the past 24 hours:

Highest temperature is 27 degrees centigrade.

Lowest temperature is 25 degrees centigrade.

Temperature (degrades centigrade)

100|

95|

90|

85|

80|

75|

70|

65|

60|

55|

50|

45|

40|

35|

30|

25| # # # # # # # # # # # # # # # # # # # # # # # #

20| # # # # # # # # # # # # # # # # # # # # # # # #

15| # # # # # # # # # # # # # # # # # # # # # # # #

10| # # # # # # # # # # # # # # # # # # # # # # # #

5| # # # # # # # # # # # # # # # # # # # # # # # #

0| # # # # # # # # # # # # # # # # # # # # # # # #

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

6 12 18 24 (hours)

# (In IRF mode.) Display the historical temperature information of outflow sensor 1 on a slot during the past 30 days.

<Sysname> display environment history chassis 0 slot 1 30days outflow 2

Temperature readings of outflow sensor 2 (in chassis 1 slot 1) during the past 30 days:

Highest temperature is 27 degrees centigrade.

Lowest temperature is 25 degrees centigrade.

Temperature (degrades centigrade)

100|

95|

90|

85|

80|

75|

70|

65|

60|

55|

50|

45|

40|

35|

30|

25| # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

20| # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

15| # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

10| # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

5| # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

0| # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

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

10 20 30 (days)

Related commands

display environment

temperature-limit

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

mdc-admin

mdc-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 MDC.

Examples

# Display the operating states of all fan trays.

<Sysname> display fan

Fan Frame 0 State: Normal

Table 6 Command output

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

Field

Description

Fan Frame

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.

‌

display hardware-failure-detection

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

Syntax

display hardware-failure-detection

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

In standalone mode, the fix records are stored on the active MPU. You can use the display hardware-failure-detection command to display the records for a card even if the card is removed or replaced. The fix records are lost only when you remove or power cycle the active MPU.

In IRF mode, the fix records are stored on the local active MPU. You can use the display hardware-failure-detection command to display the records for a card even if the card is removed or replaced. The fix records are lost only when you remove or power cycle the local active MPU.

This command is supported only on the default MDC.

Examples

# (In standalone mode.) Display hardware failure detection settings and fix records.

<Sysname> display hardware-failure-detection

Current level:

chip : isolate

board : isolate

forwarding : warning

Recent record:

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

There is no record.

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

There is no record.

Table 7 Command output

Field	Description
Current level	Fix actions specified for hardware failures.
chip	Fix action for hardware failures on components of cards.
board	Fix action for hardware failures on control paths.
forwarding	Fix action for hardware failures on the forwarding plane.
Recent record	Recent failure fix records.
xxx executed records	Fix records stored on an MPU.
xxx trapped records	Trap records stored on an MPU.

‌

display hardware-failure-protection

Use display hardware-failure-protection to display the hardware failure protection settings.

Syntax

display hardware-failure-protection [ aggregation | port { auto-down | interface-type interface-number } ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

aggregation: Displays the hardware failure protection settings for aggregation groups.

port: Displays the hardware failure protection settings for interfaces.

auto-down: Displays the interfaces on which hardware failure protection is enabled.

interface-type interface-number: Displays the hardware failure protection settings for an interface.

Usage guidelines

If you do not specify any options, the command displays all hardware failure protection settings on the device.

To display the hardware failure protection settings for Ethernet interfaces that have been assigned to a non-default MDC, you must log in to the MDC first.

Examples

# Display all hardware failure protection settings.

<Sysname> display hardware-failure-protection

Aggregation: on

Port: HGE3/0/1 HGE3/0/2

# Display the interfaces on which hardware failure protection is enabled.

<Sysname> display hardware-failure-protection port auto-down

Port: HGE3/0/1 HGE3/0/2

# Display whether hardware failure protection is enabled for interface HundredGigE 3/0/2.

<Sysname> display hardware-failure-protection port HundredGigE 3/0/2

Auto-down is NOT allowed while hardware-failure happened.

Table 8 Command output

Field	Description
Aggregation	Whether hardware failure protection is enabled for aggregation groups.
Port	Interfaces on which hardware failure protection is enabled.

‌

display hardware-resource tcam

Use display hardware-resource tcam to display operating mode information about ternary content addressable memory resources (TCAM).

Syntax

display hardware-resource [ tcam ]

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

This command is supported only on the default MDC.

If you do not specify the tcam keyword, the command displays operating mode information about all hardware resources.

Examples

# Display TCAM hardware resource mode information.

<Sysname> display hardware-resource tcam

Tcam resource(tcam), all supported modes:

NORMAL The normal mode

MAC The mac mode

ROUTING The routing mode

ARP The arp mode

DUAL-STACK The dual-stack mode

MIX The mix bridging routing mode

ENHANCE-IPV6 The enhance ipv6 mode

ENHANCE-ARPND The enhance arpnd mode

ACL The acl mode

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

Default Current Next

NORMAL NORMAL NORMAL

Table 9 Command output

Field	Description
Tcam resource(tcam), all supported modes	Supported modes of TCAM: · ACL—ACL mode. · ARP—ARP mode. · DUAL-STACK—Dual-stack mode. · ENHANCE-IPV6—Enhanced IPv6 mode. · ENHANCE-ARPND—Enhanced ARP/ND mode. · MAC—MAC mode. · MIX—Extended mixed mode. · NORMAL—Normal mode. · ROUTING—Routing mode.
Default	Default operating mode.
Current	Current operating mode.
Next	Operating mode for the next startup.

‌

Related commands

hardware-resource tcam

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

mdc-admin

mdc-operator

Parameters

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

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 an MDC displays memory usage information for the MDC.

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

LowMem: 739824 375552 364272 -- -- -- 49.2%

HighMem: 244736 80576 164160 -- -- -- 67.1%

# (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%

Low memory statistics are measured in KB:

Slot CPU Total Used Free Buffers Caches FreeRatio

1 0 739824 375552 364272 -- -- 49.2%

High memory statistics are measured in KB:

Slot CPU Total Used Free Buffers Caches FreeRatio

1 0 244736 80576 164160 -- -- 67.1%

Table 10 Command output

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

‌

display memory-threshold

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

Syntax

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

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

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

Examples

# Display memory alarm thresholds and statistics.

<Sysname> display memory-threshold

Memory usage threshold: 100%

Free-memory thresholds:

Minor: 96M

Severe: 64M

Critical: 48M

Normal: 128M

Early-warning: 256M

Secure: 304M

Current free-memory state: Normal (secure)

Free-memory event statistics:

[Back to secure state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Entered early-warning state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to normal state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Entered minor alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to minor alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Entered severe alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to severe alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Entered critical alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

display power

Use display power to display power supply information.

Syntax

In standalone mode:

display power [ power-id | verbose ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays power supply information for all member devices. (In IRF mode.)

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

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

This command is supported only on the default MDC.

Examples

# Display brief power supply information.

<Sysname> display power

Input Power: 317.0 W

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

1 Normal AC -- -- -- --

2 Absent -- -- -- -- --

Table 11 Command output

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

‌

# (In standalone mode.) Display detailed power supply information.

<Sysname> display power verbose

System power information:

Power modules installed: 1

Power modules usable: 1

Rated power: 1400 W

Usable power: 1370 W

Used power: 317.0 W

Redundant power: 0 W

Total DC output : -- A

PowerID State InVoltage(V) InPower(W) OutVoltage(V) OutCurrent(A) OutPower(W)

1 Normal -- -- -- -- --

2 Absent -- -- -- -- --

Power information by slot:

Slot Type Current(A) Power(W) Status

0 None -- -- Absent

1 None -- 60.0 Absent

Table 12 Command output

Field	Description
Power modules installed	Number of power supplies installed on the device.
Power modules usable	Number of available power supplies.
Rated power	Total rated power of power supplies that are in Normal state, in watts.
Usable power	Total available power of power supplies that are in Normal state, in watts.
Used power	Total used power, in watts.
Redundant power	Redundant power, in watts.
Total DC output	Total output current of all power supplies, in amperes.
PowerID	Power supply ID.
State	Power supply status: · Absent—The slot is not installed with a power supply. · Fault—The power supply is faulty. · Normal—The power supply is operating correctly.
InVoltage(V)	Input voltage of the power supply, in volts.
InPower(W)	Input power of the power supply, in watts.
OutVoltage(V)	Output voltage of the power supply, in volts.
OutCurrent(A)	Output current of the power supply, in amperes.
OutPower(W)	Output power of the power supply, in watts.
Power information by slot	Power supply usage information for slots.
Type	Card type.
Current(A)	Input current of the card, in amperes. If this field is not supported, two hyphens (--) are displayed.
Power(W)	Rated power of the card, in watts. If this field is not supported, two hyphens (--) are displayed.
Status	Status of the card: · Absent—The slot is not installed with a card. · Fault—The card is faulty. · Normal—The card is operating correctly.

‌

display power history

Use display power-supply to display the historical power consumption information in a coordinate system.

Syntax

In standalone mode:

display power history { 30days | day | hour }

In IRF mode:

display power history { 30days | day | hour } [ chassis chassis-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

30days: Displays the historical power consumption information during the past 30 days.

day: Displays the historical power consumption information during the past 24 hours.

hour: Displays the historical power consumption information during the past 60 minutes.

chassis chassis-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays the historical power consumption information of all member devices. (In IRF mode.)

Usage guidelines

This command is supported only on the default MDC.

The device periodically samples the power consumption and buffers the samples. When you execute this command, the device calculates and displays the most recent average power consumption values as follows:

· For the power consumption information during the past 60 minutes, the device calculates the average power consumption value during every 1-minute interval.

· For the power consumption information during the past 24 hours, the device calculates the average power consumption value during every 1-hour interval.

· For the power consumption information during the past 30 days, the device calculates the average temperature value during every 1-day interval.

This command displays power consumption values in a coordinate system.

· The vertical axis represents the power consumption in watts (W).

If a value is not a multiple of the 5-watt step, it is rounded up or down to the closest multiple of the step.

· The horizontal axis represents the time. The unit varies by the specified time keyword.

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

Examples

# (In standalone mode.) Display the historical power consumption information.

<Sysname> display power history hour

Power consumption during the past 60 minutes:

Highest power consumption is 163W.

Lowest power consumption is 82W.

Consumption (W)

180|

175|

170|

165|####

160|####

155|####

150|####

145|####

140|####

135|####

130|####

125|####

120|####

115|####

110|####

105|####

100|####

95|####

90|####

85|####

80|####

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

10 20 30 40 50 60 (minutes)

Related commands

display power

display power-supply

Use display power-supply to display power supply management information.

Syntax

In standalone mode:

display power-supply

In IRF mode:

display power-supply [ 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 power supply management information for all member devices. (In IRF mode.)

Usage guidelines

This command is supported only on the default MDC.

Examples

# Display power supply management information.

<Sysname> display power-supply

Power supply policy: Disable

Power modules redundant (setting): 0

Board power supply information:

Slot Type Priority Status

0 LSUM2GT24TSSE0 5 Powered On

1 None 5 Absent

2 LSUM2GT48SE0 5 Powered On

3 None 5 Absent

4 None 5 Absent

5 None 5 Absent

6 None -- Reserved

7 LSUM1SUPXD0 -- Powered On

8 None -- Powered On

9 None -- Powered On

Table 13 Command output

Field	Description
Power supply policy	Status of the power supply management feature: · Disable—The feature is disabled. · Enable—The feature is enabled.
Power modules redundant (setting)	Number of redundant power supplies specified.
Slot	Slot number of the card.
Type	Card type.
Priority	Power supply priority for the card.
Status	Card status: · Powered On—The card is powered on. · Powered Off—The power is not enough for powering on the card. · Reserved—This slot is not installed with a card but the system has reserved power for this slot. · Off(manual)—The card has been powered off manually. · Off(Temp)—The card has been powered off because of high temperature. · Off(Isolated)—The card is isolated. · Absent—The slot is not installed with a card. · --—The command failed to obtain power information about the card.

‌

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

mdc-admin

mdc-operator

Parameters

resource resource-name: Specifies a resource type by its name. Table 27 shows the resource types that can be monitored.

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.

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 14 Command output

Field	Description
Minor alarms resending	Status of the minor resource depletion alarm resending feature, Enabled or 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

mdc-admin

mdc-operator

Parameters

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

Examples

# Display configuration information for all jobs.

<Sysname> display scheduler job

Job name: saveconfig

copy startup.cfg backup.cfg

Job name: backupconfig

Job name: 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

mdc-admin

mdc-operator

Examples

# Display job execution log information.

<Sysname> display scheduler logfile

Logfile Size: 1902 Bytes.

Job name : shutdown

Schedule name : shutdown

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

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

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

<Sysname>system-view

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

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

[Sysname-if-range]shutdown

Table 15 Command output

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

‌

Related commands

reset scheduler logfile

display scheduler reboot

Use display scheduler reboot to display the automatic reboot schedule.

Syntax

display scheduler reboot

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display the automatic reboot schedule.

<Sysname> display scheduler reboot

System will reboot at 16:32:00 05/23/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

mdc-admin

mdc-operator

Parameters

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

Examples

# Display information about all schedules.

<Sysname> display scheduler schedule

Schedule name : shutdown

Schedule type : Run once after 0 hours 2 minutes

Start time : Tue Dec 27 10:44:42 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 16 Command output

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

‌

display switch-mode status

Use display switch-mode status to display forwarding mode information about service module slots.

Syntax

In standalone mode:

display switch-mode status

In IRF mode:

display switch-mode status chassis chassis-number

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

# (In standalone mode.) Display forwarding mode information about all service module slots on the device.

<Sysname> display switch-mode status

CurrentFabricMode: normal

NextFabricMode: normal

Table 17 Command output

Field

Description

CurrentFabricMode

Current forwarding mode for service module slots:

· all-broadcast—All broadcast mode.

· normal—Normal mode.

NextFabricMode

Forwarding mode for service module slots to be used at the next startup:

· all-broadcast—All broadcast mode.

· normal—Normal mode.

‌

Related commands

fabric-mode

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

Upon an IRF fabric split, the system uses the health status information to determine the IRF fabrics to place in Recovery state.

Examples

# (In standalone mode.) Display system health status information.

<Sysname> display system health

Health: Faulty(3)

Memory: Normal(0)

Communication: Normal(0)

DBM monitor: Normal(0)

Chip jam: Normal(0)

CPU deadloop: Normal(0)

Forwarding channel: Normal(0)

HG: Normal(0)

External TCAM: Normal(0)

LSW CPU: Normal(0)

MMU: Normal(0)

LSW port: Normal(0)

Board status: Faulty(3)

Fan status: Normal(0)

Temperature: Normal(0)

# (In IRF mode.) Display system health status information.

<Sysname> display system health

Chassis 1 health: Normal(0)

Memory: Normal(0)

Communication: Normal(0)

DBM monitor: Normal(0)

Chip jam: Normal(0)

CPU deadloop: Normal(0)

Forwarding channel: Normal(0)

HG: Normal(0)

External TCAM: Normal(0)

LSW CPU: Normal(0)

MMU: Normal(0)

LSW port: Normal(0)

Board status: Normal(0)

Fan status: Normal(0)

Temperature: Normal(0)

Chassis 2 health: Normal(0)

Memory: Normal(0)

Communication: Normal(0)

DBM monitor: Normal(0)

Chip jam: Normal(0)

CPU deadloop: Normal(0)

Forwarding channel: Normal(0)

HG: Normal(0)

External TCAM: Normal(0)

LSW CPU: Normal(0)

MMU: Normal(0)

LSW port: Normal(0)

Board status: Normal(0)

Fan status: Normal(0)

Temperature: Normal(0)

Table 18 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 situation.
Memory	Memory health status.
Communication	Communication health status.
DBM monitor	DBM health status.
Chip jam	Chip jam status.
CPU deadloop	CPU deadloop status.
Forwarding channel	Health status of cross-card services on the device.
HG	HG health status.
External TCAM	External TCAM health status.
LSW CPU	LSW CPU health status.
MMU	MMU health status.
LSW port	LSW port health status.
Board status	Card health status.
Fan status	Fan health status.
Temperature	Temperature sensor health status.

‌

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)

Chip jam:

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 19 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 situation.
Chip jam: Faulty(1) 2019-10-10 18:00:00 on slot 1	Historical status change information of items. For more information about the supported items on the device, see Table 18. A maximum of 30 historical status change entries are supported for each item.

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

Chip jam:

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

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

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[ mdc { mdc-id | all } ] [ summary ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

mdc { mdc-id | all }: Specifies an MDC by its ID or specifies all MDCs. The value range is 1 to 9.

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

Usage guidelines

If you do not specify an MDC, this command displays stability information for the system.

Before performing an ISSU or a switchover, execute this command multiple times to identify whether the system is operating stably. If the value of the System State field is not Stable, you cannot perform an ISSU. If the value of the Redundancy Stable field is not Stable, you cannot perform a switchover.

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

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

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

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

Examples

# Display brief system stability and status information.

<Sysname> display system stable state summary

System state : Stable

Redundancy state : No redundance

NSR state : No standby

# (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 20 Command output

Field	Description
System state	Operating status of all cards: · Stable—All cards are operating stably. · Not ready—One or more cards are not operating stably. You cannot perform an ISSU.
Redundancy state	System redundancy status: · Stable—Both MPUs are operating stably. You can perform a switchover. · No redundance—The system has only one MPU. You cannot perform a switchover. · Not ready—The system is not operating stably. You cannot perform a switchover.
NSR state	NSR status of all cards: · Stable—NSR is operating correctly on all cards where it is enabled. · Not ready—NSR is not operating correctly on all cards where it is enabled. You cannot perform a process or MPU switchover or an ISSU. · No standby—The system has only one MPU. · Not configured—NSR is not enabled.
Role	Role of the card in the system: · Active—The card is the active MPU. · Standby—The card is the standby MPU. · Other—The card is a service card.
State	Operating status of the card: · Stable—The card is operating stably. · Board inserted—The card has just been installed. · Kernel initiating—Card kernel is being initialized. · Service starting—Services are starting. · Service stopping—Services are stopping. · HA Batch backup—An HA batch backup is going on. · Interface data batch backup—An interface data batch backup is in progress. · MDC starting—MDCs are starting. · MDC stopping—MDCs are stopping. · Automatic configuration—MDCs are being automatically configured. Support for this value depends on the device model.
*	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 system-working-mode

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

Syntax

display system-working-mode

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

This command is supported only on the default MDC.

Examples

# Display system working mode information.

<Sysname> display system-working-mode

The current system working mode is standard.

The system working mode for next startup is standard.

display transceiver alarm

Use display transceiver alarm to display transceiver alarms.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Usage guidelines

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

Table 21 Common transceiver alarm components

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

‌

Examples

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

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

HundredGigE3/0/1 transceiver current alarm information:

RX signal loss

RX power low

Table 22 Command output

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

‌

display transceiver diagnosis

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

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

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

HundredGigE3/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 23 Command output

Field	Description
transceiver diagnostic information	Digital diagnosis information for the transceiver module in the interface.
Wave.er(nm)	Wavelength offset in nm, accurate to 0.001 nm. This field is supported only on the SFP-XG-LH80-Tunable transceiver module.
Freq.er(GHz)	Frequency offset in GHz, accurate to 0.1 GHz. This field is supported only on the SFP-XG-LH80-Tunable transceiver module.
Temp.(°C)	Temperature in °C, accurate to 1°C.
Voltage(V)	Voltage in V, accurate to 0.01 V.
Bias(mA)	Bias current in mA, accurate to 0.01 mA.
RX power(dBm)	Receive power in dBm, accurate to 0.01 dBm.
TX power(dBm)	Transmit power in dBm, accurate to 0.01 dBm.

‌

display transceiver interface

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

Syntax

display transceiver interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

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

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

...

display transceiver itu-channel

Use display transceiver itu-channel to display ITU channel information for transceiver modules.

Syntax

display transceiver itu-channel interface [ interface-type interface-number [ supported-channel ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

supported channel: Specifies ITU channels supported on the interface. If this keyword is not specified, the command displays the ITU channel that is in use on the interface.

Usage guidelines

This command is supported only on the SFP-XG-LH80-Tunable transceiver module.

Examples

# Display ITU channels used by the transceiver module in Ten-GigabitEthernet 1/0/1.

<Sysname> display transceiver itu-channel interface ten-gigabitethernet 1/0/1

Interface Channel WaveLength(nm) Frequency(THz)

XGE1/0/1 1 1566.72 191.35

# Display ITU channels supported by the transceiver module in Ten-GigabitEthernet 1/0/1.

<Sysname> display transceiver itu-channel interface ten-gigabitethernet 1/0/1 supported-channel

ITU channel settings supported on Ten-GigabitEthernet1/0/1 :

Channel WaveLength(nm) Frequency(THz)

1 1566.72 191.35

2 1566.31 191.40

3 1565.90 191.45

4 1565.50 191.50

5 1565.09 191.55

6 1564.68 191.60

7 1564.27 191.65

8 1563.86 191.70

Omitted….

Table 24 Command output

Field	Description
WaveLength(nm)	Wavelength of the channel in nm, accurate to 0.01 nm. This field displays a hyphen (-) in the following situations: · No transceiver module is installed on the interface. · The transceiver module does not support specifying an ITU channel number. · The command failed to obtain the ITU channel information. · The device does not support the ITU channel number stored on the transceiver module.
Frequency(THz)	Frequency of the channel in THz, accurate to 0.01 THz. This field displays a hyphen (-) in the following situations: · No transceiver module is installed on the interface. · The transceiver module does not support specifying an ITU channel number. · The command failed to obtain the ITU channel information. · The device does not support the ITU channel number stored on the transceiver module.

Field

Description

WaveLength(nm)

Wavelength of the channel in nm, accurate to 0.01 nm. This field displays a hyphen (-) in the following situations:

· No transceiver module is installed on the interface.

· The transceiver module does not support specifying an ITU channel number.

· The command failed to obtain the ITU channel information.

· The device does not support the ITU channel number stored on the transceiver module.

Frequency(THz)

Frequency of the channel in THz, accurate to 0.01 THz. This field displays a hyphen (-) in the following situations:

· No transceiver module is installed on the interface.

· The transceiver module does not support specifying an ITU channel number.

· The command failed to obtain the ITU channel information.

· The device does not support the ITU channel number stored on the transceiver module.

‌

Related commands

itu-channel

display transceiver manuinfo

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

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

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

...

display version

Use display version to display system version information.

Syntax

display version

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display system version information.

<Sysname> display version

...

display version-update-record

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

Syntax

display version-update-record

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

This command is supported only on the default MDC.

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

Examples

# Display the startup software image upgrade records.

<Sysname> display version-update-record

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

*Name : simware-cmw710-boot.bin

Version : 7.1.070 Test 0001

Compile time: Mar 25 2015 15:52:43

*Name : simware-cmw710-system.bin

Version : 7.1.070 Test 0001

Compile time: Mar 25 2015 15:52:43

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

fabric load-sharing mode

Use fabric load-sharing mode to specify load sharing modes for a service card.

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

If the LSXM1SFT16F2 switching fabric module is installed, load sharing mode ingress-port is used for a service card. If the other switching fabric modules are installed, load sharing mode flexible is used for a service card.

Views

System view

Predefined user roles

network-admin

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

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

fabric-mode

Use fabric-mode to specify a forwarding mode for service module slots.

Use undo fabric-mode to restore the default.

Syntax

In standalone mode:

fabric-mode { all-broadcast | normal }

undo fabric-mode

In IRF mode:

fabric-mode { all-broadcast | normal } chassis chassis-number

undo fabric-mode chassis chassis-number

Default

Service module slots operate in normal mode.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

all-broadcast: Specifies the all broadcast mode. As a best practice, specify this mode if there is a large amount of broadcast, unknown unicast, known multicast, or unknown multicast traffic.

normal: Specifies the normal mode.

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

Usage guidelines

In different forwarding modes, service module slots support different card models and different amounts of bandwidth. For more information, see device management in Fundamentals Configuration Guide.

A forwarding mode change takes effect after a device reboot.

This command is supported only on the default MDC. For more information about MDC, see Virtual Technologies Configuration Guide.

Examples

# Set the forwarding mode for service module slots to normal.

<Sysname> system-view

[Sysname] fabric-mode normal

This command takes effect after a device reboot. Execute this command? [Y/N]:y

Process OK.

Related commands

display switch-mode status

reboot

forward-path-detection enable

Use forward-path-detection enable to enable data forwarding path failure detection.

Use undo forward-path-detection enable to disable data forwarding path failure detection.

Syntax

forward-path-detection enable

undo forward-path-detection enable

Default

Data forwarding path failure detection is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default MDC.

You can enable the device to automatically detect data forwarding path failures and output log information for notification.

Examples

# Enable data forwarding path failure detection.

<Sysname> system-view

[Sysname] forward-path-detection enable

hardware-failure-detection

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

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

Syntax

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

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

Default

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

Views

System view

Predefined user roles

network-admin

Parameters

board: Specifies failures on control paths.

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

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

isolate: Takes one or more of the following actions:

· Shuts down the relevant ports.

· Prohibits loading software for the relevant cards.

· Isolates the relevant cards.

· Powers off the relevant cards to reduce impact from the failures.

off: Takes no action.

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

warning: Sends traps to notify you of the failures.

Usage guidelines

This command is supported only on the default MDC.

The device automatically detects hardware failures on components, cards, and the forwarding plane. You can specify the actions to be taken in response to detected failures.

Examples

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

<Sysname> system-view

[Sysname] hardware-failure-detection chip warning

hardware-failure-protection aggregation

Use hardware-failure-protection aggregation to enable hardware failure protection for aggregation groups.

Use undo hardware-failure-protection aggregation to disable hardware failure protection for aggregation groups.

Syntax

hardware-failure-protection aggregation

undo hardware-failure-protection aggregation

Default

Hardware failure protection is disabled for aggregation groups.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command takes effect only when the hardware-failure-detection forwarding isolate command is configured.

When the hardware-failure-protection aggregation command is configured, the system uses the following rules when it detects a hardware failure on an aggregation group member interface:

· If the undo hardware-failure-protection auto-down command is configured on the member interface and the member interface is the only member in up state in the group, the system does not shut down the interface.

· If the undo hardware-failure-protection auto-down command is configured on the member interface and the member interface is not the only member in up state in the group, the system shuts down the interface.

· If the hardware-failure-protection auto-down command is configured on the member interface, the system shuts down the interface, whether or not the member interface is the only member in up state in the group.

This command does not take effect on a member interface in the following situations:

· Loopback testing is enabled (using the loopback { external | internal } command).

· The interface is forcibly brought up (using the port up-mode command).

· The interface is a physical IRF port.

· The undo hardware-failure-protection auto-down command is not configured on the interface.

This command is supported only on the default MDC.

Examples

# Enable hardware failure protection for aggregation groups.

<Sysname> system-view

[Sysname] hardware-failure-protection aggregation

Related commands

hardware-failure-detection

hardware-failure-protection auto-down

Use hardware-failure-protection auto-down to enable hardware failure protection for an interface.

Use undo hardware-failure-protection auto-down to disable hardware failure protection for an interface.

Syntax

hardware-failure-protection auto-down

undo hardware-failure-protection auto-down

Default

Hardware failure protection is enabled for an interface.

Views

Ethernet interface view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

To ensure service continuity, verify that the interface has a backup link before configuring this command.

After you enable hardware failure protection on an interface, the system automatically shuts down the interface when it detects a hardware failure on the interface. An interface shut down this way is in Protect Down state. After the failure on an interface is removed, bring the interface up by using the undo shutdown command.

This command takes effect only when the hardware-failure-detection forwarding isolate command is configured.

This command does not take effect on an interface in the following situations:

· Loopback testing is enabled (using the loopback { external | internal } command).

· The interface is forcibly brought up (using the port up-mode command).

· The interface is a physical IRF port.

Examples

# Enable hardware failure protection on interface HundredGigE 3/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 3/0/1

[Sysname-HundredGigE3/0/1] hardware-failure-protection auto-down

hardware-resource tcam

Use hardware-resource tcam to set the TCAM operating mode.

Use undo hardware-resource tcam to restore the default.

Syntax

hardware-resource tcam { acl | arp | dual-stack | enhance-arpnd | enhance-ipv6 | mac | mix | nat | normal | routing }

undo hardware-resource tcam

Default

The TCAM operating mode is normal.

Views

System view

Predefined user roles

network-admin

Parameters

acl: Specifies the ACL mode.

arp: Specifies the ARP mode.

dual-stack: Specifies the dual-stack mode.

enhance-ipv6: Specifies the enhanced IPv6 mode.

enhance-arpnd: Specifies the enhanced ARP/ND mode.

mac: Specifies the MAC mode.

mix: Specifies the extended mixed mode.

nat: Specifies the MC-NAT mode.

normal: Specifies the normal mode.

routing: Specifies the routing mode.

Usage guidelines

This command is supported only on the default MDC.

This command takes effect only for the TD cards.

For a TCAM operating mode change to take effect, perform the following tasks:

1. Save the running configuration to the next-startup configuration file.

2. Delete the .mdb binary file for the next-startup configuration file.

3. Reboot the device.

The ternary content addressable memory (TCAM) provides an extended memory space for the device to store ARP, ACL, and routing entries, or others. The TCAM operating mode determines the types of entries that the TCAM stores.

The S12516G-AF switch does not support setting the TCAM operating mode to enhance-ipv6 or enhance-arpnd.

When the VXLAN hardware resource mode is the Layer 2 gateway mode, the device does not support setting the TCAM operating mode to enhance-ipv6 or enhance-arpnd. For more information about VXLAN hardware resource modes, see VXLAN Configuration Guide.

Table 26 describes the feature highlights and application scenarios of the TCAM operating modes.

Table 26 TCAM operating modes and the feature highlights and application scenarios

TCAM operating mode	Feature highlights	Recommended application scenario
ACL mode	Increases the ACL capacity to provide large-scale exact ACL matching.	Access environment that requires abundant MQC and packet filter configurations.
ARP mode	Increases the capacity of host routes to provide host access performance.	Layer 3 gateways.
Dual-stack mode	Increases the capacities of the IPv4 routing table and IPv6 routing table to provide higher Layer 3 routing performance.	Both a large IPv4 routing table and a large IPv6 routing table are required.
Enhanced IPv6 mode	Increases the IPv6 routing table capacity to provide higher Layer 3 routing performance.	A large IPv6 routing table is required.
Enhanced ARP/ND mode	Increases the capacity of host routes to provide higher host access performance.	A large IPv4 routing table, a large IPv6 routing table, and many hosts are required.
MAC mode	Increases the MAC address table capacity to provide higher Layer 2 packet forwarding performance.	A large MAC address table is required.
Mixed mode	Increases the capacities of the MAC address table and routing tables to provide higher Layer 2 and Layer 3 packet forwarding performance.	Both a large MAC address table and large routing tables are required.
Normal mode	Uses only the default MAC address table and the default routing table.	No specific requirements.
Routing mode	Increases the IPv4 routing table capacity to provide higher Layer 3 routing performance.	A large IPv4 routing table is required.
MC-NAT mode	Supports the MC-NAT feature.	The MC-NAT feature is required.

‌

Examples

# Set the TCAM operating mode to routing.

<Sysname> system-view

[Sysname] hardware-resource tcam routing

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

The hardware resource working mode is changed, please save the configuration and reboot the system to make it effective.

Related commands

display hardware-resource

header

Use header to configure a banner.

Use undo header to delete a banner.

Syntax

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

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

Default

The device does not have banners.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

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

Examples

# Configure the legal banner.

<Sysname> system-view

[Sysname] header legal

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

Welcome to use the legal banner%

itu-channel

Use itu-channel to set the ITU channel number for a transceiver module.

Use undo itu-channel to restore the default.

Syntax

itu-channel channel-number

undo itu-channel

Default

The ITU channel number is 1.

Views

Ethernet interface view

Predefined user roles

network-admin

mdc-admin

Parameters

channel-number: Specifies the ITU channel number.

Usage guidelines

This command is supported only on the SFP-XG-LH80-Tunable transceiver module.

The ITU channel number is saved in a register on the transceiver module. It is not saved to the configuration file.

Examples

# Set the ITU channel number to 2 for the transceiver module in Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] itu-channel 2

Changing the channel number causes the service to be down for a while. Continue? [Y/N]:Y

Related commands

display transceiver itu-channel

job

Use job to assign a job to a schedule.

Use undo job to revoke a job.

Syntax

job job-name

undo job job-name

Default

No job is assigned to a schedule.

Views

Schedule view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

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

Examples

# Assign job save-job to schedule saveconfig.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] job save-job

Related commands

scheduler job

scheduler schedule

memory-threshold

Use memory-threshold to set free-memory thresholds.

Use undo memory-threshold to restore the defaults.

Syntax

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

Minor alarm threshold: 10 % of the total memory on the slot.

Severe alarm threshold: 7 % of the total memory on the slot.

Critical alarm threshold: 4 % of the total memory on the slot.

Normal state threshold: 13 % of the total memory on the slot.

Early-warning threshold: 16 % of the total memory on the slot.

Sufficient-memory threshold: 18 % of the total memory on the slot.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

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

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

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

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

slot slot-number: Specifies 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.

Usage guidelines

This command is supported only on the default MDC.

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

For slots that support low memory, the system monitors only the amount of free low-memory space. You can use the display memory command to display memory usage information. If the LowMem field is displayed for a slot, the slot supports low memory.

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

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

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

Examples

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

<Sysname> system-view

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

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

<Sysname> system-view

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

Related commands

display memory-threshold

memory-threshold usage

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

Use undo memory-threshold usage to restore the default.

Syntax

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 100%.

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

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

Examples

# Set the memory usage threshold to 80%.

<Sysname> system-view

[Sysname] memory-threshold usage 80

Related commands

display memory-threshold

monitor cpu-usage enable

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

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

Syntax

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

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

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

Examples

# Enable CPU usage monitoring.

<Sysname> system-view

[Sysname] monitor cpu-usage enable

Related commands

display cpu-usage configuration

display cpu-usage history

monitor cpu-usage interval

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

The system samples CPU usage every 1 minute.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

Examples

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

<Sysname> system-view

[Sysname] monitor cpu-usage interval 5Sec

Related commands

display cpu-usage configuration

display cpu-usage history

monitor cpu-usage enable

monitor cpu-usage logging interval

Use monitor cpu-usage logging interval to enable periodic CPU usage logging.

Use undo monitor cpu-usage logging interval to disable periodic CPU usage logging.

Syntax

monitor cpu-usage logging interval interval-time

undo monitor cpu-usage logging interval

Default

Periodic CPU usage logging is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

interval interval-time: Specifies the logging interval in seconds, a multiple of five in the range of 5 to 300.

Examples

# Enable periodic CPU usage logging and set the logging interval to 60 seconds.

<Sysname> system-view

[Sysname] monitor cpu-usage logging interval 60

monitor cpu-usage threshold

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

Severe CPU usage alarm threshold: 99%.

Minor CPU usage alarm threshold: 80%.

CPU usage recovery threshold: 60%.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

slot slot-number: Specifies 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

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

Examples

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

<Sysname> system-view

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

Related commands

display cpu-usage configuration

monitor handshake-timeout disable-port

Use monitor handshake-timeout disable-port to enable the port-down feature globally.

Use undo monitor handshake-timeout disable-port to disable the feature globally.

Syntax

monitor handshake-timeout disable-port

undo monitor handshake-timeout disable-port

Default

The port-down feature is enabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

The port-down feature applies to scenarios where two devices (one active and one standby) are used for high availability, for example, a network deployed with VRRP. This feature shuts down all service ports on the active device immediately after both MPUs on the active device are removed or reboot abnormally. The shutdown operation ensures quick service switchover to the standby device.

This feature takes effect only when no MPUs are available on the active device.

Examples

# Enable the port-down feature globally.

<Sysname> system-view

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

[Sysname] monitor handshake-timeout disable-port

Set successful!

monitor memory-usage logging interval

Use monitor memory-usage logging interval to enable periodic memory usage logging.

Use undo monitor memory-usage logging interval to disable periodic memory usage logging.

Syntax

monitor memory-usage logging interval interval-time

undo monitor memory-usage logging interval

Default

Periodic memory usage logging is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

interval interval-time: Specifies the logging interval in seconds, a multiple of five in the range of 5 to 300.

Examples

# Enable periodic memory usage logging and set the logging interval to 60 seconds.

<Sysname> system-view

[Sysname] monitor memory-usage logging interval 60

monitor resend cpu-usage

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

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

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command sets alarm resending intervals 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 alarm resending intervals for the global active MPU. (In IRF mode.)

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

Usage guidelines

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

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

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

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

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

Examples

# (In standalone mode.) Set the CPU usage minor alarm resending interval to 60 seconds for CPU 0 in slot 1.

<Sysname> system-view

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

monitor resend memory-threshold

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

Default

· Early warning resending interval: 1 hour.

· Minor alarm resending interval: 12 hours.

· Severe alarm resending interval: 3 hours.

· Critical alarm resending interval: 1 hour.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command sets alarm resending intervals 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 alarm resending intervals for the global active MPU. (In IRF mode.)

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

Usage guidelines

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

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

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

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

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

Examples

# (In standalone mode.) Set the minor memory depletion alarm resending interval to 12 hours for CPU 0 in slot 1.

<Sysname> system-view

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

password-recovery enable

Use password-recovery enable to enable password recovery capability.

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

Syntax

password-recovery enable

undo password-recovery enable

Default

Password recovery capability is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default MDC.

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

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

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

To enhance system security, disable password recovery capability.

(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 Fundamentals Configuration Guide. .

Examples

# Disable password recovery capability.

<Sysname> system-view

[Sysname] undo password-recovery enable

power-supply off

Use power-supply off to power off a card.

Syntax

In standalone mode:

power-supply off slot slot-number

In IRF mode:

power-supply off chassis chassis-number slot slot-number

Views

User view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

This command is supported only on the default MDC.

To use this command, you must enable power supply management first.

When power is insufficient, you can power off interface cards that are idle or connected to unimportant network nodes to ensure power supply to critical interface cards.

(In IRF mode.) Do not power off an interface card that contains IRF physical interfaces.

Examples

# (In standalone mode.) Power off a card.

<Sysname> power-supply off slot 2

Related commands

power-supply policy enable

power-supply on

Use power-supply on to power on a card or subcard.

Syntax

In standalone mode:

power-supply on slot slot-number

In IRF mode:

power-supply on chassis chassis-number slot slot-number

Views

User view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

This command is supported only on the default MDC.

To use this command, you must enable power supply management first.

Examples

# (In standalone mode.) Power on a card.

<Sysname> power-supply on slot 2

Related commands

power-supply policy enable

Use power-supply policy enable to enable power supply management.

Use undo power-supply policy enable to disable power supply management.

Syntax

In standalone mode:

power-supply policy enable

undo power-supply policy enable

In IRF mode:

power-supply policy chassis chassis-number enable

undo power-supply policy chassis chassis-number enable

Default

Power supply management is disabled.

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

This command is supported only on the default MDC.

Examples

# (In standalone mode.) Enable power supply management.

<Sysname> system-view

[Sysname] power-supply policy enable

power-supply policy priority

Use power-supply policy priority to specify a power supply priority for an interface card.

Use undo power-supply policy priority to restore the default.

Syntax

In standalone mode:

power-supply policy slot slot-number priority priority

undo power-supply policy slot slot-number priority

In IRF mode:

power-supply policy chassis chassis-number slot slot-number priority priority

undo power-supply policy chassis chassis-number slot slot-number priority

Default

The power supply priority is 5 for an interface card.

Views

System view

Predefined user roles

network-admin

Parameters

priority: Specifies the priority value. The value range is 0 to 10. A smaller priority value represents a higher priority.

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

chassis chassis-number slot slot-number: Specifies an interface 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. (In IRF mode.)

Usage guidelines

This command is supported only on the default MDC.

This command takes effect only if power supply management is enabled.

Specify smaller priority values for critical-service cards so they are preferentially powered.

The system automatically guarantees that an interface card that holds IRF physical interfaces receives a higher priority.

· After you bind interfaces on an interface card to IRF ports, the system automatically assigns the interface card a higher priority. You cannot use this command to change the power supply priority for the card anymore.

· If you specify a power supply priority for an interface card and then bind its interfaces to IRF ports, the priority setting is retained but does not take effect.

Examples

# (In standalone mode.) Set the power supply priority for a card to 10.

<Sysname> system-view

[Sysname] power-supply policy slot 2 priority 10

Related commands

power-supply policy enable

power-supply policy redundant

Use power-supply policy redundant to specify the number of redundant power supplies.

Use undo power-supply policy redundant to restore the default.

Syntax

In standalone mode:

power-supply policy redundant module-count

undo power-supply policy redundant

In IRF mode:

power-supply policy chassis chassis-number redundant module-count

undo power-supply policy chassis chassis-number redundant

Default

The number of redundant power supplies is 0.

Views

System view

Predefined user roles

network-admin

Parameters

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

module-count: Specifies the number of redundant power supplies. To view the value range for this argument, enter a question mark (?) in the place of this argument. The upper limit for the value range is the maximum number of redundant power supplies supported by the system. The actual number of redundant power supplies that you can specify varies by the number of the interface cards and their power consumption. The actual number is smaller than or equal to the maximum number.

Usage guidelines

This command is supported only on the default MDC.

This command takes effect only if power supply management is enabled.

Examples

# (In standalone mode.) Set the number of redundant power supplies to 1.

<Sysname> system-view

[Sysname] power-supply policy redundant 1

Related commands

power-supply policy 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

mdc-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.)

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

Usage guidelines

CAUTION:

· A reboot might interrupt network services.

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

‌

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

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

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 asset-info

Use reset asset-info to clear the asset profile for a physical component.

Syntax

In standalone mode:

reset asset-info { chassis | fan fan-id | power power-id | slot slot-number } [ csn | custom | department | description | location | service-date | state ]

In IRF mode:

reset asset-info chassis chassis-number { chassis | fan fan-id | power power-id | slot slot-number } [ csn | custom| department | description | location | service-date | state ]

Views

System view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

chassis: Clears the asset profile for the frame.

fan fan-id: Clears the asset profile of the specified fan tray. The value range for the fan-id argument is 0 to 14.

power power-id: Clears the asset profile for the specified power module. The value range for the power-id argument is 0 to 16.

slot slot-number: Clears the asset profile for the card in the specified slot.

csn: Clears the asset ID.

custom: Clears customized asset items.

department: Clears the department name.

description: Clears the asset description.

location: Clears the asset location.

service-date: Clears the service start date.

state: Clears the usage status

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

Usage guidelines

To clear an item in an asset profile, specify the corresponding keyword for the command. To clear all items in an asset profile, do not specify the item keywords.

If you specify a fan tray or power module that does not exist, the system prompts that the fan tray or power module is absent.

Examples

# (In standalone mode.) Clear the asset ID for fan tray 0.

<Sysname> system-view

[Sysname] reset asset-info fan 0 csn

Related commands

display asset-info

set asset-info

reset scheduler logfile

Use reset scheduler logfile to clear job execution log information.

Syntax

reset scheduler logfile

Views

User view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default MDC.

Examples

# Clear job execution log information.

<Sysname> reset scheduler logfile

Related commands

display scheduler logfile

reset version-update-record

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

Syntax

reset version-update-record

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default MDC.

Examples

# Clear the startup software image upgrade records.

<Sysname> system-view

[Sysname] reset version-update-record

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

Related commands

display version-update-record

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 feature is not supported when uRPF is configured on the device. For more information about uRPF, see Security Configuration Guide.

This feature is not supported when the arp mode uni command is configured on the device. For more information, see ARP configuration in Layer 3–IP Services Configuration Guide.

This feature is not supported when the ipv6 nd mode uni command is configured on the device. For more information, see IPv6 basics in Layer 3–IP Services Configuration Guide.

This feature is not supported on EC interface modules.

This feature is not supported on FD, FE, and SG interface modules when the service module operating mode is bridging or enhance-bridge.

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 feature is not supported when uRPF is configured on the device. For more information about uRPF, see Security Configuration Guide.

This feature is not supported when the arp mode uni command is configured on the device. For more information, see ARP configuration in Layer 3–IP Services Configuration Guide.

This feature is not supported when the ipv6 nd mode uni command is configured on the device. For more information, see IPv6 basics in Layer 3–IP Services Configuration Guide.

This feature is not supported on EC interface modules.

This feature is not supported on FD, FE, and SG interface modules when the service module operating mode is bridging or enhance-bridge.

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 27 shows the resource types that can be monitored.

Table 27 Resource types that can be monitored

Resource type	Description
ac	Ethernet service instances.
agg_group	Aggregation group resources.
arp	ARP resources.
ecmpgroup	ECMP group resources.
host	Host route resources.
ipmc	Layer 3 multicast replication table resources.
ipv6_127	Resources for IPv6 routes with a prefix length of 65 to 127 bits.
ipv6_128	Resources for IPv6 routes with a prefix length of 128 bits.
ipv6_64	Resources for IPv6 routes with a prefix length of 0 to 64 bits.
l2mc	Multicast replication table resources for a VLAN.
mac	MAC address table resources.
mqcin	Inbound MQC resources.
mqcout	Outbound MQC resources.
nd	ND resources.
nexthoppool1	Next-hop pool resources for the underlay network.
openflow	OpenFlow resources.
pbr	PBR resources.
pfilterin	Inbound packet filter resources.
pfilterout	Outbound packet filter resources.
route	Routing resources.
rport	Layer 3 Ethernet interface resources.
vlaninterface	VLAN interface resources.
vrf	VPN instance resources.
vsi	VSIs.
vsiintf	VSI interface 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 feature is not supported when uRPF is configured on the device. For more information about uRPF, see Security Configuration Guide.

This feature is not supported when the arp mode uni command is configured on the device. For more information, see ARP configuration in Layer 3–IP Services Configuration Guide.

This feature is not supported when the ipv6 nd mode uni command is configured on the device. For more information, see IPv6 basics in Layer 3–IP Services Configuration Guide.

This feature is not supported on EC interface modules.

This feature is not supported on FD, FE, and SG interface modules when the service module operating mode is bridging or enhance-bridge.

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 ARP entry resources on slot 1.

<Sysname> system-view

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

Related commands

display resource-monitor

resource-monitor minor resend enable

resource-monitor output

restart standby

Use restart standby to reboot the standby MPU.

Syntax

restart standby

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is available only in standalone mode.

This command is supported only on the default MDC.

Executing this command has the same effect as specifying the slot number for the reboot slot slot-number command and executing the command. This command does not require an argument and is easier to use.

Examples

# Reboot the standby MPU.

<Sysname> system-view

[Sysname] restart standby

Rebooting the standby MPU. Continue?[Y/N]:y

The standby MPU is rebooting. Please wait...

Related commands

reboot

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

This command is supported only on the default MDC.

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

Examples

# Restore the factory-default configuration for the device.

<Sysname> restore factory-default

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

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

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

Related commands

reboot

scheduler job

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

Use undo scheduler job to delete a job.

Syntax

scheduler job job-name

undo scheduler job job-name

Default

No job exists.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

Examples

# Create a job named backupconfig and enter job view.

<Sysname> system-view

[Sysname] scheduler job backupconfig

[Sysname-job-backupconfig]

Related commands

command

scheduler schedule

scheduler logfile size

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

Syntax

scheduler logfile size value

Default

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

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] scheduler logfile size 32

Related commands

display scheduler logfile

scheduler reboot at

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

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot at time [ date ]

undo scheduler reboot

Default

No reboot date or time is specified.

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

CAUTION:

Device reboot interrupts network services.

‌

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

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

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

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

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

Examples

# Configure the device to reboot at 12:00 p.m. This example assumes that the current time is 11:43 a.m. on June 6, 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

mdc-admin

Parameters

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

Usage guidelines

CAUTION:

Device reboot interrupts network services.

‌

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

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

Examples

# Configure the device to reboot after 88 minutes. This example assumes that the current time is 11:48 a.m. on June 6, 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

mdc-admin

Parameters

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

Usage guidelines

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

To configure a schedule:

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

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

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

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

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

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

Examples

# Create a schedule named saveconfig.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

Related commands

job

time at

time once

set asset-info

Use set asset-info to configure an asset profile for a physical component.

Syntax

In standalone mode:

set asset-info { chassis | fan fan-id | power power-id | slot slot-number } { csn csn-number | custom name value | department department | description description | location location | service-date date | state state }

In IRF mode:

set asset-info chassis chassis-number { chassis | fan fan-id | power power-id | slot slot-number } { csn csn-number | custom name value | department department | description description | location location | service-date date | state state }

Views

System view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

chassis: Configures an asset profile for the frame.

fan fan-id: Configures an asset profile for the specified fan tray. The value range for the fan-id argument is 0 to 14.

power power-id: Configures an asset profile for the specified power module. The value range for the power-id argument is 0 to 16.

slot slot-number: Configures an asset profile for the card in the specified slot.

csn csn-number: Specifies an asset ID for the asset. The asset ID is a string of 1 to 64 characters for a fan tray or card, and a string of 1 to 47 characters for a power supply module.

custom name value: Defines an asset profile item and specifies the value. The value can be a string of 1 to 64 characters.

department department: Specifies the department name, a string of 1 to 64 characters.

description description: Specifies the asset description, a string of 1 to 64 characters.

location location: Specifies the asset location, a string of 1 to 64 characters.

service-date date: Specifies the service start date, a string of 1 to 25 characters.

state state: Specifies the asset usage status, a string of 1 to 64 characters.

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

Usage guidelines

If you configure an asset profile for a non-existent fan tray or power module, the system prompts that the fan tray or power module is not in position.

Examples

# (In standalone mode.) Set the asset ID to 123456 for slot 0.

<Sysname> system-view

[Sysname] set asset-info slot 0 csn 123456

Related commands

display asset-info

reset asset-info

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

mdc-admin

Parameters

interval: Specifies the port status detection timer value in seconds. The value range is 0 to 300. To disable port status detection, set this argument to 0.

Usage guidelines

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

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

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

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

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

Examples

# Set the port status detection timer to 100 seconds.

<Sysname> system-view

[Sysname] shutdown-interval 100

switch-fabric isolate

Use switch-fabric isolate to isolate a switching fabric module or channel from the data plane.

Use undo switch-fabric isolate to cancel the isolation of a switching fabric module or channel.

Syntax

In standalone mode:

switch-fabric isolate slot slot-number

undo switch-fabric isolate slot slot-number

In IRF mode:

switch-fabric isolate chassis chassis-number slot slot-number

undo switch-fabric isolate chassis chassis-number slot slot-number

Default

A switching fabric module is not isolated from the data plane and can forward traffic.

Views

System view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies a switching fabric module by its slot number. (In standalone mode.)

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

Usage guidelines

CAUTION:

· Do not isolate the only switching fabric module of the device.

· Do not reboot the device when a switching fabric module is isolated.

This command is supported only on the default MDC.

Use this command only if required. If the device has multiple switching fabric modules, isolating a switching fabric module or channel decreases the forwarding bandwidth and reduces the forwarding performance.

An isolated switching fabric module continues to communicate with the MPU, and can forward traffic immediately after the isolation is canceled. The isolation does not affect protocol packet parsing and protocol calculation on the control plane.

You can use this command to identify whether switching fabric modules can forward traffic correctly.

Before replacing a switching fabric module, isolate the module to prevent packet loss.

To use an isolated switching fabric module or channel, use the undo switch-fabric isolate command to cancel the isolation.

Examples

# (In standalone mode.) Isolate the switching fabric module in slot 10.

<Sysname> system-view

[Sysname] switch-fabric isolate slot 10

The command will isolate the switch fabric from the system. Continue? [Y/N]y

switch-fabric removal-signal-suppression

Use switch-fabric removal-signal-suppression to suppress removal interrupt signals from switching fabric modules.

Use undo switch-fabric removal-signal-suppression to restore the default.

Syntax

switch-fabric removal-signal-suppression

undo switch-fabric removal-signal-suppression

Default

Removal interrupt signals from switching fabric modules are not suppressed.

Views

System view

Predefined user roles

network-admin

Usage guidelines

CAUTION:

Use this command with caution. This command might result in packet loss and service outage.

‌

This command is supported only on the default MDC.

Typically, removing a switching fabric module triggers one removal interrupt signal. Upon receiving the signal, the system switches traffic on the switching fabric module to other switching fabric modules to ensure service continuity. Upon hardware failure or signal interference, however, removal interrupt signals might be frequently triggered. To prevent the interrupt signals from affecting system operation, you can execute this command to suppress the interrupt signals.

Examples

# Suppress removal interrupt signals from switching fabric modules.

<Sysname> system-view

[Sysname] switch-fabric removal-signal-suppression

sysname

Use sysname to set the device name.

Use undo sysname to restore the default.

Syntax

sysname sysname

undo sysname

Default

The device name is H3C.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

Examples

# Set the name of the device to R2000.

<Sysname> system-view

[Sysname] sysname R2000

[R2000]

system switchover

Use system switchover to manually trigger an active/standby switchover.

Syntax

system switchover

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is available only in standalone mode.

This command is supported only on the default MDC.

As a best practice, save the running configuration before executing this command. After you execute this command, the current active MPU reboots.

Examples

# Manually trigger an active/standby switchover when the running configuration is the same as the startup configuration.

<Sysname> system-view

[Sysname] system switchover

Switching to the standby MPU. Continue? [Y/N]:y

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

This command will perform a switchover. Continue? [Y/N]:y

Now rebooting, please wait...

# Manually trigger an active/standby switchover when the running configuration is different from the startup configuration.

<Sysname> system-view

[Sysname] system switchover

Switching to the standby MPU. Continue? [Y/N]:y

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

Current configuration may be lost after the reboot, save current configuration?

[Y/N]:y

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

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

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

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

This command will perform a switchover. Continue? [Y/N]:y

Now rebooting, please wait...

system-working-mode

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

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

Syntax

system-working-mode { advance | expert | standard }

undo system-working-mode

Default

The device operates in standard mode.

Views

System view

Predefined user roles

network-admin

Parameters

advance: Sets the system operating mode to advanced.

expert: Sets the system operating mode to expert.

standard: Sets the system operating mode to standard.

Usage guidelines

This command is supported only on the default MDC.

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

Change to the operating mode takes effect after a reboot.

Examples

# Set the system operating mode to advanced.

<Sysname> system-view

[Sysname] system-working-mode advance

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

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

temperature-limit

Use temperature-limit to set the temperature alarm thresholds.

Use undo temperature-limit to restore the default.

Syntax

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

mdc-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 located near a high-heat chip to monitor the chip temperature.

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

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

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

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

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

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

Usage guidelines

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

· Sends log messages and traps.

· Sets LEDs on the device panel.

This command is supported only on the default MDC.

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

mdc-admin

Parameters

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

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

Usage guidelines

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

The time at command, the time once command, and the time repeating command overwrite one another. The most recently configured 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

mdc-admin

Parameters

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

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

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

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

Usage guidelines

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

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

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

The time at command, the time once command, and the time repeating command overwrite one another. The most recently configured 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

mdc-admin

Parameters

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

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

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

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

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

Usage guidelines

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

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

The time at command, the time once command, and the time repeating command overwrite one another, whichever is configured 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

mdc-admin

Parameters

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

Usage guidelines

A schedule must have one or more user roles. A command in a schedule can be executed if it is permitted by one or more user roles of the schedule. For more information about user roles, see 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

clock datetime

display copyright

display device manuinfo chassis-only

display fan

display hardware-resource tcam

display power-supply

display scheduler job

display system stable state

display version-update-record

job

memory-threshold usage

monitor cpu-usage interval

resource-monitor minor resend enable

resource-monitor resource

scheduler reboot at

sysname

system-working-mode

time once

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us