· oc-12-atm: Specifies the oc-12-atm mode. All interfaces on the interface 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 interface subcard act as 622 Mbps POS interfaces.

· oc-3-atm: Specifies the oc-3-atm mode. All interfaces on the interface 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 interface subcard act as 155 Mbps POS interfaces.

Usage guidelines

This command is supported only on MIC-SP4L subcards.

The oc-3-atm and oc-12-atm modes are supported only on MIC-SP4L subcards installed on the following cards: CMPE-1104, CSPEX-1104-E, CSPEX-1304X, CSPEX-1404X, and CSPEX-1504X.

On a subcard operating in oc-12-atm or oc-12-pos mode, only the first interface is available.

If you change the operating mode for an interface subcard, the subcard reboots to operate in the new operating mode.

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 device uses the factory-default system time.

Views

User view

Predefined user roles

network-admin

Parameters

time: Specifies the 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 the 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

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 configure 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 uses the NTP time source .

Views

System view

Predefined user roles

network-admin

Parameters

none: Uses the local system time, which is 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, 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, see Network Management and Monitoring Configuration Guide.

mdc mdc-id: Specifies the MDC to be used for time synchronization.

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 configure the clock protocol none command, the device uses the locally set system time. The device then uses the clock signals generated by its built-in crystal oscillator to maintain the system time.

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

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

<Sysname> system-view

[Sysname] scheduler job shutdownGE

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

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

Use display alarm to display alarm information.

Syntax

In standalone mode:

display alarm [ slot slot-number ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Examples

# (In standalone mode.) Display alarm information.

<Sysname> display alarm

Slot CPU Level Info

1 0 ERROR faulty

Table 1 Command output

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

‌

display 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/2012

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

<Sysname> display clock

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

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/2012

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 | data-plane ] [ summary ] [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

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

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

data-plane: Displays CPU usage statistics for the data plane. If you do not specify this keyword or the control-plane keyword, the command displays 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 | all }: Displays CPU core usage statistics. The core-number: argument specifies a CPU core by its number. The all keyword specifies all CPU cores.

Examples

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

<Sysname> display cpu-usage

Slot 1 CPU 0 CPU usage:

1% in last 5 seconds

1% in last 1 minute

1% in last 5 minutes

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

<Sysname> display cpu-usage

Slot CPU Last 5 sec Last 1 min Last 5 min

1 0 17% 29% 28%

Table 2 Command output

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

display cpu-usage configuration

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

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

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. 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. This option is available only if multiple CPUs are available on the specified slot.

Examples

# 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 1 slot 2 cpu 0

CPU overload summary information:

Slot/CPU Time Overload status Processes

2/0 2019-02-27 14:14:50:441 Recovered 243

2019-02-27 14:13:50:475 Minor alarm 243

2019-02-27 14:08:50:476 Minor alarm 243

2019-02-27 14:03:50:475 Minor alarm 243

2019-02-27 13:58:50:478 Minor alarm 243

2019-02-27 13:53:50:961 Recovered 243

2019-02-27 13:53:50:474 Minor alarm 243

2019-02-27 13:52:50:484 Severe alarm 243

2019-02-27 13:50:50:471 Minor alarm 243

2019-02-27 13:45:50:475 Minor alarm 243

CPU overload history on overload time 2019-02-27 14:14:50:441.

CPU utilization in recent 5 secs: 3.4%; 1 min: 3.24%; 5 mins: 3.16%.

Top processes in recent 5 secs:

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

192 192 192 5 R 0K 2.0% 2.2% 2.1% [RxShaper]

237 237 237 6 D 0K 0.3% 0.3% 0.3% [NAT0]

239 239 239 7 D 0K 0.3% 0.3% 0.3% [NAT1]

155 155 155 0 D 0K 0.0% 0.0% 0.0% [bLK0]

243 243 243 1 R 11508K 0.0% 0.0% 0.0% diagd

182 182 182 3 D 0K 0.0% 0.0% 0.0% [bRX_CleanUp]

152 152 152 0 D 0K 0.0% 0.0% 0.0% [bC.0]

226 226 226 3 S 0K 0.0% 0.0% 0.0% [IbcCntRcd]

161 161 161 0 S 0K 0.0% 0.0% 0.0% [DQIT]

217 217 217 0 S 0K 0.0% 0.0% 0.0% [sock/1]

176 176 176 0 D 0K 0.0% 0.0% 0.0% [SCAR]

109 109 109 3 D 0K 0.0% 0.0% 0.0% [RECV]

106 106 106 0 D 0K 0.0% 0.0% 0.0% [TMTH]

133 133 133 0 D 0K 0.0% 0.0% 0.0% [DTIM]

147 147 147 2 D 0K 0.0% 0.0% 0.0% [bPAR]

163 163 163 0 S 0K 0.0% 0.0% 0.0% [FMCK]

282 282 282 0 S 64532K 0.0% 0.0% 0.0% pppd

166 166 166 0 S 0K 0.0% 0.0% 0.0% [mIPC]

162 162 162 0 S 0K 0.0% 0.0% 0.0% [STAT]

164 164 164 0 D 0K 0.0% 0.0% 0.0% [OMA]

# 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 slot 2 cpu 0

CPU overload summary information:

Slot/CPU Time Overload status Processes

2/0 2019-02-27 14:14:50:441 Recovered 243

2019-02-27 14:13:50:475 Minor alarm 243

2019-02-27 14:08:50:476 Minor alarm 243

2019-02-27 14:03:50:475 Minor alarm 243

2019-02-27 13:58:50:478 Minor alarm 243

2019-02-27 13:53:50:961 Recovered 243

2019-02-27 13:53:50:474 Minor alarm 243

2019-02-27 13:52:50:484 Severe alarm 243

2019-02-27 13:50:50:471 Minor alarm 243

2019-02-27 13:45:50:475 Minor alarm 243

CPU overload history on overload time 2019-02-27 14:14:50:441.

CPU utilization in recent 5 secs: 3.4%; 1 min: 3.24%; 5 mins: 3.16%.

Top processes in recent 5 secs:

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

192 192 192 5 R 0K 2.0% 2.2% 2.1% [RxShaper]

237 237 237 6 D 0K 0.3% 0.3% 0.3% [NAT0]

239 239 239 7 D 0K 0.3% 0.3% 0.3% [NAT1]

155 155 155 0 D 0K 0.0% 0.0% 0.0% [bLK0]

243 243 243 1 R 11508K 0.0% 0.0% 0.0% diagd

182 182 182 3 D 0K 0.0% 0.0% 0.0% [bRX_CleanUp]

152 152 152 0 D 0K 0.0% 0.0% 0.0% [bC.0]

226 226 226 3 S 0K 0.0% 0.0% 0.0% [IbcCntRcd]

161 161 161 0 S 0K 0.0% 0.0% 0.0% [DQIT]

217 217 217 0 S 0K 0.0% 0.0% 0.0% [sock/1]

176 176 176 0 D 0K 0.0% 0.0% 0.0% [SCAR]

109 109 109 3 D 0K 0.0% 0.0% 0.0% [RECV]

106 106 106 0 D 0K 0.0% 0.0% 0.0% [TMTH]

133 133 133 0 D 0K 0.0% 0.0% 0.0% [DTIM]

147 147 147 2 D 0K 0.0% 0.0% 0.0% [bPAR]

163 163 163 0 S 0K 0.0% 0.0% 0.0% [FMCK]

282 282 282 0 S 64532K 0.0% 0.0% 0.0% pppd

166 166 166 0 S 0K 0.0% 0.0% 0.0% [mIPC]

162 162 162 0 S 0K 0.0% 0.0% 0.0% [STAT]

164 164 164 0 D 0K 0.0% 0.0% 0.0% [OMA]

Stack information of process 155 ([bLK0]):

Kernel stack:

[<8038efb0>] schedule+0x960/0x12b0

[<8038fb78>] schedule_timeout+0x68/0xf0

[<e68cb4f8>] sal_sem_take+0x1c8/0x250 [system]

[<e68cb878>] sal_mutex_give+0x108/0x1f0 [system]

[<e680b0b8>] soc_schan_op+0x468/0x1130 [system]

[<e681b39c>] soc_reg64_read+0x14c/0x3e0 [system]

Stack information of process 243 (diagd):

Thread LWP 243:

Switches: 361247

User stack:

Kernel stack:

[<8038efb0>] schedule+0x960/0x12b0

[<8038fbb0>] schedule_timeout+0xa0/0xf0

[<802251b4>] sys_epoll_wait+0x474/0x530

[<80102c78>] stack_done_ra+0x0/0x1c

Thread LWP 338796:

Switches: 1

User stack:

Kernel stack:

[<80126c9c>] save_stack_trace_tsk+0x8c/0xd0

[<8023e660>] proc_pid_stack+0x60/0xd0

[<802402a8>] proc_single_show+0x68/0xe0

[<80208b30>] seq_read+0x90/0x420

[<801e2728>] vfs_read+0xb8/0x160

[<801e28c0>] sys_read+0x50/0x90

[<80102c78>] stack_done_ra+0x0/0x1c

Stack information of process 152 ([bC.0]):

Kernel stack:

[<8038efb0>] schedule+0x960/0x12b0

[<8038fb78>] schedule_timeout+0x68/0xf0

[<e68cb4f8>] sal_sem_take+0x1c8/0x250 [system]

[<e68aee58>] soc_counter_thread+0x248/0x17f0 [system]

[<8016ecac>] kthread+0xfc/0x140

[<8011ee20>] kernel_thread_helper+0x10/0x20

CPU overload history on overload time 2019-02-27 14:13:50:475.

CPU utilization in recent 5 secs: 4.45%; 1 min: 3.6%; 5 mins: 3.16%.

Top processes in recent 5 secs:

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

192 192 192 5 R 0K 3.0% 2.1% 2.1% [RxShaper]

239 239 239 7 R 0K 0.4% 0.2% 0.3% [NAT1]

237 237 237 6 D 0K 0.4% 0.3% 0.3% [NAT0]

155 155 155 0 D 0K 0.1% 0.0% 0.0% [bLK0]

243 243 243 1 R 11508K 0.0% 0.0% 0.0% diagd

182 182 182 3 D 0K 0.0% 0.0% 0.0% [bRX_CleanUp]

152 152 152 0 D 0K 0.0% 0.0% 0.0% [bC.0]

226 226 226 3 S 0K 0.0% 0.0% 0.0% [IbcCntRcd]

217 217 217 0 S 0K 0.0% 0.0% 0.0% [sock/1]

161 161 161 0 S 0K 0.0% 0.0% 0.0% [DQIT]

176 176 176 0 D 0K 0.0% 0.0% 0.0% [SCAR]

133 133 133 0 D 0K 0.0% 0.0% 0.0% [DTIM]

282 282 282 0 S 64532K 0.0% 0.0% 0.0% pppd

106 106 106 0 D 0K 0.0% 0.0% 0.0% [TMTH]

109 109 109 3 D 0K 0.0% 0.0% 0.0% [RECV]

147 147 147 2 D 0K 0.0% 0.0% 0.0% [bPAR]

163 163 163 0 S 0K 0.0% 0.0% 0.0% [FMCK]

169 169 169 0 S 0K 0.0% 0.0% 0.0% [T_SI]

162 162 162 0 S 0K 0.0% 0.0% 0.0% [STAT]

164 164 164 0 D 0K 0.0% 0.0% 0.0% [OMA]

Stack information of process 155 ([bLK0]):

Kernel stack:

[<8038efb0>] schedule+0x960/0x12b0

[<8038fb78>] schedule_timeout+0x68/0xf0

[<e68cb4f8>] sal_sem_take+0x1c8/0x250 [system]

[<e6c4c108>] _bcm_esw_linkscan_thread+0x288/0x650 [system]

[<8016ecac>] kthread+0xfc/0x140

[<8011ee20>] kernel_thread_helper+0x10/0x20

Stack information of process 243 (diagd):

Thread LWP 243:

Switches: 361208

User stack:

Kernel stack:

[<8038efb0>] schedule+0x960/0x12b0

[<80100b94>] work_resched+0x8/0x40

Thread LWP 338795:

Switches: 1

User stack:

Kernel stack:

[<80126c9c>] save_stack_trace_tsk+0x8c/0xd0

[<8023e660>] proc_pid_stack+0x60/0xd0

[<802402a8>] proc_single_show+0x68/0xe0

[<80208b30>] seq_read+0x90/0x420

[<801e2728>] vfs_read+0xb8/0x160

[<801e28c0>] sys_read+0x50/0x90

[<80102c78>] stack_done_ra+0x0/0x1c

Stack information of process 152 ([bC.0]):

Kernel stack:

[<8038efb0>] schedule+0x960/0x12b0

[<8038fb78>] schedule_timeout+0x68/0xf0

[<e68cb4f8>] sal_sem_take+0x1c8/0x250 [system]

[<e68aee58>] soc_counter_thread+0x248/0x17f0 [system]

[<8016ecac>] kthread+0xfc/0x140

[<8011ee20>] kernel_thread_helper+0x10/0x20

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.

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

# Display summary CPU overload information.

<Sysname> display cpu-usage overload summary

CPU overload summary information:

Slot/CPU Time Overload status Processes

0/0 2019-02-27 14:32:59:831 Recovered 356

2019-02-27 14:31:59:884 Severe alarm 356

2019-02-27 14:30:59:848 Severe alarm 358

2019-02-27 14:29:59:868 Severe alarm 358

2019-02-27 14:28:59:840 Severe alarm 358

2019-02-27 14:27:59:862 Severe alarm 356

2019-02-27 14:26:59:830 Severe alarm 356

2019-02-27 14:25:59:857 Severe alarm 356

2019-02-27 14:24:59:838 Severe alarm 356

2019-02-27 14:23:59:867 Severe alarm 356

2/0 2019-02-27 14:14:50:441 Recovered 243

2019-02-27 14:13:50:475 Minor alarm 243

2019-02-27 14:08:50:476 Minor alarm 243

2019-02-27 14:03:50:475 Minor alarm 243

2019-02-27 13:58:50:478 Minor alarm 243

2019-02-27 13:53:50:961 Recovered 243

2019-02-27 13:53:50:474 Minor alarm 243

2019-02-27 13:52:50:484 Severe alarm 243

2019-02-27 13:50:50:471 Minor alarm 243

2019-02-27 13:45:50:475 Minor alarm 243

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 | sd-card ] [ slot slot-number [ subslot subslot-number ] | verbose ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

cf-card: Specifies the CF cards.

sd-card: Specifies the SD cards. This keyword is supported only on CSR05SRP1P3 cards.

chassis chassis-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays hardware 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 hardware 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 hardware information. If you do not specify this keyword, the command displays brief information, and does not display firewall card information.

Usage guidelines

If you do not specify the cf-card or sd-card keyword, this command displays information about cards.

Examples

# 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 card is not supported in the current software version and cannot operate correctly. · Offline—The card is isolated.
Subslot Num	Maximum number of subcards that the card supports.
Software version	Software version of the card.

‌

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 [ subslot subslot-number ] ]

In IRF mode:

display device manuinfo [ chassis chassis-number [ slot slot-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.

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 card serial number, manufacturing date, MAC address, and vendor name. The data is written to the storage component during card 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

...

Table 5 Command output

Field	Description
DEVICE_NAME	Device name.
DEVICE_SERIAL_NUMBER	Serial number.
MAC_ADDRESS	MAC address.
MANUFACTURING_DATE	Manufacturing date.
VENDOR_NAME	Vendor name.

display 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

...

Table 6 Command output

Field	Description
DEVICE_NAME	Device name.
DEVICE_SERIAL_NUMBER	Serial number.
MAC_ADDRESS	MAC address.
MANUFACTURING_DATE	Manufacturing date.
VENDOR_NAME	Vendor name.

display 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 0

...

Table 7 Command output

Field	Description
DEVICE_NAME	Device name.
DEVICE_SERIAL_NUMBER	Serial number.
MAC_ADDRESS	MAC address.
MANUFACTURING_DATE	Manufacturing date.
VENDOR_NAME	Vendor name.

display device manuinfo power

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

Syntax

In standalone mode:

display device manuinfo power power-id

In IRF mode:

display device manuinfo chassis chassis-number power power-id

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

Examples

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

<Sysname> display device manuinfo power 1

...

Table 8 Command output

Field	Description
DEVICE_NAME	Device name.
DEVICE_SERIAL_NUMBER	Serial number.
MAC_ADDRESS	MAC address.
MANUFACTURING_DATE	Manufacturing date.
VENDOR_NAME	Vendor name.

display diagnostic-information

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

hardware: Specifies hardware-related operating information.

infrastructure: Specifies operating information for the fundamental features.

l2: Specifies operating information for the Layer 2 features.

l3: Specifies operating information for the Layer 3 features.

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

key-info: Displays or saves only critical operating information. The device might have a large amount of operating information if an exception occurs or after the device runs 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.

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

Field	Description
System Temperature information (degree centigrade)	Temperature information (°C).
sensor	Temperature sensor: · hotspot—Hotspot sensor. · inflow—Air inlet sensor. · outflow—Air outlet sensor.
Slot	Sensor position. For a sensor on the chassis or fan tray, this field displays Vent.
Temperature	Current temperature.
LowerLimit	Lower temperature limit.
WarningLimit	Warning temperature threshold.
AlarmLimit	Alarming temperature threshold.
ShutdownLimit	Shutdown temperature threshold. When the sensor temperature reaches the limit, the system automatically shuts down some cards.

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

Field	Description
Fan Frame	Fan tray ID.
State	Status of the fan tray: · Normal—The fan tray is operating correctly. · Absent—No fan tray is installed in the fan tray slot. · Fault—The fan tray is faulty.

Field

Description

Fan Frame

Fan tray ID.

State

Status of the fan tray:

· Normal—The fan tray is operating correctly.

· Absent—No fan tray is installed in the fan tray slot.

· Fault—The fan tray is faulty.

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

# Display the current fan operating mode and the speeds of fans.

<Sysname> system-view

[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:

forwarding : warning

Recent record:

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

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

Table 11 Command output

Field	Description
Current level	Fix actions specified for hardware failures.
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: GE3/1/1 GE3/1/2

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

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

Port: GE3/1/1 GE3/1/2

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

<Sysname> display hardware-failure-protection port 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 12 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

chassis chassis-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays CPU and memory usage on 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 CPU and memory usage on all cards.

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

Examples

# (In standalone mode.) Display the CPU and memory usage on a card.

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

Field	Description
Role	Role of the card: · MPU(Master)—The card is the active MPU. (In standalone mode.) · MPU(Standby)—The card is the standby MPU. (In standalone mode.) · MPU(Master)—The card is the global active MPU. (In IRF mode.) · MPU(Standby)—The card is a global standby MPU. (In IRF mode.) · LPU—The card is an interface card. · BLADE—The card is a blade card.
CPU Usage(%)	Average CPU usage during the most recent 5 seconds.
Memory Usage(%)	Current memory usage in percentage.
Used/Total(MB)	Current memory usage and total memory size in MB.

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.

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: 984504 576428 408076 0 12 131056 41.5%

-/+ Buffers/Cache: 445360 539144

Swap: 0 0 0

LowMem: 739768 352152 387616 -- -- -- 52.4%

HighMem: 244736 224276 20460 -- -- -- 8.4%

# (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 984504 576428 408076 12 131056 41.4%

Low memory statistics are measured in KB:

Slot CPU Total Used Free Buffers Caches FreeRatio

1 0 739768 352152 387616 -- -- 52.4%

High memory statistics are measured in KB:

Slot CPU Total Used Free Buffers Caches FreeRatio

1 0 244736 224276 20460 -- -- 8.4%

Table 14 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. 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.
Buffers	Physical memory used for buffers.
Cached Caches	Physical memory used for caches.
FreeRatio	Free memory ratio.
-/+ Buffers/Cache	-/+ Buffers/Cache:used = Mem:Used – Mem:Buffers – Mem:Cached, which indicates the physical memory used by applications. -/+ Buffers/Cache:free = Mem:Free + Mem:Buffers + Mem:Cached, which indicates the physical memory available for applications.
Swap	Swap memory.

display memory-threshold

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

Parameters

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

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

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

Usage guidelines

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

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

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

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

Examples

# Display power supply 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
State	Status of the power supply: · Normal—The power supply is operating correctly. · Absent—The power supply is not in postion. · Error—The power supply is faulty.

Field

Description

State

Status of the power supply:

· Normal—The power supply is operating correctly.

· Absent—The power supply is not in postion.

· Error—The power supply is faulty.

display power-information

Use display power-information to display power information about power supplies 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 supplies and cards.

<Sysname> system-view

[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
Device Power	Rated power of the device.
Power control mode	Card power-on control mode: · loose—Loose mode. · strict—Strict model.
Surplus power	Remaining power of the device.
Fan Power	Maximum power of the fans.

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

Usage guidelines

This command is supported on the following cards:

· CSPC cards (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) that have an interface capacity greater than 80 Gbps. The interface capacity of a card is the sum of speeds of all interfaces on the card. For example, the interface capacity of a CSPC-XP24LCX card is 240 Gbps (24 x 10 Gbps).

· CMPE-1104 cards and IM-MSUX cards.

· CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX cards, and CEPC cards.

· Switching fabric modules.

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 scheduler job

Use display scheduler job to display job configuration information.

Syntax

display scheduler job [ job-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Examples

# Display configuration information for all jobs.

<Sysname> display scheduler job

Job name: saveconfig

copy startup.cfg backup.cfg

Job name: backupconfig

Job name: creat-VLAN100

system-view

vlan 100

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

display scheduler logfile

Use display scheduler logfile to display job execution log information.

Syntax

display scheduler logfile

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display job execution log information.

<Sysname> display scheduler logfile

Logfile Size: 1902 Bytes.

Job name : shutdown

Schedule name : shutdown

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

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

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

<Sysname>system-view

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

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

[Sysname-if-range]shutdown

Table 18 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 19 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 service-mode status

Use display service-mode status to display the current operating modes of cards.

Syntax

In standalone mode:

display service-mode status

In IRF mode:

display service-mode status chassis chassis-number

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Examples

# (In standalone mode.) Display the current operating modes of cards.

<Sysname> display service-mode status

Slot No. Service-mode

1 MIX-BRIDGING-ROUTING

4 ROUTING

5 NONE

6 NONE

14 NONE

Table 20 Command output

Field	Description
Service-mode	Operating mode of the card. · MIX-BRIDGING-ROUTING—Extended hybrid mode.. · ROUTING—Extended routing mode. · NONE—The card does not support setting the operating mode.

Field

Description

Service-mode

Operating mode of the card.

· MIX-BRIDGING-ROUTING—Extended hybrid mode..

· ROUTING—Extended routing mode.

· NONE—The card does not support setting the operating mode.

‌

Related commands

service-mode

display system stable state

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

Syntax

display system stable state

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

The device or card startup takes some time. If the values of the status fields do not change to Stable, execute this command multiple times to identify the devices or 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.

Examples

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

<Sysname> display system stable state

System state : Stable

Redundancy state: Stable

Slot CPU Role State

* 1 0 Active Stable

Table 21 Command output

Field	Description
System state	System status: · Stable—The system is operating stably. · Not ready—The system 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.
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	Card status: · Stable—The card is operating stably. · Board inserted—The card has just been installed. · Kernel initiating—Card kernel is being initialized. · Service starting—Services are starting. · Service stopping—Services are stopping. · HA Batch backup—An HA batch backup is going on. · Interface data batch backup—An interface data batch backup is in progress.
*	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 operating mode information.

Syntax

display system-working-mode

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display system operating 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

‌

Examples

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

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

GigabitEthernet3/1/1 transceiver current alarm information:

RX loss of signal

RX power low

Table 23 Command output

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

display transceiver diagnosis

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Examples

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

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

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

Table 24 Command output

Field	Description
transceiver diagnostic information	Digital diagnosis information for the transceiver module in the interface.
Temp.(°C)	Temperature in °C, accurate to 1°C.
Voltage(V)	Voltage in V, accurate to 0.01 V.
Bias(mA)	Bias current in mA, accurate to 0.01 mA.
RX power(dBm)	Receive power in dBm, accurate to 0.01 dBm.
TX power(dBm)	Transmit power in dBm, accurate to 0.01 dBm.

display transceiver interface

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

Syntax

display transceiver interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Examples

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

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

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 25 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 multimode fiber. · 62.5 um—62.5/125 µm multimode fiber. · TP—Twisted pair. · CX4—CX4 cable.
Digital Diagnostic Monitoring	Support for digital diagnosis: · YES—Supported. · NO—Not supported.

display transceiver manuinfo

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Examples

# Display electronic label information for the transceiver module on interface GigabitEthernet 3/1/1.

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

GigabitEthernet3/1/1 transceiver manufacture information:

Manu. Serial Number : 213410A0000054000251

Manufacturing Date : 2012-09-01

Vendor Name : H3C

Table 26 Command output

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

display version

Use display version to display system version information.

Syntax

display version

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display system version information.

<Sysname> display version

display version-update-record

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

Syntax

display version-update-record

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

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

Examples

# Display the startup software image upgrade records.

<Sysname> display version-update-record

Record 1 (updated on Sep 30 2 at 08:35:21):

Name : CR16000-F-CMW710-BOOT-B7603.bin

Version : 7.1.075 Beta 7603

Compile time: Aug 22 2016 16:00:00

Name : CR16000-F-CMW710-SYSTEM-B7603.bin

Version : 7.1.075 Beta 7603

Compile time: Aug 22 2016 16:00:00

Table 27 Command output

Field	Description
Record n	Number of the startup software image upgrade record. Record 1 is the most recent record.
Name	Software image file name.
*	The software image version changed during the upgrade.

Related commands

reset version-update-record

fabric load-sharing algorithm

Use fabric load-sharing algorithm to specify a load sharing algorithm for a service module.

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

Syntax

In standalone mode:

fabric load-sharing algorithm algorithm-number slot slot-number

undo fabric load-sharing algorithm algorithm-number slot slot-number

In IRF mode:

fabric load-sharing algorithm algorithm-number chassis chassis-number slot slot-number

undo fabric load-sharing algorithm algorithm-number chassis chassis-number slot slot-number

Default

No load sharing algorithm is specified for a service module.

Views

System view

Predefined user roles

network-admin

Parameters

algorithm-number: Specifies a load sharing algorithm, in the range of 1 to 9.

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

Usage guidelines

This command is supported only on CSPC cards (except CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, and CSPC-CP2LB cards) that have an interface capacity greater than 80 Gbps. The interface capacity of a card is the total speed of the interfaces on the card. For example, the interface capacity of a CSPC-XP24LCX card is 240 Gbps (24 × 10 Gbps).

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

Examples

# (In standalone mode.) Specify load sharing algorithm 3 for a card.

<Sysname> system-view

[Sysname] fabric load-sharing algorithm 3 slot 2

fabric load-sharing mode

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

Load sharing for a service module is performed based on ingress interface.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

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

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

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

Usage guidelines

This command is supported on CMPE-1104 cards and CSPC cards except CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, and CSPC-CP2LB.

On CSPC cards (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) and CMPE-1104 cards, the flexible mode takes effect only for uplink interfaces, including IRF physical interfaces.

If a service module does not support the specified mode, the command displays an error message.

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

If you do not specify any keywords for the undo fabric load-sharing mode command, the command deletes all load sharing modes for the specified card.

Examples

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

<Sysname> system-view

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

fan-speed

Use fan-speed to set the fan operating mode.

Syntax

In standalone mode:

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

In IRF mode:

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

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. If you do not specify a member device, this command set the fan operating mode for all member devices. (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-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 forwarding { isolate | off | reset | warning }

undo hardware-failure-detection forwarding

Default

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

Views

System view

Predefined user roles

network-admin

Parameters

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 device automatically detects hardware failures on 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 the forwarding plane.

<Sysname> system-view

[Sysname] hardware-failure-detection forwarding warning

hardware-failure-protection aggregation

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

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

Syntax

hardware-failure-protection aggregation

undo hardware-failure-protection aggregation

Default

Hardware failure protection is disabled for aggregation groups.

Views

System view

Predefined user roles

network-admin

Usage guidelines

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

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

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

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

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

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

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

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

· The interface is a physical IRF port.

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

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

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

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

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

· The interface is a physical IRF port.

Examples

# Enable hardware failure protection on interface GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

header

Use header to configure a banner.

Use undo header to delete a banner.

Syntax

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

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

Default

No banners exist.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

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

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

Examples

# Configure the legal banner.

<Sysname> system-view

[Sysname] header legal

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

Welcome to use the legal banner%

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

Syntax

In standalone mode:

memory-threshold [ slot slot-number [ cpu cpu-number ] ] minor minor-value severe severe-value critical critical-value normal normal-value

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

In IRF mode:

memory-threshold [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] minor minor-value severe severe-value critical critical-value normal normal-value

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

Default

Minor alarm threshold: 96 MB.

Severe alarm threshold: 64 MB.

Critical alarm threshold: 48 MB.

Normal state threshold: 128 MB.

Views

System view

Predefined user roles

network-admin

Parameters

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.

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 exceeds a free-memory threshold, the system generates an alarm notification and sends it to affected service modules or processes. For more information about the thresholds, see Fundamentals Configuration Guide.

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.

Examples

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

<Sysname> system-view

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

Related commands

display memory-threshold

memory-threshold usage

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

Use undo memory-threshold usage to restore the default.

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

The memory usage threshold is 100%.

Views

System view

Predefined user roles

network-admin

Parameters

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

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.

Usage guidelines

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

Examples

# Set the memory usage threshold to 80%.

<Sysname> system-view

[Sysname] memory-threshold usage 80

Related commands

display memory-threshold

monitor cpu-usage enable

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

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

Syntax

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 ] [ slot slot-number [ cpu cpu-number ] ]

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

In IRF mode:

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

undo monitor cpu-usage threshold [ minor-threshold minor-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%.

Views

System view

Predefined user roles

network-admin

Parameters

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

minor-threshold minor-threshold: Specifies the minor CPU usage alarm threshold in percentage. The value range 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 severe-threshold * 0.8.

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

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

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

Usage guidelines

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

Examples

# Set the severe CPU usage alarm threshold to 80%.

<Sysname> system-view

[Sysname] monitor cpu-usage threshold 80

Related commands

display cpu-usage configuration

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

power-off high-temp-board clear

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. You can use this command to power on the card as appropriate.

This command is supported on the following cards:

· CSPC cards except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E with an interface capacity greater than 80 Gbps. The interface capacity of a card is the sum of speeds of all interfaces on the card. For example, the interface capacity of a CSPC-XP24LCX card is 240 Gbps (24 x 10 Gbps).

· CMPE-1104 cards and IM-MSUX cards.

· CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX cards, and CEPC cards.

· Switching fabric modules.

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.

This command is supported on the following cards:

· CMPE-1104 cards and IM-MSUX cards.

· CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX cards, and CEPC cards.

· Switching fabric modules.

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 [ subslot subslot-number ] ] [ force ]

In IRF mode:

reboot [ chassis chassis-number [ slot slot-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. (In IRF mode.)

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

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

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:

To reboot the entire device, do not specify the slot number option.

To reboot a card, specify the slot number and do not specify a subslot number.

To reboot the active MPU, first perform the following tasks:

· Identify whether the standby MPU is installed and operating correctly.

· Use the display system stable state command to display system stability and status information.

If the standby MPU is not installed, the entire device will be rebooted. If the standby MPU is installed and is operating correctly, a switchover will occur.

IMPORTANT:

To ensure correct operation of the system and cards, do not trigger a switchover by rebooting the active MPU if the status of a card is not Stable.

In IRF mode:

To reboot all IRF member devices, do not specify the member ID option.

To reboot an IRF member device, specify only the member ID.

To reboot a card, specify both the member ID and the slot number.

To reboot the global active MPU, first perform the following tasks:

· Identify whether the IRF fabric has global standby MPUs and whether the global standby MPUs are operating correctly.

· Use the display system stable state command to display system stability and status information.

If the IRF fabric has only one MPU, the IRF fabric will be rebooted. If the IRF fabric has a global standby MPU and the MPU is operating correctly, a switchover will occur.

IMPORTANT:

To ensure correct operation of the IRF fabric and MPUs, do not trigger a switchover by rebooting the global active MPU if the status of a card is not Stable.

Examples

# Reboot the device. Save the running configuration at prompt.

<Sysname> reboot

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

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

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

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

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

Validating file. Please wait...

Configuration is saved to flash successfully.

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

Now rebooting, please wait...

# Reboot the device immediately without performing software check.

<Sysname> reboot force

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

Now rebooting, please wait...

Related commands

display system stable state

reset scheduler logfile

Use reset scheduler logfile to clear job execution log information.

Syntax

reset scheduler logfile

Views

User view

Predefined user roles

network-admin

Examples

# Clear job execution log information.

<Sysname> reset scheduler logfile

Related commands

display scheduler logfile

reset version-update-record

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

Syntax

reset version-update-record

Views

System view

Predefined user roles

network-admin

Examples

# Clear the startup software image upgrade records.

<Sysname> system-view

[Sysname] reset version-update-record

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

Related commands

display version-update-record

restore factory-default

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

Syntax

restore factory-default

Views

User view

Predefined user roles

network-admin

Usage guidelines

CAUTION:

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

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:

Device reboot interrupts network services.

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

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

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

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

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

Examples

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

Device reboot interrupts network services.

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

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

Examples

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

service-mode

Use switch-mode to specify an operating mode for a service module.

Use undo switch-mode to restore the default.

Syntax

In standalone mode:

service-mode { routing | mix-bridging-routing } slot slot-number

undo service-mode slot slot-number

In IRF mode:

service-mode { routing | mix-bridging-routing } chassis chassis-number slot slot-number

undo service-mode chassis chassis-number slot slot-number

Default

A service module operates in mix-bridging-routing mode.

Views

System view

Predefined user roles

network-admin

Parameters

routing: Specifies the extended routing mode.

mix-bridging-routing: Specifies the extended hybrid mode.

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

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

Usage guidelines

Contact H3C Support before executing this command.

This command is supported only on the following cards:

· CSPC cards except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E that have an interface capacity of less than or equal to 80 Gbps.

· CMPE-1104 cards.

The interface capacity of a card is the total speed of interfaces on the card. For example, the interface capacity of the CSPC-GP24XP2LB card is 44 Gbps (2 x 10 Gbps + 24 x 1 Gbps).

Change to the operating mode of a service module takes effect after you save the running configuration and reboot the service module.

Changing the operating mode for a service module changes only the performance of the service module. The performance of the device is not affected.

Examples

# (In standalone mode.) Set the operating mode to routing for the service module in slot 3.

<Sysname> system-view

[Sysname] service-mode routing slot 3

Related commands

display service-mode status

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. To disable port status detection, set this argument to 0.

Usage guidelines

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

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

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

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

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

Examples

# Set the port status detection timer to 100 seconds.

<Sysname> system-view

[Sysname] shutdown-interval 100

switch-fabric isolate

Use switch-fabric isolate to isolate a switching fabric module or channel.

Use undo switch-fabric isolate to restore the default.

Syntax

In standalone mode:

switch-fabric isolate slot slot-number [ channel channel-number ]

undo switch-fabric isolate slot slot-number [ channel channel-number ]

In IRF mode:

switch-fabric isolate chassis chassis-number slot slot-number [ channel channel-number ]

undo switch-fabric isolate chassis chassis-number slot slot-number [ channel channel-number ]

Default

A switching fabric module is not isolated from the forwarding plane and forwards traffic.

Views

System view

Predefined user roles

network-admin

Parameters

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

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. (In IRF mode.)

channel channel-number: Specifies a switching fabric channel by its number. If you do not specify a switching fabric channel, the command isolates the switching fabric module. This option is not supported in the current software version.

Usage guidelines

CAUTION:

· Isolating the only switching fabric module of the device disables the forwarding feature.

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

This command does not take effect for CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX-1104-E, and CSPEX-1204 cards. Traffic of the cards go through an isolated switching fabric module or channel as normal.

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 leave a switching fabric module isolated for a long time. If you do not want to use the module, remove the module after isolating the module. To use the module, use the undo switch-fabric isolate command to cancel the isolation.

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

Examples

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

<Sysname> system-view

[Sysname] switch-fabric isolate slot 10 channel 1

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

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-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 system operating mode is standard.

Views

System view

Predefined user roles

network-admin

Parameters

sdn-wan: Specifies WAN SDN mode.

standard: Specifies standard mode.

Usage guidelines

Supported features vary by system operating mode. For more information, see device management in Fundamentals Configuration Guide.

A system operating mode change takes effect after a device reboot.

Examples

# Set the system operating mode to WAN SDN mode.

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

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 temperature alarm thresholds depend on the device model. To view the default temperature alarm thresholds, use the undo temperature-limit command to restore the default and execute the display environment command.

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 near the chip that generates a great amount of heat and used to monitor the chip.

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

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

sensor-number: Specifies a sensor by its number, an integer starting from 1. Each number represents a temperature sensor on the device.

lowlimit: Specifies the low-temperature threshold in Celsius degrees.

warninglimit: Specifies the high-temperature warning threshold in Celsius degrees. This threshold must be greater than the low-temperature threshold.

alarmlimit: Specifies the high-temperature alarming threshold in Celsius degrees. This threshold must be greater than the high-temperature warning threshold.

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 inlet sensor 1 in a slot.

<Sysname> system-view

[Sysname] temperature-limit slot 1 inflow 1 -10 70 100

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 configured 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 configured 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 an interval 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 configured most recently takes effect.

Examples

# Configure the device to execute the saveconfig schedule once an hour from 8:00 a.m. on.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 interval 60

# Configure the device to execute the saveconfig schedule at 12:00 p.m. every day.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 12:00

# Configure the device to execute the saveconfig schedule at 8:00 a.m. on the 5th of every month.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 month-date 5

# Configure the device to execute the saveconfig schedule at 8:00 a.m. on the last day of every month.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 month-date last

# Configure the device to execute the saveconfig schedule at 8:00 a.m. every Friday and Saturday.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 week-day fri sat

Related commands

scheduler schedule

user-role

Use user-role to assign user roles to a schedule.

Use undo user-role to remove user roles from a schedule.

Syntax

user-role role-name

undo user-role role-name

Default

A schedule has the user roles of the schedule creator.

Views

Schedule view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

A schedule must have one or more user roles. A command in a schedule can be executed if it is permitted by one or more user roles of the schedule. For more information about user roles, see the RBAC configuration in Fundamentals Configuration Guide.

A schedule can have a maximum of 64 user roles. After the limit is reached, you cannot assign additional user roles to the schedule.

Examples

# Assign the rolename user role to the test schedule.

<sysname> system-view

[Sysname] scheduler schedule test

[Sysname-schedule-test] user-role rolename

Related commands

command

scheduler schedule

01-Fundamentals Command Reference

display copyright

display device manuinfo chassis-only

display fan

display scheduler job

display service-mode status

display version-update-record

job

memory-threshold usage

monitor cpu-usage interval

restore factory-default

scheduler reboot at

switch-fabric isolate

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