mode-name: Specifies an operating mode for a subcard. Available operating modes depend on the subcard type. The following shows all operating mode values:

· oc-12-atm: Specifies the oc-12-atm mode. All interfaces on the subcard act as ATM OC-12c/STM-4 interfaces and use SONET/SDH for data transmission.

· oc-12-pos: Specifies the oc-12-pos mode. All interfaces on the subcard act as 622 Mbps POS interfaces.

· oc-3-atm: Specifies the oc-3-atm mode. All interfaces on the subcard act as ATM OC-3c/STM-1 interfaces and use SONET/SDH for data transmission.

· oc-3-pos: Specifies the oc-3-pos mode. All interfaces on the subcard act as 155 Mbps POS interfaces.

· ethernet: Specifies the Ethernet mode. All interfaces on the subcard act as Ethernet interfaces.

· flexe: Specifies the flexible Ethernet mode. All interfaces on the subcard act as FlexE interfaces.

Usage guidelines

For the new operating mode to take effect immediately, restart the subcard.

If the subcard is damaged and replaced with a new one of the same model, the operating mode configured currently on the device takes effect for the new subcard.

For more information about interface types, see Interface Configuration Guide.

Examples

# (In standalone mode.) Set the operating mode to oc-12-atm for a subcard.

<Sysname> system-view

[Sysname] card-mode slot 2 subslot 1 oc-12-atm

clock datetime

Use clock datetime to set the system time.

Syntax

clock datetime time date

Default

The factory-default system time is used.

Views

User view

Predefined user roles

network-admin

Parameters

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

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

Usage guidelines

CAUTION:

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

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

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

If you set the time zone or daylight saving time after you execute this command, the device recalculates the system time. To view the system time, use the display clock command.

Examples

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

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

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

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

Related commands

clock protocol

clock summer-time

clock timezone

display clock

clock protocol

Use clock protocol to specify the system time source.

Use undo clock protocol to restore the default.

Syntax

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

undo clock protocol

Default

The device obtains the UTC time from an NTP time source.

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 an MDC by its ID.

Usage guidelines

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

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

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

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

The system time calculated by using the UTC time from an NTP or PTP time source is more precise.

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

If you set the time zone or daylight saving time after you execute this command, the device recalculates the system time. To view the system time, use the display clock command.

Examples

# Configure the device to use the local system time.

<Sysname> system-view

[Sysname] clock protocol none

clock summer-time

Use clock summer-time to set the daylight saving time.

Use undo clock summer-time to restore the default.

Syntax

clock summer-time name start-time start-date end-time end-date add-time

undo clock summer-time

Default

The daylight saving time is not set.

Views

System view

Predefined user roles

network-admin

Parameters

name: Specifies a name for the daylight saving time schedule, a case-sensitive string of 1 to 32 characters.

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

start-date: Specifies the start date in one of the following formats:

· MM/DD. The value range for MM is 1 to 12. The value range for DD varies by month.

· month week day, where:

¡ month—Takes January, February, March, April, May, June, July, August, September, October, November, or December.

¡ week—Represents week of the month. It takes first, second, third, fourth, fifth, or last.

¡ day—Takes Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.

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

end-date: Specifies the end date in one of the following formats:

· MM/DD. The value range for MM is 1 to 12. The value range for DD varies by month.

· month week day, where:

¡ month—Takes January, February, March, April, May, June, July, August, September, October, November or December.

¡ week—Represents week of the month. It takes first, second, third, fourth, fifth, or last.

¡ day—Takes Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.

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

Usage guidelines

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

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

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

Examples

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

<Sysname> system-view

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

Related commands

clock datetime

clock timezone

display clock

clock timezone

Use clock timezone to set the time zone.

Use undo clock timezone to restore the default.

Syntax

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

undo clock timezone

Default

The UTC time zone is used.

Views

System view

Predefined user roles

network-admin

Parameters

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

add: Adds an offset to the UTC time or local system time.

minus: Decreases the UTC time or local system time by an offset.

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

Usage guidelines

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

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

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

Examples

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

<Sysname> system-view

[Sysname] clock timezone Z5 add 5

Related commands

clock datetime

clock summer-time

display clock

command

Use command to assign a command to a job.

Use undo command to revoke a command.

Syntax

command id command

undo command id

Default

No command is assigned to a job.

Views

Job view

Predefined user roles

network-admin

Parameters

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

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

Usage guidelines

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] scheduler job backupconfig

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

# Assign commands to the shutdownGE job to shut down Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] scheduler job shutdownGE

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

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

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 clock

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

Syntax

display clock

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

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

<Sysname> display clock

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

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

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

<Sysname> display clock

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

Time Zone : Z5 add 05:00:00

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

<Sysname> display clock

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

Time Zone : Z5 add 05:00:00

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

Related commands

clock datetime

clock timezone

clock summer-time

display copyright

Use display copyright to display the copyright statement.

Syntax

display copyright

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display the copyright statement.

<Sysname> display copyright

...

display cpu-usage

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

Syntax

In standalone mode:

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

display cpu-usage [ control-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 ] [ summary ] [ chassis chassis-number slot slot-number [ cpu cpu-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

control-plane: Displays CPU usage statistics for the control plane.

summary: Displays CPU usage statistics in table form. If you do not specify this keyword, the command displays CPU usage statistics in text form.

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

If two hyphens (--) are displayed for the CPU usage during the most recent 5-second, 1-minute, and 5-minute intervals, the command might fail to obtain data from the database on the device. Try the command later.

Examples

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

<Sysname> display cpu-usage

Slot 1 CPU 0 CPU usage:

1% in last 5 seconds

1% in last 1 minute

1% in last 5 minutes

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

<Sysname> display cpu-usage summary

Slot CPU Last 5 sec Last 1 min Last 5 min

1 0 17% 29% 28%

Table 1 Command output

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

‌

display cpu-usage configuration

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

Syntax

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

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.

Examples

# Display the CPU usage monitoring settings.

<Sysname> display cpu-usage configuration

CPU usage monitor is enabled.

Current monitor interval is 60 seconds.

Current severe alarm threshold is 99%.

Current minor alarm threshold is 79%.

Current recovery threshold is 69%.

Table 2 Command output

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

‌

Related commands

monitor cpu-usage enable

monitor cpu-usage interval

monitor cpu-usage threshold

display cpu-usage history

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

Syntax

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

Parameters

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

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.

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 cpu-usage overload

Use display cpu-usage overload to display CPU overload records.

Syntax

In standalone mode:

display cpu-usage overload show-number [ stack-info ] slot slot-number [ cpu cpu-number ]

In IRF mode:

display cpu-usage overload show-number [ stack-info ] chassis chassis-number slot slot-number [ cpu cpu-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

show-number: Specifies the number of CPU overload records to be displayed, in the range of 1 to 10.

stack-info: Displays the stack information about the top three CPU resource-intensive processes. If you do not specify this keyword, the command does not display stack information.

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

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

Examples

# (In standalone mode.) Display the most recent CPU overload record of a slot, excluding the stack information about the top three CPU resource-intensive processes.

<Sysname> display cpu-usage overload 2 slot 1

CPU overload summary information:

Slot/CPU Time Overload status Processes

1/0 0000-00-00 00:00:00:000 No overloaded NA

No CPU overload history.

# (In IRF mode.) Display the most recent CPU overload record of a card, excluding the stack information about the top three CPU resource-intensive processes.

<Sysname> display cpu-usage overload 1 chassis 1 slot 2 cpu 0

CPU overload summary information:

Chassis/Slot/CPU Time Overload status Processes

1/2/0 2018-11-12 12:00:00:000 Recovered 300

2018-11-12 11:00:00:000 Minor alarm 400

2018-11-12 10:00:00:000 Severe alarm 500

2018-11-12 09:00:00:000 Minor alarm 400

CPU overload history on overload time 2018-11-12 11:00:00:000.

CPU utilization in recent 5 secs: 100.0%; 1 min: 100.0%; 5 mins: 100.0%.

Top processes in recent 5 secs:

JID PID PPID CPU State Mem 5sec 1min 5min Name

811795 811795 811792 0 S 21584K 0.6% 0.0% 0.0% login

811801 811801 811799 0 S 21524K 0.6% 0.0% 0.0% login

811796 811796 811794 0 S 21524K 0.5% 0.0% 0.0% login

257 257 2 0 S 0K 0.0% 0.0% 0.0% [CLKM]

206 206 2 0 S 0K 0.0% 0.0% 0.0% [DIPC]

679 679 342 0 S 137324K 0.1% 0.0% 0.0% comsh

211 211 2 0 D 0K 0.0% 0.0% 0.0% [DTIM]

1778 1778 342 0 S 95352K 0.0% 0.0% 0.0% comsh

261 261 2 0 D 0K 0.0% 0.0% 0.0% [TEMP]

# (In IRF mode.) Display the most recent two CPU overload records of a card, including the stack information about the top three CPU resource-intensive processes.

<Sysname> display cpu-usage overload 2 stack-info chassis 1 slot 2 cpu 0

CPU overload information:

Chassis/Slot/CPU Time Overload status Processes

1/2/0 2018-11-12 11:00:00:000 Minor alarm 400

2018-11-12 10:00:00:000 Severe alarm 500

2018-11-12 09:00:00:000 Minor alarm 400

CPU overload history on overload time 2018-11-12 11:00:00:000.

CPU utilization in 5 secs: 100.0%; 1 min: 100.0%; 5 mins: 100.0%.

Top processes in recent 5 secs:

JID PID PPID CPU State Mem 5sec 1min 5min Name

1 1 0 0 S 21584K 0.6% 0.0% 0.0% scmd

152 152 1 0 S 21524K 0.6% 0.0% 0.0% ifmgr

153 153 1 0 S 21524K 0.5% 0.0% 0.0% edev

805 805 804 0 S 21440K 0.4% 0.0% 0.0% login

257 257 2 0 S 0K 0.0% 0.0% 0.0% [CLKM]

206 206 2 0 S 0K 0.0% 0.0% 0.0% [DIPC]

679 679 342 0 S 137324K 0.1% 0.0% 0.0% comsh

211 211 2 0 D 0K 0.0% 0.0% 0.0% [DTIM]

1778 1778 342 0 S 95352K 0.0% 0.0% 0.0% comsh

261 261 2 0 D 0K 0.0% 0.0% 0.0% [TEMP]

Stack information of process 1 (scmd):

Thread LWP 1:

Switches: 2205

User stack:

#0 0x00007f957d47b320 in epoll_wait+0x14/0x2e

#1 0x0000000000422c1c in ScmMainThread+0x51/0x125

#2 0x0000000000422650 in main+0xd0/0xd7

#3 0x00007f957d4a7ad0 in __uClibc_main+0x242/0x26c

#4 0x0000000000407519 in _start+0x29/0x2a

Kernel stack:

[<ffffffff811eeca3>] ep_poll+0x2f3/0x370

[<ffffffff811eedf0>] SyS_epoll_wait+0xd0/0xe0

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

Stack information of process 152 (ifmgr):

Thread LWP 152:

Switches: 177

User stack:

#0 0x00007f4418429154 in pthread_cond_wait+0xc4/0x203

#1 0x00007f4416b138d0 in logicFlowRoutine+0x1b/0x49

#2 0x0000000000403e33 in main+0x12c/0x133

#3 0x00007f4415deaad0 in __uClibc_main+0x242/0x26c

#4 0x00000000004038f9 in _start+0x29/0x2a

Kernel stack:

[<ffffffff81107287>] futex_wait_queue_me+0xd7/0x140

[<ffffffff811074f0>] futex_wait+0x190/0x280

[<ffffffff81109725>] do_futex+0xe5/0xcf0

[<ffffffff8110a477>] SyS_futex+0x147/0x180

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

Thread LWP 154:

Switches: 3222

User stack:

#0 0x00007f4415dbe320 in epoll_wait+0x14/0x2e

#1 0x00007f4416b106ef in lipcRoutine+0x6f/0xa5

#2 0x00007f44184219e0 in ??

#3 0x00007f4418427fe5 in __clone+0x79/0x83

Kernel stack:

[<ffffffff811eeca3>] ep_poll+0x2f3/0x370

[<ffffffff811eedf0>] SyS_epoll_wait+0xd0/0xe0

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

Thread LWP 156:

Switches: 3151

User stack:

#0 0x00007f4418429154 in pthread_cond_wait+0xc4/0x203

#1 0x00007f4416b15cf8 in miscJobsRoutine+0x18/0x80

#2 0x00007f44184219e0 in ??

#3 0x00007f4418427fe5 in __clone+0x79/0x83

Kernel stack:

[<ffffffff81107287>] futex_wait_queue_me+0xd7/0x140

[<ffffffff811074f0>] futex_wait+0x190/0x280

[<ffffffff81109725>] do_futex+0xe5/0xcf0

[<ffffffff8110a477>] SyS_futex+0x147/0x180

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

Stack information of process 153 (edev):

Thread LWP 153:

Switches: 163

User stack:

#0 0x00007f7d3c276320 in epoll_wait+0x14/0x2e

#1 0x0000000000413748 in main+0x9f/0x10f

#2 0x00007f7d3c2a2ad0 in __uClibc_main+0x242/0x26c

#3 0x00000000004082f9 in _start+0x29/0x2a

Kernel stack:

[<ffffffff811eeca3>] ep_poll+0x2f3/0x370

[<ffffffff811eedf0>] SyS_epoll_wait+0xd0/0xe0

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

Thread LWP 155:

Switches: 1

User stack:

#0 0x00007f7d3c2a22fd in __read+0x2d/0x5e

#1 0x0000000000414be6 in EdevDisioctlThread+0x2d/0x72

#2 0x00007f7d3dacc9e0 in ??

#3 0x00007f7d3dad2fe5 in __clone+0x79/0x83

Kernel stack:

[<ffffffff811f15dd>] eventfd_ctx_read+0x15d/0x210

[<ffffffff811f16dd>] eventfd_read+0x4d/0x80

[<ffffffff811ab621>] vfs_read+0xa1/0x160

[<ffffffff811ab7c4>] SyS_read+0x54/0xc0

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

CPU Overload history on overload time 2018-11-12 10:00:00:000.

CPU utilization in 5 secs: 100.0%; 1 min: 100.0%; 5 mins: 100.0%.

Top processes in recent 5 secs:

JID PID PPID CPU State Mem 5sec 1min 5min Name

1 1 0 0 S 21584K 0.6% 0.0% 0.0% scmd

152 152 1 0 S 21524K 0.6% 0.0% 0.0% ifmgr

153 153 1 0 S 21524K 0.5% 0.0% 0.0% edev

805 805 804 0 S 21440K 0.4% 0.0% 0.0% login

257 257 2 0 S 0K 0.0% 0.0% 0.0% [CLKM]

206 206 2 0 S 0K 0.0% 0.0% 0.0% [DIPC]

679 679 342 0 S 137324K 0.1% 0.0% 0.0% comsh

211 211 2 0 D 0K 0.0% 0.0% 0.0% [DTIM]

1778 1778 342 0 S 95352K 0.0% 0.0% 0.0% comsh

261 261 2 0 D 0K 0.0% 0.0% 0.0% [TEMP]

Stack information of process 1 (scmd):

Thread (LWP 1):

Switches: 2205

User stack:

#0 0x00007f957d47b320 in epoll_wait+0x14/0x2e

#1 0x0000000000422c1c in ScmMainThread+0x51/0x125

#2 0x0000000000422650 in main+0xd0/0xd7

#3 0x00007f957d4a7ad0 in __uClibc_main+0x242/0x26c

#4 0x0000000000407519 in _start+0x29/0x2a

Kernel stack:

[<ffffffff811eeca3>] ep_poll+0x2f3/0x370

[<ffffffff811eedf0>] SyS_epoll_wait+0xd0/0xe0

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

Stack information of process 152 (ifmgr):

Thread (LWP 152):

Switches: 177

User stack:

#0 0x00007f4418429154 in pthread_cond_wait+0xc4/0x203

#1 0x00007f4416b138d0 in logicFlowRoutine+0x1b/0x49

#2 0x0000000000403e33 in main+0x12c/0x133

#3 0x00007f4415deaad0 in __uClibc_main+0x242/0x26c

#4 0x00000000004038f9 in _start+0x29/0x2a

Kernel stack:

[<ffffffff81107287>] futex_wait_queue_me+0xd7/0x140

[<ffffffff811074f0>] futex_wait+0x190/0x280

[<ffffffff81109725>] do_futex+0xe5/0xcf0

[<ffffffff8110a477>] SyS_futex+0x147/0x180

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

Thread (LWP 154):

Switches: 3222

User stack:

#0 0x00007f4415dbe320 in epoll_wait+0x14/0x2e

#1 0x00007f4416b106ef in lipcRoutine+0x6f/0xa5

#2 0x00007f44184219e0 in ??

#3 0x00007f4418427fe5 in __clone+0x79/0x83

Kernel stack:

[<ffffffff811eeca3>] ep_poll+0x2f3/0x370

[<ffffffff811eedf0>] SyS_epoll_wait+0xd0/0xe0

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

Thread (LWP 156):

Switches: 3151

User stack:

#0 0x00007f4418429154 in pthread_cond_wait+0xc4/0x203

#1 0x00007f4416b15cf8 in miscJobsRoutine+0x18/0x80

#2 0x00007f44184219e0 in ??

#3 0x00007f4418427fe5 in __clone+0x79/0x83

Kernel stack:

[<ffffffff81107287>] futex_wait_queue_me+0xd7/0x140

[<ffffffff811074f0>] futex_wait+0x190/0x280

[<ffffffff81109725>] do_futex+0xe5/0xcf0

[<ffffffff8110a477>] SyS_futex+0x147/0x180

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

Stack information of process 153 (edev):

Thread (LWP 153):

Switches: 163

User stack:

#0 0x00007f7d3c276320 in epoll_wait+0x14/0x2e

#1 0x0000000000413748 in main+0x9f/0x10f

#2 0x00007f7d3c2a2ad0 in __uClibc_main+0x242/0x26c

#3 0x00000000004082f9 in _start+0x29/0x2a

Kernel stack:

[<ffffffff811eeca3>] ep_poll+0x2f3/0x370

[<ffffffff811eedf0>] SyS_epoll_wait+0xd0/0xe0

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

Thread (LWP 155):

Switches: 1

User stack:

#0 0x00007f7d3c2a22fd in __read+0x2d/0x5e

#1 0x0000000000414be6 in EdevDisioctlThread+0x2d/0x72

#2 0x00007f7d3dacc9e0 in ??

#3 0x00007f7d3dad2fe5 in __clone+0x79/0x83

Kernel stack:

[<ffffffff811f15dd>] eventfd_ctx_read+0x15d/0x210

[<ffffffff811f16dd>] eventfd_read+0x4d/0x80

[<ffffffff811ab621>] vfs_read+0xa1/0x160

[<ffffffff811ab7c4>] SyS_read+0x54/0xc0

[<ffffffff814deb39>] system_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

Table 3 Command output

Field	Description
Time	Time when the overload event occurred. If no overload events occurred, this field displays 0000-00-00 00:00:00:000.
Overload status	Overload status: · No overloaded—The CPU is not overloaded. This state is the initial state. · Minor alarm—The CPU load exceeded the minor alarm threshold. · Severe alarm—The CPU load exceeded the severe alarm threshold. · Recovered—The CPU load dropped below the CPU overload alarm-removed threshold.
Processes	Number of processes when the overload event occurred. If no overload events occurred, this field displays NA.
CPU overload history on overload time 2018-11-12 10:00:00:000:	Detailed CPU overload information. If no overload events occurred, this field displays No CPU overload history.
Overload time	Time when the overload event occurred. If no overload events occurred, this field displays 0000-00-00 00:00:00:000.
Top processes in recent 5 secs	Top CPU resource-intensive processes in recent 5 seconds, in descending order.
JID	Job ID. A job ID uniquely identifies a process and does not change after a process reboot.
PID	Process ID.
PPID	ID of the parent process.
CPU	CPU where the process was running when it was most recently scheduled.
State	Process status: · R—The process is running or in the run queue. · S—The process is in interruptible sleeping state. · T—The process is in traced or stopped state. · D—The process is in uninterruptible sleeping state. · Z—The process is in zombie state.
Mem	Memory space used by the process. For a kernel thread, this field displays 0.
5sec	CPU utilization in the last 5 seconds.
1min	CPU utilization in the last minute.
5min	CPU utilization in the last 5 minutes.
Name	Process name. For a kernel thread, this field displays the name in a pair of brackets ([ ]).
Stack information of process PID (process name):	Stack information of a process. The PID indicates the process ID.
Thread LWP 1:	Child process of a traced process.
Switches	Total number of switches.
User stack	User space stack information. This field is displayed only for a process in the user space.
Kernel stack	Kernel space stack information. This field is displayed only for a process in the kernel space.

‌

Related commands

display cpu-usage overload summary

Use display cpu-usage overload summary to display summary CPU overload information.

Syntax

display cpu-usage overload summary

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# (In standalone mode.) Display summary CPU overload information.

<Sysname> display cpu-usage overload summary

CPU overload summary information:

Slot/CPU Time Overload status Processes

1/0 2018-11-12 12:00:00:000 Recovered 300

2018-11-12 11:00:00:000 Minor alarm 400

2018-11-12 10:00:00:000 Severe alarm 500

2018-11-12 09:00:00:000 Minor alarm 400

# (In IRF mode.) Display summary CPU overload information.

<Sysname> display cpu-usage overload summary

CPU overload summary information:

Chassis/Slot/CPU Time Overload status Processes

1/1/0 0000-00-00 00:00:00:000 No overloaded NA

1/2/0 2018-11-12 12:00:00:000 Recovered 300

2018-11-12 11:00:00:000 Minor alarm 400

2018-11-12 10:00:00:000 Severe alarm 500

2018-11-12 09:00:00:000 Minor alarm 400

1/3/0 0000-00-00 00:00:00:000 No overloaded NA

For information about the fields in the command output, see Table 3.

Related commands

display cpu-usage overload

display device

Use display device to display device information.

Syntax

In standalone mode:

display device [ cf-card | flash | sd-card ] [ slot slot-number [ cpu cpu-number ] [ subslot subslot-number ] | verbose ]

In IRF mode:

display device [ cf-card | flash | sd-card ] [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] [ subslot subslot-number ] ] | verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

cf-card: Displays CF card information.

flash: Displays flash memory information.

sd-card: Displays SD card information. This keyword is supported only on the CSR05SRP1P3 card.

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

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

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

verbose: Displays detailed information. If you do not specify this keyword, this command displays brief information, and does not display firewall card information.

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

Usage guidelines

If you do not specify the cf-card, flash, and sd-card keywords, this command displays information about cards.

Examples

# (In standalone mode.) Display device information.

<Sysname> display device

...

Table 4 Command output

Field

Description

Brd Type

Hardware type of the card.

Brd Status

Card status:

· Standby—The card is the standby MPU.

· Master—The card is the active MPU.

· Absent—The slot is not installed with a card.

· Fault—The card is faulty and cannot start up.

· Normal—The card is an interface card and is operating correctly.

· Off—The card is not powered on.

· Illegal—The current software version does not support the card. The card cannot operate correctly.

· Offline—The card is isolated.

‌

display device manuinfo

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

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

Usage guidelines

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

Examples

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

Parameters

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

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

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

Fan 1:

DEVICE_NAME : fan

DEVICE_SERIAL_NUMBER : 210235A36L1234567890

MAC_ADDRESS : NONE

MANUFACTURING_DATE : 2010-01-20

VENDOR_NAME : H3C

display device manuinfo power

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

Syntax

In standalone mode:

display device manuinfo power power-id

In IRF mode:

display device manuinfo chassis chassis-number power power-id

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

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

Examples

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

<Sysname> display device manuinfo power 1

...

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 ] [ background ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

background: Saves operating information in the background. If you do not specify this keyword, the system displays or saves operating information in the CLI and you cannot execute other commands during the process. It is time consuming if a large amount of operating information is to be collected. If you specify this keyword, the system saves operating information in the background and users can execute other commands in the CLI during the process.

hardware: Specifies hardware-related operating information.

infrastructure: Specifies operating information for the fundamental features.

l2: Specifies operating information for the Layer 2 features.

l3: Specifies operating information for the Layer 3 features.

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

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

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

Usage guidelines

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

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

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

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

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

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

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

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

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

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

This command does not support the |, >, or >> option.

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

Examples

# Display the operating information for all features and modules.

<Sysname> display diagnostic-information

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

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

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

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

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

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

...

# Save the operating information for all features and modules to the default file.

<Sysname> display diagnostic-information

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

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

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

Please wait...

Save successfully.

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

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

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

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

Please wait...

Save successfully.

# Save the operating information in the background to the default file.

<Sysname> display diagnostic-information background

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

Diagnostic information is outputting to flash:/diag_Sysname_20201215-163501.tar.gz in the background.

Related commands

gunzip

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

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.

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

0 inflow 1 25 0 48 60 NA

0 hotspot 1 31 0 80 95 NA

2 inflow 1 29 0 80 97 NA

2 outflow 1 26 0 80 97 NA

2 hotspot 1 31 0 80 97 NA

2 hotspot 2 42 0 80 97 NA

3 inflow 1 31 0 80 97 NA

3 outflow 1 32 0 80 97 NA

3 hotspot 1 47 0 80 97 NA

3 hotspot 2 38 0 80 97 NA

4 hotspot 1 30 0 75 90 NA

6 hotspot 1 41 0 88 100 110

Table 5 Command output

Field	Description
System Temperature information (degree centigrade)	Temperature information (°C).
Slot	slot ID.
sensor	Temperature sensor: · hotspot—Hotspot sensor. · inflow—Air inlet sensor. · outflow—Air outlet sensor.
Temperature	Current temperature.
Lower	Lower temperature limit. If the device does not support this field, this field displays NA.
Warning	Warning temperature threshold. If the device does not support this field, this field displays NA.
Alarm	Alarming temperature threshold. If the device does not support this field, this field displays NA.
Shutdown	Shutdown temperature threshold. When the sensor temperature reaches the limit, the system shuts down automatically. If the device does not support this field, this field displays NA.

‌

display fan

Use display fan to display fan tray operating status information.

Syntax

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

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.

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:

· Normal—The fan tray is operating correctly.

· Fault—The fan tray is faulty.

· Absent—The slot is not installed with a fan tray.

‌

display fan-speed

Use display fan-speed to display the current fan operating mode and the speeds of fans.

Syntax

In standalone mode:

display fan-speed

In IRF mode:

display fan-speed [ chassis chassis-number ]

Views

Any view

Predefined user roles

network-admin

Parameters

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

Examples

# (In standalone mode.) Display the current fan operating mode and the speeds of fans.

<Sysname> display fan-speed

Current fan speed mode is auto

Frame 0 fan 1 speed is 2414 (R.P.M)

Frame 0 fan 2 speed is 2406 (R.P.M)

Frame 0 fan 3 speed is 3364 (R.P.M)

Frame 0 fan 4 speed is 3342 (R.P.M)

Frame 0 fan 5 speed is 3357 (R.P.M)

Frame 0 fan 6 speed is 3324 (R.P.M)

Frame 0 fan 7 speed is 3361 (R.P.M)

Frame 0 fan 8 speed is 3288 (R.P.M)

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

Examples

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

<Sysname> display hardware-failure-detection

Current level:

chip : warning

board : warning

forwarding : warning

Recent record:

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

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

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 detection settings and the latest 10 fix records for each card.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-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 option, the command displays all hardware failure protection settings on the device.

Examples

# Display all hardware failure protection settings.

<Sysname> display hardware-failure-protection

Aggregation: on

Port: XGE3/1/1 XGE3/1/2

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

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

Port: XGE3/1/1 XGE3/1/2

# Display whether hardware failure protection is enabled for interface Ten-GigabitEthernet 3/1/2.

<Sysname> display hardware-failure-protection port ten-gigabitethernet 3/1/2

Hardware failure protection is enabled on the interface. The system will shut down the interface when it detects a hardware failure on the interface.

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 health

Use display health to display CPU and memory usage.

Syntax

In standalone mode:

display health [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays CPU and memory usage on all cards. (In standalone mode.)

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

Examples

# (In standalone mode.) Display the CPU and memory usage on all cards.

<Sysname> display health

Slot CPU Role CPU Usage(%) Memory Usage(%) Used/Total(MB)

1 0 MPU(Master) 7 23 1902504/8130012

2 0 LPU 9 48 963064/1991292

3 0 LPU 7 47 1913916/4052524

5 0 LPU 4 18 1538196/8158684

6 0 SFU 3 36 361296/984332

7 0 SFU 6 36 361348/984332

Table 9 Command output

Field	Description
Role	Card role: · MPU(Master)—Active MPU. (In standalone mode.) · MPU(Standby)—Standby MPU. (In standalone mode.) · MPU(Master)—Global active MPU. (In IRF mode.) · MPU(Standby)—Global standby MPU. (In IRF mode.) · LPU—LPU. · Blade—Blade MPU.
CPU Usage(%)	Average CPU usage during the past 5 seconds, in percentage.
Memory Usage(%)	Memory usage in percentage.
Used/Total(MB)	Used memory size and total memory size in MB.

‌

display kernel memory alloc-failure

Use display kernel memory alloc-failure to display kernel memory allocation failure information.

Syntax

In standalone mode:

display kernel memory alloc-failure [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

display kernel memory fragment free [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays kernel memory allocation failure information 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 kernel memory allocation failure information for the global active MPU. (In IRF mode.)

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

Examples

# Display kernel memory allocation failure information.

<System> display kernel memory alloc-failure

kmalloc_tag failures: 55.

kcalloc_tag failures: 0.

kzalloc_tag failures: 0.

krealloc_tag failures: 0.

kmem_cache_alloc_tag failures: 0.

Table 10 Command output

Field	Description
kmalloc_tag failures	Number of memory allocation failures on the use of kmalloc_tag.
kcalloc_tag failures	Number of memory allocation failures on the use of kcalloc_tag.
kzalloc_tag failures	Number of memory allocation failures on the use of kzalloc_tag.
krealloc_tag failures	Number of memory allocation failures on the use of krealloc_tag.
kmem_cache_alloc_tag failures	Number of memory allocation failures on the use of kmem_cache_alloc_tag.

‌

display kernel memory fragment free

Use display kernel memory fragment free to display the kernel memory fragment statistics.

Syntax

In standalone mode:

display kernel memory fragment free [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

display kernel memory fragment free [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays kernel memory fragment 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 kernel memory fragment statistics for the global active MPU. (In IRF mode.)

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

Examples

# Display the kernel memory fragment statistics.

<Sysname> display kernel memory fragment free

Kernel memory free ratio: 0.13%

cfq_io_context memory free (in kbytes): 0

LFIB_NhlfeEntryCache26 memory free (in kbytes): 0

LFIB_NhlfeEntryCache74 memory free (in kbytes): 0

L2VFIB_TUNNELBMP_Cache memory free (in kbytes): 0

NAT_SESSION_EXT_INFO memory free (in kbytes): 0

ARP_VSISUP_Entry_cache memory free (in kbytes): 0

LFIB_NhlfeEntryCache1 memory free (in kbytes): 0

FVN_FwdCache19 memory free (in kbytes): 0

...

Table 11 Command output

Field	Description
Kernel memory free ratio	Memory fragment ratio in the kernel space.
cfq_io_context memory free (in kbytes)	Memory fragment size in the slab named cfq_io_context, in KB.

‌

display memory

Use display memory to display memory usage information.

Syntax

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

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

If two hyphens (--) are displayed for all the fields in a line of the command output, the command might fail to obtain data from the database on the device. Try the command later.

Examples

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

<Sysname> display memory

Memory statistics are measured in KB:

Slot 1:

Total Used Free Shared Buffers Cached FreeRatio

Mem: 984560 456128 528432 0 4 45616 53.7%

-/+ Buffers/Cache: 410508 574052

Swap: 0 0 0

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

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

‌

display memory dma

Use display memory dma to display DMA memory usage information.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays DMA memory usage information 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 DMA memory usage information for the global active MPU. (In IRF mode.)

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

Examples

# (In standalone mode.) Display DMA memory usage information for slot 1.

<System> display memory dma slot 1

DMA memory statistics measured in KB on slot 1:

Total Used Free FreeRatio

16384 6140 10244 63%

Table 13 Command output

Field	Description
Total	Total size of the DMA memory space, including the free and used DMA memory.
Used	Used DMA memory.
Free	Free DMA memory.
FreeRatio	Free DMA memory ratio.

‌

display memory-threshold

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

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

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

Examples

# Display memory alarm thresholds and statistics.

<Sysname> display memory-threshold

Memory usage threshold: 100%

Free memory threshold:

Minor: 64M

Severe: 48M

Critical: 32M

Normal: 96M

Current memory state: Normal

Event statistics:

[Back to normal state]

First notification: 2012-5-15 09:21:35.546

Latest notification: 2012-5-15 09:21:35.546

Total number of notifications sent: 1

[Enter minor low-memory state]

First notification at: 2012-5-15 09:07:05.941

Latest notification at: 2012-5-15 09:07:05.941

Total number of notifications sent: 1

[Back to minor low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Enter severe low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to severe low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Enter critical low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

Table 14 Command output

Field	Description
Free-memory thresholds Minor Severe Critical Normal Early-warning Secure	Free-memory thresholds: · Minor—Minor alarm threshold in MB. If two hyphens (--) are displayed, the device does not obtain the threhsold. · Severe—Severe alarm threshold in MB. If two hyphens (--) are displayed, the device does not obtain the threhsold. · Critical—Critical alarm threshold in MB. If two hyphens (--) are displayed, the device does not obtain the threhsold. · Normal—Normal state threshold in MB. If two hyphens (--) are displayed, the device does not obtain the threhsold. · Early-warning—Early-warning threshold in MB. If two hyphens (--) are displayed, the device does not obtain the threhsold. · Secure—Sufficient-memory threshold in MB. If two hyphens (--) are displayed, the device does not obtain the threhsold.
Current free-memory state	Current state of the free memory in the system: · Normal—Normal state. · Minor—Minor alarm threshold. · Severe—Severe alarm threshold. · Critical—Critical alarm threshold. · Normal (early-warning)—Early-warning threshold. · Normal (secure)—Sufficient-memory state.
First notification at	Time when the alarm notification was sent for the first time, in the format of yyyy-mm-dd hh:mm:ss.msec.
Latest notification at	Time when the alarm notification was sent most recently in the format of yyyy-mm-dd hh:mm:ss.msec.
Total number of notification send	Total number of the alarm notifications that were sent.

‌

display memory-threshold dma

Use display memory-threshold dma to display DMA memory alarm information.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

Examples

# Display DMA memory alarm information.

<Sysname> display memory-threshold dma

Free DMA memory thresholds:

Critical: 2048KB

Normal: 4096KB

Current DMA memory state: Normal

Free memory event statistics:

[Back to normal state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Entered to critcal state]

First notificatio: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

display non-stop-routing status

Use display non-stop-routing status to display nonstop routing (NSR) status information for modules that support the NSR feature.

Syntax

display non-stop-routing status

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display NSR status information for modules that support the NSR feature.

<Sysname> display non-stop-routing status

NSR status: Not ready

Module name(instance name/process ID) Status

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

MSDP Not ready

OSPF(1) Ready

OSPF(2) Ready

BGP(default) Ready

BGP(aaa) Ready

PIM Not configured

Table 15 Command output

Field	Description
NSR status	Global NSR status: · Ready—NSR is in stable state for all NSR-enabled modules. · Not ready—NSR is not in stable state for one or more NSR-enabled modules. · Not configured—NSR is not enabled for any modules. · No standby—No backup hardware exists for NSR.
Module name(instance name/process ID)	Name of an NSR-capable module and the instance name or process ID, for example, BGP(default) and OSPF(1). If there is no instance name or process, this field displays only the module name.
Status	NSR status: · Ready—NSR is in stable state status for the module. · Not ready—NSR is not in stable state for the module. You cannot perform a process switchover or active/standby switchover. · Not configured—NSR is not enabled for the module. You cannot perform a process switchover or active/standby switchover.

‌

display power

Use display power to display power module information.

Syntax

In standalone mode:

display power [ power-id ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

Examples

# Display brief power module information.

<Sysname> display power

Power 0 State: Normal

Power 1 State: Absent

Power 2 State: Absent

Power 3 State: Absent

Table 16 Command output

Field

Description

Power n State

Power module status.

· Absent—The slot is not installed with a power module.

· Error—The power module is faulty.

· Normal—The power module is operating correctly.

‌

display power-off high-temp-board

Use display power-off high-temp-board to display whether the overtemperature auto shutdown feature is enabled.

Syntax

display power-off high-temp-board

Views

Any view

Predefined user roles

network-admin

Examples

# Display whether the overtemperature auto shutdown feature is enabled.

<Sysname> display power-off high-temp-board

Power off high temperature board mode: Enable

display power-information

Use display power-information to display power information about power modules and cards.

Syntax

In standalone mode:

display power-information [ verbose ]

In IRF mode:

display power-information [ chassis chassis-number ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

Parameters

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

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

Examples

# (In standalone mode.) Display power information about power modules and cards.

<Sysname> display power-information

Power control mode: strict

Device power: 2500W

Surplus power: 1296W (contain 100W reserve power)

Fan power: 300W

Slot No. Power(W)

0 100 reserve for mainboard

1 100 reserve for mainboard

3 95

4 300

5 164

6 65

7 80

Table 17 Command output

Field	Description
Chassis n	Member ID of an IRF member device. (In IRF mode.)
Device Power	Rated power of the device.
Power control mode	Power control mode of cards: · loose. · strict.
Surplus power	Remaining power of the device.
Fan Power	Maximum fan power.
contain 100 reserve power	Reserved power of 100W.
Slot No.	Slot number of the card.
Power(W)	Maximum card power.
reserve for mainboard	Reserved power for the MPU.
Power No.	Slot number of the power module.
Status	Power module status.
Input(V)	Input voltage of the power module.
Output(V)	Output voltage of the power module.
Input(A)	Input current of the power module.
Output(A)	Output current of the power module.
Input(W)	Input power of the power module.
Output(W)	Output power of the power module.
Current input total power	Total power of power modules.
Current output total power	Total output power of power modules.

‌

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

Parameters

resource resource-name: Specifies a resource type by its name.

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 arpnd

Minor alarms resending: Enabled

Slot 1:

Resource Minor Severe Free/Total

(percentage)

arpnd 50% 20% 99

Table 18 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 (percentage)	Numbers of available resources and total resources, in percentage.

‌

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

Parameters

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

Examples

# Display configuration information for all jobs.

<Sysname> display scheduler job

Job name: saveconfig

copy startup.cfg backup.cfg

Job name: backupconfig

Job name: 123

// The output shows that the device has three jobs: the first has one command, the second does not have any commands, and the third has two commands. Jobs are separated by blank lines.

display scheduler logfile

Use display scheduler logfile to display job execution log information.

Syntax

display scheduler logfile

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display job execution log information.

<Sysname> display scheduler logfile

Logfile Size: 1902 Bytes.

Job name : shutdown

Schedule name : shutdown

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

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

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

<Sysname>system-view

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

[Sysname]interface rang ten-gigabitethernet 3/1/1 to ten-gigabitethernet 3/1/3

[Sysname-if-range]shutdown

Table 19 Command output

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

‌

Related commands

reset scheduler logfile

display scheduler reboot

Use display scheduler reboot to display the automatic reboot schedule.

Syntax

display scheduler reboot

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display the automatic reboot schedule.

<Sysname> display scheduler reboot

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

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

Parameters

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

Examples

# Display information about all schedules.

<Sysname> display scheduler schedule

Schedule name : shutdown

Schedule type : Run once after 0 hours 2 minutes

Start time : Tue Dec 27 10:44:42 2011

Last execution time : Tue Dec 27 10:44:42 2011

Last completion time : Tue Dec 27 10:44:47 2011

Execution counts : 1

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

Job name Last execution status

shutdown Successful

Table 20 Command output

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

‌

display system stable state

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

Syntax

display system stable state [ summary ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Usage guidelines

The device/card 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 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.

The display ha service-group all command is automatically executed when you execute the display system stable state command. You can identify system stability and status through the display ha service-group all command. For more information about the display ha service-group all command, see process placement commands in High Availability Command Reference.

Examples

# Display brief information about system stability and status.

<Sysname> display system stable state summary

System state : Stable

Redundancy state : No redundancy

NSR state : No standby

# Display CPU status summary, redundancy status, and detailed information about CPU operation.

<Sysname> display system stable state

System state : Stable

Redundancy state : No redundance

Slot CPU Role State

0 0 Active Stable

2 0 Other Stable

3 0 Other Stable

Table 21 Command output

Field	Description
System state	Operating status summary of all CPUs: · Stable—All CPUs are operating stably. · Not ready—The CPUs are not operating stably. At least one CPU is not operating stably.
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	Readiness of modules for nonstop routing: · Ready—NSR is operating correctly. · Not ready—NSR is not operating correctly. You cannot perform a process or active/standby switchover. · No standby—No backup MPU exists. · 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 module.
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. · Service module data batch backup—A service module data batch backup is in progress.
*	The object is not operating stably.

‌

Related commands

display device

display ha service-group (High Availability Command Reference)

display 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

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.

Related commands

system-working-mode

display transceiver alarm

Use display transceiver alarm to display transceiver alarms.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Usage guidelines

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

Table 22 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
CDR	Clock and data recovery
CDR loss of lock	Indicates that the signal is in bad condition.

‌

Examples

# Display the alarms present on the transceiver module in interface Ten-GigabitEthernet 3/1/1.

<Sysname> display transceiver alarm interface ten-gigabitethernet 3/1/1

Ten-GigabitEthernet3/1/1 transceiver current alarm information:

RX signal loss

RX power low

Table 23 Command output

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

‌

display transceiver brief

Use display transceiver brief to display information about all transceiver modules, including transceiver module types, receive power, and transmit power.

Syntax

display transceiver brief

Views

Any view

Predefined user roles

network-admin

Examples

# Display transceiver module types, receive power, and transmit power of all transceiver modules on the device.

<Sysname> display transceiver brief

Interface TransceiverType WaveL(nm) Mode Rx(dBm) Tx(dBm) Status

Current/Range Current/Range

XGE3/1/1 10G-10km-QSFPDD 1310 SM -15.0/[-18.5,-3.0] -15.0/[-18.5,-3.0] Normal

XGE3/1/2 10G-10km-QSFPDD 1310 SM -15.0/[-18.5,-3.0] -29.0/[-18.5,-3.0] Beyond threshold

XGE3/1/3 10G-10km-QSFPDD 1310 SM NA/[-18.5,-3.0] NA/[-18.5,-3.0] Unknown

HGE4/0/4 100G-10km-QSFPDD 1310 SM -15.0/[-18.5,-3.0] -29.0/[-18.5,-3.0] Normal

-15.0/[-18.5,-3.0] -29.0/[-18.5,-3.0] Normal

Table 24 Command output

Field	Description
Interface	Abbreviated Interface name.
Type	Type of the transceiver module, consisting of the rate, transmission distance, and interface type. Two hyphens (--) indicate that the device failed to obtain data or the transceiver module does not support obtaining type information.
WaveL	Wavelength of the interface. Two hyphens (--) indicate that the device failed to obtain data or the transceiver module does not support obtaining wavelength information.
Mode	Mode of the transceiver module: · MM—Multimode · SM—Single mode. · Two hyphens (--)—The device failed to obtain data or the transceiver module does not support obtaining mode information.
Rx(dBm) Current/Range	Current receive power/normal receive power range. Two hyphens (--) indicate that the device failed to obtain data or the transceiver module does not support obtaining power information. N/A indicates that the obtained power value is invalid.
Tx(dBm) Current/Range	Current transmit power/normal transmit power range. Two hyphens (--) indicate that the device failed to obtain data or the transceiver module does not support obtaining power information. N/A indicates that the obtained power value is invalid.
Status	Current power status: · Normal—The power is in the normal range. · Beyond threshold—The power exceeds the normal range. · Unknown—The status is unknown. · Two hyphens (--)—The device failed to obtain data or the transceiver module does not support obtaining status information.

‌

display transceiver diagnosis

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Examples

# Display the current values of the digital diagnosis parameters on the transceiver module in interface Ten-GigabitEthernet 3/1/1.

<Sysname> display transceiver diagnosis interface ten-gigabitethernet 3/1/1

Ten-GigabitEthernet3/1/1 transceiver diagnostic information:

Current diagnostic parameters:

Temp(°C) Voltage(V) Bias(mA) RX power(dBm) TX power(dBm)

36 3.31 6.13 -35.64 -5.19

Alarm thresholds:

Temp(°C) Voltage(V) Bias(mA) RX power(dBM) TX power(dBM)

High 50 3.55 1.44 -10.00 5.00

Low 30 3.01 1.01 -30.00 0.00

Warning thresholds:

Temp(°C) Voltage(V) Bias(mA) RX power(dBM) TX power(dBM)

High 45 3.25 1.25 -15.00 4.00

Low 25 2.85 0.85 -25.00 1.00

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

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

HundredGigE3/1/1 transceiver diagnostic information:

Current diagnostic parameters:

[module] Temp.(°C) Voltage(V) Total RX power(dBm) Total TX power(dBm)

29 3.33 -33.61 8.41

[channel] Bias(mA) RX power(dBm) TX power(dBm)

1 0.00 -36.96 -36.96

2 0.00 -36.96 -36.96

3 0.00 -36.96 -36.96

4 0.00 -36.96 -36.96

Alarm thresholds:

Temp.(°C) Voltage(V) Bias(mA) RX power(dBm) TX power(dBm)

High 75 3.47 13.00 3.40 5.00

Low -5 3.13 3.00 -14.00 -10.00

Warning thresholds:

Temp.(°C) Voltage(V) Bias(mA) RX power(dBm) TX power(dBm)

High 70 3.45 11.00 2.40 3.00

Low 0 3.15 5.00 -11.00 -8.00

Total average launch power(dBm): 5.90

Table 25 Command output

Field	Description
transceiver diagnostic information	Digital diagnosis information for the transceiver module in the interface.
Temp.(°C)	Temperature in °C, accurate to 1°C.
Voltage(V)	Voltage in V, accurate to 0.01 V.
Total RX power(dBm)	Total receive power in dBm, accurate to 0.01 dBm.
Total TX power(dBm)	Total transmit power in dBm, accurate to 0.01 dBm.
Bias(mA)	Bias current in mA, accurate to 0.01 mA.
RX power(dBm)	Receive power in dBm, accurate to 0.01 dBm.
TX power(dBm)	Transmit power in dBm, accurate to 0.01 dBm.
Total average launch power(dBm)	Total average launch power on the multi-lane transceiver module in dBM, accurate to 0.01 dBm.

‌

display transceiver interface

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

Syntax

display transceiver interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Examples

# Display the key parameters of the transceiver module in interface Ten-GigabitEthernet 3/1/1.

<Sysname> display transceiver interface ten-gigabitethernet 3/1/1

Ten-GigabitEthernet3/1/1 transceiver information:

Transceiver Type : 1000_BASE_SX_SFP

Connector Type : LC

Wavelength(nm) : 850

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

Digital Diagnostic Monitoring : YES

Vendor Name : H3C

Table 26 Command output

Field	Description
Connector Type	Connector types: · SC—Fiber connector developed by NTT. · LC—1.25 mm/RJ-45 fiber connector developed by Lucent. · RJ-45. · CX 4.
Wavelength(nm)	Central wavelength (in nm) of the transmit laser. If the transceiver supports multiple wavelengths, every two wavelength values are separated by a comma. For a copper cable, this field displays N/A.
Transfer Distance(xx)	Transmission distance, where xx indicates the distance unit: · km—Kilometers, for single-mode transceiver modules. · m—Meters, for other transceiver modules. If the transceiver module supports multiple types of transmission media, this field displays the transmission distance for each type, in the form of transmission distance (medium type). Transmission medium types include: · 9 um—9/125 µm single-mode fiber. · 50 um—50/125 µm OM2 multimode fiber. · 62.5 um—62.5/125 µm OM1 multimode fiber. · CX4—CX4 cable. · OM3—50 µm OM3 multimode fiber. · OM4—50 µm OM4 multimode fiber. · OM5—50 µm OM5 multimode fiber. · STACK—Stack cable. · TP—Twisted pair.
Digital Diagnostic Monitoring	Support for digital diagnosis: · YES—Supported. · NO—Not supported.

‌

display transceiver itu-channel

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

Usage guidelines

This command is available only for the HPE X130 10G SFP+ LC LH80 Tunable Transceiver (JL250A), SFP-XG-LH80-Tunable, and CFP2-200G-DCO-Tunable transceiver modules.

Examples

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

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

Interface Channel WaveLength(nm) Frequency(THz)

XGE3/1/1 1 1566.72 191.35

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

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

ITU channel settings supported on ten-gigabitethernet 3/1/1 :

Channel WaveLength(nm) Frequency(THz)

1 1566.72 191.35

2 1566.31 191.40

3 1565.90 191.45

4 1565.50 191.50

5 1565.09 191.55

6 1564.68 191.60

7 1564.27 191.65

8 1563.86 191.70

...

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

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 Ten-GigabitEthernet 3/1/1.

<Sysname> display transceiver manuinfo interface ten-gigabitethernet 3/1/1

Ten-GigabitEthernet3/1/1 transceiver manufacture information:

Manu. Serial Number : 213410A0000054000251

Manufacturing Date : 2012-09-01

Vendor Name : H3C

Table 28 Command output

Field	Description
Manu. Serial Number	Serial number generated during production of the transceiver module.
Manufacturing Date	Date when the electronic label information was written to the transceiver module.

‌

display transceiver status

Use display transceiver status to display transceiver module status information.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface [ interface-type interface-number ]: Specifies an interface by its type and number. If you do not specify an interface, this command applies to all interfaces.

Usage guidelines

If an error occurs on transceiver modules on the device, you can execute this command to obtain transceiver module status information. For example, you can identify whether a transceiver module is reset, power mode of a transceiver module, and operation information of each lane on the transceiver module.

This command is supported only on the SFP and QSFP transceiver modules.

Examples

# Display status information for the QSFP transceiver module in interface HundredGigE 3/1/1.

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

HundredGigE3/1/1 transceiver status information:

Initialization Complete Flag : Finish

Power Mode : High

Lane Tx Disable Tx CDR Rx CDR

Lane1 Yes ON OFF

Lane2 Yes ON OFF

Lane3 Yes ON OFF

Lane4 Yes ON OFF

Table 29 Command output

Field	Description
Initialization Complete Flag	Whether the transceiver module has finished initialization: · Finish—The initialization has finished. · Unkown—No initialization status is detected.
Power Mode	Power mode of the transceiver module: · High. · Low.
Tx Disable	Whether packet transmission is enabled for a lane: · Yes—Packet transmission is disabled. · No—Packet transmission is enabled.
Tx CDR	Whether CDR on the transmit side is enabled: · On—Tx CDR is enabled. · Off—Tx CDR is disabled.
Rx CDR	Whether CDR on the receive side is enabled: · On—Rx CDR is enabled. · Off—Rx CDR is disabled.
Lane	Lane ID.

‌

# Display status information for the SFP transceiver module in interface Ten-GigabitEthernet 3/1/1.

<Sysname> display transceiver status interface ten-gigabitethernet 3/1/1

Ten-GigabitEthernet3/1/1 transceiver status information:

Hardware Tx Disable : YES

Table 30 Command output

Field

Description

Hardware Tx Disable

Whether packet transmission is enabled for a lane via hardware pins:

· Yes—Packet transmission is disabled.

· No—Packet transmission is enabled.

‌

Related commands

reset transceiver interface

transceiver cdr

transceiver lane enable

transceiver power-mode

display version

Use display version to display system version information.

Syntax

display version

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display system version information.

<Sysname> display version

display version-update-record

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

Syntax

display version-update-record

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

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

Examples

# Display the startup software image upgrade records.

<Sysname> display version-update-record

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

*Name : boot-test.bin

Version : 7.1.053 Alpha 7153

Compile time: Mar 25 2014 15:52:43

*Name : system-test.bin

Version : 7.1.053 Alpha 7153

Compile time: Mar 25 2014 15:52:43

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

fan-speed

Use fan-speed to set the fan operating mode.

Use undo fan-speed to restore the default.

Syntax

In standalone mode:

fan-speed { auto | high | middle | low }

undo fan-speed

In IRF mode:

fan-speed [ chassis chassis-number ] { auto | high | middle | low }

undo fan-speed

Default

Fans operate in auto mode.

Views

System view

Predefined user roles

network-admin

Parameters

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

auto: Operates at an adjustable speed. The device adjusts the speed automatically based on the card temperature. As a best practice, use this mode.

high: Operates at a higher speed to provide better cooling service.

middle: Operates at a middle speed.

low: Operates at a lower speed to reduce the noise at the cost of lower cooling service quality. This mode applies to noise-sensitive environments.

Examples

# (In standalone mode.) Set the fan operating mode to auto.

<Sysname> system-view

[Sysname] fan-speed auto

Fan speed changed successfully!

forward per-packet

Use forward per-packet to specify the per-packet load sharing forwarding mode.

Use undo forward per-packet to restore the default.

Syntax

In standalone mode:

forward per-packet [ slot slot-number ]

undo forward per-packet [ slot slot-number ]

In IRF mode:

forward per-packet [ chassis chassis-number slot slot-number ]

undo forward per-packet [ chassis chassis-number slot slot-number ]

Default

The per-flow load sharing forwarding mode is used.

Views

System 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 available only for testing.

In the per-packet load sharing forwarding mode, when the device forwards packets from service modules to switching fabric modules, the packets are forwarded in sequence for load sharing.

In the per-flow load sharing forwarding mode, when the device forwards packets from service modules to switching fabric modules, the packets are distributed into different flows according to specific rules before being forwarded.

Switching the load sharing forwarding mode might cause packet loss. Contact Technical Support before executing this command.

Examples

# Specify the per-packet load sharing forwarding mode.

<Sysname> system-view

[Sysname] forward per-packet

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

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 { chip | forwarding } { isolate | off | reset | warning }

undo hardware-failure-detection { chip | forwarding }

Default

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

Views

System view

Predefined user roles

network-admin

Parameters

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

The system 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 executed.

When the hardware-failure-protection aggregation command is executed, 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 executed 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 executed 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 executed 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 executed on the interface.

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

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

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 Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] hardware-failure-protection auto-down

header

Use header to configure a banner.

Use undo header to delete a banner.

Syntax

header { legal | login | motd | shell } text

undo header { legal | login | motd | shell }

Default

No banner is configured.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

shell: Configures the banner to be displayed before a user accesses user view.

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

Examples

# Configure the legal banner.

<Sysname> system-view

[Sysname] header legal

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

Welcome to use the legal banner%

isolate fabric-number

Use isolate fabric-number to specify the number of switching fabric modules that can be automatically isolated by the system.

Use undo isolate fabric-number to restore the default.

Syntax

isolate fabric-number fabric-number

undo isolate fabric-number

Default

The number of switching fabric modules that can be automatically isolated by the system is 1.

Views

System view

Predefined user roles

network-admin

Parameters

fabric-number: Specifies the number of switching fabric modules, in the range of 0 to 3.

Usage guidelines

After you use this command, the system automatically isolates switching fabric modules when a failure is detected on switching fabric modules. If the device has four switching fabric modules, a maximum of two switching fabric modules can be isolated. If the device has five switching fabric modules, a maximum of three switching fabric modules can be isolated.

This command does not take effect when the number of switching fabric modules is less than or equal to 2 on the device.

Examples

# Specify the number of switching fabric modules that can be automatically isolated by the system as 2.

<Sysname> system-view

[Sysname] isolate fabric-number 2

This command might cause packet loss. Continue? [Y/N]:

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

Parameters

channel-number: Specifies the ITU channel number.

Usage guidelines

This command is available only for the HPE X130 10G SFP+ LC LH80 tunable Transceiver (JL250A), SFP-XG-LH80-Tunable, and CFP2-200G-DCO-Tunable transceiver modules.

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 3/1/1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/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

Parameters

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

Usage guidelines

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

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

Examples

# Assign the save-job job to the saveconfig schedule.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] job save-job

Related commands

scheduler job

scheduler schedule

memory-threshold

Use memory-threshold to set free-memory thresholds.

Use undo memory-threshold to restore the default.

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

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

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. This threshold must be equal to or less than the normal state threshold. Setting this threshold to 0 disables the minor alarm feature.

severe severe-value: Specifies the severe alarm threshold. This threshold must be equal to or less than the minor alarm threshold. Setting this threshold to 0 disables the severe alarm feature.

critical critical-value: Specifies the critical alarm threshold. This threshold must be equal to or less than the severe alarm threshold. Setting this threshold to 0 disables the critical alarm feature.

normal normal-value: Specifies the normal state threshold. This threshold must be equal to or less than the total memory size.

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

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.

For more information about the alarm 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

Related commands

display memory-threshold

memory-threshold dma

Use memory-threshold dma to set DMA memory thresholds.

Use undo memory-threshold dma to restore the default.

Syntax

In standalone mode:

memory-threshold dma [ slot slot-number [ cpu cpu-number ] ] [ ratio ] critical critical-value normal normal-value

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

In IRF mode:

memory-threshold dma [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ ratio ] critical critical-value normal normal-value

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

Default

The DMA memory alarm threshold is 2048 KB, and the normal state threshold is 4096 KB.

Views

System view

Predefined user roles

network-admin

network-operator

Parameters

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

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

ratio: Specifies DMA memory thresholds in percentage.

critical critical-value: Specifies the DMA memory alarm threshold. If the ratio keyword is specified, the value range for the critical-value argument is 1 to 100 in percentage. If the ratio keyword is not specified, the value range is 0 to 3145728.

normal normal-value: Specifies the normal state threshold. If the ratio keyword is specified, the value range for the normal-value argument is 1 to 100 in percentage. If the ratio keyword is not specified, the value is in the range of critical-value to 3145728.

Usage guidelines

To ensure correct operation of the services that require DMA memory, the system monitors the amount of free DMA memory space regularly. If the amount of free DMA memory space decreases to or below the alarm threshold, the system generates a notification indicating that the DMA memory space is insufficient. If the amount of free DMA memory space increases above the normal state threshold, the system generates a notification indicating that the DMA memory space is sufficient.

Examples

# (In standalone mode.) Set the DMA memory alarm threshold and the normal state threshold to 32KB and 96 KB, respectively, for slot 1.

<System> system-view

[System] memory-threshold dma slot 1 critical 32 normal 96

memory-threshold usage

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

Use undo memory-threshold usage to restore the default.

Syntax

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

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

Examples

# Set the memory usage threshold to 80%.

<Sysname> system-view

[Sysname] memory-threshold usage 80

Related commands

display memory-threshold

memory-threshold usage resend-interval

Use memory-threshold usage resend-interval to set the memory usage alarm resending interval.

Use undo memory-threshold usage resend-interval to restore the default.

Syntax

In standalone mode:

memory-threshold [ slot slot-number [ cpu cpu-number ] ] usage resend-interval interval-value

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

In IRF mode:

memory-threshold [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] usage resend-interval interval-value

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

Default

The memory usage alarm resending interval is 300 seconds.

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 interval for the active MPU. (In standalone mode.)

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

resend-intervel interval-value: Specifies the memory usage alarm resending interval in the range of 1 to 3600, in minutes.

Usage guidelines

The device samples memory usage periodically, and compares the sampled value with the memory usage thresholds. If the sampled value exceeds an alarm threshold, the device enters alarm state and generates an alarm (log and trap) to notify the administrator. If the memory usage remains in the alarm state after the memory usage alarm resending interval is reached, the device outputs the alarm again.

Examples

# In standalone mode:Set the memory usage alarm resending interval to 60 minutes for CPU 0 in slot 1.

<Sysname> system-view

[Sysname] memory-threshold slot 1 cpu 0 usage resend-interval 60

monitor cpu-usage enable

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

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

Syntax

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

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 the default.

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

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 threshold

Use monitor cpu-usage threshold to set the CPU usage threshold.

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

Syntax

In standalone mode:

monitor cpu-usage threshold cpu-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 cpu-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

The severe CPU usage alarm threshold is 99%. The minor CPU usage alarm threshold is 79%. The CPU usage recovery threshold is 69%.

Views

System view

Predefined user roles

network-admin

Parameters

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

minor-threshold minor-threshold: Specifies the minor CPU usage alarm threshold in percentage. The value range for this argument is 1 to the severe CPU usage alarm threshold minus 1. If you do not specify this option, the minor CPU usage alarm threshold is 80 percent of the severe CPU usage alarm threshold.

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. If you do not specify this option, the CPU usage recovery threshold is 70 percent of the severe CPU usage alarm threshold.

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

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

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

Usage guidelines

CAUTION:

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

The device samples CPU usage at 1-minute intervals. If the sample is greater than a CPU usage alarm threshold, the device sends a trap. If the sample is equal to or less than the CPU usage recovery threshold, the device determines that the CPU usage is normal.

Examples

# Set the severe CPU usage threshold to 80%.

<Sysname> system-view

[Sysname] monitor cpu-usage threshold 80

Related commands

display cpu-usage configuration

monitor disk-usage disk

Use monitor disk-usage disk to set the disk usage threshold.

Use undo monitor disk-usage disk to restore the default.

Syntax

In standalone mode:

monitor disk-usage [ slot slot-number [ cpu cpu-number ] ] disk disk-name threshold threshold-value

undo monitor disk-usage [ slot slot-number [ cpu cpu-number ] ] disk disk-name threshold

In IRF mode:

monitor disk-usage [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] disk disk-name threshold threshold-value

undo monitor disk-usage [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] disk disk-name threshold

Default

The disk usage threshold is 95%.

Views

System view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, the command applies to the active MPU. (In standalone mode.)

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

disk disk-name: Specifies a disk by its name. This option is case sensitive. The system will prompt a parameter error if you enter this option incorrectly.

threshold threshold-value: Specifies the disk usage threshold in percentage, in the range of 1 to 100.

Usage guidelines

After you set the disk usage threshold, the device compares the usage of the disk with the threshold at each sampling. If the usage exceeds the threshold, the device sends a high disk usage alarm to the NETCONF module. For more information about the NETCONF module see Network Management and Monitoring Configuration Guide.

Examples

# Set the disk usage threshold to 80%.

<Sysname> system-view

[Sysname] monitor disk-usage disk flash threshold 80

Related commands

monitor disk-usage interval

Use monitor disk-usage interval to set the disk usage sampling interval.

Use undo monitor disk-usage interval to restore the default.

Syntax

monitor disk-usage interval interval

undo monitor disk-usage interval

Default

The disk usage sampling interval is 300 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

interval interval-time: Specifies the disk usage sampling interval in seconds, a multiple of 5 in the range of 5 to 1800.

Usage guidelines

After you set the disk usage sampling interval, the device samples the disk usage at the specified intervals.

Examples

# Set the disk usage sampling interval to 120 seconds.

<Sysname> system-view

[Sysname] monitor disk-usage interval 120

Related commands

monitor disk-usage disk

monitor kernel memory fragment interval

Use monitor kernel memory fragment interval to set the interval for collecting kernel memory fragment information.

Use undo monitor kernel memory fragment interval to restore the default.

Syntax

In standalone mode:

monitor kernel memory fragment interval interval-value [ slot slot-number [ cpu cpu-number ] ]

undo monitor kernel memory fragment interval [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

monitor kernel memory fragment interval interval-value [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

undo monitor kernel memory fragment interval [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Default

The interval is five minutes for collecting kernel memory fragment information.

Views

System view

Predefined user roles

network-admin

network-operator

Parameters

interval-value: Specifies the interval in minutes. The value range is 1 to 65535.

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

The device collects kernel memory fragment statistics at the intervals specified by this command. To view the statistics and identify whether the kernel memory fragment ratio is normal, execute the display kernel memory fragment free command.

Examples

# Set the interval for collecting memory fragment information to 5 minutes.

<System> system-view

[System] monitor kernel memory fragment interval 5

monitor kernel memory fragment ratio

Use monitor kernel memory fragment ratio to set the kernel memory fragment ratio alarm threshold.

Use undo monitor kernel memory fragment ratio to restore the default.

Syntax

In standalone mode:

monitor kernel memory fragment ratio ratio-value [ slot slot-number [ cpu cpu-number ] ]

undo monitor kernel memory fragment ratio [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

monitor kernel memory fragment ratio ratio-value [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

undo monitor kernel memory fragment ratio [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Default

The kernel memory fragment ratio alarm threshold is 20%.

Views

System view

Predefined user roles

network-admin

network-operator

Parameters

ratio ratio-value: Specifies the kernel memory fragment ratio alarm threshold in percentage, in the range of 1 to 100.

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

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

Usage guidelines

A running kernel thread's process requires memory allocation from the system. The system allocates and releases this memory as a whole. If the process is still running and some memory blocks have been used but are no longer used, these memory blocks will not be released in advance. These free but currently unusable memory blocks are also referred to as memory fragments.

This command enables the device to monitor the kernel memory fragment ratio. If the kernel memory fragment ratio decreases to or below the alarm threshold, the kernel memory usage is low and an alarm notification is generated. If the kernel memory fragment ratio increases above the alarm threshold, the kernel memory usage returns to the normal state and a recovery notification is generated.

Examples

# (In standalone mode.) Set the kernel memory fragment ratio alarm threshold to 80 for a slot.

<System> system-view

[System] monitor kernel memory fragment ratio 80 slot 1

monitor resend cpu-usage

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

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

Syntax

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 CPU usage alarm resending interval is 300 seconds. The severe CPU usage alarm resending interval is 60 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

The device samples CPU usage at intervals, and compares the samples with CPU usage thresholds to identify the CPU usage status and send alarms or notifications accordingly.

In minor alarm state, the device sends minor alarms periodically until the CPU usage increases above the severe threshold or the minor alarm is removed. In severe alarm state, the device sends severe alarms periodically until the severe alarm is removed. This command sets the alarm resending intervals.

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

Examples

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

<Sysname> system-view

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

monitor resend cpu-usage core-interval

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

The minor CPU core usage alarm resending interval is 300 seconds and severe CPU core usage alarm resending interval is 60 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

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

Usage guidelines

The device samples CPU core usage at intervals, and compares the samples with CPU core usage thresholds to identify the CPU core usage status and send alarms or notifications accordingly.

In minor alarm state, the device sends minor alarms periodically until the CPU core usage increases above the severe threshold or the minor alarm is removed. In severe alarm state, the device sends severe alarms periodically until the severe alarm is removed. This command sets the alarm resending intervals.

Examples

# Set the resending interval for minor CPU core usage alarms to 100 seconds and the resending interval for severe CPU core usage alarms 60 seconds.

<Sysname> system-view

[Sysname] monitor resend cpu-usage core-interval minor-interval 100 severe-interval 60

monitor resend memory-threshold

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

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

Syntax

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

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 sampled value with free-memory thresholds. If the sampled value decreases to or below a threshold, the device enters a memory depletion alarm state and sends an alarm.

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

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

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

Examples

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

monitor resend memory-threshold dma

Use monitor resend memory-threshold dma to set the DMA memory alarm resending interval.

Use undo monitor resend memory-threshold dma to restore the default.

Syntax

In standalone mode:

monitor resend memory-threshold dma critical-interval critical-interval [ slot slot-number [ cpu cpu-number ] ]

undo monitor resend memory-threshold dma critical-interval [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

monitor resend memory-threshold dma critical-interval critical-interval [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

undo monitor resend memory-threshold dma critical-interval [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Default

The DMA memory alarm resending interval is 300 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

critical-interval critical-interval: Specifies the resending interval for the DMA memory alarms in seconds, a multiple of 5 in the range of 10 to 3600.

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

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

Usage guidelines

The device samples DMA memory usage at intervals, and compares the samples with the DMA memory alarm threshold to identify the DMA memory usage status and send alarms or notifications accordingly.

Examples

# Set the resending interval for the DMA memory alarms to 100 seconds.

<Sysname> system-view

[Sysname] monitor resend memory-threshold dma critical-interval 100<Sysname> system-view

password-recovery enable

Use password-recovery enable to enable password recovery capability.

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

Syntax

password-recovery enable

undo password-recovery enable

Default

Password recovery capability is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

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

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

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

To enhance system security, disable password recovery capability.

To access the device configuration without authentication, you must connect to the active MPU and access the BootWare menu while the MPU is starting up.

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

Examples

# Disable password recovery capability.

<Sysname> system-view

[Sysname] undo password-recovery enable

power control-mode

Use power control-mode to set the card power-on control mode.

Use undo power control-mode to restore the default.

Syntax

power control-mode { loose | strict }

undo power control-mode

Default

The card power-on control mode is strict.

Views

System view

Predefined user roles

network-admin

Parameters

loose: Specifies the loose mode.

strict: Specifies the strict mode.

Usage guidelines

When you install a service module or switching fabric module, the device calculates the following items:

· Total power reserved for fans and MPUs.

· Total maximum power of all service modules and switching fabric modules, including the newly installed module.

In strict mode, the device powers on the newly installed module only if the sum of the two items is equal to or less than the rated power of the device.

In loose mode, the device powers on the newly installed module as long as the sum of the two items is equal to or less than the rated power of the device * 1.2.

Examples

# Set the card power-on control mode to loose.

<Sysname> system-view

[Sysname] power control-mode loose

power-off high-temp-board clear

Use power-off high-temp-board clear to restore power supply for cards shut down because of overtemperature.

Syntax

In standalone mode:

power-off high-temp-board clear

In IRF mode:

power-off high-temp-board clear chassis chassis-number

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

When the temperature on a card reaches the shutdown temperature threshold, the overtemperature auto shutdown feature automatically shuts down the card. You can use this command to power on the card as appropriate.

Examples

# Restore power supply for cards shut down because of overtemperature.

<Sysname> system-view

[Sysname] power-off high-temp-board clear

power-off high-temp-board enable

Use power-off high-temp-board enable to enable the overtemperature auto shutdown feature.

Syntax

power-off high-temp-board enable

undo power-off high-temp-board enable

Default

The overtemperature auto shutdown feature is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

When the temperature on a card reaches the shutdown temperature threshold, the overtemperature auto shutdown feature automatically shuts down the card.

Examples

# Enable the overtemperature auto shutdown feature.

<Sysname> system-view

[Sysname] power-off high-temp-board enable

Related commands

display power-off high-temp-board

reboot

Use reboot to reboot the device.

Syntax

In standalone mode:

reboot [ slot slot-number [ cpu cpu-number | subslot subslot-number ] ] [ force ]

In IRF mode:

reboot [ chassis chassis-number [ slot slot-number [ cpu cpu-number | subslot subslot-number ] ] ] [ force ]

Views

User view

Predefined user roles

network-admin

Parameters

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

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

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

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

subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subslot number, the command reboots the slot.

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

Usage guidelines

CAUTION:

· A reboot might interrupt network services.

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

‌

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

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

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

receive

Use receive to specify a packet receiving mode for load balancing.

Use undo receive to restore the default.

Syntax

receive { per-flow { non-dip | non-sip } | per-packet }

undo receive

Default

The per-flow packet receiving mode is specified for load balancing.

Views

System view

Predefined user roles

network-admin

Parameters

per-flow: Specifies the per-flow mode. In this mode, after receiving packets, an interface divided the packets into different flows, and then send these flows to CPUs. The packets of the same flow are sent through the same link.

per-packet: Specifies the per-packet mode. In this mode, after an interface receives packets, the packets are load-balanced to each link based on the receiving sequence, and then are sent to CPUs.

non-dip: Configures the packet receiving mode for load balancing to be independent of destination IP addresses.

non-sip: Configures the packet receiving mode for load balancing to be independent of source IP addresses.

Usage guidelines

This command is available only for testing.

This command is supported only on the IM-SFMX card.

Contact Technical Support before executing this command.

Examples

# Set the packet receiving mode for load balancing to per-packet.

<Sysname> system

[Sysname] receive per-packet

reset scheduler logfile

Use reset scheduler logfile to clear job execution log information.

Syntax

reset scheduler logfile

Views

User view

Predefined user roles

network-admin

Examples

# Clear job execution log information.

<Sysname> reset scheduler logfile

Related commands

display scheduler logfile

reset transceiver interface

Use reset transceiver interface to reset a QSFP transceiver module.

Syntax

reset transceiver interface [ interface-type interface-number ]

Views

User view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command applies to all interfaces.

Usage guidelines

This command is disruptive. Use this command only when you cannot troubleshoot transceiver modules by using other methods.

This command will restart the transceiver module.

Examples

# Reset the QSFP transceiver module in HundredGigE 3/1/1.

<Sysname> reset transceiver interface hundredgige 3/1/1

This operation causes services on the transceiver module to be down for a while. Continue? [Y/N]: Y

reset version-update-record

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

Syntax

reset version-update-record

Views

System view

Predefined user roles

network-admin

Examples

# Clear the startup software image upgrade records.

<Sysname> system-view

[Sysname] reset version-update-record

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

Related commands

display version-update-record

resource-monitor minor resend enable

Use resource-monitor minor resend enable to enable resending of minor resource depletion alarms.

Use undo resource-monitor minor resend enable to disable resending of minor resource depletion alarms.

Syntax

resource-monitor minor resend enable

undo resource-monitor minor resend enable

Default

Resending of minor resource depletion alarms is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

When a resource type enters minor alarm state, the device issues a minor alarm. If the resource type stays in minor alarm state or changes from severe alarm state to minor alarm state, the device identifies whether resending of minor resource depletion alarms is enabled. If the feature is disabled, the device does not issue additional minor alarms. If the feature is enabled, the device resends minor alarms periodically.

The resending period is fixed at 24 hours for a severe alarm and is fixed at 7 * 24 hours for a minor alarm.

Examples

# Enable resending of minor resource depletion alarms.

<Sysname> system-view

[Sysname] resource-monitor minor resend enable

Related commands

display resource-monitor

resource-monitor output

resource-monitor resource

resource-monitor output

Use resource-monitor output to specify destinations for resource depletion alarms.

Use undo resource-monitor output to remove destinations for resource depletion alarms.

Syntax

resource-monitor output { netconf-event | snmp-notification | syslog } *

undo resource-monitor output [ netconf-event | snmp-notification | syslog ] *

Default

Resource depletion alarms are sent to NETCONF, SNMP, and the information center.

Views

System view

Predefined user roles

network-admin

Parameters

netconf-event: Sends resource depletion alarms to the NETCONF feature to encapsulate the alarms in NETCONF events. For more information, see NETCONF in Network Management and Monitoring Configuration Guide.

snmp-notification: Sends resource depletion alarms to the SNMP feature to encapsulate the alarms in SNMP traps and informs. For more information, see SNMP in Network Management and Monitoring Configuration Guide.

syslog: Sends resource depletion alarms to the information center to encapsulate the alarms in log messages. For more information, see information center in Network Management and Monitoring Configuration Guide.

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] resource-monitor output syslog

Related commands

resource-monitor minor resend enable

resource-monitor resource

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-absolute | 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-absolute | 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. The resource types that can be monitored are as shown in Table 32. The resource types that can be monitored vary by card.

Table 32 Resource types that can be monitored

Resource type	Description
acl_car	CAR template resources.
acl_counter	ACL counter resources.
arp	ARP resources.
arpnd	ARP and ND resources.
bfd_hardbfd_session	Hardware BFD sessions
bpa_counter_in	Inbound BGP statistics resources.
bpa_counter_out	Inbound BGP statistics resources.
cfd_counterid_index	CFD counterid index resources.
cfd_watchdog_index	CFD watchdog index resources.
ecmp	ECMP resources.
efp_acl	Outbound ACL resources.
eth_subif_statistic	Route subinterface statistics counter resources.
flow_mirror	Flow mirror resources.
Ifp_acl	Inbound ACL resources.
ipmc	Layer 3 multicast replication table resources.
ipv4_acl	IPv4 ACL resources.
ipv4_defip	IPv4 route reources.
ipv4fib	IPv4 FIB hardware entry resources.
ipv4mc	IPv4 multicast forwarding entry resources.
ipv6_acl	IPv6 ACL resources.
ipv6_defip	IPv6 route resources.
ipv6_defip64	Resources for IPv6 routes with a prefix length of 0 to 64 bits.
ipv6_defip128	Resources for IPv6 routes with a prefix length of 65 to 128 bits.
ipv6_sr_list	SRv6 list resources
ipv6fib	IPv6 FIB hardware entry resources.
ipv6mc	IPv6 multicst forwarding entry resources.
mac	MAC address table resources.
maptable_in	Inbound flexible priority mapping table resources.
maptable_out	Outbound flexible priority mapping table resources.
mpls_cbts	CBTS statistics resources.
mpls_dynvpnid	VXLAN flooding MAC resources.
mpls_ecmplsp	ECMP LSP resources.
mpls_ilm	ILM label resources.
mpls_inlabel	Inbound MPLS label resources.
mpls_l3vpn	Number of L3VPN instances.
mpls_label	Label index resources.
mpls_lsp	MPLS LSP statistics resources.
mpls_outlabel	Outbound MPLS label resources.
mpls_te	Configured number of MPLS TE tunnels
mpls_outlif	MPLS outlif resources.
mpls_vp	MPLS VP resources.
mpls_vpls_pw	Number of PWs for VPLS instances
mpls_vpws	Configured VPWS number.
mpls_vsi	Number of VSIs.
mpls_vxlan_tunnel	Number of VXLAN tunnels.
mpls_vxlanvni	VXLAN private wire statistics resources.
mtunnel	Multicast tunnel interface resources.
mpls_tecar_profile	Profile resources for CAR rate limit of MPLS TE tunnels.
mpls_tecar_tb	TB resources for CAR rate limit of MPLS TE tunnels.
nd	ND resources.
nexthop	Next hop resources.
nqa_client_1564	Number of NQA client 1564 sessions.
nqa_client_2544	Number of NQA client 2544 sessions.
nqa_client_twamplight	Number of NQA client twamp sessions.
nqa_reflector_remote	Number of NQA server 1564 and 2544 sessions.
nqa_reflector_twamplight	NQA servertwamp sessions.
nqa_veinlif	NQA VEinlif resources.
port_shape	Main interface shaping resources.
qinq_inlif_0	Subinterface QinQ Inlif entry resources where 0 indicates forwarding chip ID.
qinq_inlif_tree_0	Subinterface QinQ Inlif tree entry resources, where 0 indicates forwarding chip ID.
qos_queue	QoS eight-queue resources.
queue_shape	Queue shaping resources.
queue_buffer	Queue buffering resources.
rport	Protocol port entry resources.
sampler	Sampler resources.
share_policy_in	Inbound shared MQC resources.
share_policy_out	Outbound shared MQC resources.
subif_tb_in	Inbound subinterface statistics resources.
subif_tb_out	Outbound subinterface statistics resources.
subport_shape	Subinterface shaping resources.
tunnel	Tunnel interface resources.
v4mcpro	IPv4 multicast entry resources.
v6mcpro	IPv6 multicast entry resources.
vfp_acl	VLAN-related ACL resources.
wfq_weight	Weight resources for weighted fair queuing.
wred_table	WRED template resources.
bras_out	Outbound BRAS user count resources.
bras_in	Inbound BRAS user count resources.
bras_car	CAR profile resources used by BRAS users.

‌

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

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

by-absolute: Specifies resource depletion thresholds by using absolute values.

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

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 arpnd slot 1 cpu 0 by-percent minor-threshold 30 severe-threshold 10

Related commands

display resource-monitor

resource-monitor minor resend enable

resource-monitor output

restore factory-default

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

Syntax

restore factory-default

Views

User view

Predefined user roles

network-admin

Usage guidelines

CAUTION:

This command restores the device to the factory default settings. Before using this command, make sure you fully understand its impact on your live network.

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

The command takes effect after the device reboots.

Examples

# Restore the factory-default configuration for the device.

<Sysname> restore factory-default

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

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

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

Related commands

reboot

scheduler job

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

Use undo scheduler job to delete a job.

Syntax

scheduler job job-name

undo scheduler job job-name

Default

No job exists.

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

# Create a job named backupconfig and enter job view.

<Sysname> system-view

[Sysname] scheduler job backupconfig

[Sysname-job-backupconfig]

Related commands

command

scheduler schedule

scheduler logfile size

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

Syntax

scheduler logfile size value

Default

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

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] scheduler logfile size 32

Related commands

display scheduler logfile

scheduler reboot at

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

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot at time [ date ]

undo scheduler reboot

Default

No reboot date or time is specified.

Views

User view

Predefined user roles

network-admin

Parameters

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

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

Usage guidelines

CAUTION:

This command enables the device to reboot at a scheduled time, which causes service interruption. Before using this command, make sure you fully understand its impact on your live network.

‌

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

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

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

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

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

Examples

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

<Sysname> scheduler reboot at 12:00

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

Related commands

scheduler reboot delay

Use scheduler reboot delay to specify the reboot delay time.

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot delay time

undo scheduler reboot

Default

No reboot delay time is specified.

Views

User view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

CAUTION:

This command enables the device to reboot at a scheduled time, which causes service interruption. Before using this command, make sure you fully understand its impact on your live network.

‌

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

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

Examples

# Configure the device to reboot after 88 minutes. This example assumes that the current time is 11:48 a.m. on June 6, 2011.

<Sysname> scheduler reboot delay 88

Reboot system at 13:16 06/06/2011(in 1 hours and 28 minutes). Confirm? [Y/N]:

scheduler schedule

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

Use undo scheduler schedule to delete a schedule.

Syntax

scheduler schedule schedule-name

undo scheduler schedule schedule-name

Default

No schedule exists.

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

To configure a schedule:

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

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

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

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

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

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

Examples

# Create a schedule named saveconfig.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

Related commands

job

time at

time once

shutdown-interval

Use shutdown-interval to set the port status detection timer.

Use undo shutdown-interval to restore the default.

Syntax

shutdown-interval interval

undo shutdown-interval

Default

The port status detection timer setting is 30 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the port status detection timer value in seconds. The value range is 0 to 300. The value of 0 indicates that port status detection is not automatically performed, and you need to execute the undo shutdown command to restore the port status manually.

Usage guidelines

The device starts a port status detection timer when a port is shut down by a protocol. If the port has been in down state before the timer expires, the device will set the port status to the port's physical status.

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

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

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

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

Examples

# Set the port status detection timer to 100 seconds.

<Sysname> system-view

[Sysname] shutdown-interval 100

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:

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

· 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 does not isolate an MPU.

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 or a channel from the system. Continu

e? [Y/N]y

switch-fabric removal-signal-report enable

Use switch-fabric removal-signal-report enable to enable removal interrupt signal reporting from switching fabric modules.

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

Syntax

switch-fabric removal-signal-report enable

undo switch-fabric removal-signal-report enable

Default

Removal interrupt signal reporting is disabled for switching fabric modules

Views

System view

Predefined user roles

network-admin

Usage guidelines

After this command is used, 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 avoid service interruption.

Examples

# Enable removal interrupt signal reporting from switching fabric modules.

<Sysname> system-view

[Sysname] switch-fabric removal-signal-report enable

sysname

Use sysname to set the device name.

Use undo sysname to restore the default.

Syntax

sysname sysname

undo sysname

Default

The device name is H3C.

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

# Set the name of the device to R2000.

<Sysname> system-view

[Sysname] sysname R2000

[R2000]

system forward-mode extended

Use system forward-mode extended to set the system forwarding mode to extended.

Use undo system forward-mode extended to restore the default.

Syntax

system forward-mode extended

undo system forward-mode extended

Default

The system forwarding mode is standard.

Views

System view

Predefined user roles

network-admin

Usage guidelines

In standard mode, the device operates in good condition.

In extended mode, the device records the logs of forwarding modules. This mode is used only for device maintenance.

A system forwarding mode change takes effect after a device reboot.

Examples

# Set the system forwarding mode to extended.

<Sysname> system

[Sysname] system forward-mode extended

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

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

system turbo enable

Use system turbo enable to enable system performance optimization.

Use undo system turbo enable to disable system performance optimization.

Syntax

system turbo enable

undo system turbo enable

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is available only for testing.

Contact Technical Support before using this command.

Examples

# Enable system performance optimization.

<Sysname> system

[Sysname] system turbo enable

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{ sdn-wan | standard }

undo system-working-mode

Default

The device operates in standard mode.

Views

System view

Predefined user roles

network-admin

Parameters

sdn-wan:Sets the system operating mode to SDN-WAN.

standard: Sets the system operating mode to standard.

Usage guidelines

The supported features and the specifications of the supported features vary by system operating mode.

Change to the operating mode takes effect after a reboot.

Examples

# Set the system operating mode to SDN-WAN.

<Sysname> system-view

[Sysname] system-working-mode sdn-wan

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.

Related commands

display system-working-mode

subslot-working-mode

Use subslot-working-mode to set the operating mode of a subslot for a subcard.

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

Syntax

In standalone mode:

subslot-working-mode slot slot-number subslot subslot-number { ethernet | ethernet-flexe }

undo subslot-working-mode slot slot-number subslot subslot-number [ ethernet | ethernet-flexe ]

In IRF mode:

subslot-working-mode chassis chassis-number slot slot-number subslot subslot-number { ethernet | ethernet-flexe }

undo subslot-working-mode chassis chassis-number slot slot-number subslot subslot-number [ ethernet | ethernet-flexe ]

Default

The operating mode is ethernet.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

ethernet: Sets the subslot operating mode to ethernet. In this mode, an interface of the subcard installed to the specified subslot supports only standard Ethernet mode.

ethernet-flexe: Sets the subslot operating mode to ethernet-flexe. In this mode, an interface of the subcard installed to the specified subslot supports switching between standard Ethernet mode and flexible Ethernet mode.

Usage guidelines

This command is supported only the RX-NIC-LGQ4L subcard.

If a subcard installed in the specified subslot does not support this feature, the feature setting will be deleted or fails to be configured.

For information about switching between standard Ethernet mode and flexible Ethernet mode, see FlexE interface configuration in Interface Configuration Guide.

Follow these restrictions and guidelines:

· The subcard on the subslot reboots for the configuration to take effect.

· The device removes the settings not supported by the subcard interfaces in the subslot in the current operating mode.

Examples

# Set the operating mode of subslot 2 to ethernet-flexe.

<Sysname> system

[Sysname] subslot-working-mode slot 3 sublot 2 ethernet-flexe

Change of the subslot working mode will reboot the subcard. Continue? [Y/N]:

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

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.

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

Parameters

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

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

Usage guidelines

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

The time at command, the time once command, and the time repeating command overwrite each other. The most recently executed command takes effect.

Examples

# Configure the device to execute the saveconfig schedule at 01:01 a.m. on May 11, 2011.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time at 1:1 2011/05/11

Related commands

scheduler schedule

time once

Use time once to specify one or more execution days and the execution time for a non-periodic schedule.

Use undo time to delete the execution day and time configuration for a non-periodic schedule.

Syntax

time once at time [ month-date month-day | week-day week-day&<1-7> ]

time once delay time

undo time

Default

No execution time or day is specified for a non-periodic schedule.

Views

Schedule view

Predefined user roles

network-admin

Parameters

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

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

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

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

Usage guidelines

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

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

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

The time at command, the time once command, and the time repeating command overwrite each other. The most recently executed command takes effect.

Examples

# Configure the device to execute the saveconfig schedule once at 15:00.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 15:00

Schedule starts at 15:00 5/11/2011.

# Configure the device to execute the saveconfig schedule once at 15:00 on the coming 15th day in a month.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 15:00 month-date 15

# Configure the device to execute the saveconfig schedule at 12:00 p.m. on the coming Monday and Friday.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 12:00 week-day mon fri

# Configure the device to execute the saveconfig schedule after 10 minutes.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once delay 10

Related commands

scheduler schedule

time repeating

Use time repeating to specify an execution time table for a periodic schedule.

Use undo time to delete the execution time table configuration for a periodic schedule.

Syntax

time repeating [ at time [ date ] ] interval interval

time repeating at time [ month-date [ month-day | last ] | week-day week-day&<1-7> ]

undo time

Default

No execution time table is specified for a periodic schedule.

Views

Schedule view

Predefined user roles

network-admin

Parameters

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

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

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

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

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

Usage guidelines

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

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

The time at command, the time once command, and the time repeating command overwrite each other, whichever is executed most recently takes effect.

Examples

# Configure the device to execute the saveconfig schedule once an hour from 8:00 a.m. on.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 interval 60

# Configure the device to execute the saveconfig schedule at 12:00 p.m. every day.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 12:00

# Configure the device to execute the saveconfig schedule at 8:00 a.m. on the 5th of every month.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 month-date 5

# Configure the device to execute the saveconfig schedule at 8:00 a.m. on the last day of every month.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 month-date last

# Configure the device to execute the saveconfig schedule at 8:00 a.m. every Friday and Saturday.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 week-day fri sat

Related commands

scheduler schedule

transceiver lane cdr

Use transceiver lane cdr to configure CDR on a transmit or receive lane for a QSFP transceiver module.

Use undo transceiver lane cdr to restore the default.

Syntax

transceiver lane [ lane-number ] cdr { tx | rx } { on | off }

undo transceiver lane [ lane-number ] cdr { tx | rx }

Default

CDR is enabled on a transmit or receive lane on a QSFP transceiver module.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

lane-number: Specifies a transceiver lane number, in the range of 1 to 4. If you do not specify a transceiver lane, the command applies to all transceiver lanes.

tx: Specifies the transmit link on the transceiver module.

rx: : Specifies the receive link on the transceiver module.

on: Enables CDR.

off: Disables CDR.

Usage guidelines

Enabling CDR can reduce the jitter to improve transmission performance, and disabling CDR degrades transmission performance. Both the enable and disable operations might cause oscillation on device ports.

The configuration by this command is saved in a register on the transceiver module. It is not saved to the configuration file.

This command is supported only on the QSFP transceiver modules.

Examples

# Enable CDR on the transmit side on the QSFP transceiver module in interface HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 3/1/1

[Sysname-HundredGigE3/1/1] transceiver lane cdr tx on

This command will engage the internal retiming function of transceiver Tx route. Continue? [Y/N]:Y

# Disable CDR on the receive side on the QSFP transceiver module in interface HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 3/1/1

[Sysname-HundredGigE3/1/1] transceiver lane cdr rx off

This command will enable an internal bypassing mode of transceiver Rx route, which directs traffic around the internal CDR. Continue? [Y/N]:Y

Related commands

display transceiver status

transceiver lane enable

Use transceiver lane enable to enable a lane on an SFP or QSFP transceiver module.

Use undo transceiver lane to disable a lane on an SFP or QSFP transceiver module.

Syntax

transceiver lane [ lane-number ] enable

undo transceiver lane [ lane-number ] enable

Default

All lanes on a transceiver module are enabled.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

lane-number: Specifies a lane by its number. The value range is fixed at 1 for an SFP transceiver module and is 1 to 4 for a QSFP transceiver module. If you do not specify a lane, this command enables all lanes on the transceiver module.

Usage guidelines

Execute this command only to verify that a transceiver module operates correctly.

Disabling a lane will stop signal transmission on the lane.

Disabling a lane will stop signal transmission on the fiber port where the lane is located.

This setting is saved in a register on the transceiver module. It is not saved to the configuration file.

This command is supported only on the SFP and QSFP transceiver modules.

Examples

# Enable lane 1 on the QSFP transceiver module in interface HundredGigE 3/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 3/1/1

[Sysname-HundredGigE3/1/1] transceiver lane 1 enable

Related commands

display transceiver status

transceiver power-mode

Use transceiver power-mode to set the power mode for a QSFP transceiver module.

Use undo transceiver power-mode to restore the default.

Syntax

transceiver power-mode { high | low }

undo transceiver power-mode

Default

The QSFP transceiver module operates in high power mode.

Views

Ethernet interface view

Predefined user roles

network-admin

Usage guidelines

A transceiver module typically operates in high power mode. If a transceiver module will be idle for a long time, you can switch it to low power mode to reduce power consumption. In low power mode, the transceiver module does not transmit signals. For a transceiver module to transmit signals, you must configure it to operate in high power mode.

This setting is saved in a register on the transceiver module. It is not saved to the configuration file.

This command is supported only on a QSFP transceiver modules.

Examples

# Configure the QSFP transceiver module in HundredGigE 3/1/1 to operate in high power mode.

<Sysname> system-view

[Sysname] interface hundredgige 3/1/1

[Sysname-HundredGigE3/1/1] transceiver power-mode high

# Configure the QSFP transceiver module in HundredGigE3/1/1 to operate in low power mode.

<Sysname> system-view

[Sysname] interface hundredgige 3/1/1

[Sysname-HundredGigE3/1/1] transceiver power-mode low

This command will place the transceiver module in low-power-consumption mode, disabling the transceiver module from transmitting data. Continue? [Y/N]:Y

Related commands

display transceiver status

user-role

Use user-role to assign user roles to a schedule.

Use undo user-role to remove user roles from a schedule.

Syntax

user-role role-name

undo user-role role-name

Default

A schedule has the user roles of the schedule creator.

Views

Schedule view

Predefined user roles

network-admin

Parameters

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

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.

The security log manager user role is mutually exclusive with other user roles. That is, if the security log manager user role has been assigned, the system will automatically remove the existing other user roles. If the other user roles have been assigned, the system will automatically remove the existing security log manager user role.

Examples

# Assign the rolename user role to the test schedule.

<sysname> system-view

[Sysname] scheduler schedule test

[Sysname-schedule-test] user-role rolename

# Assign the security-audit user role to the test schedule.

<sysname> system-view

[Sysname] scheduler schedule test

[Sysname-schedule-test]user-role security-audit

This operation will delete all other user roles for the schedule. Are you sure? [Y/N]:y

# Change the user role assigned to the test schedule from security-audit to network-admin.

<sysname> system-view

[Sysname] scheduler schedule test

[Sysname-schedule-test]user-role network-admin

This operation will delete security auditor user role for the schedule. Are you sure? [Y/N]:y

Related commands

command

scheduler schedule

01-Fundamentals Command Reference

display cpu-usage overload

display device manuinfo chassis-only

display fan-speed

display scheduler job

display system-working-mode

display version-update-record

isolate fabric-number

job

resource-monitor resource

restore factory-default

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