MDC is supported only when the device operates in standalone mode. For more information about standalone mode, see IRF configuration in Virtual Technologies Configuration Guide. For more information about MDC and device models that support MDC, see MDC configuration in Virtual Technologies Configuration Guide.

clock datetime

Use clock datetime to set the system time.

Syntax

clock datetime time date

Default

The system time is UTC time 00:00:00 01/01/2011.

Views

User view

Predefined user roles

network-admin

Parameters

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

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

Usage guidelines

CAUTION:

Change of the system time affects execution of system time-related features (such as scheduled tasks) and cooperative operation with other devices (such as log reporting and statistics collection). Before executing this command, make sure you understand its impact on the live network.

This command is supported only on the default MDC.

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

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

A device power cycling operation restores the local system time to the default. After the device is power cycled, you must execute this command again to set the local system time.

Examples

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

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

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

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

Related commands

clock protocol

clock summer-time

clock timezone

display clock

clock protocol

Use clock protocol to specify the system time source.

Use undo clock protocol to restore the default.

Syntax

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

undo clock protocol

Default

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

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

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

Usage guidelines

This command is supported only on the default MDC.

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

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

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

If you execute the clock protocol ntp command, the device obtains the UTC time through NTP and calculates the system time. The device then periodically synchronizes the UTC time and recalculates the system time.

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

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

Examples

# Configure the device to use the local UTC time.

<Sysname> system-view

[Sysname] clock protocol none

clock summer-time

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

Use undo clock summer-time to restore the default.

Syntax

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

undo clock summer-time

Default

The daylight saving time is not set.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

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

· month week day, where:

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

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

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

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

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

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

· month week day, where:

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

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

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

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

Usage guidelines

This command is supported only on the default MDC.

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

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

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

Examples

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

<Sysname> system-view

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

Related commands

clock datetime

clock timezone

display clock

clock timezone

Use clock timezone to set the time zone.

Use undo clock timezone to restore the default.

Syntax

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

undo clock timezone

Default

The UTC time zone is used.

Views

System view

Predefined user roles

network-admin

Parameters

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

add: Adds an offset to the UTC time.

minus: Decreases the UTC time by an offset.

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

Usage guidelines

This command is supported only on the default MDC.

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

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

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

Examples

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

<Sysname> system-view

[Sysname] clock timezone Z5 add 5

Related commands

clock datetime

clock summer-time

display clock

command

Use command to assign a command to a job.

Use undo command to revoke a command.

Syntax

command id command

undo command id

Default

No command is assigned to a job.

Views

Job view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] scheduler job backupconfig

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

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

<Sysname> system-view

[Sysname] scheduler job shutdownGE

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

[Sysname-job-shutdownGE] command 2 interface ten-gigabitethernet 3/0/1

[Sysname-job-shutdownGE] command 3 shutdown

Related commands

scheduler job

copyright-info enable

Use copyright-info enable to enable copyright statement display.

Use undo copyright-info enable to disable copyright statement display.

Syntax

undo copyright-info enable

Default

Views

System view

Predefined user roles

network-admin

mdc-admin

Examples

# Enable copyright statement display.

<Sysname> system-view

[Sysname] copyright-info enable

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

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

* Without the owner's prior written consent, *

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

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

display alarm

Use display alarm to display alarm information.

Syntax

In standalone mode:

display alarm [ slot slot-number ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Usage guidelines

This command is supported only on the default MDC.

Examples

# (In standalone mode.) Display alarm information.

<Sysname> display alarm

Slot CPU Level Info

1 0 ERROR faulty

Table 1 Command output

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

‌

display asset-info

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

mdc-admin

network-operator

mdc-operator

Parameters

chassis: Displays the asset profile for the frame. The device does not support this keyword.

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

csn: Displays the asset ID for the asset.

custom: Displays the customized asset items.

department: Displays the department name.

description: Displays the asset description.

location: Displays the asset location.

service-date: Displays the service start date.

state: Displays the asset usage status.

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

Usage guidelines

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

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

Examples

# (In standalone mode.) Display the asset ID for the frame.

<Sysname> display asset-info chassis csn

Type : Chassis

csn : 123456789

# (In standalone mode.) Display the asset information for the frame.

<Sysname> display asset-info chassis 1 chassis

Type : Chassis

csn : 123456789

description : frameA

location :

service-date:

department :MKT

state :Normal

custom :1:789

Related commands

reset asset-info

set asset-info

display clock

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

Syntax

display clock

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

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

<Sysname> display clock

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

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

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

<Sysname> display clock

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

Time Zone : Z5 add 05:00:00

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

<Sysname> display clock

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

Time Zone : Z5 add 05:00:00

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

Related commands

clock datetime

clock timezone

clock summer-time

display copyright

Use display copyright to display the copyright statement.

Syntax

display copyright

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display the copyright statement.

<Sysname> display copyright

...

display cpu-usage

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

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

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

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

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

core all: Specifies all CPU cores.

Usage guidelines

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

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

Examples

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

<Sysname> display cpu-usage

Slot 1 CPU 0 CPU usage:

1% in last 5 seconds

1% in last 1 minute

1% in last 5 minutes

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

<Sysname> display cpu-usage

Slot CPU Last 5 sec Last 1 min Last 5 min

1 0 17% 29% 28%

Table 2 Command output

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

‌

display cpu-usage configuration

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

Usage guidelines

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

Examples

# Display the CPU usage monitoring settings.

<Sysname> display cpu-usage configuration

CPU usage monitor is enabled.

Current monitor interval is 60 seconds.

Current severe alarm threshold is 90%.

Current minor alarm threshold is 80%.

Current recovery-threshold is 40%.

Table 3 Command output

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

‌

Related commands

monitor cpu-usage enable

monitor cpu-usage interval

monitor cpu-usage threshold

display cpu-usage history

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

slot slot-number: Specifies a card by its slot number. If you specify a process but do not specify a card, this command displays the statistics for the process on the active MPU. If you do not specify any options, this command displays the statistics for all processes on all cards. (In standalone mode.)

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

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

Usage guidelines

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

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

· The horizontal axis represents the time.

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

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

Examples

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

<Sysname> display cpu-usage history

100%|

95%|

90%|

85%|

80%|

75%|

70%|

65%|

60%|

55%|

50%|

45%|

40%|

35%|

30%|

25%|

20%|

15%| #

10%| ### #

5%| ########

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

10 20 30 40 50 60 (minutes)

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

The output shows the following items:

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

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

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

¡ 12 minutes ago—Approximately 5%.

¡ 13 minutes ago—Approximately 10%.

¡ 14 minutes ago—Approximately 15%.

¡ 15 minutes ago—Approximately 10%.

¡ 16 and 17 minutes ago—Approximately 5%.

¡ 18 minutes ago—Approximately 10%.

¡ 19 minutes ago—Approximately 5%.

¡ Other time—2% or lower.

Related commands

monitor cpu-usage enable

monitor cpu-usage interval

display device

Use display device to display device information.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

flash: Displays flash memory information.

usb: Displays USB interface information.

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

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

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

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

Usage guidelines

If you do not specify the flash and usb keywords, this command displays information about cards.

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

Examples

# (In standalone mode.) Display device information.

<Sysname> display device

...

Table 4 Command output

Field	Description
Brd Type	Hardware type of the card.
Status	Card status: · Standby—The card is the standby MPU. · Master—The card is the active MPU. · Absent—The slot is not installed with a card. · Fault—The card is starting up, powered off, or faulty. · Normal—The card is an interface card and is operating correctly.
Subslot	Maximum number of interface subcards supported by the card.
Sft Ver	Software version of the card.
Patch Ver	Most recently released patch image version that is running on the device. If no patch image is installed, this field displays None. If both incremental and non-incremental patch images are running on the device, this field displays the most recently released incremental patch image version. For more information about patch image types, see "Upgrading software."

‌

display device manuinfo

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

Syntax

In standalone mode:

display device manuinfo [ slot slot-number ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

Usage guidelines

This command is supported only on the default MDC.

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

Examples

# Display electronic label information for the device.

<Sysname> display device manuinfo

...

display device manuinfo chassis-only

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

Syntax

In standalone mode:

display device manuinfo chassis-only

In IRF mode:

display device manuinfo chassis chassis-number chassis-only

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Usage guidelines

This command is supported only on the default MDC.

Examples

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

<Sysname> display device manuinfo chassis-only

...

display device manuinfo power

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

Syntax

In standalone mode:

display device manuinfo power power-id

In IRF mode:

display device manuinfo chassis chassis-number power power-id

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

Usage guidelines

This command is supported only on the default MDC.

This command is supported only on the S7506X-G and S7510X-G switches.

Examples

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

<Sysname> display device manuinfo power 1

...

display device uptime

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

Syntax

display device uptime

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

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

<Sysname> display device uptime

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

0 LSCM1SUP03A0 Master 0 0001:05:37

1 NONE Absent 0 None

2 NONE Absent 0 None

3 LSCM1QGS8CSSE0 Normal 0 0001:05:34

4 LSCM1TGS48SE0 Normal 0 0001:05:34

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

<Sysname> display device uptime

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

1/0 LSCM1SUP03A0 Master 0 0001:05:37

1/1 NONE Absent 0 None

1/2 NONE Absent 0 None

1/3 LSCM1QGS8CSSE0 Normal 0 0001:05:34

1/4 LSCM1TGS48SE0 Normal 0 0001:05:34

display diagnostic-information

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

Syntax

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

hardware: Specifies hardware-related operating information.

ifmgr: Specifies IFMGR-related operating information.

infrastructure: Specifies operating information for the fundamental features.

l2: Specifies operating information for the Layer 2 features.

l3: Specifies operating information for the Layer 3 features.

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

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

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

Usage guidelines

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

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

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

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

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

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

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

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

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

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

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

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

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

Examples

# Display the operating information for all features and modules.

<Sysname> display diagnostic-information

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

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

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

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

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

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

...

# Save the operating information to the default file.

<Sysname> display diagnostic-information

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

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

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

Please wait...

Save successfully.

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

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

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

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

Please wait...

Save successfully.

Related commands

gunzip

tar extract

display environment

Use display environment to display temperature information.

Syntax

In standalone mode:

display environment [ slot slot-number ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

Usage guidelines

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

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

This command is supported only on the default MDC.

Examples

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

<Sysname> display environment

System temperature information (degree centigrade):

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

Slot Sensor Temperature Lower Warning Alarm Shutdown

1 hotspot 1 38 10 40 50 100

1 hotspot 2 42 10 50 80 100

Table 5 Command output

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

‌

display fabric multicast-forwarding mode

Use display fabric multicast-forwarding mode to display the multicast forwarding mode.

NOTE:

Only the SE interface modules support this command.

Syntax

display fabric multicast-forwarding mode

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display the multicast forwarding mode.

<Sysname> display fabric multicast-forwarding mode

The current mode is standard.

The mode at the next startup is standard.

display fan

Use display fan to display fan tray operating status information.

Syntax

In standalone mode:

display fan [ verbose ]

In IRF mode:

display fan [ chassis chassis-number ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

Usage guidelines

This command is supported only on the default MDC.

Examples

# Display the operating states of all fan trays.

<Sysname> display fan

Fan 1 State: Normal

Fan 2 State: Normal

Table 6 Command output

Field	Description
Fan 1	Fan tray number.
State	Fan tray status: · Absent—The slot is not installed with a fan tray. · Faulty—The fan tray is faulty. · Normal—The fan tray is operating correctly.

Field

Description

Fan 1

Fan tray number.

State

Fan tray status:

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

· Faulty—The fan tray is faulty.

· Normal—The fan tray is operating correctly.

‌

display hardware-failure-detection

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

Syntax

display hardware-failure-detection

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

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

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

This command is supported only on the default MDC.

Examples

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

<Sysname> display hardware-failure-detection

Current level:

chip : isolate

board : isolate

forwarding : warning

Recent record:

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

There is no record.

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

There is no record.

Table 7 Command output

Field	Description
Current level	Fix actions specified for hardware failures.
chip	Fix action for hardware failures on components of cards.
board	Fix action for hardware failures on cards.
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 memory

Use display memory to display memory usage information.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

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

Usage guidelines

Executing this command on an MDC displays memory usage information for the MDC.

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

Examples

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

<Sysname> display memory

Memory statistics are measured in KB:

Slot 0:

Total Used Free Shared Buffers Cached FreeRatio

Mem: 1993056 1643360 349696 0 2592 914912 51.4%

-/+ Buffers/Cache: 725856 1267200

Swap: 0 0 0

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

<Sysname> display memory summary

Memory statistics are measured in KB:

Slot CPU Total Used Free Buffers Caches FreeRatio

0 0 1993056 1643536 349520 2592 914912 51.4%

3 0 1993056 349584 1643472 96 54272 82.5%

4 0 1993056 351408 1641648 96 54272 82.4%

Table 8 Command output

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

‌

display memory dma

Use display memory dma to display DMA memory usage information.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

Examples

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

<System> display memory dma slot 1

DMA memory statistics measured in KB on slot 1:

Total Used Free FreeRatio

16384 6140 10244 63%

Table 9 Command output

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

‌

display memory-threshold

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

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

Usage guidelines

This command is supported only on the default MDC.

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

Examples

# Display memory alarm thresholds and statistics.

<Sysname> display memory-threshold

Memory usage threshold: 100%

Free-memory thresholds:

Minor: 194M

Severe: 136M

Critical: 77M

Normal: 252M

Early-warning: 311M

Secure: 350M

Current free-memory state: Normal (secure)

Free-memory event statistics:

[Back to secure state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Entered early-warning state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to normal state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Entered minor alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to minor alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Entered severe alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to severe alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Entered critical alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

Table 10 Command output

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

‌

display memory-threshold dma

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

Usage guidelines

# Display DMA memory alarm information.

<Sysname> display memory-threshold dma

Free DMA memory thresholds:

Critical: 2048KB

Normal: 4096KB

Current DMA memory state: Normal

Free memory event statistics:

[Back to normal state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Entered to critcal state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

display power

Use display power to display power module information.

Syntax

In standalone mode:

display power [ power-id | verbose ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

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

This command is supported only on the default MDC.

Examples

# Display brief power supply information.

<Sysname> display power

Input Power: 1600.0 W

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

1 Absent -- -- -- -- --

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

3 Absent -- -- -- -- --

4 Absent -- -- -- -- --

5 Normal AC 13.5 54.7 738.2 --

6 Absent -- -- -- -- --

7 Absent -- -- -- -- --

8 Absent -- -- -- -- --

Table 11 Command output

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

‌

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

<Sysname> display power verbose

System power information:

Power modules installed: 1

Power modules usable: 1

Rated power: 2000 W

Usable power: 1495 W

Used power: 139.60 W

Redundant power: 0 W

Total DC output : 2.8 A

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

1 Normal 220 2000 50 2.8 140

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

Power information by slot:

Slot Type Current(A) Power(W) Status

1 None 5 10 Normal

Table 12 Command output

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

‌

display power-supply

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

Syntax

In standalone mode:

display power-supply

In IRF mode:

display power-supply [ chassis chassis-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Usage guidelines

This command does not display information about power supply priorities for cards where the MPUs and IRF physical ports are located.

Examples

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

<Sysname> display power-supply

Power supply policy: Disable

Power modules redundant (setting): 0

Board power supply information:

Slot Type Priority Status

0 LSCM1SUP03A0 -- Powered on

1 None -- Reserved

2 LSCM1TGS48SE0 5 Powered on

3 LSCM1QGS8CSSE0 5 Powered on

4 None 5 Absent

Table 13 Command output

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

‌

display resource-monitor

Use display resource-monitor to display resource monitoring information.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

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

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

Usage guidelines

This command is supported on the LSCM1GT48SC0 card.

Examples

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

<Sysname> display resource-monitor resource arp

Minor alarms resending: Enabled

Slot 1:

Resource Minor Severe Free/Total

(%) (%) (absolute)

arp 50 20 90095/90098

Table 14 Command output

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

‌

Related commands

resource-monitor minor resend enable

resource-monitor resource

display scheduler job

Use display scheduler job to display job configuration information.

Syntax

display scheduler job [ job-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

# Display configuration information for all jobs.

<Sysname> display scheduler job

Job name: saveconfig

copy startup.cfg backup.cfg

Job name: backupconfig

Job name: creat-VLAN100

system-view

vlan 100

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

display scheduler logfile

Use display scheduler logfile to display job execution log information.

Syntax

display scheduler logfile

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display job execution log information.

<Sysname> display scheduler logfile

Logfile Size: 1902 Bytes.

Job name : shutdown

Schedule name : shutdown

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

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

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

<Sysname>system-view

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

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

[Sysname-if-range]shutdown

Table 15 Command output

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

‌

Related commands

reset scheduler logfile

display scheduler reboot

Use display scheduler reboot to display the automatic reboot schedule.

Syntax

display scheduler reboot

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display the automatic reboot schedule.

<Sysname> display scheduler reboot

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

Related commands

scheduler reboot at

scheduler reboot delay

display scheduler schedule

Use display scheduler schedule to display schedule information.

Syntax

display scheduler schedule [ schedule-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

# Display information about all schedules.

<Sysname> display scheduler schedule

Schedule name : shutdown

Schedule type : Run once after 0 hours 2 minutes

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

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

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

Execution counts : 1

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

Job name Last execution status

shutdown Successful

Table 16 Command output

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

‌

display switch-mode status

Use display switch-mode status to display operating mode information about service modules.

Syntax

In standalone mode:

display switch-mode status

In IRF mode:

display switch-mode status chassis chassis-number

Views

Any view

Predefined user roles

network-admin

mdc-admin

network-operator

mdc-operator

Parameters

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

Usage guidelines

If a service module does not have an operating mode specified, the Config field displays NONE. The service module will operate in the default mode after you save the running configuration and reboot the service module.

Examples

# Display operating mode information about all service modules on the device.

<Sysname> display switch-mode status

LPU switch mode:

Slot Current Config

0 NORMAL NONE

2 NORMAL NONE

3 NORMAL NONE

Table 17 Command output

Field	Description
LPU switch mode	Operating mode information.
Slot	Slot number.
Current	Current operating mode of the service module: · NONE—The service module does not support operating mode configuration. · NORMAL—The service module is operating in normal mode. · BALANCE—The service module is operating in balanced mode. · BRIDGING—The service module is operating in extended MAC mode. · ROUTING—The service module is operating in extended routing mode. · ENHANCE—The service module is operating in enhanced mode. · EHC-BALANCE—The service module is operating in enhanced balanced mode. · EHC-BRIDGING—The service module is operating in enhanced extended MAC mode. · EHC-ROUTING—The service module is operating in enhanced extended routing mode.
Config	Operating mode specified for the service module: · NONE—No operating mode or proxy mode is specified for the service module. · NORMAL—The normal mode is specified for the service module. · BALANCE—The balanced mode is specified for the service module. · BRIDGING—The extended MAC mode is specified for the service module. · ROUTING—The extended routing mode is specified for the service module. · ENHANCE—The enhanced mode is specified for the service module. · EHC-BALANCE—The enhanced balanced mode is specified for the service module. · EHC-BRIDGING—The enhanced extended MAC mode is specified for the service module. · EHC-ROUTING—The enhanced extended routing mode is specified for the service module.

‌

Related commands

switch-mode

display system health

Use display system health to display system health status information.

Syntax

In standalone mode:

display system health

In IRF mode:

display system health [ chassis chassis-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> display system health

Health: Faulty(3)

Memory: Normal(0)

Communication: Normal(0)

DBM monitor: Normal(0)

Chip jam: Normal(0)

CPU deadloop: Normal(0)

Forwarding channel: Normal(0)

HG: Normal(0)

LSW CPU: Normal(0)

LSW port: Normal(0)

Board status: Faulty(3)

Fan status: Normal(0)

Temperature: Normal(0)

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

<Sysname> display system health

Chassis 1 health: Normal(0)

Memory: Normal(0)

Communication: Normal(0)

DBM monitor: Normal(0)

Chip jam: Normal(0)

CPU deadloop: Normal(0)

Forwarding channel: Normal(0)

HG: Normal(0)

LSW CPU: Normal(0)

LSW port: Normal(0)

Board status: Normal(0)

Fan status: Normal(0)

Temperature: Normal(0)

Chassis 2 health: Normal(0)

Memory: Normal(0)

Communication: Normal(0)

DBM monitor: Normal(0)

Chip jam: Normal(0)

CPU deadloop: Normal(0)

Forwarding channel: Normal(0)

HG: Normal(0)

LSW CPU: Normal(0)

LSW port: Normal(0)

Board status: Normal(0)

Fan status: Normal(0)

Temperature: Normal(0)

Table 18 Command output

Field	Description
Health: Normal(0)	System health status: · Normal(0)—The system is healthy. · Faulty(n)—The system is faulty. A greater value of n indicates a worse situation.
Memory	Memory health status.
Communication	Communication health status.
DBM monitor	DBM health status.
Chip jam	Chip jam status.
CPU deadloop	CPU deadloop status.
Forwarding channel	Health status of cross-card services on the device. This field is not supported on the S7503X-G and S7503X-M-G switches.
HG	HG health status.
LSW CPU	LSW CPU health status.
LSW port	LSW port health status.
Board status	Card health status.
Fan status	Fan health status.
Temperature	Temperature sensor health status.

‌

Related commands

display system health history

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

Syntax

In standalone mode:

display system health history

In IRF mode:

display system health history[ chassis chassis-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Examples

# Display historical system health status change information.

<Sysname> display system health history

Health: Faulty(1)

Chip jam:

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

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

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

Table 19 Command output

Field

Description

Health: Normal(0)

System health status:

· Normal(0)—The system is healthy.

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

Chip jam:

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

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

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

‌

Related commands

display system health

display system stable state

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

Usage guidelines

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

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

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

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

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

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

Examples

# Display brief system stability and status information.

<Sysname> display system stable state summary

System state : Stable

Redundancy state : No redundancy

NSR state : No standby

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

<Sysname> display system stable state

System state : Stable

Redundancy state : Stable

Slot CPU Role State

0 0 Active Stable

1 0 Standby Stable

3 0 Other Stable

15 0 Other Stable

Table 20 Command output

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

‌

Related commands

display context (Virtual Technologies Command Reference)

display device

display ha service-group (High Availability Command Reference)

display system-working-mode

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

Syntax

display system-working-mode

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

This command is supported only on the default MDC.

Examples

# Display system working mode information.

<Sysname> display system-working-mode

The current system working mode is standard.

The system working mode for next startup is standard.

display transceiver alarm

Use display transceiver alarm to display transceiver alarms.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Usage guidelines

You can use the display transceiver alarm command to display alarm information on transceiver modules.

If no error occurs, None is displayed. The following tables describe the alarm information that might be present on transceiver module.

Table 21 Command output for SFP/SFP28/SFP+/GBIC/SFF transceiver modules

Field	Description
RX signal loss	Receive signal loss.
RX power high alarm	Alarm on a high receive optical power.
RX power high warning	Early warning on a high receive optical power.
RX power low alarm	Alarm on a low receive optical power.
RX power low warning	Early warning on a low receive optical power.
TX fault	Transmit fault.
TX bias high alarm	Alarm on a high transmit bias current.
TX bias high warning	Early warning on a high transmit bias current.
TX bias low alarm	Alarm on a low transmit bias current.
TX bias low warning	Early warning on a low transmit bias current.
TX power high alarm	Alarm on a high transmit optical power.
TX power high warning	Early warning on a high transmit optical power.
TX power low alarm	Alarm on a low transmit optical power.
TX power low warning	Early warning on a low transmit optical power.
Temp high alarm	Alarm on a high temperature.
Temp high warning	Early warning on a high temperature.
Temp low alarm	Alarm on a low temperature.
Temp low warning	Early warning on a low temperature.
Voltage high alarm	Alarm on a high voltage.
Voltage high warning	Early warning on a high voltage.
Voltage low alarm	Alarm on a low voltage.
Voltage low warning	Early warning on a low voltage.
Transceiver info I/O error	N/A
Transceiver info checksum error	N/A
Transceiver type and port configuration mismatch	The transceiver type does not match port configuration.
Transceiver type not supported by port hardware	The transceiver type is not supported on the port.
RX CDR loss of lock	Receive CDR loss of lock, indicating poor signal.
TX CDR loss of lock	Transmit CDR loss of lock, indicating poor signal.

‌

Table 22 Command output for QSFP+/QSFP28 transceiver modules

Field	Description
Temp high alarm	Alarm on a high temperature.
Temp high warning	Early warning on a high temperature.
Temp low alarm	Alarm on a low temperature.
Temp low warning	Early warning on a low temperature.
Voltage high alarm	Alarm on a high voltage.
Voltage high warning	Early warning on a high voltage.
Voltage low alarm	Alarm on a low voltage.
Voltage low warning	Early warning on a low voltage.
RX loss of signal(channel x)	Loss of receive signal in channel x.
TX fault(channel x)	Packet transmission fault in channel x.
TX loss of signal(channel x)	Loss of transmit signal in channel x.
RX power high(channel x)	Alarm on a high receive optical power in channel x.
RX power low(channel x)	Alarm on a low receive optical power in channel x.
TX power high alarm(channel x)	Alarm on a high transmit optical power in channel x.
TX power high warning(channel x)	Early warning on a high transmit optical power in channel x.
TX power low alarm(channel x)	Alarm on a low transmit optical power in channel x.
TX power low warning(channel x)	Early warning on a low transmit optical power in channel x.
TX bias high(channel x)	Alarm on a high bias current in channel x.
TX bias low(channel x)	Alarm on a low bias current in channel x.
Transceiver info I/O error	N/A
Transceiver info checksum error	N/A
Transceiver type and port configuration mismatched	The transceiver type does not match port configuration.
Transceiver type not supported	The transceiver type is not supported on the port.

‌

Table 23 Command output for CFP transceiver modules

Field	Description
TX jitter PLL unlocked	Transmit Jitter PLL is out of lock.
TX CMU unlocked	Transmit CMU is out of lock.
Overloaded	Alarm on being overloaded.
Loss of REFCLK input	Alarm on loss of REFCLK input.
Channel signals out of alignment	Alarm on channel signals out of alignment.
PLD or flash initialization error	PLD or flash initialization error
Power supply fault	N/A
CFP checksum error	N/A
TX bias high	The transmit bias current is high.
TX bias low	The transmit bias current is low.
Temp high	The temperature is high.
Temp low	The temperature is low.
Voltage high	The voltage is high.
Voltage low	The voltage is low.
RX signal loss in channel x	Receive signal loss in in channel x.
RX IC unlocked in channel x	Receive IC is out of lock in channel x.
RX FIFO error in channel x	Receive FIFO error in channel x.
TX signal loss in channel x	Transmit signal loss in channel x.
TX IC unlocked in channel x	Transmit IC is out of lock in channel x.
TX FIFO error in channel x	Transmit FIFO error in channel x.
TX IC unlocked in channel x	Transmit IC is out of lock in channel x.
APD supply fault in channel x	N/A
TEC fault in channel x	N/A
Wavelength unlocked in channel x	Optical signal wavelength is out of lock in channel x.
RX power high in lane x	Alarm on a high receive optical power in lane x.
RX power low in lane x	Alarm on a low receive optical power in lane x.
TX power high in lane x	Alarm on a high transmit optical power in lane x.
TX power low in lane x	Alarm on a low transmit optical power in lane x.
TX bias high in lane x	Alarm on a high bias current in lane x.
TX bias low in lane x	Alarm on a low bias current in lane x.
Temp high in lane x	Alarm on a high temperature in lane x.
Temp low in lane x	Alarm on a low temperature in lane x.
Transceiver info I/O error	N/A
Transceiver info checksum error	N/A
Transceiver type and port configuration mismatched	The transceiver type does not match port configuration.
Transceiver type not supported	The transceiver type is not supported on the port.

‌

Table 24 Common alarms for XFP transceiver modules

Field	Description
RX signal loss	Receive signal loss.
RX not ready	The receiving status is not ready.
RX CDR loss of lock	Receive CDR loss of lock.
RX power high alarm	Alarm on a high receive optical power.
RX power high warning	Early warning on a high receive optical power.
RX power low alarm	Alarm on a low receive optical power.
RX power low warning	Early warning on a low receive optical power.
TX not ready	The transmission status is ready.
TX fault	Transmit fault.
TX CDR loss of lock	Transmit CDR loss of lock.
TX bias high alarm	Alarm on a high transmit bias current.
TX bias high warning	Early warning on a high transmit bias current.
TX bias low alarm	Alarm on a low transmit bias current.
TX bias low warning	Early warning on a low transmit bias current.
TX power high alarm	Alarm on a high transmit optical power.
TX power high warning	Early warning on a high transmit optical power.
TX power low alarm	Alarm on a low transmit optical power.
TX power low warning	Early warning on a low transmit optical power.
Module not ready	The module is not ready.
APD supply fault	Avalanche Photo Diode (APD) supply error.
TEC fault	Thermoelectric Cooler (TEC) error.
Wavelength unlocked	Optical signal wavelength is out of lock.
Temp high alarm	Alarm on a high temperature.
Temp high warning	Early warning on a high temperature.
Temp low alarm	Alarm on a low temperature.
Temp low warning	Early warning on a low temperature.
Voltage high alarm(3.3V)	Alarm on a high voltage (3.3 V).
Voltage high warning(3.3V)	Early warning on a high voltage (3.3 V).
Voltage low alarm(3.3V)	Alarm on a low voltage (3.3 V).
Voltage low warning(3.3V)	Early warning on a low voltage (3.3 V).
Voltage high alarm(5.5V)	Alarm on a high voltage (5.5 V).
Voltage high warning(5.5V)	Early warning on a high voltage (5.5 V).
Voltage low alarm(5.5V)	Alarm on a low voltage (5.5 V).
Voltage low warning(5.5V)	Early warning on a low voltage (5.5 V).
Voltage high alarm(1.8V)	Alarm on a high voltage (1.8 V).
Voltage high warning(1.8V)	Early warning on a high voltage (1.8 V).
Voltage low alarm(1.8V)	Alarm on a low voltage (1.8 V).
Voltage low warning(1.8V)	Early warning on a low voltage (1.8 V).
Voltage high alarm(5.2V)	Alarm on a high voltage (5.2 V).
Voltage high warning(5.2V)	Early warning on a high voltage (5.2 V).
Voltage low alarm(5.2V)	Alarm on a low voltage (5.2 V).
Voltage low warning(5.2V)	Early warning on a low voltage (5.2 V).
Transceiver info I/O error	N/A
Transceiver info checksum error	N/A
Transceiver type and port configuration mismatch	The transceiver type does not match port configuration.
Transceiver type not supported by port hardware	The transceiver type is not supported on the port.

‌

Table 25 Command output for XENPAK transceiver modules

Field	Description
WIS local fault	WAN Interface Sublayer (WIS) local fault.
Receive optical power fault	N/A
PMA/PMD receiver local fault	Physical Medium Attachment (PMA)/Physical Medium Dependent (PMD) receiver local fault.
PCS receive local fault	Physical Coding Sublayer (PCS) receive local fault.
PHY XS receive local fault	PHY Extended Sublayer (PHY XS) receive local fault.
RX power high	The receive power is high.
RX power low	The receive power is low.
Laser bias current fault	N/A
Laser temperature fault	N/A
Laser output power fault	N/A
TX fault	Transmit fault.
TX bias high	The transmit bias current is high.
TX bias low	The transmit bias current is low.
TX power high	The temperature is high.
TX power low	The temperature is low.
Temp high	The voltage is high.
Temp low	The voltage is low.
Transceiver info I/O error	N/A
Transceiver info checksum error	N/A
Transceiver type and port configuration mismatch	The transceiver type does not match port configuration.
Transceiver type not supported by port hardware	The transceiver type is not supported on the port.

‌

Table 26 Command output for QSFP-DD transceiver modules

Field	Description
Data path firmware fault	N/A
Module firmware fault	N/A
Module state changed	N/A
Data path state changed in channel x	N/A
TX loss in channel x	Transmit signal loss in channel x.
TX CDR LOL in channel x	Transmit CDR loss of lock in channel x.
TX input eq fault in channel x	Transmit input eq fault in channel x.
RX CDR LOL in channel x	Receive CDR loss of lock in channel x.
Loss of reference clock	N/A
L-Host Pattern Generator LOL in channel x	Pattern generator loss of lock on the host side in channel x.
L-Media Pattern Generator LOL in channel x	Pattern generator loss of lock on the media side in channel x.
L-Host Pattern Checker LOL in channel x	Pattern checker loss of lock on the host side in channel x.
L-Media Pattern Checker LOL in channel x	Pattern checker loss of lock on the media side in channel x.

‌

Examples

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

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

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

RX signal loss

RX power low

Table 27 Command output

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

‌

display transceiver diagnosis

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

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

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

Ten-GigabitEthernet3/0/1 transceiver diagnostic information:

Current diagnostic parameters:

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

36 3.31 6.13 -35.64 -5.19

Alarm thresholds:

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

High 50 3.55 1.44 -10.00 5.00

Low 30 3.01 1.01 -30.00 0.00

Warning thresholds:

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

High 45 3.25 1.25 -15.00 4.00

Low 25 2.85 0.85 -25.00 1.00

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

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

HundredGigE1/0/49 transceiver diagnostic information:

Current diagnostic parameters:

[module] Temp.(C) Voltage(V)

29 3.33

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

1 0.00 -36.96 -36.96

2 0.00 -36.96 -36.96

3 0.00 -36.96 -36.96

4 0.00 -36.96 -36.96

Alarm thresholds:

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

High 75 3.47 13.00 3.40 5.00

Low -5 3.13 3.00 -14.00 -10.00

Warning thresholds:

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

High 70 3.45 11.00 2.40 3.00

Low 0 3.15 5.00 -11.00 -8.00

Total average launch power(dBm): 5.90

# Display the current values of the digital diagnosis parameters for the transceiver module in FourHundredGigE 1/0/1.

<Sysname> display transceiver diagnosis interface fourhundredgige 1/0/1

FourHundredGigE1/0/1 transceiver diagnostic information:

Current diagnostic parameters:

[Module] Temp.(C) Voltage(V) TEC Curr. (%) Laser Temp.(C)

40 3.34 38 53

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

1 1.13 -20.43 -1.0

2 1.13 -20.43 -1.0

3 1.13 -20.43 -1.0

4 1.13 -20.43 -1.0

5 1.13 -20.43 -1.0

6 1.13 -20.43 -1.0

7 1.13 -20.43 -1.0

8 1.13 -20.43 -1.0

Alarm thresholds:

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

High 80 3.64 15.00 5.00 5.50

Low -10 2.97 4.50 -12.00 -3.50

Table 28 Command output

Field	Description
transceiver diagnostic information	Digital diagnosis information for the transceiver module in the interface.
Temp.(C)	Temperature in °C, accurate to 1°C.
Voltage(V)	Voltage in V, accurate to 0.01 V.
TEC Curr. (%)	TEC current in percentage, accurate to 0.01%.
Laser Temp.(C)	Laser temperature in °C, accurate to 0.01°C.
Bias(mA)	Bias current in mA, accurate to 0.01 mA.
Total RX power(dBm)	Total receive power in dBm, accurate to 0.01 dBm.
Total TX power(dBm)	Total transmit power in dBm, accurate to 0.01 dBm.
RX power(dBm)	Receive power in dBm, accurate to 0.01 dBm.
TX power(dBm)	Transmit power in dBm, accurate to 0.01 dBm.
High	High alarm threshold or high early warning threshold.
Low	Low alarm threshold or low early warning threshold.
Warning threshold	Early warning threshold.
Total average launch power(dBm)	Total average launch power on the multi-lane transceiver module in dBM, accurate to 0.01 dBm.

‌

display transceiver health

Use display transceiver health to display health information of transceiver modules.

Syntax

display transceiver health 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 health information of all transceiver modules.

Examples

# Display health information of the transceiver module in interface Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] display transceiver health interface ten-gigabitethernet 3/0/1

Ten-GigabitEthernet3/0/1 transceiver health information:

LinkStatus health: 10

Transceiver health:

Temp. Voltage Bias RX power TX power Total

10 10 10 10 10 10

Table 29 Command output

Field	Description
Transceiver health	Health information of the transceiver module in the interface.
LinkStatus health	Link health, whose calculation is related to the health of the error packet rate. · If the health of the error packet rate is 1, the link health is 1. · If the health of the error packet rate is 2 to 9, the link health = (Receive power health + the health of the error packet rate)/2. · If the health of the error packet rate is 10, the link health = Round-off number for [(receive power health + 10)/2 + 0.5].
Tem	Temperature health.
Voltage	Voltage health.
Bias	Bias current health.
RX power	Receive power health.
TX power	Transmit power health.
Total	Overall transceiver module health, sum of the health of each element multiplied by its corresponding weight.

‌

Related commands

transceiver health check enable

transceiver health weight

display transceiver interface

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

Syntax

display transceiver interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

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

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

...

display transceiver manuinfo

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

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

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

...

display transceiver power

Use display transceiver power to display power information for transceiver modules.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

# Display power information for all transceiver modules.

<Sysname> display transceiver power

Interface Transceiver type Current power(w) Max power(w)

XGE3/0/1 100G_BASE_SR4_QSFP28 2.30 3.50

XGE3/0/2 100G_BASE_LR4_QSFP28 2.50 4.00

XGE3/0/3 100G_BASE_ER4_QSFP28 3.51 5.00

XGE3/0/4 Absent -- --

XGE3/0/5 100G_BASE_SR4_QSFP28 -- --

XGE3/0/6 10G_BASE_LR_SFP -- 1.50

10G_BASE_LR_SFP 1.00 --

Current total power : 9.31w

Maximum total Power : 15.5w

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

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

Interface Transceiver type Current power(w) Max power(w)

XGE3/0/1 10G_BASE_LR_SFP 1.00 1.50

Table 30 Command output

Field	Description
Current power(w)	Current power of a transceiver module, in watts, accurate to 0.01 w.
Max power(w)	Maximum power of a transceiver module, in watts, accurate to 0.01 w.
Current total power	Current total power of all transceiver modules, in watts, accurate to 0.01 w.
Max total power	Maximum total power of all transceiver modules, in watts, accurate to 0.01 w

‌

display transceiver status

Use display transceiver status to display transceiver module status information.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Usage guidelines

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

Examples

# Display status information for the QSFP transceiver module in interface HundredGigE1/0/1.

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

HundredGigE1/0/1 transceiver status information:

Module state : ModuleReady

Interrupt : YES

Lane Data Path State Media Lane State

Lane1 Activated Enable

Lane2 Activated Enable

Lane3 Activated Enable

Lane4 Activated Enable

Lane5 Activated Enable

Lane6 Activated Enable

Lane7 Activated Enable

Lane8 Activated Enable

Table 31 Command output

Field	Description
Module state	Transceiver module status: · ModuleLowPwr—The transceiver module operates in low power. · ModulePwrUp—The transceiver module is powered on. · ModuleReady—The transceiver module is ready. · ModulePwrDn—The transceiver module is powered off. · Fault state—The transceiver module is faulty. · Unknown.
Interrupt	Indicates whether the transceiver module is in interrupt alarm status: · YES. · NO.
Data Path State	Data path status: · UNKNOWN. · Deactivated. · Init—The transceiver module is performing initialization tasks on the data path. · Deinit—The data path is deinitialized. · Activated. · TxTurnOn—Tx output is enabled. · TxTurnOff—Tx output is disabled. · Initialized—The data path is fully initialized.
Media Lane State	Media lane status: · Enable. · Disable.

‌

display version

Use display version to display system version information.

Syntax

display version

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display system version information.

<Sysname> display version

...

display version-update-record

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

Syntax

display version-update-record

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

This command is supported only on the default MDC.

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

Examples

# Display the startup software image upgrade records.

<Sysname> display version-update-record

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

*Name : boot-test.bin

Version : 7.1.070 Test 0001

Compile time: Mar 25 2015 15:52:43

*Name : system-test.bin

Version : 7.1.070 Test 0001

Compile time: Mar 25 2015 15:52:43

Table 32 Command output

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

‌

Related commands

reset version-update-record

display xbar

Use display xbar to display the load modes for MPUs.

Syntax

In standalone mode:

display xbar

In IRF mode:

display xbar [ chassis chassis-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Usage guidelines

This command is supported only on the default MDC.

The running load mode might be different from the configured load mode. The load-balance mode takes effect only when both the active and standby MPUs are present. If the standby MPU is not present, the active MPU operates in load-single mode.

The output from this command does not take effect on the S7503X-G and S7503X-M-G switches.

Examples

# (In standalone mode.) Display the load modes for MPUs.

<Sysname> display xbar

The configured system HA xbar load mode is BALANCE

The activated system HA xbar load mode is SINGLE

The output shows that the configured load mode is the load-balance mode but the running load mode is the load-single mode.

Related commands

xbar

fabric multicast-forwarding mode

Use fabric multicast-forwarding mode to specify the multicast forwarding mode.

Use undo fabric multicast-forwarding mode to restore the default.

Syntax

fabric multicast-forwarding mode { enhanced | standard }

undo fabric multicast-forwarding mode

Default

The multicast forwarding mode is standard.

Views

System view

Predefined user roles

network-admin

Parameters

enhanced: Specifies enhanced mode.

standard: Specifies standard mode.

Usage guidelines

For this command to take effect, save the running configuration and reboot the device.

If the multicast traffic across cards is large, set the multicast forwarding mode to enhanced as a best practice.

The SF interfaces do not support the enhanced mode.

This command is not supported on the S7503X-G and S7503X-M-G switches.

This command is supported only on the default MDC.

The device supports specifying a multicast forwarding mode only when the device are installed with MPUs prefixed with LSCM1 and interface modules prefixed with LSCM1.

To form an IRF fabric, all member devices must be configured with the same multicast forwarding mode. For more information about IRF, see Virtual Technologies Configuration Guide.

Before setting the multicast forwarding mode to enhanced, make sure the following requirements are met:

· The device is configured with local-first load sharing for link aggregation. For more information about local-first load sharing for link aggregation, see Ethernet link aggregation configuration in Layer 2—LAN Switching Configuration Guide.

· The marks and interface numbers on the cards that host the IRF physical interfaces at both ends of an IRF link must be the same. For more information about IRF, see Virtual Technologies Configuration Guide.

If you specify the multicast forwarding mode as enhanced, only MPUs prefixed with LSCM1 and interface modules prefixed with LSCM1 (except LSCM1GT48SC0) can operate correctly.

Examples

# Set the multicast forwarding mode to enhanced.

<Sysname> system-view

[Sysname] fabric multicast-forwarding mode enhanced

Are you sure you want to change the forwarding mode for multicast packets between internal interfaces? [Y/N]:y

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

forward-path-detection enable

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

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

Syntax

forward-path-detection enable

undo forward-path-detection enable

Default

Data forwarding path failure detection is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default MDC.

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

Examples

# Enable data forwarding path failure detection.

<Sysname> system-view

[Sysname] forward-path-detection enable

hardware-alarm disable

Use hardware-alarm disable to disable the notification of hardware resource alarms.

Syntax

hardware-alarm { syslog | trap } resource-type { all | board | bus | chip-channel | chip-port | device | disk | fan | interface | power | subcard | transceiver | voltage } disable

undo hardware-alarm { syslog | trap } resource-type { all | board | bus | chip-channel | chip-port | device | disk | fan | interface | power | subcard | transceiver | voltage } disable

Views

System view

Default

The notification of all hardware resource alarms is enabled.

Predefined user roles

network-admin

Parameters

all: Specifies all types of resource alarms.

board: Specifies card-related resource alarms.

bus: Specifies bus-related resource alarms.

chip-channel: Specifies chip channel-related resource alarms.

chip-port: Specifies chip port-related resource alarms.

device: Specifies device-related resource alarms.

disk: Specifies disk-related resource alarms.

fan: Specifies fan-related resource alarms.

interface: Specifies interface-related resource alarms.

syslog: Sends hardware resources alarms in syslog messages.

subcard: Specifies subcard-related resource alarms.

transceiver: Specifies transceiver -related resource alarms.

trap: Sends hardware resources alarms in traps.

power: Specifies power supply-related resource alarms.

voltage: Specifies voltage-related resource alarms.

Examples

# Disable trap notification for all hardware resource alarms.

<Sysname> system

[Sysname] hardware-alarm trap resource-type all disable

# Disable syslog notification for device-related resource alarms.

<Sysname> system

[Sysname] hardware-alarm syslog resource-type device disable

hardware-failure-detection

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

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

Syntax

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

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

Default

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

Views

System view

Predefined user roles

network-admin

Parameters

board: Specifies failures on control paths and cards.

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

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

isolate: Takes one or more of the following actions:

· 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 report the failures. If a card failure is detected on control paths, the system will try to recover from the failure by restarting the card.

Usage guidelines

This command is supported only on the default MDC.

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

Examples

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

<Sysname> system-view

[Sysname] hardware-failure-detection chip warning

header

Use header to configure a banner.

Use undo header to delete a banner.

Syntax

header { legal | login | motd | shell } text

undo header { legal | login | motd | shell }

Default

The device does not have banners.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

Examples

# Configure the legal banner.

<Sysname> system-view

[Sysname] header legal

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

Welcome to use the legal banner%

job

Use job to assign a job to a schedule.

Use undo job to revoke a job.

Syntax

job job-name

undo job job-name

Default

No job is assigned to a schedule.

Views

Schedule view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

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

Examples

# Assign job save-job to schedule saveconfig.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] job save-job

Related commands

scheduler job

scheduler schedule

memory-threshold

Use memory-threshold to set free-memory thresholds.

Use undo memory-threshold to restore the defaults.

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

Minor alarm threshold: 194 MB.

Severe alarm threshold: 136 MB.

Critical alarm threshold: 77 MB.

Normal state threshold: 252 MB.

Early-warning threshold: 311 MB.

Sufficient-memory threshold: 350 MB.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

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

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

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

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

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

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

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

Usage guidelines

This command is supported only on the default MDC.

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

You can use the display memory command to display memory usage information.

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

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

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

The system will restart a card if one of the following conditions is met:

· After a critical alarm occurs, the remaining free-memory value has been smaller than the critical alarm threshold for 30 seconds.

· The interval between two consecutive critical alarms is shorter than 30 seconds.

· The critical alarm has occurred three times within three minutes.

· After a critical alarm occurs, the system will periodically sample free memory space and predict if the free memory space will be exhausted within 30 seconds. If the prediction result indicates that the free memory space will be exhausted within 30 seconds, the system will restart the card.

Once the free memory space reaches the early warning, minor, severe, or critical alarm threshold, the device will display the current memory usage information when you log in to the device through console or Telnet login, or execute every command.

Examples

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

<Sysname> system-view

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

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

<Sysname> system-view

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

Related commands

display memory-threshold

memory-threshold dma

Use memory-threshold dma to set DMA memory thresholds.

Use undo memory-threshold dma to restore the default.

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

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

Views

System view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

ratio: Specifies DMA memory thresholds in percentage.

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

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

Usage guidelines

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

Examples

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

<System> system-view

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

memory-threshold usage

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

Use undo memory-threshold usage to restore the default.

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

The memory usage threshold is 100%.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

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

Usage guidelines

This command is supported only on the default MDC.

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

Examples

# Set the memory usage threshold to 80%.

<Sysname> system-view

[Sysname] memory-threshold usage 80

Related commands

display memory-threshold

monitor cpu-usage enable

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

CPU usage monitoring is enabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

Usage guidelines

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

Examples

# Enable CPU usage monitoring.

<Sysname> system-view

[Sysname] monitor cpu-usage enable

Related commands

display cpu-usage configuration

display cpu-usage history

monitor cpu-usage interval

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

Use undo monitor cpu-usage interval to restore 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

mdc-admin

Parameters

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

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

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] monitor cpu-usage interval 5Sec

Related commands

display cpu-usage configuration

display cpu-usage history

monitor cpu-usage enable

monitor cpu-usage logging interval

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

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

Syntax

monitor cpu-usage logging interval interval-time

undo monitor cpu-usage logging interval

Default

Periodic CPU usage logging is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Examples

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

<Sysname> system-view

[Sysname] monitor cpu-usage logging interval 60

monitor cpu-usage threshold

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

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

Syntax

In standalone mode:

monitor cpu-usage threshold severe-threshold { minor-threshold minor-threshold recovery-threshold recovery-threshold [ slot slot-number [ cpu cpu-number ] ] | slot slot-number cpu cpu-number [ core core-id-list ] }

undo monitor cpu-usage threshold { minor-threshold recovery-threshold [ slot slot-number [ cpu cpu-number ] ] | slot slot-number cpu cpu-number [ core core-id-list ] }

In IRF mode:

monitor cpu-usage threshold severe-threshold { minor-threshold minor-threshold recovery-threshold recovery-threshold [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] | chassis chassis-number slot slot-number cpu cpu-number [ core core-id-list ] }

undo monitor cpu-usage threshold { minor-threshold recovery-threshold [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] | chassis chassis-number slot slot-number cpu cpu-number [ core core-id-list ] }

Default

Severe CPU usage alarm threshold: 99%.

Minor CPU usage alarm threshold: 80%.

CPU usage recovery threshold: 60%.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

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

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

core core-id-list: Specifies a space-separated list of up to 10 CPU core items. Each item specifies a CPU core or a range of CPU cores in the form of core-id1 [ to core-id2 ]. The value for core-id2 must be equal to or greater than the value for core-id1.

Usage guidelines

CAUTION:

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

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

Examples

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

<Sysname> system-view

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

Related commands

display cpu-usage configuration

monitor handshake-timeout disable-port

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

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

Syntax

monitor handshake-timeout disable-port

undo monitor handshake-timeout disable-port

Default

The port-down feature is enabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

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

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

Examples

# Enable the port-down feature globally.

<Sysname> system-view

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

[Sysname] monitor handshake-timeout disable-port

Set successful!

monitor memory-usage logging interval

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

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

Syntax

monitor memory-usage logging interval interval-time

undo monitor memory-usage logging interval

Default

Periodic memory usage logging is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Examples

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

<Sysname> system-view

[Sysname] monitor memory-usage logging interval 60

monitor resend cpu-usage

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

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

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

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

Usage guidelines

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

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

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

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

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

Examples

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

<Sysname> system-view

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

monitor resend memory-threshold

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

Default

· Early warning resending interval: 1 hour.

· Minor alarm resending interval: 12 hours.

· Severe alarm resending interval: 3 hours.

· Critical alarm resending interval: 1 hour.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

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

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

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

Usage guidelines

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

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

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

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

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

Examples

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

<Sysname> system-view

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

parity-error consistency-check log enable

Use parity-error consistency-check log enable to enable consistency error logging for software and hardware forwarding entries.

Use undo parity-error consistency-check log enable to disable consistency error logging for software and hardware forwarding entries.

Syntax

parity-error consistency-check log enable

undo parity-error consistency-check log enable

Default

Consistency error logging is enabled for software and hardware forwarding entries.

Views

System view

Predefined user roles

network-admin

Usage guidelines

To forward packets, the device generates hardware forwarding entries on forwarding chips and software forwarding entries in memory at the same time. The device automatically detects whether the hardware forwarding entries and the software forwarding entries are consistent.

After you execute this command, the device collects consistency errors periodically. If the number of consistency errors in a statistics period reaches or exceeds the logging threshold, the device generates and sends a log message to the information center module. The information center module determines how and where to send the message. For more information about the information center module, see information center configuration in Network Management and Monitoring Configuration Guide.

Examples

# Enable consistency error logging for software and hardware forwarding entries.

<Sysname> system-view

[Sysname] parity-error consistency-check log enable

Related commands

parity-error consistency-check threshold

parity-error consistency-check period

Use parity-error consistency-check period to set the statistics period for consistency errors between software and hardware forwarding entries.

Use undo parity-error consistency-check period to restore the default.

Syntax

parity-error consistency-check period value

undo parity-error consistency-check period

Default

The statistics period is 3600 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

value: Specifies the statistics period (in seconds) for consistency errors between software and hardware forwarding entries, in the range of 600 to 31536000.

Usage guidelines

To forward packets, the device generates hardware forwarding entries in forwarding chips and software forwarding entries in memory at the same time. The device automatically detects whether the hardware forwarding entries and the software forwarding entries are consistent.

This command determines the period for the device to collect consistency error statistics.

As a best practice, set the consistency error statistics period to a value greater than 3600 seconds.

Examples

# Set the statistics period to 600 seconds for consistency errors between software and hardware forwarding entries.

<Sysname> system-view

[Sysname] parity-error consistency-check period 600

Related commands

parity-error consistency-check log enable

parity-error consistency-check threshold

Use parity-error consistency-check threshold to set the logging threshold for consistency errors between software and hardware forwarding entries.

Use undo parity-error consistency-check threshold to restore the default.

Syntax

parity-error consistency-check threshold value

undo parity-error consistency-check threshold

Default

The logging threshold is 10.

Views

System view

Predefined user roles

network-admin

Parameters

value: Specifies the logging threshold for consistency errors between software and hardware forwarding entries, in the range of 1 to 2147483647.

Usage guidelines

After you enable consistency error logging for software and hardware forwarding entries, the device collects statistics for consistency errors periodically. If the number of consistency errors reaches or exceeds the logging threshold, the device generates a log message.

Examples

# Set the logging threshold to 20 for consistency errors between software and hardware forwarding entries.

<Sysname> system-view

[Sysname] parity-error consistency-check threshold 20

Related commands

parity-error consistency-check log enable

parity-error consistency-check period

parity-error monitor log enable

Use parity-error monitor log enable to enable parity error and ECC error logging for entries on forwarding chips.

Use undo parity-error monitor log enable to disable parity error and ECC error logging for entries on forwarding chips.

Syntax

parity-error monitor log enable

undo parity-error monitor log enable

Default

Parity error and ECC error logging is enabled for entries on forwarding chips.

Views

System view

Predefined user roles

network-admin

Usage guidelines

The device automatically detects parity errors and ECC errors in entries on forwarding chips.

After you execute this command, the device collects parity errors and ECC errors periodically. If the number of parity errors and ECC errors in a statistics period reaches or exceeds the logging threshold, the device generates and sends a parity error and ECC error log message to the information center module. The information center module determines how and where to send the message. For more information about the information center module, see information center configuration in Network Management and Monitoring Configuration Guide.

Examples

# Enable parity error and ECC error logging for entries on forwarding chips.

<Sysname> system-view

[Sysname] parity-error monitor log enable

Related commands

parity-error monitor period

parity-error monitor threshold

parity-error monitor period

Use parity-error monitor period to set the parity error and ECC error statistics period for entries on forwarding chips.

Use undo parity-error monitor period to restore the default.

Syntax

parity-error monitor period value

undo parity-error monitor period

Default

The parity error and ECC error statistics period is 60 seconds for entries on forwarding chips.

Views

System view

Parameters

period: Specifies the parity error and ECC error statistics period in seconds, in the range of 1 to 86400.

Predefined user roles

network-admin

Usage guidelines

The device automatically detects parity errors and ECC errors in entries on forwarding chips. The parity error and ECC error logging feature collects parity error and ECC error statistics periodically, and generates a log message if the number of parity error and ECC errors reaches the logging threshold.

This command determines the period for the device to collect parity error and ECC error statistics.

Examples

# Set the parity error and ECC error statistics period to 120 seconds.

<Sysname> system-view

[Sysname] parity-error monitor period 120

Related commands

parity-error monitor log enable

parity-error monitor threshold

Use parity-error monitor threshold to set the parity error and ECC error logging threshold for entries on forwarding chips.

Use undo parity-error monitor threshold to restore the default.

Syntax

parity-error monitor threshold value

undo parity-error monitor threshold

Default

The parity error and ECC error logging threshold is 5000 for entries on forwarding chips.

Views

System view

Predefined user roles

network-admin

Parameters

value: Specifies the parity error and ECC error logging threshold for entries on forwarding chips, in the range of 1 to 1000000.

Usage guidelines

The device detects parity error and ECC errors in entries on forwarding chips. The parity error and ECC error logging feature collects parity error and ECC error statistics periodically, and generates a log message if the number of parity error and ECC errors reaches the logging threshold. This command sets the logging threshold.

Examples

# Set the parity error and ECC error logging threshold to 8000 for entries on forwarding chips.

<Sysname> system-view

[Sysname] parity-error monitor threshold 8000

Related commands

parity-error monitor log enable

parity-error monitor period

parity-error unrecoverable log enable

Use parity-error unrecoverable log enable to enable uncorrectable parity error and ECC error logging for entries on forwarding chips.

Use undo parity-error unrecoverable log enable to disable uncorrectable parity error and ECC error logging for entries on forwarding chips.

Syntax

parity-error unrecoverable log enable

undo parity-error unrecoverable log enable

Default

Uncorrectable parity error and ECC error logging is enabled for entries on forwarding chips

Views

System view

Predefined user roles

network-admin

Usage guidelines

The device automatically detects parity errors and ECC errors in entries on forwarding chips and tries to correct the error when an error is detected. The uncorrectable parity error and ECC error logging feature enables the device to collect uncorrectable parity error and ECC error statistics periodically. If the number of uncorrectable parity errors and ECC errors reaches or exceeds the logging threshold, the device generates and sends an uncorrectable parity error and ECC error log message to the information center module. The information center module determines how and where to send the log message. For more information about the information center module, see information center configuration in Network Management and Monitoring Configuration Guide.

Examples

# Enable uncorrectable parity error and ECC error logging for entries on forwarding chips

<Sysname> system-view

[Sysname] parity-error unrecoverable log enable

Related commands

parity-error unrecoverable period

parity-error unrecoverable reboot

parity-error unrecoverable threshold

parity-error unrecoverable period

Use parity-error unrecoverable period to set the statistics period for uncorrectable parity errors and ECC errors for entries on forwarding chips.

Use undo parity-error unrecoverable period to restore the default.

Syntax

parity-error unrecoverable period period

undo parity-error unrecoverable period

Default

The statistics period is 60 seconds for uncorrectable parity errors and ECC errors for entries on forwarding chips.

Views

System view

Predefined user roles

network-admin

Parameters

period: Specifies the statistics period for uncorrectable parity errors and ECC errors for entries on forwarding chips, in the range of 1 to 86400, in seconds.

Usage guidelines

This command sets the period for the device to collect uncorrectable parity error and ECC error statistics.

Examples

# Set the statistics period for uncorrectable parity errors and ECC errors in entries on forwarding chips to 120 seconds.

<Sysname> system-view

[Sysname] parity-error unrecoverable period 120

Related commands

parity-error unrecoverable log enable

parity-error unrecoverable reboot

parity-error unrecoverable threshold

parity-error unrecoverable reboot

Use parity-error unrecoverable reboot to enable automatic card reboot upon generation of an uncorrectable parity error and ECC error log.

Use undo parity-error unrecoverable reboot to disable automatic card reboot upon generation of an uncorrectable parity error and ECC error log

Syntax

parity-error unrecoverable reboot

undo parity-error unrecoverable reboot

Default

The card reboots automatically upon generation of an uncorrectable parity error and ECC error log.

Views

System view

Predefined user roles

network-admin

Usage guidelines

Uncorrectable parity errors and ECC errors in entries on forwarding chips might affect system services. To remove the errors from the entries on forwarding chips, you can execute this command to enable automatic card reboot upon generation of an uncorrectable parity error and ECC error log.

Examples

# Enable automatic card reboot upon generation of an uncorrectable parity error and ECC error log.

<Sysname> system-view

[Sysname] parity-error unrecoverable reboot

Related commands

parity-error unrecoverable log enable

parity-error unrecoverable period

parity-error unrecoverable threshold

Use parity-error unrecoverable threshold to set the logging threshold for uncorrectable parity errors and ECC errors on entries on forwarding chips.

Use undo parity-error unrecoverable threshold to restore the default.

Syntax

parity-error unrecoverable threshold value

undo parity-error unrecoverable threshold

Default

The logging threshold is 1 for uncorrectable parity errors and ECC errors in entries on forwarding chips.

Views

System view

Predefined user roles

network-admin

Parameters

value: Specifies the logging threshold for uncorrectable parity errors and ECC errors in entries on forwarding chips, in the range of 1 to 1000000.

Usage guidelines

This command sets the logging threshold.

Examples

# Set the logging threshold for uncorrectable parity errors and ECC errors in entries on forwarding chips to 10.

<Sysname> system-view

[Sysname] parity-error unrecoverable log threshold 10

Related commands

parity-error unrecoverable log enable

parity-error unrecoverable period

parity-error unrecoverable reboot

password-recovery enable

Use password-recovery enable to enable password recovery capability.

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

Syntax

password-recovery enable

undo password-recovery enable

Default

Password recovery capability is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default MDC.

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

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

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

To enhance system security, disable password recovery capability.

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

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

Examples

# Disable password recovery capability.

<Sysname> system-view

[Sysname] undo password-recovery enable

power-supply off

Use power-supply off to power off a card.

Syntax

In standalone mode:

power-supply off slot slot-number

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

CAUTION:

A card cannot receive or send packets after a forced power-off. Before executing this command, make sure you understand its impact on the live network.

This command is supported only on the default MDC.

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

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

(In IRF mode.) To avoid IRF split, do not power off an interface module that contains the only active physical IRF port.

Examples

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

<Sysname> power-supply off slot 2

Related commands

power-supply policy enable

power-supply on

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

Syntax

In standalone mode:

power-supply on slot slot-number

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

This command is supported only on the default MDC.

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

Examples

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

<Sysname> power-supply on slot 2

Related commands

power-supply policy enable

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

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

Syntax

In standalone mode:

power-supply policy enable

undo power-supply policy enable

In IRF mode:

power-supply policy chassis chassis-number enable

undo power-supply policy chassis chassis-number enable

Default

Power supply management is disabled.

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

This command is supported only on the default MDC.

Examples

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

<Sysname> system-view

[Sysname] power-supply policy enable

power-supply policy priority

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

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

Syntax

In standalone mode:

power-supply policy slot slot-number priority priority

undo power-supply policy slot slot-number priority

In IRF mode:

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

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

Default

The power supply priority is 5 for an interface card.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

chassis chassis-number slot slot-number: Specifies an interface module on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)

Usage guidelines

This command is supported only on the default MDC.

This command is supported only on service modules.

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] power-supply policy slot 2 priority 10

Related commands

power-supply policy enable

power-supply policy redundant

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

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

Syntax

In standalone mode:

power-supply policy redundant module-count

undo power-supply policy redundant

In IRF mode:

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

undo power-supply policy chassis chassis-number redundant

Default

The number of redundant power supplies is 0.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

Usage guidelines

This command is supported only on the default MDC.

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

Examples

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

<Sysname> system-view

[Sysname] power-supply policy redundant 1

Related commands

power-supply policy enable

reboot

Use reboot to reboot the device.

Syntax

In standalone mode:

reboot [ slot slot-number ] [ force ]

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

Usage guidelines

CAUTION:

· A reboot might interrupt network services.

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

‌

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

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

In standalone mode:

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

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

In IRF mode:

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

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

Examples

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

<Sysname> reboot

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

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

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

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

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

Validating file. Please wait...

Configuration is saved to mainboard device successfully.

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

Now rebooting, please wait...

# Reboot the device immediately without performing software check.

<Sysname> reboot force

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

Now rebooting, please wait...

Related commands

display system stable state

reset asset-info

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

System view

Predefined user roles

network-admin

mdc-admin

network-operator

mdc-operator

Parameters

chassis: Clears the asset profile for the frame. The device does not support this keyword.

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

csn: Clears the asset ID.

custom: Clears customized asset items.

department: Clears the department name.

description: Clears the asset description.

location: Clears the asset location.

service-date: Clears the service start date.

state: Clears the usage status

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] reset asset-info slot 0 csn

Related commands

display asset-info

set asset-info

reset scheduler logfile

Use reset scheduler logfile to clear job execution log information.

Syntax

reset scheduler logfile

Views

User view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default MDC.

Examples

# Clear job execution log information.

<Sysname> reset scheduler logfile

Related commands

display scheduler logfile

reset transceiver interface

Use reset transceiver interface to reset a transceiver module.

Syntax

reset transceiver interface [ interface-type interface-number ]

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

This command will restart a transceiver module. Use this command only when you cannot troubleshoot transceiver modules by using other methods. Before using this command, make sure you understand its compact on the live network.

This command is supported only on the QSPF transceiver modules.

Examples

# Reset the QSFP28 transceiver module in interface HundredGigE 1/0/1.

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

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

reset version-update-record

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

Syntax

reset version-update-record

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default MDC.

Examples

# Clear the startup software image upgrade records.

<Sysname> system-view

[Sysname] reset version-update-record

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

Related commands

display version-update-record

resource-monitor minor resend enable

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

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

Syntax

resource-monitor minor resend enable

undo resource-monitor minor resend enable

Default

Resending of minor resource depletion alarms is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is not supported on the LSCM1GT48SC0 card.

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

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

Examples

# Enable resending of minor resource depletion alarms.

<Sysname> system-view

[Sysname] resource-monitor minor resend enable

Related commands

display resource-monitor

resource-monitor output

resource-monitor resource

resource-monitor output

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

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

Syntax

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

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

Default

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

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

Usage guidelines

This command is not supported on the LSCM1GT48SC0 card.

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

Examples

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

<Sysname> system-view

[Sysname] resource-monitor output syslog

Related commands

resource-monitor minor resend enable

resource-monitor resource

Use resource-monitor resource to set resource depletion thresholds.

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

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

Views

System view

Predefined user roles

network-admin

Parameters

resource-name: Specifies a resource type by its name. The values for this argument are case insensitive and cannot be abbreviated. Table 33 shows the resource types that can be monitored.

Table 33 Resource types that can be monitored

Resource type	Description
agg_group	Aggregation group resources.
agg_member	Member ports in an aggregation group.
arp	ARP resource.
egr_hash_scl_0_group	Hash SCL resources in the group 0 outbound direction.
egr_hash_scl_1_group	Hash SCL resources in the group 1 outbound direction.
egs_acl	Outbound ACL resources.
egs_counter	Outbound counter resources.
igs_acl	Inbound ACL resources.
igs_counter	Inbound counter resources.
input_flowrate	Inbound traffic flow rate resources
ing_hash_scl_0_group	Hash SCL resources in the group 0 inbound direction.
ing_hash_scl_1_group	Hash SCL resources in the group 1 inbound direction.
ipmc	Layer 3 multicast replication table resources.
ipv6	IPv6 routing table resources.
l2mc	Multicast replication table resources for a VLAN.
local_mc	Local replication table resources (multicast local replication table resource pools, affecting the number of VXLANs that can be added to a VXLAN tunnel).
mac	MAC address table resources.
meter	Meter resources.
mqcin	Inbound MQC resources.
mqcout	Outbound MQC resources.
nd	ND resources.
nexthoppool1	Next-hop pool resources for the underlay network.
nexthoppool2	Next-hop pool resources for the overlay network.
nexthoppool3	Local next-hop resource pool resources (next-hop resource pool used by local services such as multicast).
openflow	OpenFlow resources.
output_flowrate	Outbound traffic flow rate resources.
pbr	PBR resources.
pfilterin	Inbound packet filter resources.
pfilterout	Outbound packet filter resources.
port	Layer 2 Ethernet interface resources.
route	Routing resources.
rport	Layer 3 Ethernet interface resources.
stg	STP instance resources.
vlaninterface	VLAN interface resources.
vrf	VPN instance resources.

‌

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

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

by-percent: Specifies resource depletion thresholds in percentage.

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

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

Usage guidelines

This command is not supported on the LSCM1GT48SC0 card.

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

Examples

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

<Sysname> system-view

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

Related commands

display resource-monitor

resource-monitor minor resend enable

resource-monitor output

restart standby

Use restart standby to reboot the standby MPU.

Syntax

restart standby

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is available only in standalone mode.

This command is supported only on the default MDC.

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

Examples

# Reboot the standby MPU.

<Sysname> system-view

[Sysname] restart standby

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

The standby MPU is rebooting. Please wait...

Related commands

reboot

restore factory-default

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

Syntax

restore factory-default

Views

User view

Predefined user roles

network-admin

Usage guidelines

CAUTION:

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

This command is supported only on the default MDC.

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

Examples

# Restore the factory-default configuration for the device.

<Sysname> restore factory-default

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

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

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

Related commands

reboot

scheduler job

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

Use undo scheduler job to delete a job.

Syntax

scheduler job job-name

undo scheduler job job-name

Default

No job exists.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

Examples

# Create a job named backupconfig and enter job view.

<Sysname> system-view

[Sysname] scheduler job backupconfig

[Sysname-job-backupconfig]

Related commands

command

scheduler schedule

scheduler logfile size

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

Syntax

scheduler logfile size value

Default

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

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] scheduler logfile size 32

Related commands

display scheduler logfile

scheduler reboot at

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

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot at time [ date ]

undo scheduler reboot

Default

No reboot date or time is specified.

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

CAUTION:

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

‌

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

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

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

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

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

Examples

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

<Sysname> scheduler reboot at 12:00

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

Related commands

scheduler reboot delay

Use scheduler reboot delay to specify the reboot delay time.

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot delay time

undo scheduler reboot

Default

No reboot delay time is specified.

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

CAUTION:

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

‌

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

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

Examples

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

<Sysname> scheduler reboot delay 88

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

scheduler schedule

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

Use undo scheduler schedule to delete a schedule.

Syntax

scheduler schedule schedule-name

undo scheduler schedule schedule-name

Default

No schedule exists.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

To configure a schedule:

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

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

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

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

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

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

Examples

# Create a schedule named saveconfig.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

Related commands

job

time at

time once

set asset-info

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

System view

Predefined user roles

network-admin

mdc-admin

network-operator

mdc-operator

Parameters

chassis: Configures an asset profile for the frame.

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

csn csn-number: Specifies an asset ID for the asset, a string of 1 to 64 characters.

custom name value: Defines an asset profile item and specifies the value.

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

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] set asset-info slot 0 csn 123456

Related commands

display asset-info

reset asset-info

shutdown-interval

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

Use undo shutdown-interval to restore the default.

Syntax

shutdown-interval interval

undo shutdown-interval

Default

The port status detection timer setting is 30 seconds.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

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

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

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

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

Examples

# Set the port status detection timer to 100 seconds.

<Sysname> system-view

[Sysname] shutdown-interval 100

switch-mode

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

Use undo switch-mode to remove the operating mode settings for a service module. The service module does not have an operating mode specified.

Syntax

In standalone mode:

switch-mode slot slot-number { balance | bridging | enhance | enhance-balance | enhance-bridging | enhance-routing | normal | routing }

undo switch-mode slot slot-number

In IRF mode:

switch-mode chassis chassis-number slot slot-number { balance | bridging | enhance | enhance-balance | enhance-bridging | enhance-routing | normal | routing}

undo switch-mode chassis chassis-number slot slot-number

Default

The operating mode of a service module is normal.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

balance: Specifies the balanced mode.

bridging: Specifies the extended MAC mode.

enhance: Specifies the enhanced mode.

enhance-balance: Specifies the enhanced balanced mode.

enhance-bridging: Specifies the enhanced extended MAC mode.

enhance-routing: Specifies the enhanced extended routing mode.

normal: Specifies the normal mode.

routing: Specifies the extended routing mode.

slot slot-number: Specifies the ID of the slot where the service module resides.

chassis chassis-number: Specifies the ID of the IRF member device. (In IRF mode.)

Usage guidelines

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

The LSCM1GT48SC0 service module supports only the normal, bridging, routing, and balance modes.

The SF interfaces do not support enhanced modes.

Examples

# (In standalone mode.) Set the operating mode to bridging for the interface module in slot 2.

<Sysname> system-view

[Sysname] switch-mode bridging slot 2

Related commands

display switch-mode status

sysid

Use sysid to set the system ID.

Use undo sysid to restore the default.

Syntax

sysid system-id

undo sysid

Default

The device does not have a system ID.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

system-id: Specifies the system ID for the device. You can use this argument to indicate the position or functionality of the device or any other information.

Examples

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

<Sysname> system-view

[Sysname] sysid positon-hall

sysname

Use sysname to set the device name.

Use undo sysname to restore the default.

Syntax

sysname sysname

undo sysname

Default

The device name is H3C.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

Examples

# Set the name of the device to R2000.

<Sysname> system-view

[Sysname] sysname R2000

[R2000]

system handshake timeout

Use system handshake timeout to set the handshake timeout time between an MPU and an interface module.

Use undo system handshake timeout to restore the default.

Syntax

system handshake timeout timeout

undo system handshake timeout

Default

The handshake timeout time between an MPU and an interface card is 60 seconds.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

timeout: Specify the handshake timeout time between an MPU and an interface module. The value range for this argument is 10 to 60 seconds.

Usage guidelines

After starting up, an interface module will actively register with an MPU so that it can be managed by the MPU. During device operation, the MPU will periodically send handshake packets to the interface to identify whether the interface module is operating correctly. If the interface module does not reply to the MPU before the specified timeout time expires, the MPU considers the interface module to be faulty and will restart the interface module.

In some scenarios with handshake timeout requirements, you can execute this command to specify a handshake timeout time as needed to identify faulty interfaces as soon as possible. For example, some scenarios might require a short traffic interruption due to card restart.

Examples

# Set the handshake timeout time to 40 seconds between the MPU and an interface module.

<Sysname> system-view

[Sysname] system handshake timeout 40

system switchover

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

Syntax

system switchover

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is available only in standalone mode.

This command is supported only on the default MDC.

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

Examples

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

<Sysname> system-view

[Sysname] system switchover

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

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

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

Now rebooting, please wait...

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

<Sysname> system-view

[Sysname] system switchover

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

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

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

[Y/N]:y

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

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

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

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

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

Now rebooting, please wait...

system-working-mode

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

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

Syntax

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

undo system-working-mode

Default

The device operates in standard mode.

Views

System view

Predefined user roles

network-admin

Parameters

advance: Sets the system operating mode to advanced.

expert: Sets the system operating mode to expert.

standard: Sets the system operating mode to standard.

Usage guidelines

This command is supported only on the default MDC.

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

Change to the operating mode takes effect after a reboot.

Examples

# Set the system operating mode to advanced.

<Sysname> system-view

[Sysname] system-working-mode advance

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

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

temperature-limit

Use temperature-limit to set the temperature alarm thresholds.

Use undo temperature-limit to restore the default.

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

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

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

hotspot: Configures temperature alarm thresholds for hotspot sensors. A hotspot sensor is typically located near a high-heat chip to monitor the chip temperature.

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

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

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

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

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

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

Usage guidelines

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

· Sends log messages and traps.

· Sets LEDs on the device panel.

This command is supported only on the default MDC.

Examples

# (In standalone mode.) Set temperature alarm thresholds for hotspot sensor 1 in a slot.

<Sysname> system-view

[Sysname] temperature-limit slot 1 hotspot 1 -10 50 60

Related commands

display environment

time at

Use time at to specify an execution date and time for a non-periodic schedule.

Use undo time to delete the execution date and time configuration for a non-periodic schedule.

Syntax

time at time date

undo time

Default

No execution time or date is specified for a non-periodic schedule.

Views

Schedule view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

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

The time at command, the time once command, and the time repeating command overwrite one another. The most recently executed command takes effect.

Examples

# Configure the device to execute schedule saveconfig at 01:01 a.m. on May 11, 2015.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time at 1:1 2015/05/11

Related commands

scheduler schedule

time once

Use time once to specify one or more execution days and the execution time for a non-periodic schedule.

Use undo time to delete the execution day and time configuration for a non-periodic schedule.

Syntax

time once at time [ month-date month-day | week-day week-day&<1-7> ]

time once delay time

undo time

Default

No execution time or day is specified for a non-periodic schedule.

Views

Schedule view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

Usage guidelines

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

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

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

The time at command, the time once command, and the time repeating command overwrite one another. The most recently executed command takes effect.

Examples

# Configure the device to execute schedule saveconfig once at 15:00.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 15:00

Schedule starts at 15:00 5/11/2011.

# Configure the device to execute schedule saveconfig once at 15:00 on the coming 15th day in a month.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 15:00 month-date 15

# Configure the device to execute schedule saveconfig at 12:00 p.m. on the coming Monday and Friday.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 12:00 week-day mon fri

# Configure the device to execute schedule saveconfig after 10 minutes.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once delay 10

Related commands

scheduler schedule

time repeating

Use time repeating to specify an execution time table for a periodic schedule.

Use undo time to delete the execution time table configuration for a periodic schedule.

Syntax

time repeating [ at time [ date ] ] interval interval

time repeating at time [ month-date [ month-day | last ] | week-day week-day&<1-7> ]

undo time

Default

No execution time table is specified for a periodic schedule.

Views

Schedule view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

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

Usage guidelines

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

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

The time at command, the time once command, and the time repeating command overwrite one another, whichever is executed most recently takes effect.

Examples

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

Related commands

scheduler schedule

transceiver health check enable

Use transceiver health check enable to enable transceiver health check.

Use undo transceiver health check enable to restore the default.

Syntax

transceiver health check enable

undo transceiver health check enable

Default

Transceiver health check is disabled.

Views

System view

Predefined user roles

network-admin

Examples

# Enable transceiver health check.

<Sysname> system-view

[Sysname] transceiver health check enable

Related commands

display transceiver health

transceiver health weight

Use transceiver health weight to set the weights for transceiver health calculation.

Use undo transceiver health weight to restore the default.

Syntax

transceiver health weight temp temp-weight voltage voltage-weight bias bias-weight rxpower rxpower-weight txpower txpower-weight

undo transceiver health weight

Default

The weights for calculating transceiver health are as follows:

· Temperature weight: 15.

· Voltage weight: 5.

· Bias current weight: 30.

· Receive power weight: 10.

· Transmit power weight: 40.

Views

System view

Predefined user roles

network-admin

Parameters

temp temp-weight: Specifies the temperature weight in transceiver health calculation. The value range is 1 to 96.

voltage voltage-weight: Specifies the voltage weight in transceiver health calculation. The value range is 1 to 96.

bias bias-weight: Specifies the bias current weight in transceiver health calculation. The value range is 1 to 96.

rxpower rxpower-weight: Specifies the receive power weight in transceiver health calculation. The value range is 1 to 96.

txpower txpower-weight: Specifies the transmit power weight in transceiver health calculation. The value range is 1 to 96.

Usage guidelines

Use this command to set the weights of five diagnosis parameters for transceiver health calculation, including temperature, voltage, bias current, receive power, and transmit power.

The sum of the weight of each diagnosis parameter for transceiver health calculation must be 100.

Examples

# Set the weights of the temperature, voltage, bias current, receive power, and transmit power to 20.

<Sysname> system-view

[Sysname] transceiver health weight temp 20 voltage 20 bias 20 rxpower 20 txpower 20

Related commands

display transceiver health

transceiver health check enable

transceiver monitor enable

Use transceiver monitor enable to enable transceiver monitoring.

Use undo transceiver monitor enable to restore the default.

Syntax

transceiver monitor enable

undo transceiver monitor enable

Default

Transceiver monitoring is disabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is supported only on the default MDC.

After transceiver monitoring is enabled, the device samples the parameters of transceiver modules periodically, including the input power and output power of transceiver modules. If a sampled value reaches the alarm threshold, the device generates a log to notify users.

Examples

# Enable transceiver monitoring.

<Sysname> system-view

[Sysname] transceiver monitor enable

Related commands

transceiver monitor interval

Use transceiver monitor interval to set a transceiver monitoring interval.

Use undo transceiver monitor interval to restore the default.

Syntax

transceiver monitor interval interval

undo transceiver monitor interval

Default

The transceiver monitoring interval is 600 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the transceiver monitoring interval in seconds. The value range is 300 to 3600.

Usage guidelines

This command is supported only on the default MDC.

This command takes effect only when the transceiver monitor enable command is used.

Examples

# Set the transceiver monitoring interval to 500 seconds.

<Sysname> system-view

[Sysname] transceiver monitor interval 500

Related commands

transceiver monitor enable

user-role

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

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

Syntax

user-role role-name

undo user-role role-name

Default

A schedule has the user roles of the schedule creator.

Views

Schedule view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

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

Examples

# Assign user role rolename to schedule test.

<Sysname> system-view

[Sysname] scheduler schedule test

[Sysname-schedule-test] user-role rolename

Related commands

command

scheduler schedule

xbar

Use xbar to set the load mode for MPUs.

Syntax

In standalone mode:

xbar { load-balance | load-single }

In IRF mode:

xbar chassis chassis-number { load-balance | load-single }

Default

The MPUs operate in load-balance mode.

Views

System view

Predefined user roles

network-admin

Parameters

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

load-balance: Configures the active MPU and standby MPUs to balance the load for processing and forwarding packets.

load-single: Configures the MPUs so only the active MPU processes and forwards packets. The standby MPU backs up data and monitors the status of the active MPU.

Usage guidelines

This command is supported only on the default MDC.

A single-MPU device supports only the load-single mode. If you set the MPU load mode to load-balance, the device automatically switches to load-single mode.

This command does not take effect on the S7503X-G and S7503X-M-G devices.

Examples

# (In standalone mode.) Set the load mode for the active MPU and the standby MPUs to load-balance.

<Sysname> system-view

[Sysname] xbar load-balance

Related commands

display xbar

01-Fundamentals Command Reference

clock datetime

display copyright

Usage guidelines

display device manuinfo chassis-only

display fan

display memory

display power-supply

display scheduler job

display system stable state

display version-update-record

job

memory-threshold usage

monitor cpu-usage interval

resource-monitor minor resend enable

resource-monitor resource

scheduler reboot at

sysid

system-working-mode

time once

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us