Device management commands -- accelerate

Use accelerate to enable forwarding acceleration for a card.

Use undo accelerate to disable forwarding acceleration for a card.

Syntax

Distributed devices in standalone mode:

accelerate slot slot-number

undo accelerate slot slot-number

Distributed devices in IRF mode:

accelerate chassis chassis-number slot slot-number

undo accelerate chassis chassis-number slot slot-number

Default

Forwarding acceleration is disabled for all cards.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (Distributed devices in IRF mode.)

Usage guidelines

| IMPORTANT: Use the forwarding acceleration feature under the guidance of H3C Support. Although this feature improves forwarding performance, enabling this feature on multiple cards might cause traffic bursts and packet loss.

‌

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

For this command to take effect, you must use the reboot command to reboot the card.

Examples

# (Distributed devices in standalone mode.) Enable forwarding acceleration for the card in a slot.

<Sysname> system-view

[Sysname] accelerate slot 3

Forwarding acceleration configured. Please reboot the card to place it into effect.

Device management commands -- bootrom-access enable

Use bootrom-access enable to allow access to the BootWare menu during device startup.

Use undo bootrom-access enable to disable access to the BootWare menu during device startup.

Syntax

bootrom-access enable

undo bootrom-access enable

Default

A login user can press Ctrl+B during device startup to access the BootWare menu.

Views

User view

Predefined user roles

network-admin

Usage guidelines

By default, anyone can press Ctrl+B during startup to access the BootWare menu, load software, and manage storage media. To prevent unauthorized BootWare menu access, set a BootWare menu password or disable BootWare menu access.

Examples

# Disable access to the BootWare menu during device startup.

<Sysname> undo bootrom-access enable

Related commands

display bootrom-access

Device management commands -- brand

Use brand to change the brand name of an MPU.

Syntax

Distributed devices in standalone mode:

brand { hp | h3c } [ slot slot-number ]

Distributed devices in IRF mode:

brand { hp | h3c } [ chassis chassis-number slot slot-number ]

Default

The default varies by MPU model and device model.

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

hp: Sets the brand name to HP.

h3c: Sets the brand name to H3C.

slot slot-number: Specifies an MPU by its slot number. If you do not specify an MPU, this command configures a brand name for both MPUs. (Distributed devices in standalone mode.)

chassis chassis-number slot slot-number: Specifies an MPU on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the MPU. If you do not specify an MPU, this command configures a brand name for all MPUs. (Distributed devices in IRF mode.)

Usage guidelines

An MPU brand name change takes effect after the MPU reboots.

Examples

# Set the brand names of the MPUs to HP.

<Sysname> brand hp

Configuration will take effect after next reboot, do you want to continue? [Y/N]: Y

Configuration is successful.

Related commands

display brand

Device management commands -- card-mode

Use card-mode to set the operating mode for an interface card.

Syntax

Centralized devices:

card-mode slot slot-number mode-name

Distributed devices in standalone mode:Centralized IRF devices:

card-mode slot slot-number subslot subslot-number mode-name

Distributed devices in IRF mode:

card-mode chassis chassis-number slot slot-number subslot subslot-number mode-name

Default

The default varies by device model.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

slot slot-number: Specifies a subcard by its slot number. (Centralized devices.)

slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)

slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (Distributed devices in IRF mode.)

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

mode-name: Specifies an operating mode. Available operating modes depend on the interface card type. The following shows all operating mode values:

atm: Specifies the ATM mode. All interfaces on the interface card act as ATM interfaces.

auto: Specifies the auto negotiation mode. The interface card operates in ATM or EFM mode, depending on the negotiation result.

e: Specifies the E mode. All interfaces on the interface card act as CPOS E3-E1 interfaces.

e1: Specifies the E1 mode. All interfaces on the interface card act as CPOS E1 interfaces.

e3: Specifies the E3 mode. All interfaces on the interface card act as CPOS E3 interfaces.

e-cpos: Specifies the E-CPOS mode. All interfaces on the interface card act as 2.5 Gbps CPOS interfaces.

efm: Specifies the EFM mode. All interfaces on the interface card act as EFM interfaces.

ipsec: Specifies the IPsec mode.

oc-12: Specifies the OC-12c/STM-4c mode (622 Mbps). All interfaces on the interface card act as 622 Mbps CPOS interfaces.

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

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

oc-3: Specifies the OC-3c/STM-1c mode (155 Mbps). All interfaces on the interface card act as 155 Mbps CPOS interfaces.

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

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

pos: Specifies the POS mode. All interfaces on the interface card act as 2.5 Gbps POS interfaces.

ssl: Specifies the SSL mode.

t: Specifies the T mode. All interfaces on the interface card act as CPOS T3-T1 interfaces.

t1: Specifies the T1 mode. All interfaces on the interface card act as CPOS T1 interfaces.

t3: Specifies the T3 mode. All interfaces on the interface card act as CPOS T3 interfaces.

Usage guidelines

This command is supported only on the default MDC.

Whether the new operating mode takes effect immediately depends on the device model. If the new operating mode does not take effect immediately, you must perform one of the following tasks to activate the new operating mode:

Hot swap the interface card if the interface card supports hot swapping.

Restart the device.

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

Examples

# (Centralized devices.) Set the operating mode to E3 for an interface card.

<Sysname> system-view

[Sysname] card-mode slot 2 e3

Please reboot or hot-swap the board or card (if supported) to make the configuration take effect.

# (Centralized IRF devices.) (Distributed devices in standalone mode.) Set the operating mode to E3 for a subcard.

<Sysname> system-view

[Sysname] card-mode slot 2 subslot 1 e3

Please reboot or hot-swap the board or card (if supported) to make the configuration take effect.

Device management commands -- clock datetime

Use clock datetime to set the system time.

Syntax

clock datetime time date

Default

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

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

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

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

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

Examples

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

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

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

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

Related commands

clock protocol

clock summer-time

clock timezone

display clock

Device management commands -- clock protocol

Use clock protocol to specify the system time source.

Use undo clock protocol to restore the default.

Syntax

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

undo clock protocol

Default

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

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

context context-id: Specifies the context to be used for time synchronization. The value range of the context ID is 1 to 65279.

mdc mdc-id: Specifies the MDC to be used for time synchronization. The value range depends on the device model.

Usage guidelines

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

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

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

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

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

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

Examples

# Configure the device to use the local UTC time.

<Sysname> system-view

[Sysname] clock protocol none

Device management commands -- clock summer-time

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

Use undo clock summer-time to restore the default.

Syntax

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

undo clock summer-time

Default

The daylight saving time is not set.

Views

System view

Predefined user roles

network-admin

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 day, where:

?span style='font:7.0pt "Times New Roman"'> month—Takes January, February, March, April, May, June, July, August, September, October, November or December.

?span style='font:7.0pt "Times New Roman"'> week—Represents week of the month. It takes first, second, third, fourth, fifth, or last.

?span style='font:7.0pt "Times New Roman"'> day—Takes Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.

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

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

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

· month week day, where:

?span style='font:7.0pt "Times New Roman"'> month—Takes January, February, March, April, May, June, July, August, September, October, November or December.

?span style='font:7.0pt "Times New Roman"'> week—Represents week of the month. It takes first, second, third, fourth, fifth, or last.

?span style='font:7.0pt "Times New Roman"'> day—Takes Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.

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

Usage guidelines

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

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

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

Examples

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

<Sysname> system-view

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

Related commands

clock datetime

clock timezone

display clock

Device management commands -- clock timezone

Use clock timezone to set the time zone.

Use undo clock timezone to restore the default.

Syntax

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

undo clock timezone

Default

The UTC time zone is used.

Views

System view

Predefined user roles

network-admin

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.

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

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

Examples

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

<Sysname> system-view

[Sysname] clock timezone Z5 add 5

Related commands

clock datetime

clock summer-time

display clock

Device management commands -- command

Use command to assign a command to a job.

Use undo command to revoke a command.

Syntax

command id command

undo command id

Default

No command is assigned to a job.

Views

Job view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] scheduler job backupconfig

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

# Assign commands to the shutdownGE job to shut down 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

Device management commands -- copyright-info enable

Use copyright-info enable to enable copyright statement display.

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

Syntax

copyright-info enable

undo copyright-info enable

Default

Copyright statement display is enabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Examples

# Enable copyright statement display.

<Sysname> system-view

[Sysname] copyright-info enable

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

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

* Copyright (c) 2004-2017 New H3C Technologies Co., Ltd. All rights reserved.*

* Without the owner's prior written consent, *

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

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

Device management commands -- display alarm

Use display alarm to display alarm information.

Syntax

Centralized devices:

display alarm [ slot slot-number ]

Centralized IRF devices:Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

display alarm [ 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 the entire device. The value is fixed at 0. (Centralized devices.)

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

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays alarm information for all IRF member devices. (Centralized IRF devices.) (IRF 3 incapable.)

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

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

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Examples

# (Centralized devices.) Display alarm information.

<Sysname> display alarm

Slot CPU Level Info

0 0 ERROR faulty

Table 1 Command output

Field | Description
Slot | The value of this field is fixed at 0.
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 faulty. · Fan n is absent—The specified fan is absent.

‌

# (Centralized IRF devices.) (Distributed devices in standalone mode.) Display alarm information.

<Sysname> display alarm

Slot CPU Level Info

1 0 ERROR faulty

Table 2 Command output

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

‌

Device management commands -- display bootrom-access

Use display bootrom-access to display the BootWare menu access authorization status.

Syntax

display bootrom-access

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display the BootWare menu access authorization status.

<Sysname> display bootrom-access

Bootrom access: Enabled.

Related commands

bootrom-access enable

Device management commands -- display brand

Use display brand to display brand information for MPUs.

Syntax

display brand

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display brand information for MPUs.

<Sysname> display brand

Current BRANDs:

Slot 1: H3C.

New BRANDs:

Slot 1: H3C.

Table 3 Command output

Field | Description
Current BRANDs | Current brand names for the MPUs.
New BRANDs | Brand names for the MPUs after a reboot.

‌

Related commands

brand

Device management commands -- display clock

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

Syntax

display clock

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

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

<Sysname> display clock

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

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

<Sysname> display clock

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

Time Zone : Z5 add 05:00:00

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

<Sysname> display clock

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

Time Zone : Z5 add 05:00:00

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

Related commands

clock datetime

clock timezone

clock summer-time

Device management commands -- display copyright

Use display copyright to display the copyright statement.

Syntax

display copyright

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display the copyright statement.

<Sysname> display copyright

...

Device management commands -- display cpu-usage

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

Syntax

Centralized devices:

display cpu-usage [ summary ]

Centralized IRF devices:Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays CPU usage statistics for all member devices. (Centralized IRF devices.) (IRF 3 incapable.)

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

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays CPU usage statistics for all cards. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Usage guidelines

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

To display the CPU usage statistics for a PEX in an IRF 3.1 system, you must first log in to the MDC to which the PEX belongs.

Examples

# (Centralized devices.) Display the current CPU usage statistics in text form.

<Sysname> display cpu-usage

Unit CPU usage:

1% in last 5 seconds

1% in last 1 minute

1% in last 5 minutes

# (Centralized devices.) Display the current CPU usage statistics in table form.

<Sysname> display cpu-usage

CPU Last 5 sec Last 1 min Last 5 min

0 2% 2% 10%

# (Centralized IRF devices.) (Distributed devices in standalone mode.) Display the current CPU usage statistics in text form.

<Sysname> display cpu-usage

Slot 1 CPU 0 CPU usage:

1% in last 5 seconds

1% in last 1 minute

1% in last 5 minutes

# (Centralized IRF devices.) (Distributed devices in standalone mode.) Display the current CPU usage statistics in table form.

<Sysname> display cpu-usage

Slot CPU Last 5 sec Last 1 min Last 5 min

1 0 17% 29% 28%

Table 4 Command output

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

‌

Device management commands -- display cpu-usage configuration

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

Syntax

Centralized devices:

display cpu-usage configuration

Centralized IRF devices:Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameters

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

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays the CPU usage monitoring settings for the master device. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you do not specify a member device or PEX, this command displays the CPU usage monitoring settings for the master device. (Centralized IRF devices.) (IRF 3 capable.)

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

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Usage guidelines

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

To display CPU usage monitoring settings for a PEX in an IRF 3.1 system, you must first log in to the MDC to which the PEX belongs.

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

Related commands

monitor cpu-usage enable

monitor cpu-usage interval

monitor cpu-usage threshold

Device management commands -- display cpu-usage history

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

Syntax

Centralized devices:

display cpu-usage history [ job job-id ]

Centralized IRF devices:Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

slot slot-number: Specifies an IRF member device by its member ID. If you specify a process but do not specify a member device, this command displays the statistics for the process on the master device. If you do not specify any options, this command displays the statistics for all processes on all member devices. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you specify a process but do not specify a member device, this command displays the statistics for the process on the master device. If you do not specify any options, this command displays the statistics for all processes in the IRF fabric. (Centralized IRF devices.) (IRF 3 capable.)

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

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Usage guidelines

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

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

The horizontal axis represents the time.

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

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

To display the historical CPU usage statistics for a PEX in an IRF 3.1 system, you must first log in to the MDC to which the PEX belongs.

Examples

# (Centralized devices.) Display the historical CPU usage statistics.

<Sysname> display cpu-usage history

100%|

95%|

90%|

85%|

80%|

75%|

70%|

65%|

60%|

55%|

50%|

45%|

40%|

35%|

30%|

25%|

20%|

15%| #

10%| ### #

5%| ########

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

10 20 30 40 50 60 (minutes)

cpu-usage last 60 minutes (SYSTEM)

The output shows the following items:

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

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

?span style='font:7.0pt "Times New Roman"'> 12 minutes ago—Approximately 5%.

?span style='font:7.0pt "Times New Roman"'> 13 minutes ago—Approximately 10%.

?span style='font:7.0pt "Times New Roman"'> 14 minutes ago—Approximately 15%.

?span style='font:7.0pt "Times New Roman"'> 15 minutes ago—Approximately 10%.

?span style='font:7.0pt "Times New Roman"'> 16 and 17 minutes ago—Approximately 5%.

?span style='font:7.0pt "Times New Roman"'> 18 minutes ago—Approximately 10%.

?span style='font:7.0pt "Times New Roman"'> 19 minutes ago—Approximately 5%.

?span style='font:7.0pt "Times New Roman"'> Other time—2% or lower.

# (Centralized IRF devices.) (Distributed devices in standalone mode.) Display the historical CPU usage statistics.

<Sysname> display cpu-usage history

100%|

95%|

90%|

85%|

80%|

75%|

70%|

65%|

60%|

55%|

50%|

45%|

40%|

35%|

30%|

25%|

20%|

15%| #

10%| ### #

5%| ########

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

10 20 30 40 50 60 (minutes)

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

The output shows the following items:

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

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

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

?span style='font:7.0pt "Times New Roman"'> 12 minutes ago—Approximately 5%.

?span style='font:7.0pt "Times New Roman"'> 13 minutes ago—Approximately 10%.

?span style='font:7.0pt "Times New Roman"'> 14 minutes ago—Approximately 15%.

?span style='font:7.0pt "Times New Roman"'> 15 minutes ago—Approximately 10%.

?span style='font:7.0pt "Times New Roman"'> 16 and 17 minutes ago—Approximately 5%.

?span style='font:7.0pt "Times New Roman"'> 18 minutes ago—Approximately 10%.

?span style='font:7.0pt "Times New Roman"'> 19 minutes ago—Approximately 5%.

?span style='font:7.0pt "Times New Roman"'> Other time—2% or lower.

Related commands

monitor cpu-usage enable

monitor cpu-usage interval

Device management commands -- display device

Use display device to display device information.

Syntax

Centralized devices:

display device [ cf-card | flash | harddisk | sd-card | usb ] [ subslot subslot-number | verbose ]

Centralized IRF devices:Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

cf-card: Displays CF card information.

flash: Displays flash memory information.

harddisk: Displays hard disk information.

sd-card: Displays SD card information.

usb: Displays USB interface information.

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

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards. (Distributed devices in standalone mode.) (Distributed devices in IRF mode.) (IRF 3 incapable.)

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 information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays information for all IRF member devices and PEXs if you do not specify a member device or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies a card by its slot number or a PEX by its virtual slot number. If you do not specify a card or PEX, this command displays information for all cards and PEXs. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

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

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

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

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

Usage guidelines

(Centralized devices.) If you do not specify the cf-card, flash, harddisk, sd-card, and usb keywords, this command displays information about the device.

(Centralized IRF devices.) If you do not specify the cf-card, flash, harddisk, sd-card, and usb keywords, this command displays information about member devices.

(Distributed devices.) If you do not specify the cf-card, flash, harddisk, sd-card, and usb keywords, this command displays information about cards.

This command displays device information about the physical device, whether you execute this command on the default MDC or on a non-default MDC. (IRF 3.1-incapable devices.)

This command displays device information about the physical parent devices, whether you execute this command on the default MDC or on a non-default MDC. To display device information for a PEX, you must first log in to the MDC to which the PEX belongs. (IRF 3.1-capable devices.)

Examples

# (Centralized devices.) Display device information.

<Sysname> display device

Slot No. Board Type Status Max Ports

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

0 RPU Normal 6

Table 5 Command output (centralized devices)

Field | Description
Board Type | Hardware type of the device.
Status | Device status: · Illegal—The device is not operating correctly. · Normal—The device is operating correctly.
Max Ports | Maximum number of physical ports that the device supports.

‌

# (Distributed devices in standalone mode.) Display device information.

<Sysname> display device

Slot Type State Subslot Soft Ver Patch Ver

0 LSXM1SUPB1 Master 0 S12508X-AF-0502 None

1 LSXM1SUPB1 Standby 0 S12508X-AF-0502 None

2 NONE Absent 0 NONE None

3 LSXM1TGS48C2HB1 Normal 0 S12508X-AF-0502 None

4 NONE Absent 0 NONE None

5 NONE Absent 0 NONE None

6 NONE Absent 0 NONE None

7 NONE Absent 0 NONE None

8 NONE Absent 0 NONE None

9 NONE Absent 0 NONE None

10 NONE Absent 0 NONE None

11 NONE Absent 0 NONE None

12 NONE Absent 0 NONE None

13 NONE Absent 0 NONE None

14 NONE Absent 0 NONE None

15 LSXM1SFH08D1 Normal 0 S12508X-AF-0502 None

Table 6 Command output (distributed devices in standalone mode)

Field | Description
Type | Hardware type of the card.
Status | Card status: · Standby—The card is the standby MPU. · Master—The card is the active MPU. · Absent—The slot is not installed with a card. · Fault—The card is faulty and cannot start up. · Normal—The card is an interface card and is operating correctly. · Offline-OLO—The card is a switching fabric module and is isolated.
Soft Ver | Software version of the card.
Patch Ver | Patch version of the card.

‌

# (Centralized IRF devices.) Display device information.

<Sysname> display device

Slot 1

Slot Type State Subslot Soft Ver Patch Ver

1 S6820-32H Master 0 S6820-6103 None

Table 7 Command output (centralized IRF devices)

Field | Description
Type | Device type.
State | Role of the device in an IRF fabric: · Master—The device is the master. · Standby—The device is a subordinate member.
Soft Ver | Software version of the device.
Patch Ver | Patch version of the device. If no patch is installed, the value of this field is None.

‌

Device management commands -- display device manuinfo

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

Syntax

Centralized devices:

display device manuinfo [ subslot subslot-number ]

Centralized IRF devices:Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays electronic label information of all cards. (Distributed devices in standalone mode.) (Distributed devices in IRF mode.) (IRF 3 incapable.)

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 electronic label information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays electronic label information for all IRF member devices and PEXs if you do not specify a member device or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. On an IRF fabric, this command displays electronic label information for all cards if you do not specify a card. On an IRF 3 system, this command displays electronic label information for all cards and PEXs if you do not specify a card or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

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

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

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

Usage guidelines

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

This command is supported only on the default MDC. (IRF 3.1-incapable devices.)

To display electronic label information for the parent device, execute this command in the default MDC. To display electronic label information for a PEX, you must first log in to the MDC to which the PEX belongs. (IRF 3.1-capable devices.)

Examples

# Display electronic label information for the device.

<Sysname> display device manuinfo

...

Device management commands -- display device manuinfo chassis-only

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

Syntax

Distributed devices in standalone mode:

display device manuinfo chassis-only

Distributed devices 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. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number. (Distributed devices in IRF mode.) (IRF 3 capable.)

Usage guidelines

This command is supported only on the default MDC. (IRF 3.1-incapable devices.)

To display electronic label information for the backplane of a parent device, execute this command on the default MDC. To display electronic label information for the backplane of a PEX, you must first log in to the MDC to which the PEX belongs. (IRF 3.1-capable devices.)

Examples

# (Distributed devices in standalone mode.) Display electronic label information for the backplane.

<Sysname> display device manuinfo chassis-only

...

Device management commands -- display device manuinfo fan

Use display device manuinfo fan to display electronic label information for a fan tray.

Syntax

Centralized devices:Distributed devices in standalone mode:

display device manuinfo fan fan-id

Centralized IRF devices:

display device manuinfo slot slot-number fan fan-id

(IRF 3 incapable.) Distributed devices in IRF mode:

display device manuinfo chassis chassis-number fan fan-id

(IRF 3 capable.) Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Centralized IRF devices.) (IRF 3 capable.)

chassis chassis-number: Specifies an IRF member device by its member ID. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Usage guidelines

This command is supported only on the default MDC. (IRF 3.1-incapable devices.)

To display electronic label information for a fan tray of a parent device, execute this command on the default MDC. To display electronic label information for a fan tray of a PEX, you must first log in to the MDC to which the PEX belongs. (IRF 3.1-capable devices.)

Examples

# Display electronic label information for a fan tray.

<Sysname> display device manuinfo fan 1

...

Device management commands -- display device manuinfo power

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

Syntax

Centralized devices:Distributed devices in standalone mode:

display device manuinfo power power-id

Centralized IRF devices:

display device manuinfo slot slot-number power power-id

(IRF 3 incapable.) Distributed devices in IRF mode:

display device manuinfo chassis chassis-number power power-id

(IRF 3 capable.) Distributed devices 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

slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Centralized IRF devices.) (IRF 3 capable.)

chassis chassis-number: Specifies an IRF member device by its member ID. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Usage guidelines

This command is supported only on the default MDC. (IRF 3.1-incapable devices.)

To display electronic label information for a power supply of a parent device, execute this command on the default MDC. To display electronic label information for a power supply of a PEX, you must first log in to the MDC to which the PEX belongs. (IRF 3.1-capable devices.)

Examples

# (Centralized devices.) (Distributed devices in standalone mode.) Display electronic label information for a power supply.

<Sysname> display device manuinfo power 1

...

# (Centralized IRF devices.) Display electronic label information for a power supply.

<Sysname> display device manuinfo slot 1 power 1

...

Device management commands -- display device manuinfo power-monitor

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

Syntax

Centralized devices:Distributed devices in standalone mode:

display device manuinfo power-monitor pm-id

Centralized IRF devices:

display device manuinfo slot slot-number power-monitor pm-id

(IRF 3 incapable.) Distributed devices in IRF mode:

display device manuinfo chassis chassis-number power-monitor pm-id

(IRF 3 capable.) Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Centralized IRF devices.) (IRF 3 capable.)

chassis chassis-number: Specifies an IRF member device by its member ID. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

pm-id: Specifies a power monitoring module by its ID. The value range varies by device model.

Examples

# Display electronic label information for a power monitoring module.

<Sysname> display device manuinfo power-monitor 1

...

Device management commands -- display diagnostic-information

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

hardware: Specifies hardware-related operating information.

infrastructure: Specifies operating information for the fundamental features.

l2: Specifies operating information for the Layer 2 features.

l3: Specifies operating information for the Layer 3 features.

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

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

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

Usage guidelines

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

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

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

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

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

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

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

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

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

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

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

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

Examples

# Display the operating information for all features and modules.

<Sysname> display diagnostic-information

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

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

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

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

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

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

...

# Save the operating information to the default file.

<Sysname> display diagnostic-information

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

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

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

Please wait...

Save successfully.

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

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

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

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

Please wait...

Save successfully.

Related commands

gunzip

more

tar extract

Device management commands -- display dying-gasp host

Use display dying-gasp host to display poweroff alarm destination host settings.

Syntax

display dying-gasp host

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

This command is supported only on the default MDC.

Examples

# Display poweroff alarm destination host settings.

<Sysname> display dying-gasp host

IPv4 address: 1.1.1.0

Message type: SNMP Trap

Securityname: p1

Version: V1

IPv4 address: 1.1.1.1

Message type: Syslog

Table 8 Command output

Field | Description
IPv4 address | IPv4 address of the poweroff alarm destination host.
IPv6 address | IPv6 address of the poweroff alarm destination host.
VPN instance | VPN instance to which the poweroff alarm destination host belongs.
Message type | Message types that the poweroff alarm destination host supports: · SNMP Trap—SNMP notification. · Syslog—Log message.
Securityname | SNMPv1 or SNMPv2c community name. This field is displayed when the message type is SNMP Trap.
Version | SNMP version: · v1—SNMPv1. · v2c—SNMPv2c. This field is displayed when the message type is SNMP Trap.

‌

Related commands

dying-gasp host

Device management commands -- display environment

Use display environment to display temperature information.

Syntax

Centralized devices:

display environment

Distributed devices in standalone mode:

display environment [ slot slot-number | vent ]

Centralized IRF devices:

display environment [ slot slot-number ]

Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

slot slot-numbe r: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards. (Distributed devices in standalone mode.) (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual 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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

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

vent: Specifies the temperature sensors on the chassis and fan frame.

Usage guidelines

(Distributed devices in standalone mode.) This command displays information about all temperature sensors on the device if you do not specify a card or the vent keyword.

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

This command is supported only on the default MDC. (IRF 3.1-incapable devices.)

To display temperature information for parent devices, execute this command on the default MDC. To display temperature information for a PEX, you must first log in to the MDC to which the PEX belongs. (IRF 3.1-capable devices.)

Examples

# (Centralized devices.) Display information about all temperature sensors on the device.

<Sysname> display environment

System temperature information (degree centigrade):

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

Slot Sensor Temperature LowerLimit WarningLimit AlarmLimit ShutdownLimit

0 hotspot 1 27 -10 50 70 100

0 hotspot 2 53 10 50 80 100

# (Centralized IRF devices.) (Distributed devices in standalone mode.) Display information about all temperature sensors on the device.

<Sysname> display environment

System temperature information (degree centigrade):

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

Slot Sensor Temperature Lower Warning Alarm Shutdown

1 hotspot 1 38 10 40 50 100

1 hotspot 2 42 10 50 80 100

Table 9 Command output

Field | Description
System Temperature information (degree centigrade) | Temperature information (°C).
sensor | Temperature sensor: · hotspot—Hotspot sensor. · inflow—Air inlet sensor. · outflow—Air outlet sensor.
Slot | Sensor position. For a sensor on the chassis or fan tray, this field displays Vent.
Temperature | Current temperature.
Lower | Lower temperature limit. If the device does not support this field, this field displays NA.
Warning | Warning temperature threshold. If the device does not support this field, this field displays NA.
Alarm | Alarming temperature threshold. If the device does not support this field, this field displays NA.
Shutdown | Shutdown temperature threshold. When the sensor temperature reaches the limit, the system shuts down automatically. If the device does not support this field, this field displays NA.

‌

Device management commands -- display fabric utilization

Use display fabric utilization to display switching fabric channel usage on interface cards.

Syntax

Distributed devices in standalone mode:

display fabric utilization [ slot slot-number ]

Distributed devices in IRF mode:

display fabric utilization [ chassis chassis-number slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies an interface card by its slot number. If you do not specify an interface card, this command displays the switching fabric channel usage on all interface cards. (Distributed devices in standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays the switching fabric channel usage for all cards. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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 the switching fabric channel usage for all cards if you do not specify a card. On an IRF 3 system, this command displays the switching fabric channel usage for all cards and PEXs if you do not specify a card or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

Examples

# (Distributed devices in standalone mode.) Display the switching fabric channel usage on an interface card.

<System> display fabric utilization slot 5

Input Output

Chs Slot Chan Speed Usage Peak Usage Peak

0 2 0 10G 0% 0% 08:13:14 2012/10/30 0% 0% 08:13:14 2012/10/30

0 2 1 10G 0% 0% 08:13:14 2012/10/30 0% 0% 08:13:14 2012/10/30

0 2 2 10G 0% 0% 08:13:14 2012/10/30 0% 0% 08:13:14 2012/10/30

0 2 3 10G 0% 0% 08:13:14 2012/10/30 0% 0% 08:13:14 2012/10/30

Table 10 Command output

Field | Description
Chs | (Distributed devices in standalone mode.) The value of this field is fixed at 0. (Distributed devices in IRF mode.) This field indicates the member ID of the member device.
Slot | Slot number of the interface card.
Chan | Channel number.
Speed | Speed of the channel.
Input | Statistics in the inbound direction.
Output | Statistics in the outbound direction.
Usage | Channel usage.
Peak | Peak usage and peak time.

‌

Device management commands -- display fan

Use display fan to display fan tray operating status information.

Syntax

Centralized devices:Distributed devices in standalone mode:

display fan [ fan-id ] [ verbose ]

Centralized IRF devices:

display fan [ slot slot-number [ fan-id ] ] [ verbose ]

(IRF 3 incapable.) Distributed devices in IRF mode:

display fan [ chassis chassis-number [ fan-id ] ] [ verbose ]

(IRF 3 capable.) Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays fan tray operating status information for all member devices. (Centralized IRF devices.) (IRF 3 incapable.)

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

chassis chassis-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays fan tray operating status information for all member devices. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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 tray operating status information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays fan tray operating status information for all IRF member devices and PEXs if you do not specify a member device or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

fan-id: Specifies a fan tray by its ID. If you do not specify a fan tray, this command displays operating status information for all fan trays at the specified position.

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

Usage guidelines

This command is supported only on the default MDC. (IRF 3.1-incapable devices.)

To display fan tray operating status information for parent devices, execute this command on the default MDC. To display fan tray operating status information for a PEX, you must first log in to the MDC to which the PEX belongs. (IRF 3.1-capable devices.)

Examples

# Display the operating states of all fan trays.

<Sysname> display fan

Slot 1:

Fan 1:

State : Normal

Airflow Direction: Port-to-power

Prefer Airflow Direction: Port-to-power

Table 11 Command output

Field | Description
Slot 1 | Number of the member device.
Fan 1 | Fan tray number.
State | Fan status: · Absent—The slot is not installed with a fan tray. · Fault—The fan is faulty. · Normal—The fan is operating correctly. · FanDirectionFault—The actual airflow direction is not the preferred direction.
Airflow Direction | Actual airflow direction: · Port-to-power—From the port side to the power supply side. · Power-to-port—From the power supply side to the port side.
Prefer Airflow Direction | Preferred airflow direction: · Port-to-power—From the port side to the power supply side. · Power-to-port—From the power supply side to the port side.

‌

Device management commands -- display hardware-failure-detection

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

Syntax

display hardware-failure-detection

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

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

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

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

Examples

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

<Sysname> display hardware-failure-detection

Current level:

chip : isolate

board : isolate

forwarding : warning

Recent record:

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

There is no record.

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

There is no record.

Table 12 Command output

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

‌

Device management commands -- display hardware-failure-protection

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

port: Displays the hardware failure protection settings for interfaces.

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

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

Usage guidelines

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

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

Examples

# Display all hardware failure protection settings.

<Sysname> display hardware-failure-protection

Aggregation: on

Port: GE1/0/1 GE1/0/2

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

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

Port: GE1/0/1 GE1/0/2

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

<Sysname> display hardware-failure-protection port GigabitEthernet 1/0/2

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

Table 13 Command output

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

‌

Device management commands -- display hardware-resource tcam

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

Syntax

display hardware-resource [ tcam ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

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

Examples

# Display TCAM hardware resource operating mode information.

<Sysname> display hardware-resource tcam

Tcam resource(tcam), all supported modes:

routing The routing working mode

normal The normal working mode

acl The acl working mode

ipv6 The ipv6 working mode

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

Default Current Next

routing routing routing

Table 14 Command output

Field | Description
Tcam resource(tcam), all supported modes | Supported modes of TCAM: · routing—Route mode. · normal—Normal mode. · acl—ACL mode. · ipv6—IPv6 mode.
Default | Default operating mode.
Current | Current operating mode.
Next | Operating mode for the next startup.

‌

Related commands

hardware-resource tcam

Device management commands -- display lpu-type

Use display lpu-type to display interface card series information.

Syntax

display lpu-type

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display interface card series information.

<Sysname> display lpu-type

Current LPU type is E series.

LPU type for the next startup is F series.

Related commands

lpu-type

Device management commands -- display memory

Use display memory to display memory usage information.

Syntax

Centralized devices:

display memory [ summary ]

Centralized IRF devices:Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays memory usage for all member devices. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you do not specify a member device or PEX, this command displays memory usage for all member devices. (Centralized IRF devices.) (IRF 3 capable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays memory usage for all MPUs. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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 memory usage for all MPUs. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Usage guidelines

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

To display memory usage information for a PEX in an IRF 3.1 system, you must first log in to the MDC to which the PEX belongs.

Examples

# (Centralized devices.) Display detailed memory usage information.

<Sysname> display memory

Memory statistics are measured in KB:

Total Used Free Shared Buffers Cached FreeRatio

Mem: 507980 154896 353084 0 488 54488 69.5%

-/+ Buffers/Cache: 99920 408060

Swap: 0 0 0

LowMem: 888420 80776 807644 -- -- -- 90.9%

HighMem: 904128 564844 339284 -- -- -- 37.5%

# (Centralized devices.) Display brief memory usage information.

<Sysname> display memory summary

Memory statistics are measured in KB:

CPU Total Used Free Buffers Caches FreeRatio

0 1029476 325012 704464 2404 143008 68.4%

Low memory statistics are measured in KB:

CPU Total Used Free Buffers Caches FreeRatio

0 739824 375552 364272 -- -- 49.2%

High memory statistics are measured in KB:

CPU Total Used Free Buffers Caches FreeRatio

0 244736 80576 164160 -- -- 67.1%

# (Centralized IRF devices.) (Distributed devices in standalone mode.) Display detailed memory usage information.

<Sysname> display memory

Memory statistics are measured in KB:

Slot 1:

Total Used Free Shared Buffers Cached FreeRatio

Mem: 984560 456128 528432 0 4 45616 53.7%

-/+ Buffers/Cache: 410508 574052

Swap: 0 0 0

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

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

# (Centralized IRF devices.) (Distributed devices in standalone mode.) Display brief memory usage information.

<Sysname> display memory summary

<H3C>dis memory summary

Memory statistics are measured in KB:

Slot CPU Total Used Free Buffers Caches FreeRatio

1 0 984560 456128 528432 4 45616 53.7%

Low memory statistics are measured in KB:

Slot CPU Total Used Free Buffers Caches FreeRatio

1 0 739824 375552 364272 -- -- 49.2%

High memory statistics are measured in KB:

Slot CPU Total Used Free Buffers Caches FreeRatio

1 0 244736 80576 164160 -- -- 67.1%

Table 15 Command output

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

‌

Device management commands -- display memory-threshold

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

Syntax

Centralized devices:

display memory-threshold

Centralized IRF devices:Distributed devices in standalone mode:

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

Distributed devices 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 a card, this command displays the memory usage thresholds and statistics for the active MPU. (Distributed devices in standalone mode.)

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays the memory usage thresholds and statistics for the master device. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you do not specify a member device or PEX, this command displays the memory usage thresholds and statistics for the master device. (Centralized IRF devices.) (IRF 3 capable.)

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

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Usage guidelines

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

Examples

# Display memory alarm thresholds and statistics.

<Sysname> display memory-threshold

Memory usage threshold: 100%

Free-memory thresholds:

Minor: 96M

Severe: 64M

Critical: 48M

Normal: 128M

Early-warning: 256M

Secure: 304M

Current free-memory state: Normal (secure)

Free-memory event statistics:

[Back to secure state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Entered early-warning state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to normal state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Entered minor alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to minor alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Entered severe alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to severe alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Entered critical alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

Device management commands -- display power

Use display power to display power supply information.

Syntax

Centralized devices:Distributed devices in standalone mode:

display power [ power-id ]

Centralized IRF devices:

display power [ slot slot-number [ power-id ] ]

(IRF 3 incapable.) Distributed devices in IRF mode:

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

(IRF 3 capable.) Distributed devices 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

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

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

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

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Usage guidelines

This command is supported only on the default MDC. (IRF 3.1-incapable devices.)

To display power supply information for parent devices, execute this command on the default MDC. To display power supply information for a PEX, you must first log in to the MDC to which the PEX belongs. (IRF 3.1-capable devices.)

Examples

# Display power supply information.

<Sysname> display power

Slot 1:

Input Power: 93.5(W)

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

1 Normal AC 5.40 12.35 66 PowerToPort

2 Normal AC 2.85 10.00 28.5 PortToPower

Table 16 Command output

Field | Description
Input Power | Device input power
PowerID | Power supply ID.
State | Power supply status.
Mode | Mode of the power supply: · AC—AC power supply. · DC—DC power supply.
Current(A) | Output current of the power supply. If this field is not supported, two hyphens (--) are displayed.
Voltage(V) | Output voltage of the power supply. If this field is not supported, two hyphens (--) are displayed.
Power(W) | Output power of the power supply. If this field is not supported, two hyphens (--) are displayed.
FanDirction | Airflow direction of the power supply: · PowerToPort—From the power supply side to the port side. · PortToPower—From the port supply side to the power side.

Device management commands -- display power-supply

Use display power-supply to display power supply information.

Syntax

Centralized devices:Distributed devices in standalone mode:

display power-supply [ verbose ]

Centralized IRF devices:

display power-supply [ slot slot-number ] [ verbose ]

Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

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 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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Examples

# Display detailed power supply information.

<Sysname> display power-supply verbose

Device management commands -- display rps

Use display rps to display redundant power system (RPS) status information.

Syntax

Centralized devices:Distributed devices in standalone mode:

display rps [ rps-id ]

Centralized IRF devices:

display rps [ slot slot-number [ rps-id ] ]

(IRF 3 incapable.) Distributed devices in IRF mode:

display rps [ chassis chassis-number [ rps-id ] ]

(IRF 3 capable.) Distributed devices in IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays RPS status information for all cards. (Distributed devices in standalone mode.)

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays RPS status information for all member devices. (Centralized IRF devices.) (IRF 3 incapable.)

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

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

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 RPS status information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays RPS status information for all IRF member devices and PEXs if you do not specify a member device or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

rps-id: Specifies an RPS by its ID. The value range varies by device model. If you do not specify an RPS, this command displays status information for all RPSs at the specified position.

Examples

# Display RPS status information.

<Sysname> display rps

Device management commands -- display save-power

Use display save-power to display power saving information.

Syntax

display save-power

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display power saving information.

<Sysname> display save-power

Save-power state: enable(wake)

Save-power delay-time: 30(s)

Save-power delay-time remained: 5(s)

Table 17 Command output

Field | Description
Save-power state | Power saving mode: · disabled—Power saving is disabled. · enabled(wake)—Power saving is enabled and the device is operating in wake mode. · enabled(sleep)—Power saving is enabled and the device is operating in sleep mode.
Save-power delay-time | Wake-to-sleep delay time. This field is displayed only when power saving is enabled.
Save-power delay-time remained | Remaining time that the device will stay in wake mode before automatically transitioning to sleep mode. This field is displayed only when power saving is enabled and the device is operating in wake mode.

‌

Device management commands -- display scheduler job

Use display scheduler job to display job configuration information.

Syntax

display scheduler job [ job-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

# Display configuration information for all jobs.

<Sysname> display scheduler job

Job name: saveconfig

copy startup.cfg backup.cfg

Job name: backupconfig

Job name: creat-VLAN100

system-view

vlan 100

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

Device management commands -- display scheduler logfile

Use display scheduler logfile to display job execution log information.

Syntax

display scheduler logfile

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display job execution log information.

<Sysname> display scheduler logfile

Logfile Size: 1902 Bytes.

Job name : shutdown

Schedule name : shutdown

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

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

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

<Sysname>system-view

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

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

[Sysname-if-range]shutdown

Table 18 Command output

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

‌

Related commands

reset scheduler logfile

Device management commands -- display scheduler reboot

Use display scheduler reboot to display the automatic reboot schedule.

Syntax

display scheduler reboot

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display the automatic reboot schedule.

<Sysname> display scheduler reboot

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

Related commands

scheduler reboot at

scheduler reboot delay

Device management commands -- display scheduler schedule

Use display scheduler schedule to display schedule information.

Syntax

display scheduler schedule [ schedule-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

# Display information about all schedules.

<Sysname> display scheduler schedule

Schedule name : shutdown

Schedule type : Run once after 0 hours 2 minutes

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

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

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

Execution counts : 1

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

Job name Last execution status

shutdown Successful

Table 19 Command output

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

‌

Device management commands -- display system stable state

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

context { context-id | all }: Specifies a context by its ID or specifies all contexts. The value range of the context-id argument is 1 to 65279.

mdc { mdc-id | all }: Specifies an MDC by its ID or specifies all MDCs. The value range depends on the device model.

Usage guidelines

If you do not specify any options, this command displays stability information for the system.

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

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

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

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

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

Examples

# (Centralized devices.) Display system stability and status information.

<Sysname> display system stable state

System state : Stable

Role State

Active Stable

Table 20 Command output

Field | Description
System state | This field displays Stable if the system is operating stably.
Role | Device role. The value of this field is fixed at Active.
State | Device status: · Stable—The device is operating stably. · MDC starting—MDCs are starting. · MDC stopping—MDCs are stopping. · Context starting—Contexts are starting. · Context stopping—Contexts are stopping.
* | The object is not operating stably.

‌

# (Distributed devices in standalone mode.) Display system stability and status information.

<Sysname> display system stable state

System state : Stable

Redundancy state : Stable

Slot CPU Role State

0 0 Active Stable

1 0 Standby Stable

3 0 Other Stable

15 0 Other Stable

Table 21 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 a service card.
State | Card status: · Stable—The card is operating stably. · Board inserted—The card has just been installed. · Kernel initiating—Card kernel is being initialized. · Service starting—Services are starting. · Service stopping—Services are stopping. · HA Batch backup—An HA batch backup is going on. · Interface data batch backup—An interface data batch backup is in progress. · MDC starting—MDCs are starting. · MDC stopping—MDCs are stopping. · Context starting—Contexts are starting. · Context stopping—Contexts are stopping.
* | The object is not operating stably.

‌

# (Centralized IRF devices.) Display system stability and status information.

<Sysname> display system stable state

System state : Stable

Redundancy state: No redundance

Slot CPU Role State

1 0 Active Stable

Table 22 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—Member devices are operating stably. You can perform a switchover. · No redundance—The system has only one member device. You cannot perform a switchover. · Not ready—The system is not operating stably. You cannot perform a switchover.
Role | Role of the member device in the system: · Active—The member device is the master. · Standby—The member device is a subordinate member. · Other—The device is a PEX.
State | Member device status: · Stable—The member device is operating stably. · Board inserted—The member device has just been installed. · Kernel initiating—Member device kernel is being initialized. · Service starting—Services are starting on the member device. · Service stopping—Services are stopping on the member device. · 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. · Context starting—Contexts are starting. · Context stopping—Contexts are stopping.
* | The object is not operating stably.

‌

Related commands

display context (Virtual Technologies Command Reference)

display device

display ha service-group (High Availability Command Reference)

display mdc (Virtual Technologies Command Reference)

Device management commands -- display system-working-mode

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

Syntax

display system-working-mode

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display system working mode information.

<Sysname> display system-working-mode

The current system working mode is standard.

The system working mode for next startup is standard.

Device management commands -- 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 23 shows the common transceiver alarm components. If no error occurs, "None" is displayed.

Table 23 Common transceiver alarm components

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

‌

Examples

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

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

GigabitEthernet1/0/1 transceiver current alarm information:

RX loss of signal

RX power low

Table 24 Command output

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

‌

Device management commands -- display transceiver diagnosis

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

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

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

GigabitEthernet1/0/1 transceiver diagnostic information:

Current diagnostic parameters:

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

36 3.31 6.13 -35.64 -5.19

Alarm thresholds:

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

High 50 3.55 1.44 -10.00 5.00

Low 30 3.01 1.01 -30.00 0.00

Table 25 Command output

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

‌

Device management commands -- display transceiver interface

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

Syntax

display transceiver interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

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

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

...

Device management commands -- display transceiver itu-channel

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

Usage guidelines

This command is supported only on the HPE X130 10G SFP+ LC LH80 tunable Transceiver (JL250A) module and SFP-XG-LH80-Tunable Transceiver module.

Examples

# Display ITU channel information for the transceiver module on Ten-GigabitEthernet1/0/1.

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

Interface Channel WaveLength(nm) Frequency(THz)

XGE1/0/1 1 1566.72 191.35

# Display ITU channels supported by the transceiver module on Ten-GigabitEthernet1/0/1.

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

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

Channel WaveLength(nm) Frequency(THz)

1 1566.72 191.35

2 1566.31 191.40

3 1565.90 191.45

4 1565.50 191.50

5 1565.09 191.55

6 1564.68 191.60

7 1564.27 191.65

8 1563.86 191.70

Omitted….

Table 26 Command output

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

‌

Related commands

itu-channel

Device management commands -- 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.

Examples

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

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

...

Device management commands -- 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.070, Feature 2607

Copyright (c) 2004-2017 New H3C Technologies Co., Ltd. All rights reserved.

H3C S6800-54QT uptime is 0 weeks, 0 days, 2 hours, 14 minutes

Last reboot reason : Cold reboot

Boot image: flash:/s6800-cmw710-boot-f2607.bin

Boot image version: 7.1.070, Feature 2607

Compiled May 15 2017 16:00:00

System image: flash:/s6800-cmw710-system-f2607.bin

System image version: 7.1.070, Feature 2607

Compiled May 15 2017 16:00:00

...

Table 27 Command output

Field | Description
Last reboot reason | Reason for the last reboot: · User reboot—The reboot was manually initiated from a user interface, such as the CLI, Web interface, or SNMP. · Cold reboot—The reboot was caused by a power cycle. · Kernel abnormality reboot—The reboot was caused by kernel exceptions. · DeadLoop reboot—The reboot was caused by a kernel thread dead loop. · DEV HandShake reboot—The reboot was caused by a device management handshake failure. · SlaveSwitch reboot—The reboot was caused by a master/subordinate switchover. · IRF Merge reboot—The reboot was caused by an IRF merge. · Auto Update reboot—The reboot was caused by an automatic software upgrade. · Memory exhaust reboot—The reboot was caused by a card-memory-exhausted event.

Device management commands -- display version-update-record

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

Syntax

display version-update-record

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

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

Examples

# Display the startup software image upgrade records.

<Sysname> display version-update-record

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

*Name : simware-cmw710-boot.bin

Version : 7.1.070 Test 0001

Compile time: Mar 25 2015 15:52:43

*Name : simware-cmw710-system.bin

Version : 7.1.070 Test 0001

Compile time: Mar 25 2015 15:52:43

Table 28 Command output

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

‌

Related commands

reset version-update-record

Device management commands -- display voltage

Use display voltage to display voltage information.

Syntax

Centralized devices:

display voltage

Centralized IRF devices:Distributed devices in standalone mode:

display voltage [ slot slot-number ]

Distributed devices in IRF mode:

display voltage [ 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. (Distributed devices in IRF mode.) (IRF 3 incapable.)

slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.) (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number: Specifies 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. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies a card by its slot number or a PEX by its virtual slot number. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays voltage information for all member devices. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or a PEX by its virtual slot number. If you do not specify a member device or PEX, this command displays voltage information for all member devices and PEXs. (Centralized IRF devices.) (IRF 3 capable.)

Usage guidelines

(Distributed devices in standalone mode.) If you do not specify a card, this command displays voltage information for all cards.

(Distributed devices in IRF mode.) If you do not specify a member device, this command displays voltage information for all member devices. If you specify a member device but do not specify a card, this command displays voltage information for all cards on the member device.

If the voltage is lower than the lower limit or higher than the higher limit, the device sends a log message and a trap.

Examples

# (Centralized devices.) Display voltage information.

<Sysname> display voltage

System voltage information (volt):

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

Slot Sensor Voltage Status Required LowLimit HighLimit Description

0 0 0.763 Normal 0.750 0.675 0.825 0.75

0 1 1.051 Normal 1.050 0.945 1.155 1.05

# (Centralized IRF devices.) (Distributed devices in standalone mode.) Display voltage information.

<Sysname> display voltage

System voltage information (volt):

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

Slot Sensor Voltage Status Required LowLimit HighLimit Description

1 0 0.763 Normal 0.750 0.675 0.825 0.75

1 1 1.051 Normal 1.050 0.945 1.155 1.05

Table 29 Command output

Field | Description
Sensor | ID of the sensor.
Voltage | Current voltage of the sensor.
Description | Description for the sensor. This field is generated by the device. It displays the rated voltage of the sensor. If another sensor has the same rated voltage value, a string is automatically inserted before the rated voltage value to uniquely identify the item.

‌

Device management commands -- display xbar

Use display xbar to display the load modes for MPUs.

Syntax

Distributed devices in standalone mode:

display xbar

Distributed devices 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. (Distributed devices in IRF mode.)

Usage guidelines

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

# (Distributed devices in standalone mode.) Display the load modes for MPUs.

<Sysname> display xbar

The configured system HA xbar load mode is BALANCE

The activated system HA xbar load mode is SINGLE

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

Related commands

xbar

Device management commands -- downlink-mode

Use downlink-mode to set the downlink operating mode.

Use undo downlink-mode to restore the default.

Syntax

Centralized devices:

downlink-mode { 10g | 20g }

undo downlink-mode

Centralized IRF devices:

downlink-mode { 10g | 20g } slot slot-number

undo downlink-mode slot slot-number

Default

The downlink operating mode is 10 Gbps.

Views

System view

Predefined user roles

network-admin

parameters

10g: Sets the downlink operating mode to 10 Gbps mode.

20g: Sets the downlink operating mode to 20 Gbps mode.

slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.)

Usage guidelines

The device supports multiple downlink operating modes. If the following restrictions exist, use this task to change the device's downlink operating mode to be the same as the operating mode of downlink devices:

Some downlink devices support only 10 Gbps mode and 20 Gbps mode.

The device cannot negotiate a link operating mode automatically with the downlink devices.

To use the 20 Gbps mode, make sure all downlinks and all downlink devices support the mode. Packet loss might occur if a downlink or a downlink device does not support 20 Gbps mode.

Which interfaces on the device are downlink interfaces depends on the device model.

Examples

# (Centralized devices.) Set the downlink operating mode to 10 Gbps mode.

<Sysname> system-view

[Sysname] downlink-mode 10g

Set the downlink mode successfully. Please reboot the device to make the setting take effect.

# (Centralized IRF devices.) Set the downlink operating mode to 10 Gbps mode for member device 2.

<Sysname> system-view

[Sysname] downlink-mode 10g slot 1

Set the downlink mode successfully. Please reboot the device to make the setting take effect.

Device management commands -- dying-gasp host

Use dying-gasp host to configure poweroff alarm destination host settings.

Use undo dying-gasp host to remove poweroff alarm destination host settings.

Syntax

dying-gasp host { ip-address | ipv6 ipv6-address } [ vpn-instance vpn-instance-name ] snmp-trap version { v1 | v2c } securityname security-string

dying-gasp host { ip-address | ipv6 ipv6-address } [ vpn-instance vpn-instance-name ] syslog

undo dying-gasp host { ip-address | ipv6 ipv6-address } [ vpn-instance vpn-instance-name ] { snmp-trap | syslog }

Default

No poweroff alarm destination host settings are configured.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

ip-address: Specifies the IPv4 address of the destination host to which the device sends the poweroff alarm.

ipv6 ipv6-address: Specifies the IPv6 address of the destination host to which the device sends the poweroff alarm.

vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination host belongs. The vpn-instance-name argument represents the VPN instance name, a case-sensitive string of 1 to 31 characters. If the destination host belongs to the public network, do not specify this option.

snmp-trap: Uses an SNMP notification to send the poweroff alarm.

version: Specifies the SNMP version.

v1: Uses SNMPv1.

v2c: Uses SNMPv2c.

securityname security-string: Specifies an SNMPv1 or SNMPv2c community name, a case-sensitive string of 1 to 32 characters.

syslog: Uses a log message to send the poweroff alarm.

Usage guidelines

This command is supported only on the default MDC.

The device can send the poweroff alarm by using either or both of an SNMP notification and a log message.

The device can send the poweroff alarm to multiple destination hosts at the same time.

Examples

# Configure the device to send the poweroff alarm to the host at 1.1.1.1 by using an SNMPv1 notification. The community name is public.

<Sysname> system-view

[Sysname] dying-gasp host 1.1.1.1 snmp-trap version v1 securityname public

Related commands

display dying-gasp host

dying-gasp source

Device management commands -- dying-gasp source

Use dying-gasp source to specify the source interface for sending the poweroff alarm.

Use undo dying-gasp source to restore the default.

Syntax

dying-gasp source interface-type { interface-number | interface-number.subnumber }

undo dying-gasp source

Default

No source interface is specified. On an IPv4 network, the device uses the primary IPv4 address of the output interface for the route to the destination host as the source address. On an IPv6 network, the device selects a source IPv6 address as defined in RFC 3484.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

interface-type { interface-number | interface-number.subnumber }: Specifies a Layer 3 interface or subinterface. The interface-type argument specifies the interface type. The interface-number argument specifies the interface number. The subnumber argument specifies the subinterface number and is in the range of 1 to 4094. Support for the interface-number.subnumber argument depends on the device model.

Usage guidelines

This command is supported only on the default MDC.

The device uses the IPv6 address or primary IPv4 address of the specified source interface as the source address for outgoing poweroff alarm packets. The destination hosts use this address to identify SNMP notifications or log messages received from the device.

If no address is configured for the specified source interface, this command does not take effect. For this command to take effect, assign an address to the source interface.

Examples

# Use the Loopback 1 interface as the source interface for sending the poweroff alarm.

<Sysname> system-view

[Sysname] dying-gasp source loopback 1

Related commands

dying-gasp host

Device management commands -- fabric load-sharing mode

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

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

Syntax

Centralized IRF devices:Distributed devices in standalone mode:

fabric load-sharing mode { { destination-ip | destination-mac | destination-port | ingress-port | ip-protocol | mpls-label1 | mpls-label2 | mpls-label3 | source-ip | source-mac | source-port | vlan-id } * | flexible | per-packet } slot slot-number

undo fabric load-sharing mode slot slot-number

Distributed devices in IRF mode:

fabric load-sharing mode { { destination-ip | destination-mac | destination-port | ingress-port | ip-protocol | mpls-label1 | mpls-label2 | mpls-label3 | source-ip | source-mac | source-port | vlan-id } * | flexible | per-packet } chassis chassis-number slot slot-number

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

Default

The default varies by device model.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

destination-port: Balances load based on destination port number.

ingress-port: Balances load based on ingress interface.

ip-protocol: Balances load based on protocol type.

mpls-label1: Balances load based on the first-level MPLS label.

mpls-label2: Balances load based on the second-level MPLS label.

mpls-label3: Balances load based on the third-level MPLS label.

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

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

source-port: Balances load based on source port number.

vlan-id: Balances load based on VLAN.

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

per-packet: Balances load per packet.

slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)

slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Centralized IRF devices.) (IRF 3 capable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

Usage guidelines

This command is supported on distributed devices and IRF-capable centralized devices.

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

Examples

# (Distributed devices in standalone mode.) (Centralized IRF devices.) Set the load sharing mode to destination-mac for a card.

<Sysname> system-view

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

Related commands

display xbar

Device management commands -- fan auto-control-mode

Use fan auto-control-mode to set the fan operating mode.

Use undo fan auto-control-mode to restore the default.

Syntax

Distributed devices in standalone mode:

fan auto-control-mode { low-temperature | silence }

undo fan auto-control-mode

Distributed devices in IRF mode:

fan auto-control-mode chassis chassis-number { low-temperature | silence }

undo fan auto-control-mode chassis chassis-number

Default

Fans operate in low-temperature mode.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

low-temperature: Operates at a higher speed to provide better cooling service.

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

Examples

# (Distributed devices in standalone mode.) Set the fan operating mode to silence.

<Sysname> system-view

[Sysname] fan auto-control-mode silence

Device management commands -- fan prefer-direction

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

Use undo fan prefer-direction to restore the default.

Syntax

Centralized devices:Distributed devices in standalone mode:

fan prefer-direction { port-to-power | power-to-port }

undo fan prefer-direction

Centralized IRF devices:

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

undo fan prefer-direction slot slot-number

(IRF 3 incapable.) Distributed devices in IRF mode:

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

undo fan prefer-direction chassis chassis-number

(IRF 3 capable.) Distributed devices in IRF mode:

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

undo fan prefer-direction chassis { chassis-number | virtual-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

slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Centralized IRF devices.) (IRF 3 capable.)

chassis chassis-number: Specifies an IRF member device by its member ID. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

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

Usage guidelines

This command is supported only on the default MDC. (IRF 3.1-incapable devices.)

To specify the preferred airflow direction for parent devices, execute this command on the default MDC. To specify the preferred airflow direction for a PEX, you must first log in to the MDC to which the PEX belongs. (IRF 3.1-capable devices.)

Examples

# (Centralized devices.) (Distributed devices in standalone mode.) Set the preferred airflow direction to port-to-power.

<Sysname> system-view

[Sysname] fan prefer-direction port-to-power

# (Centralized IRF devices.) Set the preferred airflow direction to port-to-power for member device 1.

<Sysname> system-view

[Sysname] fan prefer-direction slot 1 port-to-power

Related commands

display fan

Device management commands -- forward-path-detection enable

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

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

Syntax

forward-path-detection enable

undo forward-path-detection enable

Default

Data forwarding path failure detection is enabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

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

This command is supported only on the default MDC.

Examples

# Enable data forwarding path failure detection.

<Sysname> system-view

[Sysname] forward-path-detection enable

Device management commands -- 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

Device management commands -- hardware-failure-protection aggregation

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

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

Syntax

hardware-failure-protection aggregation

undo hardware-failure-protection aggregation

Default

Hardware failure protection is disabled for aggregation groups.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

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

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

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

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

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

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

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

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

The interface is a physical IRF port.

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

This command is supported only on the default MDC.

Examples

# Enable hardware failure protection for aggregation groups.

<Sysname> system-view

[Sysname] hardware-failure-protection aggregation

Related commands

hardware-failure-detection

hardware-failure-protection auto-down

Device management commands -- hardware-failure-protection auto-down

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

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

Syntax

hardware-failure-protection auto-down

undo hardware-failure-protection auto-down

Default

Hardware failure protection is enabled for an interface.

Views

Ethernet interface view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

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

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

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

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

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

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

The interface is a physical IRF port.

Examples

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

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

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

Device management commands -- hardware-resource tcam

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

Use undo hardware-resource tcam to restore the default.

Syntax

hardware-resource tcam { acl | normal | routing | ipv6 }

undo hardware-resource tcam

Default

The TCAM operating mode is routing.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

acl: Uses the TCAM on the FE card for IPv4 ACLs to extend the storage capacity for IPv4 ACLs.

normal: Does not use the TCAM on the FE card.

routing: Uses the TCAM on the FE card for ARP entries and IPv4 routing entries to extend the storage capacity for the entries.

ipv6: Uses the TCAM on the FE card for IPv4 routing entries and IPv6 routing entries to extend the storage capacity for the entries.

Usage guidelines

This command takes effect only for the FE card.

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

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

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

Reboot the device.

Examples

# Set the TCAM operating mode to routing.

<Sysname> system-view

[Sysname] hardware-resource tcam routing

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

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

Related commands

display hardware-resource

Device management commands -- header

Use header to configure a banner.

Use undo header to delete a banner.

Syntax

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

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

Default

The device does not have banners.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

login: Configures the banner to be displayed before password or scheme authentication is performed for a login user.

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

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

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

Examples

# Configure the legal banner.

<Sysname> system-view

[Sysname] header legal

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

Welcome to use the legal banner%

Device management commands -- itu-channel

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

Use undo itu-channel to restore the default.

Syntax

itu-channel channel-number

undo itu-channel

Default

The ITU channel number is 1.

Views

Ethernet interface view

Predefined user roles

network-admin

mdc-admin

Parameters

channel-number: Specifies the ITU channel number.

Usage guidelines

This command is supported only on the HPE X130 10G SFP+ LC LH80 tunable Transceiver (JL250A) module and SFP-XG-LH80-Tunable Transceiver module.

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

Examples

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

<Sysname> system-view

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

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

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

Related commands

display transceiver itu-channel

Device management commands -- 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

Device management commands -- locator blink

Use locator blink blink-time to start LED flashing to locate devices.

Use locator blink stop to stop LED flashing.

Syntax

Centralized devices:Distributed devices in standalone mode:

locator blink blink-time

locator blink stop

Centralized IRF devices:

locator [ slot slot-number ] blink blink-time

locator [ slot slot-number ] blink stop

(IRF 3 incapable.) Distributed devices in IRF mode:

locator [ chassis chassis-number ] blink blink-time

locator [ chassis chassis-number ] blink stop

(IRF 3 capable.) Distributed devices in IRF mode:

locator [ chassis { chassis-number | virtual-chassis-number slot slot-number } ] blink blink-time

locator [ chassis { chassis-number | virtual-chassis-number slot slot-number } ] blink stop

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, the command applies to all member devices. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. On an IRF fabric, the command applies to all member devices if you do not specify a member device. On an IRF 3 system, the command applies to all IRF member devices and PEXs if you do not specify an IRF member device or PEX. (Centralized IRF devices.) (IRF 3 capable.)

chassis chassis-number: Specifies an IRF member device by its member ID. If you do not specify a member device, the command applies to all member devices. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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, the command applies to all member devices if you do not specify a member device. On an IRF 3 system, the command applies to all IRF member devices and PEXs if you do not specify a member device or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

blink-time: Specifies the flash duration in seconds. The value range is 5 to 120.

stop: Stops flashing.

Usage guidelines

The device provides a LED for device locating. The locator blink blink-time command flashes the specified LEDs quickly for a period of time unless you execute the locator blink stop command. You can use the LEDs to locate the devices.

Examples

# Start LED flashing to locate devices.

<Sysname> locator blink 30

# Stop LED flashing.

<Sysname> locator blink stop

Device management commands -- lpu-type

Use lpu-type to specify the interface card series to use.

Syntax

lpu-type { e-series | f-series }

Default

The default varies by device model.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

e-series: Uses only E series interface cards.

f-series: Uses only F series interface cards.

Usage guidelines

The device supports both E series and F series interface cards. However, the device can use only one series of interface cards at a time. Use this command to specify the series of interface cards for the device to use.

The configuration takes effect after the device reboots.

Examples

# Configure the device to use E series interface cards.

<Sysname> system-view

[Sysname] lpu-type e-series

Changing the LPU type to support. Continue? [Y/N]:y

LPU type changed. The change will take effect after a reboot.

Related commands

display lpu-type

Device management commands -- memory-threshold

Use memory-threshold to set free-memory thresholds.

Use undo memory-threshold to restore the defaults.

Syntax

Centralized devices:

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

undo memory-threshold

Centralized IRF devices:Distributed devices in standalone mode:

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

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

Distributed devices in IRF mode:

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

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

Default

Minor alarm threshold: 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

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

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

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

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

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

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

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

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

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command sets free-memory thresholds for the master device. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you do not specify a member device or PEX, this command sets free-memory thresholds for the master device. (Centralized IRF devices.) (IRF 3 capable.)

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

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Usage guidelines

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

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

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

Examples

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

<Sysname> system-view

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

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

<Sysname> system-view

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

Related commands

display memory-threshold

Device management commands -- memory-threshold usage

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

Use undo memory-threshold usage to restore the default.

Syntax

Centralized devices:

memory-threshold usage memory-threshold

undo memory-threshold usage

Centralized IRF devices:Distributed devices in standalone mode:

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

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

Distributed devices 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

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

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command sets the memory usage threshold for the master device. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you do not specify a member device or PEX, this command sets the memory usage threshold for the master device. (Centralized IRF devices.) (IRF 3 capable.)

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

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

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

Usage guidelines

The device samples memory usage at 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 usage 80

Related commands

display memory-threshold

Device management commands -- 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

Centralized devices:

monitor cpu-usage enable

undo monitor cpu-usage enable

Centralized IRF devices:Distributed devices in standalone mode:

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

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

Distributed devices in IRF mode:

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

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

Default

CPU usage monitoring is enabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command enables CPU usage monitoring for the master device. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you do not specify a member device or PEX, this command enables CPU usage monitoring for the master device. (Centralized IRF devices.) (IRF 3 capable.)

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

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Usage guidelines

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

Examples

# Enable CPU usage monitoring.

<Sysname> system-view

[Sysname] monitor cpu-usage enable

Related commands

display cpu-usage configuration

display cpu-usage history

monitor cpu-usage interval

Device management commands -- monitor cpu-usage interval

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

Syntax

Centralized devices:

monitor cpu-usage interval interval

Centralized IRF devices:Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

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

Default

The system samples CPU usage every 1 minute.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command sets the interval for the master device. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you do not specify a member device or PEX, this command sets the interval for the master device. (Centralized IRF devices.) (IRF 3 capable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets the interval for the global active MPU. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] monitor cpu-usage interval 5Sec

Related commands

display cpu-usage configuration

display cpu-usage history

monitor cpu-usage enable

Device management commands -- 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

Centralized devices:

monitor cpu-usage threshold cpu-threshold

undo monitor cpu-usage threshold

Centralized IRF devices:Distributed devices 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 ] ]

Distributed devices 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 a card, this command sets the CPU usage threshold for the active MPU. (Distributed devices in standalone mode.)

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command sets the CPU usage threshold for the master device. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you do not specify a member device or PEX, this command sets the CPU usage threshold for the master device. (Centralized IRF devices.) (IRF 3 capable.)

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

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

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

Device management commands -- password-recovery enable

Use password-recovery enable to enable password recovery capability.

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

Syntax

password-recovery enable

undo password-recovery enable

Default

Password recovery capability is enabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

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

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

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

To enhance system security, disable password recovery capability.

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

Examples

# Disable password recovery capability.

<Sysname> system-view

[Sysname] undo password-recovery enable

Device management commands -- power-supply off

Use power-supply off to power off a card.

Syntax

Distributed devices in standalone mode:

power-supply off slot slot-number [ subslot subslot-number ]

Distributed devices in IRF mode:

power-supply off chassis chassis-number slot slot-number [ subslot subslot-number ]

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (Distributed devices in IRF mode.)

subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subcard, this command stops supplying power to all subcards on the card.

Usage guidelines

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

(Distributed devices in IRF mode.) To avoid IRF split, the system does not power off an interface card that contains all active physical IRF ports of a member device.

Examples

# (Distributed devices in standalone mode.) Power off a card.

<Sysname> power-supply off slot 2

Device management commands -- power-supply on

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

Syntax

Distributed devices in standalone mode:

power-supply on slot slot-number [ subslot subslot-number ]

Distributed devices in IRF mode:

power-supply on chassis chassis-number slot slot-number [ subslot subslot-number ]

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (Distributed devices in IRF mode.)

subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subcard, this command starts power supply to all subcards on the card.

Examples

# (Distributed devices in standalone mode.) Power on a card.

<Sysname> power-supply on slot 2

Device management commands -- power-supply policy enable

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

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

Syntax

Distributed devices in standalone mode:

power-supply policy enable

undo power-supply policy enable

Distributed devices in IRF mode:

power-supply policy chassis chassis-number enable

undo power-supply policy chassis chassis-number enable

Default

The default varies by device model.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Examples

# (Distributed devices in standalone mode.) Enable power supply management.

<Sysname> system-view

[Sysname] power-supply policy enable

Device management commands -- power-supply policy priority

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

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

Syntax

Distributed devices in standalone mode:

power-supply policy slot slot-number priority priority

undo power-supply policy slot slot-number priority

Distributed devices in IRF mode:

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

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

Default

The default varies by device model.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

priority: Specifies the priority value. The value range varies by device model. A smaller priority value represents a higher priority.

slot slot-number: Specifies an interface card by its slot number. (Distributed devices in standalone mode.)

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] power-supply policy slot 2 priority 10

Device management commands -- power-supply policy redundant

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

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

Syntax

Distributed devices in standalone mode:

power-supply policy redundant module-count

undo power-supply policy redundant

Distributed devices in IRF mode:

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

undo power-supply policy chassis chassis-number redundant

Default

The default varies by device model.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

The configuration of this command takes effect only when power supply management is enabled.

Examples

# (Distributed devices in standalone mode.) Set the number of redundant power supplies to 1.

<Sysname> system-view

[Sysname] power-supply policy redundant 1

Device management commands -- reboot

Use reboot to reboot the device.

Syntax

Centralized devices:

reboot [ subslot subslot-number ] [ force ]

Centralized IRF devices:Distributed devices in standalone mode:

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

Distributed devices 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. (Distributed devices in IRF mode.) (IRF 3 incapable.)

slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.) (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Centralized IRF devices.) (IRF 3 capable.)

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

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

Usage guidelines

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

‌

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

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

Distributed devices in standalone mode:

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

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

To reboot the active MPU, perform the following tasks:

Identify whether the standby MPU is installed and operating correctly.

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

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

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

‌

Centralized IRF devices:

To reboot all member devices, do not specify the slot number option.

To reboot an IRF member device, specify the slot number and do not specify a subslot number.

To reboot the master, perform the following tasks:

Identify whether the IRF fabric has subordinate members and whether the subordinate members are operating correctly.

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

If the IRF fabric has only one member device, the IRF fabric will be rebooted. If the IRF fabric has a subordinate member and the member is operating correctly, a switchover will occur.

| IMPORTANT: To ensure correct operation of the IRF fabric and member devices, do not trigger a switchover by rebooting the master if the status of a member device is not Stable.

‌

Distributed devices in IRF mode:

To reboot all IRF member devices, do not specify the member ID option. (IRF 3 incapable.)

To reboot an IRF member device, specify only the member ID. (IRF 3 incapable.)

To reboot a card, specify both the member ID and the slot number. (IRF 3 incapable.)

To reboot all IRF member devices and PEXs, do not specify the member ID option. (IRF 3 capable.)

To reboot an IRF member device or PEX, specify only the IRF member ID or virtual chassis number. (IRF 3 capable.)

To reboot a card or PEX, specify both the IRF member ID and the slot number. (IRF 3 capable.)

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

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

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

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

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

‌

Examples

# Reboot the device. Choose to save the running configuration when prompted.

<Sysname> reboot

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

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

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

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

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

Validating file. Please wait...

Configuration is saved to flash successfully.

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

Now rebooting, please wait...

# Reboot the device immediately without performing software check.

<Sysname> reboot force

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

Now rebooting, please wait...

Related commands

display system stable state

Device management commands -- 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

Device management commands -- reset version-update-record

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

Syntax

reset version-update-record

Views

System view

Predefined user roles

network-admin

mdc-admin

Examples

# Clear the startup software image upgrade records.

<Sysname> system-view

[Sysname] reset version-update-record

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

Related commands

display version-update-record

Device management commands -- 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

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

Examples

# Restore the factory-default configuration for the device.

<Sysname> restore factory-default

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

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

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

Related commands

reboot

Device management commands -- save-power delay-timer

Use save-power delay-timer to set the wake-to-sleep delay timer.

Use undo save-power delay-timer to restore the default.

Syntax

save-power delay-timer time

undo save-power delay-timer

Default

The default varies by device model.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

time: Delay time in seconds. The value range varies by device model.

Usage guidelines

When the power saving feature is enabled, the device operates in sleep mode or wake mode. The wake-to-sleep delay timer starts when the device transitions to wake mode. If you do not enter characters on the console terminal or press the Mode button before this timer expires, the device will transition to sleep mode.

Examples

# Set the wake-to-sleep delay timer for power saving to 30 seconds.

<Sysname> system-view

[Sysname] save-power delay-timer 30

Related commands

save-power enable

save-power mode

Device management commands -- save-power enable

Use save-power enable to enable the power saving feature.

Use undo save-power enable to disable the power saving feature.

Syntax

save-power enable

undo save-power enable

Default

The power saving feature is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Examples

# Enable the power saving feature.

<Sysname> system-view

[Sysname] save-power enable

Related commands

save-power delay-timer

save-power mode

Device management commands -- save-power mode

Use save-power mode to change the power saving mode.

Syntax

save-power mode { sleep | wake }

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

sleep: Sets the power saving mode to sleep mode. In this mode, the device turns off all LEDs except for the SYS LED on the chassis panel, and enables the power saving feature for all Ethernet interfaces.

wake: Sets the power saving mode to wake mode. In this mode, the device automatically enables the power saving feature for all Ethernet interfaces, but it does not turns off LEDs.

Usage guidelines

You can use this command to change the power saving mode immediately. The device uses less power in sleep mode.

This command takes effect only if the power saving feature is enabled.

Examples

# Change the power saving mode to sleep mode.

<Sysname> save-power mode sleep

Related commands

save-power delay-timer

save-power enable

Device management commands -- scheduler job

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

Use undo scheduler job to delete a job.

Syntax

scheduler job job-name

undo scheduler job job-name

Default

No job exists.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

Examples

# Create a job named backupconfig and enter job view.

<Sysname> system-view

[Sysname] scheduler job backupconfig

[Sysname-job-backupconfig]

Related commands

command

scheduler schedule

Device management commands -- scheduler logfile size

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

Syntax

scheduler logfile size value

Default

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

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] scheduler logfile size 32

Related commands

display scheduler logfile

Device management commands -- scheduler reboot at

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

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot at time [ date ]

undo scheduler reboot

Default

No reboot date or time is specified.

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

| CAUTION: Device reboot interrupts network services.

‌

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

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

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

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

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

Examples

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

<Sysname> scheduler reboot at 12:00

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

Related commands

scheduler reboot delay

Device management commands -- scheduler reboot delay

Use scheduler reboot delay to specify the reboot delay time.

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot delay time

undo scheduler reboot

Default

No reboot delay time is specified.

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

| CAUTION: Device reboot interrupts network services.

‌

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

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

Examples

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

<Sysname> scheduler reboot delay 88

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

Device management commands -- scheduler schedule

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

Use undo scheduler schedule to delete a schedule.

Syntax

scheduler schedule schedule-name

undo scheduler schedule schedule-name

Default

No schedule exists.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

To configure a schedule:

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

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

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

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

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

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

Examples

# Create a schedule named saveconfig.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

Related commands

job

time at

time once

Device management commands -- shutdown-interval

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

Use undo shutdown-interval to restore the default.

Syntax

shutdown-interval interval

undo shutdown-interval

Default

The port status detection timer setting is 30 seconds.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

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

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

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

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

Examples

# Set the port status detection timer to 100 seconds.

<Sysname> system-view

[Sysname] shutdown-interval 100

Device management commands -- sysname

Use sysname to set the device name.

Use undo sysname to restore the default.

Syntax

sysname sysname

undo sysname

Default

The device name is H3C.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

Examples

# Set the name of the device to R2000.

<Sysname> system-view

[Sysname] sysname R2000

[R2000]

Device management commands -- 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 | bridgee | custom feature-name&<1-32> | expert | routee | 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.

bridgee: Sets the system operating mode to enhanced Layer 2.

custom feature-name&<1-32>: Sets the system operating mode to custom and specifies the features to run. The feature-name argument represents the feature name, a case-insensitive string of up to 32 characters. The &<1-32> string means you can specify a maximum of 32 features. To view the available features, use the system-working-mode custom ? command.

expert: Sets the system operating mode to expert.

routee: Sets the system operating mode to enhanced Layer 3.

standard: Sets the system operating mode to standard.

Usage guidelines

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

Change to the operating mode takes effect after a reboot.

Examples

# Set the system operating mode to advanced.

<Sysname> system-view

[Sysname] system-working-mode advance

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

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

Device management commands -- temperature-limit

Use temperature-limit to set the temperature alarm thresholds.

Use undo temperature-limit to restore the default.

Syntax

Centralized devices:

temperature-limit { hotspot | inflow | outflow } sensor-number lowlimit warninglimit [ alarmlimit ]

undo temperature-limit { hotspot | inflow | outflow } sensor-number

Distributed devices in standalone mode:

temperature-limit { slot slot-number | vent } { hotspot | inflow | outflow } sensor-number lowlimit warninglimit [ alarmlimit ]

undo temperature-limit { slot slot-number | vent } { hotspot | inflow | outflow } sensor-number

Centralized IRF devices:

temperature-limit slot slot-number { hotspot | inflow | outflow } sensor-number lowlimit warninglimit [ alarmlimit ]

undo temperature-limit slot slot-number { hotspot | inflow | outflow } sensor-number

Distributed devices in IRF mode:

temperature-limit chassis chassis-number { slot slot-number | vent } { hotspot | inflow | outflow } sensor-number lowlimit warninglimit [ alarmlimit ]

undo temperature-limit chassis chassis-number { slot slot-number | vent } { hotspot | inflow | outflow } sensor-number

Default

The defaults vary by temperature sensor model. To view the defaults, execute the undo temperature-limit and display environment commands in turn.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

chassis chassis-number: Specifies an IRF member device by its member ID. (Distributed devices in IRF mode.) (IRF 3 incapable.)

slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.) (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Centralized IRF devices.) (IRF 3 capable.)

vent: Configures temperature alarm thresholds for the temperature sensors on the chassis and fan trays.

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. To view the value range, enter a question mark (?) in the place of this argument.

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

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

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

Usage guidelines

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

· Sends log messages and traps.

· Sets LEDs on the device panel.

This command is supported only on the default MDC. (IRF 3.1-incapable devices.)

To set the temperature alarm thresholds for parent devices, execute this command on the default MDC. To set the temperature alarm thresholds for a PEX, you must first log in to the MDC to which the PEX belongs. (IRF 3.1-capable devices.)

Examples

# (Centralized devices.) Set temperature alarm thresholds for hotspot sensor 1.

<Sysname> system-view

[Sysname] temperature-limit hotspot 1 -10 50 60

# (Centralized IRF devices.) (Distributed devices in standalone mode.) Set temperature alarm thresholds for hotspot sensor 1 in a slot.

<Sysname> system-view

[Sysname] temperature-limit slot 1 hotspot 1 -10 50 60

Related commands

display environment

Device management commands -- time at

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

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

Syntax

time at time date

undo time

Default

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

Views

Schedule view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

Usage guidelines

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

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

Examples

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

Related commands

scheduler schedule

Device management commands -- time once

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

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

Syntax

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

time once delay time

undo time

Default

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

Views

Schedule view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

Usage guidelines

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

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

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once delay 10

Related commands

scheduler schedule

Device management commands -- time repeating

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

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

Syntax

time repeating [ at time [ date ] ] interval interval

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

undo time

Default

No execution time table is specified for a periodic schedule.

Views

Schedule view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

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

Usage guidelines

The time repeating [ at time [ date ] ] interval interval command configures the device to execute a schedule at 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 an hour from 8:00 a.m. on.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

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

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

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

Related commands

scheduler schedule

Device management commands -- transceiver phony-alarm-disable

Use transceiver phony-alarm-disable to disable transceiver module source alarm.

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

Syntax

transceiver phony-alarm-disable

undo transceiver phony-alarm-disable

Default

Transceiver module source alarm is enabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Disable transceiver module source alarm 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.

Examples

# Disable transceiver module source alarm.

<Sysname> system-view

[Sysname] transceiver phony-alarm-disable

Related commands

display transceiver manuinfo

Device management commands -- usb disable

Use usb disable to disable USB interfaces.

Use undo usb disable to enable USB interfaces.

Syntax

usb disable

undo usb disable

Default

All USB interfaces are enabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

This command is supported only on the default MDC.

You can use USB interfaces to upload or download files or to connect a 3G modem. By default, all USB interfaces are enabled.

Before executing this command, use the umount command to unmount all USB file systems.

Examples

# Enable USB interfaces.

<Sysname> system-view

[Sysname] undo usb disable

Device management commands -- 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

Device management commands -- vmman http enable

Use vmman http enable to enable the VM password agent service.

Use undo vmman http enable to disable the VM password agent service.

Syntax

vmman http enable

undo vmman http enable

Default

The VM password agent service is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

After you enable the VM password agent service on the device, the device can act as the VM password agent to perform the following operations:

Receive, resolve, and save passwords from the cloud stack.

Assign and send passwords to VMs in response to password requests.

The device randomly selects a password from available passwords every time it receives a password request. A VM might obtain a different password at different moments.

Examples

# Enable the VM password agent service.

<Sysname> system

[Sysname] vmman http enable

Related commands

vmman http port

vmman http url

Device management commands -- vmman http port

Use vmman http port to specify the listening port for the VM password agent service.

Use undo vmman http port to restore the default.

Syntax

vmman http port port-number

Default

The listening port is 8080 for the VM password agent service.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

port-number: Specifies the listening port number for the VM password agent service. The value range is 1 to 65535.

Usage guidelines

| IMPORTANT: Changing the listening port closes existing HTTP connections between VMs and the VM password agent service. After a listening port change, VMs must send password requests to the new listening port to obtain passwords again.

‌

VMs obtain passwords from the device through HTTP, at the URL http://Device IP address:Service listening port numberService relative path.

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

Examples

# Set the listening port number to 9090 for the VM password agent service.

<Sysname> system-view

[Sysname] vmman http port 9090

Related commands

vmman http enable

vmman http url

Device management commands -- vmman http url

Use vmman http url to specify the relative path for the VM password agent service.

Use undo vmman http url to restore the default.

Syntax

vmman http url relative-path

undo vmman http url

Default

The relative path is / for the VM password agent service.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

relative-path: Specifies the relative path for the VM password agent service, a case-insensitive string of 1 to 255 characters.

Usage guidelines

| IMPORTANT: Changing the relative path closes existing HTTP connections between VMs and the VM password agent service. After a relative path change, VMs must send password requests to the new listening port to obtain passwords again.

‌

When multiple services use the same HTTP port as the listening port, you must specify a relative path for each of the services to identify the services.

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

Examples

# Set the relative path to /vmman for the VM password agent service.

<Sysname> system-view

[Sysname] vmman http url /vmman

Related commands

vmman http enable

vmman http port

Device management commands -- warm-reboot

Use warm-reboot to warm reboot the device and upgrade software.

Syntax

warm-reboot [ file ipe ipe-filename ]

warm-reboot [ file { boot filename | system filename | feature filename&<1-30> } * ]

Views

User view

Predefined user roles

network-admin

Parameters

file: Upgrades software while rebooting the device.

ipe ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The ipe-filename argument can have a maximum of 63 characters.

boot: Specifies a boot image file.

system: Specifies a system image file.

feature: Specifies feature image files. You can specify a space-separated list of up to 30 feature image files.

filename: Specifies a .bin file in the filesystemname/filename.bin format. The ipe-filename argument can have a maximum of 63 characters.

Usage guidelines

The .ipe or .bin file must be saved in the root directory of a file system on the device.

(Distributed devices in standalone mode.) The .ipe or .bin file must be saved in the root directory of a file system on the active MPU. The filesystemname cannot contain file location information.

(Centralized IRF devices.) The .ipe or .bin file must be saved in the root directory of a file system on the master. The filesystemname cannot contain file location information.

(Distributed devices in IRF mode.) The .ipe or .bin file must be saved in the root directory of a file system on the global active MPU. The filesystemname cannot contain file location information.

To use this command to upgrade device software, make sure the following conditions are met:

The device is operating in standalone mode.

An incremental or ISSU reboot upgrade is recommended for the upgrade. For more information, see Fundamentals Configuration Guide.

Examples

# Warm reboot the device.

<Sysname> warm-reboot

This operation will warm reboot the device. Unsaved settings will be lost. Continue? [Y/N]:y

This operation maybe take several minutes, please wait..........................

# Warm reboot the device and upgrade software.

<Sysname> warm-reboot file feature flash:/cmw710-devkit.bin

This operation will warm reboot the device and upgrade software. Unsaved settings will be lost. Continue? [Y/N]:y

Verifying the file flash:/cmw710-devkit.bin on slot 1...Done.

Identifying the upgrade methods...Done.

Upgrade summary according to following table:

flash:/cmw710-devkit.bin

Running Version New Version

None Alpha 0001

Slot Upgrade Way

1 Warm Reboot

Upgrading software images to compatible versions. Continue? [Y/N]:y

This operation maybe take several minutes, please wait....

Table 30 Command output

Field | Description
Upgrade Way | Upgrade method. The value of this field is fixed at Warm Reboot.

‌

Device management commands -- xbar

Use xbar to set the load mode for MPUs.

Syntax

Distributed devices in standalone mode:

xbar { load-balance | load-single }

Distributed devices in IRF mode:

xbar chassis chassis-number { load-balance | load-single }

Default

The MPUs operate in load-balance mode.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

load-balance: Configures the active MPU and standby MPUs to balance the load for processing and forwarding packets.

load-single: Configures the MPUs so only the active MPU processes and forwards packets. The standby MPU backs up data and monitors the status of the active MPU.

Usage guidelines

A single-MPU device supports only the load-single mode. If you set the MPU load mode to load-balance, the device automatically switches to load-single mode.

Examples

# (Distributed devices in standalone mode.) Set the load mode for the active MPU and the standby MPUs to load-balance.

<Sysname> system-view

[Sysname] xbar load-balance

Related commands

display xbar