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

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 system time is determined by the UTC time, the time zone, and the daylight saving time. You can use the display clock command to view the system time.

You can use this command to specify a UTC time for the device, or configure the device to obtain the UTC time from an NTP time source. The UTC time obtained from an NTP time source is more precise.

Examples

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

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

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

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

Related commands

· clock protocol

· clock summer-time

· clock timezone

· display clock

clock protocol

Use clock protocol to specify the UTC time source.

Use undo clock protocol to restore the default.

Syntax

clock protocol { none | ntp mdc mdc-id }

undo clock protocol

Default

The device obtains the UTC time through NTP.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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.

Usage guidelines

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

The system time is determined by the UTC time, the time zone, and the daylight saving time. You can use the display clock command to view the system time.

The device can obtain the UTC time from one of the following time sources:

· None—Local UTC time set by using the clock datetime command.

· NTP—NTP time source.

The UTC time obtained from an NTP time source is more precise.

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. By default, the device uses the NTP time source specified on the default MDC.

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 configure the device to use daylight saving time during a specific period of time.

Use undo clock summer-time to cancel the configuration.

Syntax

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

undo clock summer-time

Default

Daylight saving time is disabled.

Views

System view

Predefined user roles

network-admin

mdc-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 date, 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 date, where:

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

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

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

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

Usage guidelines

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

The system time is determined by the UTC time, the time zone, and the daylight saving time. You can use the display clock command to view the system time.

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

Examples

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

<Sysname> system-view

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

Related commands

· clock datetime

· clock timezone

· display clock

clock timezone

Use clock timezone to set the time zone.

Use undo clock timezone to restore the default.

Syntax

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

undo clock timezone

Default

The time zone is not set.

Views

System view

Predefined user roles

network-admin

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

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 system time is determined by the UTC time, the time zone, and the daylight saving time. You can use the display clock command to view the system time.

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

Examples

# Set the name of the local 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.

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 job backupconfig to back up configuration file startup.cfg 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 job shutdownGE to shut down the interface GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] scheduler job shutdownGE

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

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

[Sysname-job-shutdownGE] command 3 shutdown

Related commands

scheduler job

copyright-info enable

Use copyright-info enable to enable copyright statement display.

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

Syntax

undo copyright-info enable

Default

Views

System view

Predefined user roles

network-admin

mdc-admin

Examples

# Enable copyright statement display.

<Sysname> system-view

[Sysname] copyright-info enable

· When a Telnet user logs in, the following statement appears:

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

* Without the owner's prior written consent, *

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

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

· When a console user quits user view, the system automatically restarts the session and displays the following message:

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

* Without the owner's prior written consent, *

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

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

User interface aux0 is available.

Press ENTER to get started.

# Disable copyright statement display.

<Sysname> system-view

[Sysname] undo copyright-info enable

· When a Telnet user logs in, the user view prompt appears as follows:

· When a console user quits user view, the system automatically restarts the session and displays the following message:

User interface aux0 is available.

Press ENTER to get started.

display alarm

Use display alarm to display alarm information.

Syntax

In standalone mode:

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

In IRF mode:

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

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 this option, the command displays alarm information for all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. On an IRF fabric, this command displays information for all cards if you do not specify a card. On an IRF 3 system, this command displays information for all cards and PEXs if you do not specify a card or PEX. (In IRF mode.)

Examples

# (In standalone mode.) Display alarm information.

<Sysname> display alarm

Slot CPU Level Info

- - INFO Power 1 is absent.

- - INFO Power 2 is absent.

- - INFO Power 3 is absent.

8 0 ERROR Board is faulty

9 0 ERROR Board is faulty

Table 1 Command output

Field	Description
Slot	Slot number of the card with an alarm. If the value is a hyphen (-), the alarm was generated by the chassis. (In standalone mode.)
Level	Alarm severity. Possible values include ERROR, WARNING, NOTICE, and INFO, in descending order.
Info	Detailed alarm information.
faulty	The card is starting up or is faulty.

# (In IRF mode.) Display alarm information.

<Sysname> display alarm

Chassis Slot CPU Level Info

1 - - INFO Chassis 1 Power 1 is absent.

1 - - INFO Chassis 1 Power 2 is absent.

1 8 0 ERROR Chassis 1 Board is faulty

2 9 0 ERROR Chassis 2 Board is faulty

Table 2 Command output

Field	Description
Chassis	ID of the IRF member device with an alarm.
Slot	Slot number of the card.
Level	Alarm severity. Possible values include ERROR, WARNING, NOTICE, and INFO, in descending order.
Info	Detailed alarm information.
The board in slot n is faulty.	The card in slot n is starting up or is faulty.

display asset-info

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

fan fan-id: Displays the asset profile for the specified fan tray. The device does not support this option.

power power-id: Displays the asset profile for the specified power module. The device does not support this option.

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

<Sysname> system-view

[Sysname] display asset-info slot 0 csn

Type : Slot 0

csn : 123456

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

<Sysname> system-view

[Sysname] display asset-info slot 0

Type : Slot 0

csn : 123456

description : Slot 0

location :

service-date:

department : MKT

state : Normal

custom:

# (In IRF mode.) Display the asset ID for slot 0 on IRF member device 1.

<system-view> system-view

[Sysname] display asset-info chassis 1 slot 0 csn

Type : Slot 0

csn : 123456

# (In IRF mode.) Display the asset information for slot 0 on IRF member device 1.

<Sysname> system-view

[Sysname] display asset-info chassis 1 slot 0

Type : Slot 0

csn : 123456

description : Slot 0

location :

service-date:

department : MKT

state : Normal

custom:

Related commands

· reset asset-info

· set asset-info

display clock

Use display clock to display the system time, date, local 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 local time zone is not specified.

<Sysname> display clock

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

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

<Sysname> display clock

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

Time Zone : Z5 add 05:00:00

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

<Sysname> display clock

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

Time Zone : Z5 add 05:00:00

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

Related commands

· clock datetime

· clock timezone

· clock summer-time

display copyright

Use display copyright to display the copyright statement, including software and hardware copyright statements, and software license information.

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

In IRF mode:

display cpu-usage [ 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 this option, the command displays the CPU usage statistics for all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. On an IRF fabric, this command displays CPU usage statistics for all cards if you do not specify a card. On an IRF 3 system, this command displays CPU usage statistics for all cards and PEXs if you do not specify a card or PEX. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. If you do not specify this option, the command displays the CPU usage statistics for the default CPU.

Usage guidelines

After startup, the device tracks the average CPU usage at the following intervals:

· 5 seconds.

· 1 minute.

· 5 minutes.

This command displays the average CPU usage values for the last 5 seconds, 1 minute, and 5 minutes.

Examples

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

<Sysname> display cpu-usage

Slot 3 CPU 0 CPU usage:

2% in last 5 seconds

2% in last 1 minute

2% in last 5 minutes

Slot 7 CPU 0 CPU usage:

0% in last 5 seconds

0% in last 1 minute

0% in last 5 minutes

# (In IRF mode.) Display the current CPU usage statistics for all cards.

<Sysname> display cpu-usage

Chassis 1 Slot 3 CPU 0 CPU usage:

2% in last 5 seconds

2% in last 1 minute

2% in last 5 minutes

Chassis 1 Slot 7 CPU 0 CPU usage:

0% in last 5 seconds

0% in last 1 minute

0% in last 5 minutes

Table 3 Command output

Field	Description
2% in last 5 seconds	Average CPU usage during the last 5-second interval.
2% in last 1 minute	Average CPU usage during the last 1-minute interval.
2% in last 5 minutes	Average CPU usage during the last 5-minute interval.
Slot x CPU y CPU usage	Usage statistics for CPU y of the card in slot x. (In standalone mode.)
Chassis x Slot y CPU z CPU usage	Usage statistics for CPU z of the card in slot y on member device x. (In IRF mode.)

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 this option, the 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 or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. If you do not specify a card or PEX, this command displays the CPU usage monitoring settings for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. If you do not specify this option, the command displays the CPU usage monitoring settings for the default CPU.

Examples

# Display the CPU usage monitoring settings.

<Sysname> display cpu-usage configuration

CPU usage monitor is enabled.

Current monitor interval is 60 seconds.

Current monitor threshold is 99%.

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. If you do not specify this option, the command displays the historical 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 the job job-id option but do not specify this option, the command displays the historical CPU usage statistics for the process on the active MPU. If you do not specify any options, the command displays the historical statistics for all processes on all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. If you specify a process but do not specify a card or PEX, 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 in the IRF fabric. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. If you specify the job job-id option but do not specify this option, the command displays the historical CPU usage statistics for the default CPU. If you do not specify the job job-id option or this option, the 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.

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

Examples

# Display the historical CPU usage statistics for the entire system.

<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 (Chassis 1 Slot 7 CPU 0)

The output shows the following items:

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

· CPU that is holding the process is CPU 0 in slot 7 of member device 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 than 2%.

# Display the historical CPU usage statistics for process 1.

<Sysname> display cpu-usage history job 1

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 (Chassis 1 Slot 7 CPU 0)

The output shows the following items:

· Process name, which is scmd. A process name in a pair of square brackets ([ ]) represents a kernel process.

· CPU that is holding the process is CPU 0 in slot 7 of member device 1.

· Historical CPU usage statistics for process 1 in the last 60 minutes.

¡ 20 minutes ago: Approximately 5%.

¡ Other time: 2% or lower than 2%.

Related commands

· monitor cpu-usage enable

· monitor cpu-usage interval

display device

Use display device to display device information.

Syntax

In standalone mode:

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

In IRF mode:

display device [ flash ] [ 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: Specifies the flash memory.

chassis chassis-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number. On an IRF fabric, this command displays hardware information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays hardware information for all IRF member devices and PEXs if you do not specify a member device or PEX. (In IRF mode.)

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

slot slot-number: Specifies a card or a PEX by its slot number. On an IRF fabric, this command displays hardware information for all cards if you do not specify a card. On an IRF 3 system, this command displays hardware information for all cards and PEXs if you do not specify a card or PEX. (In IRF mode.)

subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify this option, the command does not display information about any subcards. This option is not supported in the current software version.

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

Examples

# (In standalone mode.) Display device information.

<Sysname> display device

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

0 LSQM3MPUB0 Master 0 S7500E-7178 None

1 NONE Absent 0 NONE None

2 LSQ1GP48EB0 Normal 0 S7500E-7178 None

3 NONE Absent 0 NONE None

4 NONE Absent 0 NONE None

5 NONE Absent 0 NONE None

6 NONE Absent 0 NONE None

7 NONE Absent 0 NONE None

The output shows that the device has one MPU and one interface module. The MPU is in slot 0, and the interface module is in slot 2.

Table 4 Command output

Field	Description
Slot No.	Slot number of the card.
Brd Type	Hardware type of the card.
Brd Status	Card status: · Standby—The card is the standby MPU. · Master—The card is the active MPU. · Absent—The slot is not installed with a card. · Fault—The card is faulty and cannot start up. · Normal—The card is an interface module and is operating correctly.
Subslot	Maximum number of subcards that the base card supports. This field is not supported in the current software version.
Sft Ver	Software version of the card.
Patch Ver	Patch version of the card.

# (In IRF mode.) Display device information about all IRF member devices.

<Sysname> display device

Slot Type State Subslot Soft Ver Patch Ver

1/0 LSQM3MPUB0 Master 0 S7500E-7178 None

1/1 NONE Absent 0 NONE None

1/2 LSQ1GP48EB0 Normal 0 S7500E-7178 None

1/3 NONE Absent 0 NONE None

1/4 NONE Absent 0 NONE None

1/5 NONE Absent 0 NONE None

1/6 NONE Absent 0 NONE None

1/7 NONE Absent 0 NONE None

The output shows that the IRF fabric has one member device (with the member ID 1). The card in slot 0 is the global active MPU. The card in slot 2 is an interface module.

Table 5 Command output

Field	Description
Slot	Member ID of the chassis and slot number of the card, in the member ID/slot number format.
Type	Card type.
State	Card status: · Absent—No card is inserted in the slot. · Master—The card is the global active MPU. · Standby—The card is a global standby MPU. · Normal—The card is an interface module and is operating correctly. · Fault—The card is faulty.
Subslot	Maximum number of subcards that the card supports. This field is not supported in the current software version.
Soft Ver	Software version of the card.
Patch Ver	Patch version of the card. If no patch is installed, the value of this field is None.

display device manuinfo

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

slot slot-number: Specifies a card by its slot number. If you do not specify this option, the command displays electronic label information of all cards. (In standalone mode.)

slot slot-number: Specifies a card or a PEX by its slot number. If you do not specify this option, the command displays electronic label information for all cards and PEXs. (In IRF mode.)

Usage guidelines

An electronic label is a profile of a device or card. It contains the permanent configuration, including the serial number, manufacturing date, MAC address, and vendor name. The data is written to the storage component during debugging or testing.

Examples

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

<Sysname> display device manuinfo

Chassis self:

The operation is not supported on the specified chassis.

Slot 0 CPU 0:

No manuinfo in EEPROM, please download it.

Slot 2 CPU 0:

DEVICE_NAME : LSQM1GP48EB0

DEVICE_SERIAL_NUMBER : 210231A889B143000001

MAC_ADDRESS : NONE

MANUFACTURING_DATE : 2014-04-08

VENDOR_NAME : H3C

Fan 0:

The operation is not supported on the specified fan.

Power 1:

DEVICE_NAME : POWER

DEVICE_SERIAL_NUMBER : 210231A2YY0123456719

MAC_ADDRESS :

MANUFACTURING_DATE :

VENDOR_NAME : H3C

Table 6 Command output

Field	Description
Slot m CPU n	Slot number of the card and number of the CPU.
DEVICE_NAME	Device name.
DEVICE_SERIAL_NUMBER	Serial number.
MAC_ADDRESS	MAC address.
MANUFACTURING_DATE	Manufacturing date.
VENDOR_NAME	Vendor name.

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

<Sysname> display device manuinfo

Chassis 1:

Chassis self:

The operation is not supported on the specified chassis.

Slot 0 CPU 0:

No manuinfo in EEPROM, please download it.

Slot 2 CPU 0:

DEVICE_NAME : LSQM1GP48EB0

DEVICE_SERIAL_NUMBER : 210231A889B143000001

MAC_ADDRESS : NONE

MANUFACTURING_DATE : 2014-04-08

VENDOR_NAME : H3C

Fan 0:

The operation is not supported on the specified fan.

Power 1:

DEVICE_NAME : POWER

DEVICE_SERIAL_NUMBER : 210231A2YY0123456719

MAC_ADDRESS :

MANUFACTURING_DATE :

VENDOR_NAME : H3C

Table 7 Command output

Field	Description
Chassis x	Member ID of the member device
Slot y CPU z	Number of the slot and number of the CPU.
DEVICE_NAME	Device name.
DEVICE_SERIAL_NUMBER	Serial number.
MAC_ADDRESS	MAC address.
MANUFACTURING_DATE	Manufacturing date.
VENDOR_NAME	Vendor name.

display device manuinfo chassis-only

Use display device manuinfo chassis-only to display electronic label information for a 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 or specifies a PEX by its virtual chassis number. (In IRF mode.)

Examples

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

<Sysname> display device manuinfo chassis-only

Chassis self:

DEVICE_NAME : backplane

DEVICE_SERIAL_NUMBER : 210235A36L1234567890

MAC_ADDRESS : NONE

MANUFACTURING_DATE : 2010-01-20

VENDOR_NAME : H3C

# (In IRF mode.) Display electronic label information for the backplane on IRF member device 1.

<Sysname> display device manuinfo chassis 1 chassis-only

Chassis 1:

Chassis self:

DEVICE_NAME : backplane

DEVICE_SERIAL_NUMBER : 210235A36L1234567891

MAC_ADDRESS : NONE

MANUFACTURING_DATE : 2010-01-20

VENDOR_NAME : H3C

display device manuinfo power

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

Syntax

In standalone mode:

display device manuinfo power power-id

In IRF mode:

display device manuinfo chassis { chassis-number | virtual-chassis-number slot slot-number } power power-id

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

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

<Sysname> display device manuinfo power 2

Power 2:

DEVICE_NAME : power

DEVICE_SERIAL_NUMBER : 210231A2YY0123456719

MAC_ADDRESS :

MANUFACTURING_DATE :

VENDOR_NAME : H3C

# (In IRF mode.) Display electronic label information for power module 2 on IRF member device 1.

<Sysname> display device manuinfo chassis 1 power 2

Chassis 1:

Power 2:

DEVICE_NAME : power2

DEVICE_SERIAL_NUMBER : 210235A36L1234567891

MAC_ADDRESS : NONE

MANUFACTURING_DATE : 2010-01-20

VENDOR_NAME : H3C

display diagnostic-information

Use display diagnostic-information to display or save device diagnostic information.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

hardware: Displays hardware-related diagnostic information.

infrastructure: Displays diagnostic information about the fundamental modules.

l2: Displays diagnostic information about Layer 2 features.

l3: Displays diagnostic information about Layer 3 features.

service: Displays diagnostic information about upper-layer features.

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

Usage guidelines

If you do not specify any feature options, the command displays or saves diagnostic information about all feature modules.

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

You can use one of the following methods to collect device diagnostic information:

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

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

If you specify the filename argument, the device also collects and saves core files to the specified file. The file is automatically compressed to save storage space. The default file name is in the diag_sysname_YYYYMMDD-hhmmss.tar.gz format, for example, diag_sysname_20140829-083832.tar.gz.

To view the file content:

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

2. Execute the more command.

Examples

# Display diagnostic information about all feature modules.

<Sysname> display diagnostic-information

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

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

13:38:43 Z5 Wed 09/14/2157

Time Zone : Z5 add 05:00:00

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

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

H3C Comware Software, Version 7.1.045, Release 7178

H3C S7506E uptime is 0 weeks, 0 days, 7 hours, 34 minutes

Last reboot reason : Cold reboot

Boot image: flash:/S7500E-CMW710-BOOT-R7178.bin

Boot image version: 7.1.045, Release 7178

Compiled Nov 07 2014 14:31:01

System image: flash:/S7500E-CMW710-SYSTEM-R7178.bin

System image version: 7.1.045, Release 7178

Compiled Nov 07 2014 14:31:01

...

# Save the operating statistics for all feature modules to file test.tar.gz.

· Method 1: Specify the filename in interactive mode.

<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_20140829-083832.tar.gz]: test.tar.gz

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

Please wait...

Save successfully.

· Method 2: Specify the filename for the command.

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

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

Please wait...

Save successfully.

Related commands

· more

· tar extract

display environment

Use display environment to display the temperature statistics for the temperature sensors, including the current temperature and temperature thresholds.

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 or specifies a PEX by its virtual chassis number. On an IRF fabric, this command displays temperature information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays temperature information for all IRF member devices and PEXs if you do not specify a member device or PEX. (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. (In standalone mode.)

slot slot-number: Specifies a card or a PEX by its slot number. On an IRF fabric, this command displays temperature information for all cards if you do not specify a card. On an IRF 3 system, this command displays temperature information for all cards and PEXs if you do not specify a card or PEX. (In IRF mode.)

Usage guidelines

In standalone mode, this command displays statistics for all temperature sensors on the device if you do not specify a card.

In IRF mode, this command displays statistics for 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 statistics for all sensors on the member device.

Examples

# (In standalone mode.) Display the temperature statistics for all temperature sensors on the device.

<Sysname> display environment

System temperature information (degree centigrade):

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

Slot Sensor Temperature Lower Warning Alarm Shutdown

3 hotspot 1 38 0 80 97 NA

3 hotspot 2 49 0 80 97 NA

7 inflow 1 31 0 71 90 NA

7 outflow 1 44 0 80 99 NA

7 hotspot 1 47 0 81 100 NA

7 hotspot 2 53 0 88 107 NA

Table 8 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	Slot number of a card. (In standalone mode.)
Slot	Member ID and slot number of a card on an IRF member device in the member ID/slot number format. (In IRF mode.)
Temperature	Current temperature.
LowerLimit	Lower temperature limit.
WarningLimit	Warning temperature threshold.
AlarmLimit	Alarming temperature threshold.
ShutdownLimit	Shutdown temperature threshold. When the sensor temperature reaches the limit, the system shuts down automatically.

display fan

Use display fan to display the operating states of fans.

Syntax

In standalone mode:

display fan [ fan-id ]

In IRF mode:

display fan [ chassis { chassis-number | virtual-chassis-number slot slot-number } [ fan-id ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

chassis { chassis-number | virtual-chassis-number slot slot-number }: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number and slot number. The slot number is fixed at 0. On an IRF fabric, this command displays fan operating status information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays fan operating status information for all IRF member devices and PEXs if you do not specify a member device or PEX. (In IRF mode.)

fan-id: Specifies a fan by its ID. If you do not specify this option, the command displays the operating states of all fans on the device. (In standalone mode.)

Examples

# Display the operating states of all fans.

<Sysname> display fan

Fan Frame 1 State: Normal

display memory

Use display memory to display memory usage information.

Syntax

In standalone mode:

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

In IRF mode:

display memory [ 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 this option, the command displays memory usage for all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device by its slot number and the member ID. If you do not specify this option, the command displays memory usage for all cards in the IRF fabric. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. If you do not specify this option, the command displays information about the default CPU.

Examples

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

<Sysname> display memory

The statistics about memory is measured in KB:

Slot 3:

Total Used Free Shared Buffers Cached FreeRatio

Mem: 999968 345792 654176 0 0 28496 65.4%

-/+ Buffers/Cache: 317296 682672

Swap: 0 0 0

Slot 7:

Total Used Free Shared Buffers Cached FreeRatio

Mem: 8135316 737928 7397388 0 152 175584 90.9%

-/+ Buffers/Cache: 562192 7573124

Swap: 0 0 0

# (In IRF mode.) Display memory usage information.

<Sysname> display memory

The statistics about memory is measured in KB:

Chassis 1 Slot 3:

Total Used Free Shared Buffers Cached FreeRatio

Mem: 999968 345792 654176 0 0 28496 65.4%

-/+ Buffers/Cache: 317296 682672

Swap: 0 0 0

Chassis 1 Slot 7:

Total Used Free Shared Buffers Cached FreeRatio

Mem: 8135316 737928 7397388 0 152 175584 90.9%

-/+ Buffers/Cache: 562192 7573124

Swap: 0 0 0

Table 9 Command output

Field	Description
Slot	Slot number of a card. (In standalone mode.)
Chassis x Slot x	Slot number of a card on a member device. (In IRF mode.)
Mem	Memory usage information.
Total	Total size of the allocable physical memory space. The memory space is virtually divided into two parts: the allocable part and the unallocable part. The latter is used for kernel codes, kernel management, and ISSU functions. The former can be allocated and used for such tasks as running service modules and storing files.
Used	Used physical memory.
Free	Free physical memory.
Shared	Physical memory shared by processes.
Buffers	Physical memory used for buffers.
Cached	Physical memory used for caches.
FreeRatio	Free memory ratio.
-/+ Buffers/Cache	-/+ Buffers/Cache:used = Mem:Used – Mem:Buffers – Mem:Cached, which indicates the physical memory used by applications. -/+ Buffers/Cache:free = Mem:Free + Mem:Buffers + Mem:Cached, which indicates the physical memory available for applications.
Swap	Swap memory.

display memory-threshold

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify this option, the 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 or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. If you do not specify a card or PEX, 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. If you do not specify this option, the command displays the memory usage thresholds and statistics for the default CPU.

Usage guidelines

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

Examples

# Display memory alarm thresholds and statistics.

<Sysname> display memory-threshold

Memory usage threshold: 100%

Free memory threshold:

Minor: 96M

Severe: 64M

Critical: 48M

Normal: 128M

Current memory state: Normal

Event statistics:

[Back to normal state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Enter minor low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to minor low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Enter severe low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to severe low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Enter critical low-memory state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

display power

Use display power to display power module information.

Syntax

In standalone mode:

display power [ power-id ]

In IRF mode:

display power [ chassis { chassis-number | virtual-chassis-number slot slot-number } [ power-id ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

chassis { chassis-number | virtual-chassis-number slot slot-number }: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number and slot number. The slot number is fixed at 0. On an IRF fabric, this command displays power supply information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays power supply information for all IRF member devices and PEXs if you do not specify a member device or PEX. (In IRF mode.)

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

Usage guidelines

This command does not display the power of an S5130-EI switch that acts as a PEX.

Examples

# Display power module information.

<Sysname> display power

Power 1 State: Normal

Power 2 State: Absent

Power 3 State: Absent

Power 4 State: Absent

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 this option, the 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 has no command, 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 2011

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

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

<Sysname> system-view

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

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

[Sysname-if-range]shutdown

Table 10 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 has no 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/2011 (in 1 hours and 39 minutes).

Related commands

· scheduler reboot at

· scheduler reboot delay

display scheduler schedule

Use display scheduler schedule to display schedule information.

Syntax

display scheduler schedule [ schedule-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

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 this option, the command displays information about all schedules.

Examples

# Display information about all schedules.

<Sysname> display scheduler schedule

Schedule name : START-pc1/pc2

Schedule type : Run on every Mon Tue Wed Thu Fri at 08:00:00

Start time : Thu Aug 7 08:00:00 2014

Last execution time : Yet to be executed

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

Job name Last execution status

start-GigabitEthernet1/0/1 -NA-

start-GigabitEthernet1/0/2 -NA-

Schedule name : STOP-pc1/pc2

Schedule type : Run on every Mon Tue Wed Thu Fri at 18:00:00

Start time : Wed Aug 6 18:00:00 2014

Last execution time : Yet to be executed

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

Job name Last execution status

shutdown-GigabitEthernet1/0/1 -NA-

shutdown-GigabitEthernet1/0/2 -NA-

Schedule name : saveconfig

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

Job name Last execution status

1 -NA-

Table 11 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 serial-no

Use display serial-no to display serial numbers for fan trays and power modules.

Syntax

In standalone mode:

display serial-no { fan fan-id | power power-id }

In IRF mode:

display serial-no chassis chassis-number { fan fan-id | power power-id }

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

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

Examples

# (In standalone mode.) Display the serial number for fan tray 0.

<Sysname> display serial-no fan 0

DEVICE_SERIAL_NUMBER : 210212A0561234560001

# (In IRF mode.) Display the serial number for fan tray 0 on member device 1.

<Sysname> display serial-no chassis 1 fan 0

DEVICE_SERIAL_NUMBER : 210212A0561234560001

Related commands

set serial-no

display switch-mode status

Use display switch-mode status to display operating mode information about 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

network-operator

mdc-admin

mdc-operator

Parameters

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

Usage guidelines

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

Examples

# (In standalone mode.) Display operating mode information about all modules on the switch.

<Sysname> display switch-mode status

LPU switch mode:

Slot Current Config

2 NORMAL *BRIDGING

3 MIX NONE

4 NORMAL NORMAL

5 MIX BRIDGING

* indicates the mode is not supported.

CurrentForwardMode: high-speed-mode

NextForwardMode: standard-mode

# (In IRF mode.) Display operating mode information about all modules on the IRF member device 1.

<Sysname> display switch-mode status chassis 1

LPU switch mode:

Slot Current Config

2 MIX MIX

3 MIX NONE

4 NORMAL NORMAL

5 MIX BRIDGING

CurrentForwardMode: high-speed-mode

NextForwardMode: standard-mode

Table 12 Command output

Field	Description
Current	Current operating mode: · NONE—The module does not support operating mode configuration. · BRIDGING—The module is operating in the extended MAC mode. · NORMAL—The module is operating in the normal mode. · ROUTING—The module is operating in the extended routing mode. · MIX—The module is operating in the extended hybrid mode. · STANDARD-IPV6—The module is operating in the IPv6 standard mode. · IPv6—The module is operating in the IPv6 mode.
Config	Current operating mode: · NONE—No operating mode is specified for the module. · BRIDGING—The extended MAC mode is specified for the module. · NORMAL—The normal mode is specified for the module. · ROUTING—The extended routing mode is specified for the module. · MIX—The extended hybrid mode is specified for the module. · STANDARD-IPV6—The IPv6 standard mode is specified for the module. · IPv6—The IPv6 mode is specified for the module.
* indicates the mode is not supported.	The module does not support the operating mode specified for it. The module will use the default operating mode after reboot.
CurrentForwardMode	Current forwarding mode for service module slots: · standard-mode—Standard mode. · high-speed-mode—High-speed mode.
NextForwardMode	Forwarding mode for service module slots to be used at the next startup: · standard-mode—Standard mode. · high-speed-mode—High-speed mode.

Related commands

· fabric-mode

· switch-mode

display system stable state

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

mdc { id | all }: Specifies an MDC by its ID or specifies all MDCs. If you do not specify this option, the command displays stability information for the system.

Usage guidelines

Before performing an ISSU or active/standby 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 an active/standby switchover.

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

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

Examples

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

<Sysname> display system stable state

System state : Stable

Redundancy state: Stable

Slot CPU Role State

* 1 0 Active Stable

Table 13 Command output

Field	Description
System state	System status: · Stable—The system is operating stably. · Not ready—The system is not operating stably. You cannot perform an ISSU when the system is in this state.
Redundancy state	System redundancy status: · Stable—Both MPUs are operating stably. You can perform a switchover. · No Redundance—The system has only one MPU. You cannot perform a switchover. · Not Ready—The system is not operating stably. You cannot perform a switchover.
Role	Role of the card in the system: · Active—The card is the active MPU. · Standby—The card is the standby MPU. · Other—The card is not an MPU.
State	Card status: · Stable—The card is operating stably. · Board Inserted—The card has just been installed. · Kernel Init—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.
*	The object is not operating stably.

Related commands

· display device

· display ha service-group (High Availability Command Reference)

· display mdc (Virtual Technologies Command Reference)

display system-working-mode

Use display system-working-mode to display the current system working mode.

Syntax

display system-working-mode

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display the current system working mode.

<Sysname> display system-working-mode

The current system working mode is standard.

The system working mode for next startup is standard.

display transceiver alarm

Use display transceiver alarm to display transceiver alarms.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Usage guidelines

Table 14 shows the common transceiver alarms. If no error occurs, "None" is displayed.

Table 14 Common transceiver alarm components

Field	Description
SFP/SFP+:
RX	Receive
TX	Transmit
power	Optical power
Temp	Temperature
QSFP+:
RX	Receive
TX	Transmit
power	Optical power
Temp	Temperature
CFP:
RX	Receive
TX	Transmit
power	Optical power
Temp	Temperature
REFCLK	Reference clock
XFP:
RX	Receive
TX	Transmit
power	Optical power
Temp	Temperature
APD	Avalanche photo diode
TEC	Thermoelectric cooler

Examples

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

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

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

RX power low

RX signal loss

Table 15 Command output

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

display transceiver diagnosis

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

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.

Usage guidelines

This command cannot display information about some transceiver modules.

Examples

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

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

Ten-GigabitEthernet3/0/45 transceiver diagnostic information:

Current diagnostic parameters:

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

30 3.36 7.82 -35.64 -2.23

Alarm thresholds:

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

High 73 3.80 13.20 1.00 0.00

Low -3 2.81 1.00 -9.50 -10.30

Table 16 Command output

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

display transceiver interface

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

Syntax

display transceiver interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

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

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

Ten-GigabitEthernet3/0/45 transceiver information:

Transceiver Type : 10G_BASE_SR_SFP

Connector Type : LC

Wavelength(nm) : 850

Transfer Distance(m) : 80(OM2),20(OM1),300(OM3)

Digital Diagnostic Monitoring : YES

Vendor Name : FINISAR CORP.

Table 17 Command output

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

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

Usage guidelines

This command displays only part of the electronic label information.

Examples

# Display electronic label information for the transceiver module in interface Ten-GigabitEthernet 4/0/45.

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

Ten-gigabitethernet 3/0/45 transceiver manufacture information:

Manu. Serial Number : 213410A0000054000251

Manufacturing Date : 2012-09-01

Vendor Name : H3C

Table 18 Command output

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

display version

Use display version to display system version information.

Syntax

display version

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display system version information.

<Sysname> display version

H3C Comware Software, Version 7.1.045, Release 7178

H3C S7506E uptime is 0 weeks, 0 days, 7 hours, 47 minutes

Last reboot reason : Cold reboot

Boot image: flash:/S7500E-CMW710-BOOT-R7178.bin

Boot image version: 7.1.045, Release 7178

Compiled Nov 07 2014 14:31:01

System image: flash:/S7500E-CMW710-SYSTEM-R7178.bin

System image version: 7.1.045, Release 7178

Compiled Nov 07 2014 14:31:01

MPU(M) 0:

Uptime is 0 weeks,0 days,7 hours,47 minutes

BOARD TYPE: LSQM3MPUB0

DRAM: 2048M bytes

FLASH: 1024M bytes

NVRAM: 1M bytes

PCB 1 Version: VER.B

Bootrom Version: 106

CPLD 1 Version: 001

PowChip Version: None

Release Version: H3C S7506E-7178

Patch Version : None

Reboot Cause : ColdReboot

LPU 2:

Uptime is 0 weeks,0 days,7 hours,45 minutes

BOARD TYPE: LSQ1GP48EB0

DRAM: 1024M bytes

FLASH: 0M bytes

NVRAM: 0K bytes

PCB 1 Version: VER.B

Bootrom Version: 511

CPLD 1 Version: 003

CPLD 2 Version: 002

PowChip Version: None

Release Version: H3C S7506E-7178

Patch Version : None

Reboot Cause : ColdReboot

display version-update-record

Use display version-update-record to display the startup software image upgrade history records of the active MPU. (In standalone mode.)

Use display version-update-record to display the startup software image upgrade history records of the global active MPU. (In IRF mode.)

Syntax

display version-update-record

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

The device records its current startup software version information and all subsequent version update information. Such information can survive reboots.

The maximum number of records is 10.

Examples

# Display the startup software image upgrade history records.

<Sysname> display version-update-record

Name Version Compile time

Record 1 (updated on Sep 12 2157 at 01:06:24):

* S7500E-CMW710-BOOT-R7178.bin 7.1.045 Alpha 7145 Nov 07 2014 14:31:01

* S7500E-CMW710-SYSTEM-R7178.bin 7.1.045 Alpha 7145 Nov 07 2014 14:31:01

Record 2 (updated on Aug 25 2157 at 06:58:44):

* S7500E-CMW710-BOOT-A7143.bin 7.1.045 Alpha 7143 Oct 23 2014 22:48:59

* S7500E-CMW710-SYSTEM-A7143.bin 7.1.045 Alpha 7143 Oct 23 2014 22:48:59

* S7500E-CMW710-DEVKIT-A7143.bin 7.1.045 Alpha 7143 Oct 23 2014 22:48:59

* S7500E-CMW710-MANUFACTURE-A7143.bin 7.1.045 Alpha 7143 Oct 23 2014 22:48:59

...

Table 19 Command output

Field	Description
Name	Software image file name.
*	The new software image is different from the old one.

Related commands

reset version-update-record

display xbar

Use display xbar to display the load modes for MPUs, including the load mode setting and the current load mode.

Syntax

In standalone mode:

display xbar

In IRF mode:

display xbar [ chassis chassis-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID. 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 not supported on an S7502E.

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.

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.

# (In IRF mode.) Display the load modes for the MPUs on all IRF member devices.

<Sysname> display xbar

Chassis 1:

The configured system HA xbar load mode is BALANCE

The activated system HA xbar load mode is SINGLE

Chassis 2:

The configured system HA xbar load mode is SINGLE

The activated system HA xbar load mode is SINGLE

The output shows that two member devices exist in the IRF fabric. On IRF member device 1, the configured load mode is the load-balance mode but the running load mode is the load-single mode. On IRF member device 2, both the configured load mode and the running load mode are the load-single mode.

Related commands

xbar

fabric-mode

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

Use undo fabric-mode to restore the default.

Syntax

In standalone mode:

fabric-mode { high-speed-mode | standard-mode }

undo fabric-mode

In IRF mode:

fabric-mode { high-speed-mode | standard-mode } chassis chassis-number

undo fabric-mode

Default

By default, service module slots operate in standard mode.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

standard-mode: Specifies the standard mode.

high-speed-mode: Specifies the high-speed mode.

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

Usage guidelines

This command is supported only on an S7510E that uses LSQM2MPUC0.

In different forwarding modes, service module slots on an S7510E provide different amounts of bandwidth.

A forwarding mode change takes effect after a device reboot.

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

Examples

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

<Sysname> system-view

[Sysname] fabric-mode standard-mode

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

Process OK.

Related commands

· display switch-mode status

· reboot

fan prefer-direction

Use fan prefer-direction to specify the preferred airflow direction for a PEX.

Use undo fan prefer-direction to restore the default.

Syntax

fan prefer-direction chassis chassis-number slot slot-number { power-to-port | port-to-power }

undo fan prefer-direction chassis chassis-number slot slot-number

Default

The preferred airflow direction is from the power supply side to the port side.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

chassis chassis-number slot slot-number: Specifies a PEX by its virtual chassis number and virtual slot number.

power-to-port: Specifies the airflow direction from the power supply side to the port side.

port-to-power: Specifies the airflow direction from the port side to the power supply side.

Usage guidelines

This command is available only for the following PEXs:

· S5120-28SC-HI switches.

· S5130-EI switches.

· S5130-HI switches.

· S6300 switches.

Examples

# Set the preferred airflow direction to port-to-power for a PEX.

<Sysname> system-view

[Sysname] fan prefer-direction chassis 110 slot 0 port-to-power

Related commands

display fan

hardware-failure-detection

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

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

Syntax

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

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

Default

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

Views

System view

Predefined user roles

network-admin

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

· Shuts down the relevant ports.

· Prohibits loading software for the relevant cards.

· Isolates the relevant cards.

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

off: Takes no action.

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

warning: Sends traps to notify you of the failures.

Usage guidelines

The device automatically detects hardware failures on 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

# Configure the device to restart the cards on which failures are detected.

<Sysname> system-view

[Sysname] hardware-failure-detection board reset

header

Use header to create a banner.

Use undo header to delete a banner.

Syntax

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

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

Default

No banner is configured.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

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

Examples

# Create the incoming banner, legal banner, login banner, MOTD banner, and shell banner.

<Sysname> system-view

[Sysname] header incoming

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

Welcome to incoming(header incoming)%

[Sysname] header legal

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

Welcome to legal (header legal)%

[Sysname] header login

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

Welcome to login(header login)%

[Sysname] header motd

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

Welcome to motd(header motd)%

[Sysname] header shell

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

Welcome to shell(header shell)%

In this example, the percentage sign (%) is the starting and ending character of the text argument. Entering the percentage sign after the text quits the header command. Because it is the starting and ending character, the percentage sign is not included in the banner.

# Test the configuration by using Telnet. The login banner appears only when password or scheme login authentication has been configured.

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

* Without the owner's prior written consent, *

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

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

Welcome to legal (header legal)

Press Y or ENTER to continue, N to exit.

Welcome to motd(header motd)

Welcome to login(header login)

Password:

Welcome to shell(header shell)

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 ] ] minor minor-value severe severe-value critical critical-value normal normal-value

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

In IRF mode:

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

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

Default

· Minor alarm threshold: 96 MB.

· Severe alarm threshold: 64 MB.

· Critical alarm threshold: 48 MB.

· Normal state threshold: 128 MB.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

slot slot-number: Specifies a card by its slot number. If you do not specify this option, the 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 or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. If you do not specify a card or PEX, this command sets free-memory thresholds for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. If you do not specify this option, the command sets free-memory thresholds for the default CPU.

Usage guidelines

To ensure correct operation and improve memory efficiency, the system monitors the amount of free memory space in real time. When a threshold is exceeded, the system sends an alarm notification or an alarm-removed notification to affected feature modules or processes so they can take countermeasures. For more information about the thresholds, see Fundamentals Configuration Guide.

Examples

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

<Sysname> system-view

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

Related commands

display memory-threshold

memory-threshold usage

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

Use undo memory-threshold usage to restore the default.

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

The memory usage threshold is 100.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

slot slot-number: Specifies a card by its slot number. If you do not specify this option, the 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 or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. If you do not specify a card or PEX, this command sets the memory usage threshold for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. If you do not specify this option, the command sets the memory usage threshold for the default CPU.

Usage guidelines

The device samples memory usage at an interval of 1 minute. 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 chassis 1 slot 2 cpu 1 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 this option, the 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 or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. If you do not specify a card or PEX, this command enables CPU usage monitoring for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. If you do not specify this option, the command enables CPU usage monitoring for the default CPU.

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

monitor cpu-usage interval

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

Syntax

In standalone mode:

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

In IRF mode:

monitor cpu-usage interval interval-value [ 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-value: Specifies the sampling interval for CPU usage monitoring. Valid values include 5Sec for 5 seconds, 1Min for 1 minute, and 5Min for 5 minutes.

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

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

cpu cpu-number: Specifies a CPU by its number. If you do not specify this option, the command sets the interval for the default CPU.

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] monitor cpu-usage interval 5Sec

Related commands

· display cpu-usage configuration

· display cpu-usage history

· monitor cpu-usage enable

monitor cpu-usage threshold

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

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

Syntax

In standalone mode:

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

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

In IRF mode:

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

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

Default

The CPU usage threshold is 99.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

slot slot-number: Specifies a card by its slot number. If you do not specify this option, the 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 or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. If you do not specify a card or PEX, this command sets the CPU usage threshold for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. If you do not specify this option, the command sets the CPU usage threshold for the default CPU.

Usage guidelines

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

Examples

# Set the CPU usage threshold to 80%.

<Sysname> system-view

[Sysname] monitor cpu-usage threshold 80

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.

Default

The port-down feature is enabled.

Syntax

monitor handshake-timeout disable-port

undo monitor handshake-timeout disable-port

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.

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!

reboot

Use reboot to reboot a card or the entire system. (In standalone mode.)

Use reboot to reboot an IRF member device or all IRF member devices. (In IRF mode.)

Syntax

In standalone mode:

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

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number. (In IRF mode.)

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

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

subslot subslot-number: Specifies a subcard by its subslot number. This option is not supported in the current software version.

force: Reboots the device immediately without performing software or hard disk check. If this keyword is not specified, the system first checks whether the reboot might result in data loss or a system failure. For example, the system checks 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 device reboot might interrupt network services.

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

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

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

In standalone mode:

· To reboot a card, specify the slot number.

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

In IRF mode, you can use reboot [ chassis chassis-number [ slot slot-number [ subslot subslot-number ] ] ] on the master to reboot the master or a subordinate member.

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

· To reboot an IRF member device or PEX, specify only the IRF member ID or virtual chassis number.

· To reboot all IRF member devices and PEXs, do not specify the member ID or slot number option.

Examples

# Reboot the device when no configuration change has occurred since the last time you saved the running configuration.

<Sysname> reboot

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

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

Now rebooting, please wait...

# If any configuration has changed, reboot the device and save the configuration.

<Sysname> reboot

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

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

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

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

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

Validating file. Please wait...

Configuration is saved to flash successfully.

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

Now rebooting, please wait...

# If any configuration has changed, reboot the device but do not save the configuration.

<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]:n

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

# (In standalone mode.) Reboot the interface module in slot 2.

<Sysname> reboot slot 2

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

.......DONE!

This command will reboot the specified slot, Continue? [Y/N]:y

Now rebooting, please wait...

# (In standalone mode.) Reboot the interface module in slot 2 by force.

<Sysname> reboot slot 2 force

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

Now rebooting, please wait...

# (In IRF mode.) Reboot IRF member device 2.

<Sysname> reboot chassis 2

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

.......DONE!

This command will reboot the specified chassis, Continue? [Y/N]:y

Now rebooting, please wait...

# (In IRF mode.) Reboot IRF member device 2 by force.

<Sysname> reboot chassis 2 force

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

Now rebooting, please wait...

# (In IRF mode.) Reboot the interface module in slot 2 on IRF member device 2.

<Sysname> reboot chassis 2 slot 2

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

.......DONE!

This command will reboot the specified slot, Continue? [Y/N]:y

Now rebooting, please wait...

# (In IRF mode.) Reboot the interface module in slot 2 on IRF member device 2 by force.

<Sysname> reboot chassis 2 slot 2 force

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

Now rebooting, please wait...

reset asset-info

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

System view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

fan fan-id: Clears the asset profile of the specified fan tray. The device does not support this option.

power power-id: Clears the asset profile for the specified power module. The device does not support this option.

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

# (In IRF mode.) Clear the asset ID for slot 0 on IRF member device 1.

<Sysname> system-view

[Sysname] reset asset-info chassis 1 slot 0 csn

Related commands

· display asset-info

· set asset-info

reset version-update-record

Use reset version-update-record to clear the startup software image upgrade history records of the active MPU. (In standalone mode.)

Use reset version-update-record to clear the startup software image upgrade history records of the global active MPU. (In IRF mode.)

Syntax

reset version-update-record

Views

System view

Predefined user roles

network-admin

mdc-admin

Examples

# Clear the startup software image upgrade history 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

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

mdc-admin

Examples

# Clear job execution log information.

<Sysname> reset scheduler logfile

Related commands

display scheduler logfile

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

mdc-admin

Usage guidelines

CAUTION:

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

This command performs the following operations:

· Deletes all configuration files (.cfg files) in the root directories of the storage media.

· Deletes all log files (.log files in the folder /logfile).

· Clears all log information (in the log buffer), trap information, and debugging information.

· Restores the parameters for the BootWare to the factory-default settings.

· Deletes all license files (.ak files).

After this command is executed, only the items required for fundamental device operation are retained, including the .bin files, the MAC addresses, and the electronic label information.

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 job view. If the job already exists, you enter job view directly.

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: Sets the size of the job execution log file, in KB. The value range is 16 to 1024.

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] scheduler logfile size 32

Related commands

display scheduler logfile

scheduler reboot at

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

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot at time [ date ]

undo scheduler reboot

Default

No reboot date or time is specified.

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

CAUTION:

Device reboot interrupts network services.

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

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

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

For data security, if you are performing file operations at the reboot time, the system does not reboot.

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

Examples

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

<Sysname> scheduler reboot at 12:00

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

Related commands

scheduler reboot delay

Use scheduler reboot delay to specify the reboot delay time.

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot delay time

undo scheduler reboot

Default

No reboot delay time is specified.

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

CAUTION:

Device reboot interrupts network services.

For data security, if you are performing file operations at the reboot time, the system does not reboot.

Examples

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

<Sysname> scheduler reboot delay 88

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

scheduler schedule

Use scheduler schedule to create a schedule and enter schedule view. If the schedule already exists, you enter schedule view directly.

Use undo scheduler schedule to delete a schedule.

Syntax

scheduler schedule schedule-name

undo scheduler schedule schedule-name

Default

No schedule exists.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

To configure a schedule:

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

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

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

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

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

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

Examples

# Create a schedule named saveconfig.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

Related commands

· job

· time at

· time once

set asset-info

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

System view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

chassis: Configures an asset profile for the chassis. The device does not support this keyword.

fan fan-id: Configures an asset profile for the specified fan tray. The device does not support this option.

power power-id: Configures an asset profile for the specified power module. The device does not support this option.

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

Usage guidelines

You can configure an asset profile for a card.

An asset profile has the following system-defined fields:

· Asset ID.

· Department name.

· Asset description.

· Asset location.

· Service start date (when the asset started to provide services).

· Asset usage status.

You can define additional fields by using the custom name value option.

Examples

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

<Sysname> system-view

[Sysname] set asset-info slot 0 csn 123456

# (In IRF mode.) Set the asset ID to 123456 for slot 0 on IRF member device 1.

<Sysname> system-view

[Sysname] set asset-info chassis 1 slot 0 csn 123456

Related commands

· display asset-info

· reset asset-info

set serial-no

Use set serial-no to specify a serial number for a fan tray or power module.

Syntax

In standalone mode:

set serial-no { fan fan-id | power power-id } serial-no

In IRF mode:

set serial-no chassis chassis-number { fan fan-id | power power-id } serial-no

Views

System view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

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

serial-no: Specifies the serial number for the fan tray or power module.

Examples

# (In standalone mode.) Specify a serial number for fan tray 0.

<Sysname> system-view

[Sysname] set serial-no fan 0 210212A0561234560001

Set Fan Serial No Success!

# (In IRF mode.) Specify a serial number for fan tray 0 on IRF member device 1.

<Sysname> system-view

[Sysname] set serial-no chassis 1 fan 0 210212A0561234560001

Set Fan Serial No Success!

Related commands

display serial-no

shutdown-interval

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

Use undo shutdown-interval to restore the default.

Syntax

shutdown-interval time

undo shutdown-interval

Default

The port status detection timer setting is 30 seconds.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

If you change the timer 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 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 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 an a module.

Use undo switch-mode to remove the operating mode configuration. The module does not have an operating mode specified.

Syntax

In standalone mode:

switch-mode { acl-ipv4 | acl-l2 | bridging | high-speed | ipv6 | low-speed | mix-bridging-routing | normal | port-extender | routing | standard-ipv6 } slot slot-number

undo switch-mode slot slot-number

In IRF mode:

switch-mode { acl-ipv4 | acl-l2 | bridging | high-speed | ipv6 | low-speed | mix-bridging-routing | normal | port-extender | routing | standard-ipv6 } chassis chassis-number slot slot-number

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

Default

Table 20 Default operating modes for modules

Modules	Default operating mode
· LSQM1SRP8X2QE0 MPUs · EB, EC, and SD interface modules · SC interface modules: LSQM2GP44TSSC0 LSQM2GP24TSSC0 LSQM2GT24PTSSC0 LSQM2GT24TSSC0 LSQM2GT48SC0 LSQM4GV48SC0	mix-bridging-routing
· SC interface modules: LSQ1QGS4SC0 LSQ1TGS8SC0 LSQ3GV48SC0 · SF interface modules	normal

Modules

Default operating mode

· LSQM1SRP8X2QE0 MPUs

· EB, EC, and SD interface modules

· SC interface modules:
LSQM2GP44TSSC0
LSQM2GP24TSSC0
LSQM2GT24PTSSC0
LSQM2GT24TSSC0
LSQM2GT48SC0
LSQM4GV48SC0

mix-bridging-routing

· SC interface modules:
LSQ1QGS4SC0
LSQ1TGS8SC0
LSQ3GV48SC0

· SF interface modules

normal

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

acl-ipv4: Specifies the acl-ipv4 mode. This keyword is not supported in the current software version.

acl-l2: Specifies the acl-l2 mode. This keyword is not supported in the current software version.

bridging: Specifies the extended MAC mode.

high-speed: Specifies the high-speed mode. This keyword is not supported in the current software version.

ipv6: Specifies the IPv6 mode.

low-speed: Specifies the low-speed mode. This keyword is not supported in the current software version.

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

normal: Specifies the normal mode.

port-extender: Specifies the port extender mode. This keyword is not supported in the current software version.

routing: Specifies the extended routing mode.

standard-ipv6: Specifies the IPv6 standard mode.

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

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

Usage guidelines

Different types of modules support different operating modes. For more information, see Fundamentals Configuration Guide.

To make an operating mode change take effect, save the configuration and reboot the module.

If the device has multiple SD or EB interface modules, specify the same operating mode for them.

An SD or EB interface module might reboot once or twice for self-optimization the first time you perform either of the following tasks:

· Change its operating mode.

· Upgrade the software version of the switch after changing the operating mode.

The optimization and reboot process takes approximately 6 to 10 minutes.

Examples

# (In standalone mode.) Set the operating mode to standard-ipv6 for the SF interface module in slot 2.

<Sysname> system-view

[Sysname] switch-mode standard-ipv6 slot 2

# (In IRF mode.) Set the operating mode to standard-ipv6 for the SF interface module in slot 2 of IRF member device 2.

<Sysname> system-view

[Sysname] switch-mode standard-ipv6 chassis 1 slot 2

Related commands

display switch-mode status

sysname

Use sysname to set the device name.

Use undo sysname to restore the default.

Syntax

sysname sysname

undo sysname

Default

The default 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 as the user view prompt at the CLI. For example, if the device name is Sysname, the user view prompt is <Sysname>.

Examples

# Set the name of the device to R2000.

<Sysname> system-view

[Sysname] sysname R2000

[R2000]

system-working-mode

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

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

Syntax

system-working-mode { advance | standard }

undo system-working-mode

Default

The device operates in standard mode.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

advance: Sets the system operating mode to advanced.

standard: Sets the system operating mode to standard.

Usage guidelines

In different operating modes, the device supports different features, and might have different specifications for the supported features.

To change the operating mode to advance, make sure the device has enough IFP ACL resources. To display the current IFP ACL resource information, use the display qos-acl resource command. For more information about this command, see ACL and QoS Command Reference.

After changing the operating mode, you must reboot the device to make the device operate in the new mode.

Examples

# Set the system operating mode to advanced.

<Sysname> system-view

[Sysname] system-working-mode advance

The system working mode is changed, it will take effect after system restart.

temperature-limit

Use temperature-limit to set the temperature alarm thresholds for the device.

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

To view the default thresholds, use the undo form of the command to restore the default and execute the display environment command.

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

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

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

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

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

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

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

Usage guidelines

When the device temperature drops below the low-temperature threshold or reaches the high-temperature warning threshold, the device sends a log message and a trap.

When the device temperature reaches the high-temperature alarming threshold, the device sends log messages and traps repeatedly, and sets LEDs on the device panel.

Different cards have different threshold value ranges. To view the value ranges, use the CLI online help.

Examples

# (In standalone mode.) Set temperature alarm thresholds for hotspot sensor 1 on the card in slot 7.

<Sysname> system-view

[sysname] temperature-limit slot 7 hotspot 1 -5 80 95

# (In IRF mode.) Set temperature alarm thresholds for hotspot sensor 1 on the card in slot 7 on IRF member device 1.

<Sysname> system-view

[sysname] temperature-limit chassis 1 slot 7 hotspot 1 -5 80 95

time at

Use time at to specify an execution date and time for a non-periodic schedule.

Use undo time to delete the execution date and time configuration for a non-periodic schedule.

Syntax

time at time date

undo time

Default

No execution time or date is specified for a non-periodic schedule.

Views

Schedule view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

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

The time at command, the time once command, and the time repeating command overwrite one another. The most recently configured command takes effect.

Examples

# Configure the device to execute schedule saveconfig at 01:01 a.m. on May 11, 2011.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time at 1:1 2011/05/11

Related commands

scheduler schedule

time once

Use time once to specify one or more execution days and the execution time for a non-periodic schedule.

Use undo time to delete the execution day and time configuration for a non-periodic schedule.

Syntax

time once at time [ month-date month-day | week-day week-day&<1-7> ]

time once delay time

undo time

Default

No execution time or day is specified for a non-periodic schedule.

Views

Schedule view

Predefined user roles

network-admin

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 contain up to six characters. When in the hh:mm format, mm must be in the range of 0 to 59.

Usage guidelines

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

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

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

The time at command, the time once command, and the time repeating command overwrite one another. The most recently configured command takes effect.

Examples

# Configure the device to execute schedule saveconfig once at 15:00.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 15:00

Schedule starts at 15:00 5/11/2011.

# Configure the device to execute schedule saveconfig once at 15:00 on the coming 15th day in a month.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 15:00 month-date 15

# Configure the device to execute schedule saveconfig at 12:00 p.m. on the coming Monday and Friday.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 12:00 week-day mon fri

# Configure the device to execute schedule saveconfig after 10 minutes.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once delay 10

Related commands

scheduler schedule

time repeating

Use time repeating to specify an execution time table for a periodic schedule.

Use undo time to delete the execution time table configuration for a periodic schedule.

Syntax

time repeating [ at time [ date ] ] interval interval-time

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-time: Specifies the execution time interval 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. 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-time command configures the device to execute a schedule at an interval from the specified time on.

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

The time at command, the time once command, and the time repeating command overwrite one another, whichever is configured most recently takes effect.

Examples

# Configure the device to execute schedule saveconfig once a 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 phony-alarm-disable

Use transceiver phony-alarm-disable to disable alarm traps for transceiver modules.

Use undo transceiver phony-alarm-disable to restore the default.

Syntax

transceiver phony-alarm-disable

undo transceiver phony-alarm-disable

Default

Alarm traps are enabled for transceiver modules.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Disable alarm traps if the transceiver modules were manufactured or sold by H3C.

The device regularly detects transceiver modules that have a vendor name other than H3C or do not have a vendor name. Upon detecting such a transceiver module, the device repeatedly outputs traps and logs to notify the user to replace the module.

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

Examples

# Disable alarm traps for transceiver modules.

<Sysname> system-view

[Sysname] transceiver phony-alarm-disable

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

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

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

load-single: Configures the MPUs so only the global active MPU processes and forwards packets. The global standby MPUs back up data and monitor the status of the global active MPU. (In IRF mode.)

Usage guidelines

This command is not supported on an S7502E.

On a device installed with LSQM1SRP8X2QE0, LSQM2MPUDS0, or LSQM2MPUD0 MPUs, this command can be configured but does not take effect.

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.

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

# (In IRF mode.) Set the load mode for the active MPU and the standby MPUs on IRF member device 2 to load-balance.

<Sysname> system-view

[Sysname] xbar chassis 2 load-balance

Related commands

display xbar

01-Fundamentals Command Reference

display copyright

display device manuinfo chassis-only

display fan

display memory

display scheduler job

display serial-no

display version-update-record

memory-threshold usage

monitor cpu-usage interval

reset asset-info

restore factory-default

scheduler reboot at

switch-mode

system-working-mode

time once

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us