A device name (also called hostname) 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>.

Restrictions and guidelines

On an underlay network, the device uses the device name that you have configured for it. If you do not configure a device name for the device but automated underlay network deployment is enabled, the device uses the device name assigned by the VCF fabric feature. For more information about VCF fabric, see VCF fabric configuration in Network Management and Monitoring Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Configure the device name.

sysname sysname

By default, the device name is H3C.

Configuring the system identifier

About this task

Configure a system identifier for the device to indicate the location, functionality, or user-defined identifier of the device.

Procedure

1. Enter system view.

system-view

2. Configure the system identifier for the device.

sysid system-id

By default, the device does not have a system identifier.

Configuring the system time

About the system time

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

The device can use one of the following methods to obtain the system time:

· Uses the locally set system time, and then uses the clock signals generated by its built-in crystal oscillator to maintain the system time.

· Periodically obtains the UTC time from an NTP source, and uses the UTC time, time zone, and daylight saving time to calculate the system time. For more information about NTP, see Network Management and Monitoring Configuration Guide.

The system time calculated by using the UTC time from a time source is more precise.

Restrictions and guidelines for configuring the system time

After you configure the clock protocol none command, the clock datetime command determines the system time, whether or not the time zone or daylight saving time has been configured.

If you configure or change the time zone or daylight saving time after the device obtains the system time, the device recalculates the system time. To view the system time, use the display clock command.

System time configuration tasks at a glance

To configure the system time, perform the following tasks:

1. Configuring the system time

Choose one of the following tasks:

¡ Setting the system time at the CLI

¡ Obtaining the UTC time through a time protocol

2. (Optional.) Setting the time zone

Make sure each network device uses the time zone of the place where the device resides.

3. (Optional.) Setting the daylight saving time

Make sure each network device uses the daylight saving time parameters of the place where the device resides.

Setting the system time at the CLI

1. Enter system view.

system-view

2. Configure the device to use the local system time.

clock protocol none

By default, the device uses the NTP time source.

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

3. Return to user view.

quit

4. Set the local system time.

clock datetime time date

By default, the system time is UTC time 00:00:00 01/01/2011.

CAUTION:

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

‌

Obtaining the UTC time through a time protocol

1. Enter system view.

system-view

2. Specify the system time source.

clock protocol ntp

By default, the device uses the NTP time source.

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

3. Configure time protocol parameters.

For more information about NTP configuration, see Network Management and Monitoring Configuration Guide.

Setting the time zone

1. Enter system view.

system-view

2. Set the time zone.

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

By default, the system uses the UTC time zone.

Setting the daylight saving time

1. Enter system view.

system-view

2. Set the daylight saving time.

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

By default, the daylight saving time is not set.

Enabling displaying the copyright statement

About this task

This feature enables the device to display the copyright statement in the following situations:

· When a Telnet or SSH user logs in.

· When a console user quits user view. This is because the device automatically tries to restart the user session.

If you disable displaying the copyright statement, the device does not display the copyright statement in any situations.

Procedure

1. Enter system view.

system-view

2. Enable displaying the copyright statement.

By default, displaying the copyright statement is enabled.

Configuring banners

About this task

Banners are messages that the system displays when a user logs in.

The system supports the following banners:

· Legal banner—Appears after the copyright statement.

· Message of the Day (MOTD) banner—Appears after the legal banner and before the login banner.

· Login banner—Appears only when password or scheme authentication is configured.

· Shell banner—Appears when a user accesses user view.

The system displays the banners in the following order: legal banner, MOTD banner, login banner, and shell banner.

Banner input methods

You can configure a banner by using one of the following methods:

· Input the entire command line in a single line.

The banner cannot contain carriage returns. The entire command line, including the command keywords, the banner, and the delimiters, can have a maximum of 511 characters. The delimiters for the banner can be any printable character but must be the same. You cannot press Enter before you input the end delimiter.

For example, you can configure the shell banner "Have a nice day." as follows:

<System> system-view

[System] header shell %Have a nice day.%

· Input the command line in multiple lines.

The banner can contain carriage returns. A carriage return is counted as two characters.

To input a banner configuration command line in multiple lines, use one of the following methods:

¡ Press Enter after the final command keyword, type the banner, and end the final line with the delimiter character %. The banner plus the delimiter can have a maximum of 1999 characters.

For example, you can configure the banner "Have a nice day." as follows:

<System> system-view

[System] header shell

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

Have a nice day.%

¡ After you type the final command keyword, type any printable character as the start delimiter for the banner and press Enter. Then, type the banner and end the final line with the same delimiter. The banner plus the end delimiter can have a maximum of 1999 characters.

For example, you can configure the banner "Have a nice day." as follows:

<System> system-view

[System] header shell A

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

Have a nice day.A

¡ After you type the final command keyword, type the start delimiter and part of the banner. Make sure the final character of the final string is different from the start delimiter. Then, press Enter, type the rest of the banner, and end the final line with the same delimiter. The banner plus the start and end delimiters can have a maximum of 2002 characters.

For example, you can configure the banner "Have a nice day." as follows:

<System> system-view

[System] header shell AHave a nice day.

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

Procedure

1. Enter system view.

system-view

2. Configure the legal banner.

header legal text

3. Configure the MOTD banner.

header motd text

4. Configure the login banner.

header login text

5. Configure the shell banner.

header shell text

Disabling password recovery capability

About this task

Password recovery capability controls console user access to the device configuration and SDRAM from BootWare menus. For more information about BootWare menus, see the release notes.

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

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.

Restrictions and guidelines

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

Procedure

1. Enter system view.

system-view

2. Disable password recovery capability.

undo password-recovery enable

By default, password recovery capability is enabled.

Disabling USB interfaces

About this task

You can use USB interfaces to upload or download files. By default, all USB interfaces are enabled. You can disable USB interfaces as needed.

Prerequisites

Before using this command, use the umount command to unmount all USB partitions. For more information about this command, see Fundamentals Command Reference.

Procedure

1. Enter system view.

system-view

2. Disable USB interfaces.

usb disable

By default, all USB interfaces are enabled.

Setting the system operating mode

About this task

Supported features and feature specifications vary by system operating mode.

The device can operate in one of the following modes:

· advance—Advanced mode. This mode is used to support FCoE. It does not support EVPN or VXLAN.

· bridgee—Enhanced Layer 2 mode. It supports L2VPN but does not support FCoE, PVLAN, tunneling, or VXLAN.

· standard—Standard mode. This mode does not support FCoE. Typically, this mode is used.

Restrictions and guidelines

Change to the system operating mode takes effect after a device reboot.

Procedure

1. Enter system view.

system-view

2. Set the system operating mode.

system-working-mode { advance | bridgee | standard }

By default, the device operates in standard mode.

Setting the packet parsing mode

In some scenarios, the device cannot parse incoming user packets correctly. To resolve the issue, you can set the packet parsing mode to network tap so the device redirects incoming user packets to certain ports to parse the packets correctly.

Restrictions and guidelines

Use the network tap mode with caution. This mode might affect the following features: link aggregation hash, ECMP hash, redirect, and VLAN mapping.

For a packet parsing mode change to take effect, save the running configuration and reboot the device.

Procedure

1. Enter system view.

system-view

2. Set the packet parsing mode.

hardware-resource parser { normal | network-tap }

By default, the packet parsing mode is normal.

Setting the UNI operating mode

About this task

A user–network interface (UNI) is a user-side interface for ARP and ND entries to share hardware forwarding entries. You can configure the UNI operating mode to change the sharing method, as shown in Table 1.

Table 1 UNI operating modes for hardware forwarding entry sharing

UNI operating mode	Description
Normal	IPv4 ARP entries that have the same 44 bits from the left in MAC addresses share the same hardware resource entry. IPv6 ND entries with the same MAC address share the same hardware resource entry. ARP entries and ND entries do not share resources.
Enhanced mode (enhance-uni)	IPv4 ARP entries with the same MAC address share the same hardware resource entry. IPv6 ND entries with the same MAC address share the same hardware resource entry. ARP and ND entries with the same MAC address share the same hardware resource entry.

Restrictions and guidelines

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

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

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

3. Reboot the device.

Procedure

1. Enter system view.

system-view

2. Set the UNI operating mode.

hardware-resource uni { normal | enhance-uni }

By default, the UNI operating mode is normal.

Display and maintenance commands for UNI operating mode configuration

To display UNI operating mode information, execute the following command in any view:

display hardware-resource uni

Configuring route asynchonization

Restrictions and guidelines

This feature takes effect immediately after you configure it.

Software version and feature compatibility

This feature is available only in Release 2825 and later.

Procedure

1. Enter system view.

system-view

2. Configure route asynchronization.

hardware-resource route-async { enable | disable }

By default, route asynchronization is enabled.

Display and maintenance commands for route asycnhronization configuration

To display information about route asynchronization, execute the following command in any view:

display hardware-resource route-async

Setting the port status detection timer

About this task

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

Procedure

1. Enter system view.

system-view

2. Set the port status detection timer.

shutdown-interval time

The default setting is 30 seconds.

Monitoring CPU usage

About this task

To monitor CPU usage, the device performs the following operations:

· Samples CPU usage at 1-minute intervals, and compares the samples with CPU usage thresholds to identify the CPU usage status and send alarms or notifications accordingly.

· Samples CPU core usage at 1-minute intervals, and compares the samples with CPU core usage thresholds to identify the CPU core usage status. If a sample is greater than the threshold, the device sends a log message.

· Samples and saves CPU usage at a configurable interval if CPU usage tracking is enabled. You can use the display cpu-usage history command to display the historical CPU usage statistics in a coordinate system.

The device supports the following CPU usage thresholds:

· Minor threshold—If the CPU usage increases to or above the minor threshold but is less than the severe threshold, the CPU usage enters minor alarm state. The device sends minor alarms periodically until the CPU usage increases above the severe threshold or the minor alarm is removed.

· Severe threshold—If the CPU usage increases above the severe threshold, the CPU usage enters severe alarm state. The device sends severe alarms periodically until the severe alarm is removed.

· Recovery threshold—If the CPU usage decreases below the recovery threshold, the CPU usage enters recovered state. The device sends a recovery notification.

CPU usage alarms and notifications can be sent to NETCONF, SNMP, and the information center to be encapsulated as NETCONF events, SNMP traps and informs, and log messages. For more information, see NETCONF, SNMP, and information center in Network Management and Monitoring Configuration Guide.

Figure 1 CPU alarms and alarm-removed notifications

‌

Procedure

1. Enter system view.

system-view

2. Set the CPU usage alarm thresholds.

monitor cpu-usage threshold severe-threshold minor-threshold minor-threshold recovery-threshold recovery-threshold [ slot slot-number [ cpu cpu-number ] ]

The default settings are as follows:

¡ Severe CPU usage alarm threshold—99%.

¡ Minor CPU usage alarm threshold—80%.

¡ CPU usage recovery threshold—60%.

‌

CAUTION:

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

‌

3. Set CPU usage alarm resending intervals.

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

By default, the minor alarm resending interval is 300 seconds and the severe alarm resending interval is 60 seconds.

4. Set the sampling interval for CPU usage tracking.

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

By default, the sampling interval for CPU usage tracking is 1 minute.

5. Enable CPU usage tracking.

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

By default, CPU usage tracking is enabled.

Setting memory alarm thresholds

About this task

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

The system can also issue an early warning to warn you of an approaching insufficient-memory condition.

The system monitors the amount of free memory space. You can use the display memory command to display memory usage information.

As shown in the following table and figure, the system supports these free-memory thresholds:

· Sufficient-memory threshold.

· Early-warning threshold.

· Normal state threshold.

· Minor alarm threshold.

· Severe alarm threshold.

· Critical alarm threshold.

Table 2 Memory alarm notifications and memory alarm-removed notifications

Notification	Triggering condition	Remarks
Early-warning notification	The amount of free memory space decreases below the early-warning threshold.	After generating and sending an early-warning notification, the system does not generate and send any additional early-warning notifications until the early warning is removed.
Minor alarm notification	The amount of free memory space decreases below the minor alarm threshold.	After generating and sending a minor alarm notification, the system does not generate and send any additional minor alarm notifications until the minor alarm is removed.
Severe alarm notification	The amount of free memory space decreases below the severe alarm threshold.	After generating and sending a severe alarm notification, the system does not generate and send any additional severe alarm notifications until the severe alarm is removed.
Critical alarm notification	The amount of free memory space decreases below the critical alarm threshold.	After generating and sending a critical alarm notification, the system does not generate and send any additional critical alarm notifications until the critical alarm is removed.
Critical alarm-removed notification	The amount of free memory space increases above the severe alarm threshold.	N/A
Severe alarm-removed notification	The amount of free memory space increases above the minor alarm threshold.	N/A
Minor alarm-removed notification	The amount of free memory space increases above the normal state threshold.	N/A
Early-warning-removed notification	The amount of free memory space increases above the sufficient-memory threshold.	N/A

‌

Figure 2 Memory alarm notifications and alarm-removed notifications

‌

Restrictions and guidelines

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

Procedure

1. Enter system view.

system-view

2. Set the memory usage threshold.

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

By default, the memory usage threshold is 100%.

3. Set the free-memory thresholds.

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 ]

The default settings are as follows:

¡ Minor alarm threshold—256 MB.

¡ Severe alarm threshold—192 MB.

¡ Critical alarm threshold—128 MB.

¡ Normal state threshold—320 MB.

¡ Early-warning threshold—384 MB.

¡ Sufficient-memory threshold—448 MB.

4. Set memory depletion alarm resending intervals.

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

The following are the default settings:

¡ Early warning resending interval—1 hour.

¡ Minor alarm resending interval—12 hours.

¡ Severe alarm resending interval—3 hours.

¡ Critical alarm resending interval—1 hour.

Configuring resource monitoring

About this task

The resource monitoring feature enables the device to monitor the available amounts of types of resources, for example, the space for ARP entries. The device samples the available amounts periodically and compares the samples with resource depletion thresholds to identify the resource depletion status.

The device supports a minor resource depletion threshold and a severe resource depletion threshold for each supported resource type.

· If the available amount is equal to or less than the minor resource depletion threshold but greater than the severe resource depletion threshold, the resource type is in minor alarm state.

· If the available amount is equal to or less than the severe resource depletion threshold, the resource type is in severe alarm state.

· If the available amount increases above the minor resource depletion threshold, the resource type is in recovered state.

When a resource type enters severe alarm state, the device issues a severe alarm. If the resource type stays in severe alarm state, the device resends severe alarms periodically.

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

Resource depletion alarms can be sent to NETCONF, SNMP, and the information center to be encapsulated as NETCONF events, SNMP traps and informs, and log messages. For more information, see NETCONF, SNMP, and information center in Network Management and Monitoring Configuration Guide.

Figure 3 Resource depletion alarms and alarm-removed notifications

‌

Procedure

1. Enter system view.

system-view

2. Set resource depletion thresholds.

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

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

3. Specify destinations for resource depletion alarms.

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

By default, resource depletion alarms are sent to NETCONF, SNMP, and the information center.

4. Enable resending of minor resource depletion alarms.

resource-monitor minor resend enable

By default, resending of minor resource depletion alarms is enabled.

Setting the temperature alarm thresholds

About this task

The device monitors its temperature based on the following thresholds:

· Low-temperature threshold.

· High-temperature warning threshold.

· High-temperature alarming threshold.

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.

Procedure

1. Enter system view.

system-view

2. Configure the temperature alarm thresholds.

temperature-limit slot slot-number hotspot sensor-number lowlimit warninglimit [ alarmlimit ]

The defaults vary by temperature sensor model. To view the defaults, execute the undo temperature-limit and display environment commands in turn.

The high-temperature alarming threshold must be higher than the high-temperature warning threshold, and the high-temperature warning threshold must be higher than the low-temperature threshold.

Configuring hardware failure detection and protection

The device can automatically detect hardware failures on components, system, and the forwarding plane, and take actions in response.

Specifying the actions to be taken for hardware failures

About this task

The following actions can be taken in response to hardware failures:

· isolate—Performs the following tasks as appropriate to reduce impact from the failures:

¡ Shuts down the relevant ports.

¡ Isolates the device.

¡ Prohibits software loading .

¡ Powers off the device.

· reset—Restarts the relevant components or the device to recover from failures.

· warning—Sends traps to report the failures

Procedure

1. Enter system view.

system-view

2. Specify the action to be taken in response to a type of hardware failures.

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

By default, the system takes the action of warning in response to hardware failures.

Enabling hardware failure protection for aggregation groups

Procedure

1. Enter system view.

system-view

2. Set the action to be taken in response to failures on the forwarding plane to isolate.

hardware-failure-detection forwarding isolate

By default, the system takes the action of warning in response to forwarding-plane failures.

3. Enable hardware failure protection for aggregation groups.

hardware-failure-protection aggregation

By default, hardware failure protection is disabled for aggregation groups.

Configuring parity error logging for entries on forwarding chips

About this task

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

Procedure

1. Enter system view.

system-view

2. Set the parity error statistics period for entries on forwarding chips.

parity-error monitor period value

By default:

¡ In a version earlier than Release 2825, the parity error statistics period is 60 seconds for entries on forwarding chips.

¡ In Release 2825 or later, the parity error statistics period is 600 seconds for entries on forwarding chips.

3. Set the parity error logging threshold for entries on forwarding chips.

parity-error monitor threshold value

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

4. Enable parity error logging for entries on forwarding chips.

parity-error monitor log enable

By default, parity error logging is disabled for entries on forwarding chips.

Configuring consistency error logging for software and hardware forwarding entries

About this task

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

The consistency error logging for software and hardware forwarding entries enables the device to collect statistics for consistency errors periodically. If the number of consistency errors reaches or exceeds the logging threshold, the device generates a log message.

Procedure

1. Enter system view.

system-view

2. Set the statistics period for consistency errors between software and hardware forwarding entries.

parity-error consistency-check period value

The default statistics period is 3600 seconds.

3. Set the logging threshold for consistency errors between software and hardware forwarding entries.

parity-error consistency-check threshold value

The default logging threshold is 10.

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

parity-error consistency-check log enable

By default, consistency error logging is disabled for software and hardware forwarding entries.

By default:

¡ In a version earlier than Release 2825, consistency error logging is disabled for software and hardware forwarding entries.

¡ In Release 2825 or later, consistency error logging is enabled for software and hardware forwarding entries.

Configuring uncorrectable parity error and ECC error logging for entries on forwarding chips

About this task

The device automatically detects parity errors and ECC errors in entries on forwarding chips and tries to correct the error when an error is detected. The uncorrectable parity error and ECC error logging feature enables the device to collect statistics for uncorrectable parity errors and ECC errors periodically. If the number of uncorrectable parity errors and ECC errors reaches or exceeds the logging threshold, the device generates a log message.

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

Software version and feature compatibility

This feature is available only in Release 2825 and later.

Procedure

1. Enter system view.

system-view

2. Set the statistics period for uncorrectable parity error and ECC errors for entries on forwarding chips.

parity-error unrecoverable period value

By default, the statistics period for uncorrectable parity error and ECC errors for entries on forwarding chips is 600 seconds.

3. Set the logging threshold for uncorrectable parity errors and ECC errors for entries on forwarding chips.

parity-error unrecoverable threshold value

By default, the logging threshold for uncorrectable parity errors and ECC errors for entries on forwarding chips is 1.

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

parity-error unrecoverable log enable

By default, uncorrectable parity error and ECC error logging is enabled for entries on forwarding chips

5. (Optional.) Enable automatic system reboot upon generation of an uncorrectable parity error and ECC error log.

parity-error unrecoverable reboot

By default, the device reboots upon generation of an uncorrectable parity error and ECC error log.

Managing power supply

About power supply management

Power modules might have problems such as overload overcurrent, overvoltage, overtemperature, and short circuit. Some power modules use a hardware protection measure, for example, powering off the device, to protect the entire device from being damaged. The hardware protection measure helps protect the device but causes service outage. The power supply management feature can minimize service outage while protecting the device against overload problems.

The power supply management feature constantly monitors the available power and the system loads. If a potential power supply overload problem is found, this feature takes protective measures immediately to remove requirements for power supply hardware protection. Examples of protective measures include sending a notification, starting redundant power modules, and powering off certain interface cards.

Power supply management tasks at a glance

To manage power supply, perform the following tasks:

1. Enabling power supply management

2. (Optional.) Specifying the number of redundant

To avoid overload problems, you can install redundant power modules.

3. (Optional.) Configuring the exception monitoring mode for power supplies

Enabling power supply management

1. Enter system view.

system-view

2. Enable power supply management.

power-supply policy enable

By default, power supply management is enabled.

Specifying the number of redundant power modules

About this task

To avoid overload problems, you can install redundant power modules. For example, if the device requires a minimum of N power modules to operate correctly, you can install M power modules (M > N). The M power modules operate in load balance mode. When a power module fails, the load is rebalanced among the other power modules.

After you specify the number of redundant power modules, the device compares the maximum power consumption of a newly added card with the remaining power.

· If the remaining power is sufficient for the card, the device powers on the card.

· If the power is insufficient, the device does not power on the card. You can add power modules or scale the number of redundant power modules down.

Restrictions and guidelines

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

Procedure

1. Enter system view.

system-view

2. Specify the number of redundant power modules.

power-supply policy redundant module-count

The default setting is 0.

Configuring the exception monitoring mode for power supplies

Restrictions and guidelines

The enhanced exception monitoring mode for the power supplies occupies lots of system resources.

Procedure

1. Enter system view.

system-view

2. Configure the exception monitoring mode for the power supplies.

power-exception-monitor { normal | enhanced }

By default, the normal exception monitoring mode applies to the power supplies.

Verifying and diagnosing transceiver modules

Veri fying transceiver modules

About this task

You can use one of the following methods to verify the genuineness of a transceiver module:

· Display the key parameters of a transceiver module, including its transceiver type, connector type, central wavelength of the transmit laser, transfer distance, and vendor name.

· Display its electronic label. The electronic label is a profile of the transceiver module and contains the permanent configuration, including the serial number, manufacturing date, and vendor name. The data was written to the transceiver module or the device's storage component during debugging or testing of the transceiver module or device.

The device regularly checks transceiver modules for their vendor names. If a transceiver module does not have a vendor name or the vendor name is not H3C, the device repeatedly outputs traps and log messages. For information about logging rules, see Network Management and Monitoring Configuration Guide.

Procedure

To verify transceiver modules, execute the following commands in any view:

· Display the key parameters of transceiver modules.

display transceiver interface [ interface-type interface-number ]

· Display the electrical label information of transceiver modules.

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

Diagnosing transceiver modules

About this task

The device provides the alarm and digital diagnosis functions for transceiver modules. When a transceiver module fails or is not operating correctly, you can perform the following tasks:

· Check the alarms that exist on the transceiver module to identify the fault source.

· Examine the key parameters monitored by the digital diagnosis function, including the temperature, voltage, laser bias current, TX power, and RX power.

Procedure

To diagnose transceiver modules, execute the following commands in any view:

· Display transceiver alarms.

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

· Display the current values of the digital diagnosis parameters on transceiver modules.

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

Configuring transceiver monitoring

About this task

After transceiver monitoring is enabled, the device samples the parameters of transceiver modules periodically, including the input power and output power of transceiver modules. If a sampled value reaches the alarm threshold, the device generates a log to notify users.

Procedure

1. Enter system view.

system-view

2. Enable transceiver monitoring.

transceiver monitor enable

By default, transceiver monitoring is disabled.

3. Set the transceiver monitoring interval.

transceiver monitor interval interval

By default, the transceiver monitoring interval is 600 seconds.

Enabling a lane on a transceiver module

Restrictions and guidelines

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

Use this feature only to verify that a transceiver module operates correctly.

Disabling a lane on a transceiver module will stop signal transmission on the lane.

Disabling a lane will stop signal transmission on the fiber port where the lane is located.

This configuration is saved in a register on the transceiver module. It is not saved to the configuration file.

Software version and feature compatibility

This feature is available only in Release 2825 and later.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Enable a lane on the transceiver module.

transceiver lane channel-number enable

By default, the lanes on the transceiver module are enabled.

Configuring CDR on transmit or receive lanes

Restrictions and guidelines

This feature is supported only on a QSFP transceiver module.

Enabling clock and data recovery (CDR) can reduce the jitter to improve transmission performance, and disabling CDR degrades transmission performance. Both the enable and disable operations might cause oscillation on device ports.

This configuration is saved in a register on the transceiver module. It is not saved to the configuration file.

Software version and feature compatibility

This feature is available only in Release 2825 and later.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Configure CDR on transmit or receive lanes of a transceiver module.

transceiver lane [ lane-number ] cdr { tx | rx } { on | off }

By default, CDR is enabled on transmit and receive lanes of a transceiver module.

Setting the power mode for a transceiver module

Restrictions and guidelines

This feature is supported only on a QSFP transceiver module.

A transceiver module typically operates in high power mode. If a transceiver module will be idle for a long time, you can switch it to low power mode to reduce power consumption. In low power mode, the transceiver module does not transmit signals. For a transceiver module to transmit signals, you must configure it to operate in high power mode.

This configuration is saved in a register on the transceiver module, not in the configuration file.

Software version and feature compatibility

This feature is available only in Release 2825 and later.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Set the power mode for the transceiver module.

transceiver power-mode { high | low }

The default power mode for a transceiver module varies by transceiver module model.

Scheduling a task

About task scheduling

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

You can configure a periodic schedule or a non-periodic schedule. A non-periodic schedule is not saved to the configuration file and is lost when the device reboots. A periodic schedule is saved to the startup configuration file and is automatically executed periodically.

Restrictions and guidelines

· The default system time is always restored at reboot. To make sure a task schedule can be executed as expected, reconfigure the system time or configure NTP after you reboot the device. For more information about NTP, see Network Management and Monitoring Configuration Guide.

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

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

· A schedule cannot contain any one of these commands: telnet, ftp, ssh2, and monitor process.

· A schedule does not support user interaction. 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 schedule is executed in the background, and no output (except for logs, traps, and debug information) is displayed for the schedule.

Procedure

1. Enter system view.

system-view

2. Create a job.

scheduler job job-name

3. Assign a command to the job.

command id command

By default, no command is assigned to a job.

You can assign multiple commands to a job. A command with a smaller ID is executed first.

4. Exit to system view.

quit

5. Create a schedule.

scheduler schedule schedule-name

6. Assign a job to the schedule.

job job-name

By default, no job is assigned to a schedule.

You can assign multiple jobs to a schedule. The jobs will be executed concurrently.

7. Assign user roles to the schedule.

user-role role-name

By default, a schedule has the user role of the schedule creator.

You can assign a maximum of 64 user roles to a schedule. A command in a schedule can be executed if it is permitted by one or more user roles of the schedule.

8. Specify the execution time for the schedule.

Choose one option as needed:

¡ Execute the schedule at specific points of time.

time at time date

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

¡ Execute the schedule after a period of time.

time once delay time

¡ Execute the schedule at the specified time on every specified day in a month or week.

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

¡ Execute the schedule periodically from the specified time on.

time repeating [ at time [date ] ] interval interval

By default, no execution time is specified for a schedule.

The time commands overwrite each other. The most recently configured command takes effect.

9. (Optional.) Set the schedule log file size limit.

scheduler logfile size value

By default, the schedule log file size limit is 16 KB.

The schedule log file stores log messages for execution results of commands in jobs. After the limit is reached, the system deletes the oldest log messages to store the new log messages. If the remaining space of the log file is not enough for a single log message, the system truncates the message and does not store the extra part.

Example: Scheduling a task

Network configuration

As shown in Figure 4, two interfaces of the device are connected to users.

To save energy, configure the device to perform the following operations:

· Enable the interfaces at 8:00 a.m. every Monday through Friday.

· Disable the interfaces at 18:00 every Monday through Friday.

Figure 4 Network diagram

‌

Procedure

# Enter system view.

<Sysname> system-view

# Configure a job for disabling interface Ten-GigabitEthernet 1/0/1.

[Sysna me] scheduler job shutdown-Ten-GigabitEthernet1/0/1

[Sysname-job-shutdown-Ten-GigabitEthernet1/0/1] command 1 system-view

[Sysname-job-shutdown-Ten-GigabitEthernet1/0/1] command 2 interface ten-gigabitethernet 1/0/1

[Sysname-job-shutdown-Ten-GigabitEthernet1/0/1] command 3 shutdown

[Sysname-job-shutdown-Ten-GigabitEthernet1/0/1] quit

# Configure a job for enabling interface Ten-GigabitEthernet 1/0/1.

[Sysname] scheduler job start-Ten-GigabitEthernet1/0/1

[Sysname-job-start-Ten-GigabitEthernet1/0/1] command 1 system-view

[Sysname-job-start-Ten-GigabitEthernet1/0/1] command 2 interface ten-gigabitethernet 1/0/1

[Sysname-job-start-Ten-GigabitEthernet1/0/1] command 3 undo shutdown

[Sysname-job-start-Ten-GigabitEthernet1/0/1] quit

# Configure a job for disabling interface Ten-GigabitEthernet 1/0/2.

[Sysname] scheduler job shutdown-Ten-GigabitEthernet1/0/2

[Sysname-job-shutdown-Ten-GigabitEthernet1/0/2] command 1 system-view

[Sysname-job-shutdown-Ten-GigabitEthernet1/0/2] command 2 interface ten-gigabitethernet 1/0/2

[Sysname-job-shutdown-Ten-GigabitEthernet1/0/2] command 3 shutdown

[Sysname-job-shutdown-Ten-GigabitEthernet1/0/2] quit

# Configure a job for enabling interface Ten-GigabitEthernet 1/0/2.

[Sysname] scheduler job start-Ten-GigabitEthernet1/0/2

[Sysname-job-start-Ten-GigabitEthernet1/0/2] command 1 system-view

[Sysname-job-start-Ten-GigabitEthernet1/0/2] command 2 interface ten-gigabitethernet 1/0/2

[Sysname-job-start-Ten-GigabitEthernet1/0/2] command 3 undo shutdown

[Sysname-job-start-Ten-GigabitEthernet1/0/2] quit

# Configure a periodic schedule for enabling the interfaces at 8:00 a.m. every Monday through Friday.

[Sysname] scheduler schedule START-pc1/pc2

[Sysname-schedule-START-pc1/pc2] job start-Ten-GigabitEthernet1/0/1

[Sysname-schedule-START-pc1/pc2] job start-Ten-GigabitEthernet1/0/2

[Sysname-schedule-START-pc1/pc2] time repeating at 8:00 week-day mon tue wed thu fri

[Sysname-schedule-START-pc1/pc2] quit

# Configure a periodic schedule for disabling the interfaces at 18:00 every Monday through Friday.

[Sysname] scheduler schedule STOP-pc1/pc2

[Sysname-schedule-STOP-pc1/pc2] job shutdown-Ten-GigabitEthernet1/0/1

[Sysname-schedule-STOP-pc1/pc2] job shutdown-Ten-GigabitEthernet1/0/2

[Sysname-schedule-STOP-pc1/pc2] time repeating at 18:00 week-day mon tue wed thu fri

[Sysname-schedule-STOP-pc1/pc2] quit

Verifying the configuration

# Display the configuration information of all jobs.

[Sysname] display scheduler job

Job name: shutdown-Ten-GigabitEthernet1/0/1

system-view

interface ten-gigabitethernet 1/0/1

shutdown

Job name: shutdown-Ten-GigabitEthernet1/0/2

system-view

interface ten-gigabitethernet 1/0/2

shutdown

Job name: start-Ten-GigabitEthernet1/0/1

system-view

interface ten-gigabitethernet 1/0/1

undo shutdown

Job name: start-Ten-GigabitEthernet1/0/2

system-view

interface ten-gigabitethernet 1/0/2

undo shutdown

# Display the schedule information.

[Sysname] display scheduler schedule

Schedule name : START-pc1/pc2

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

Start time : Wed Sep 28 08:00:00 2011

Last execution time : Wed Sep 28 08:00:00 2011

Last completion time : Wed Sep 28 08:00:03 2011

Execution counts : 1

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

Job name Last execution status

start-Ten-GigabitEthernet1/0/1 Successful

start-Ten-GigabitEthernet1/0/2 Successful

Schedule name : STOP-pc1/pc2

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

Start time : Wed Sep 28 18:00:00 2011

Last execution time : Wed Sep 28 18:00:00 2011

Last completion time : Wed Sep 28 18:00:01 2011

Execution counts : 1

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

Job name Last execution status

shutdown-Ten-GigabitEthernet1/0/1 Successful

shutdown-Ten-GigabitEthernet1/0/2 Successful

# Display schedule log information.

[Sysname] display scheduler logfile

Job name : start-Ten-GigabitEthernet1/0/1

Schedule name : START-pc1/pc2

Execution time : Wed Sep 28 08:00:00 2011

Completion time : Wed Sep 28 08:00:02 2011

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

<Sysname>system-view

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

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

[Sysname-Ten-GigabitEthernet1/0/1]undo shutdown

Job name : start-Ten-GigabitEthernet1/0/2

Schedule name : START-pc1/pc2

Execution time : Wed Sep 28 08:00:00 2011

Completion time : Wed Sep 28 08:00:02 2011

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

<Sysname>system-view

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

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

[Sysname-Ten-GigabitEthernet1/0/2]undo shutdown

Job name : shutdown-Ten-GigabitEthernet1/0/1

Schedule name : STOP-pc1/pc2

Execution time : Wed Sep 28 18:00:00 2011

Completion time : Wed Sep 28 18:00:01 2011

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

<Sysname>system-view

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

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

[Sysname-Ten-GigabitEthernet1/0/1]shutdown

Job name : shutdown-Ten-GigabitEthernet1/0/2

Schedule name : STOP-pc1/pc2

Execution time : Wed Sep 28 18:00:00 2011

Completion time : Wed Sep 28 18:00:01 2011

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

<Sysname>system-view

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

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

[Sysname-Ten-GigabitEthernet1/0/2]shutdown

Rebooting the device

About device reboot

The following device reboot methods are available:

· Schedule a reboot at the CLI, so the device automatically reboots at the specified time or after the specified period of time.

· Immediately reboot the device at the CLI.

This method allows you to reboot the device remotely.

During the reboot process, the device performs the following operations:

a. Resets all of its chips.

b. Uses the BootWare to verify the startup software package, decompress the package, and load the images.

c. Initializes the system.

· Power off and then power on the device. This method might cause data loss, and is the least-preferred method.

Using the CLI, you can reboot the device from a remote host.

Restrictions and guidelines for device reboot

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

Rebooting the device immediately at the CLI

Prerequisites

Perform the following steps in any view:

1. Verify that the next-startup configuration file is correctly specified.

display startup

For more information about the display startup command, see Fundamentals Command Reference.

2. Verify that the startup image files are correctly specified.

display boot-loader

If one main startup image file is damaged or does not exist, you must specify another main startup image file before rebooting the device.

For more information about the display boot-loader command, see Fundamentals Command Reference.

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

save

To avoid configuration loss, save the running configuration before a reboot.

For more information about the save command, see Fundamentals Command Reference.

Procedure

To reboot the device immediately at the CLI, execute one of the following commands in user view:

reboot [ slot slot-number ] [ force ]

CAUTION:

· A device reboot might result in service interruption. Before executing this command, make sure you fully understand its impact on your live network.

· Use the force keyword to reboot the device only when the system is faulty or fails to start up normally. A forced device reboots might cause file system damage. Before using the force keyword to reboot the device, make sure you understand its impact.

‌

Scheduling a device reboot

Restrictions and guidelines

The automatic reboot configuration takes effect on all member devices. It will be canceled if a master/subordinate switchover occurs.

The device supports only one device reboot schedule. If you execute the scheduler reboot command multiple times, the most recent configuration takes effect.

Procedure

To schedule a reboot, execute one of the following commands in user view:

· scheduler reboot at time [ date ]

· scheduler reboot delay time

By default, no device reboot time is specified.

CAUTION:

A device reboot might cause service interruption.

‌

Restoring the factory-default configuration

About this task

If you want to use the device in a different scenario or you cannot troubleshoot the device by using other methods, use this task to restore the factory-default configuration.

This task does not delete .bin files and license files.

Restrictions and guidelines

CAUTION:

This task restores the device to the factory default settings. Perform this task with caution.

‌

Configuring this feature might cause loss of license files. That is, the device's installed licenses might be no longer available.

Procedure

1. Execute the following command in user view to restore the factory-default configuration for the device:

restore factory-default

2. Reboot the device.

reboot

When the command prompts you to choose whether to save the running configuration, enter N. If you choose to save the running configuration, the device loads the saved configuration at startup.

Display and maintenance commands for device management configuration

Execute display commands in any view. Execute the reset scheduler logfile and reset transceiver interface command in user view. Execute the reset version-update-record command in system view.

Task	Command
Display device alarm information.	display alarm [ slot slot-number ]
Display the system time, date, time zone, and daylight saving time.	display clock
Display the copyright statement.	display copyright
Display CPU usage statistics. The core keyword is mutually exclusive with the control-plane and data-plane keywords.	display cpu-usage [ control-plane \| data-plane ] [ summary ] [ slot slot-number [ cpu cpu-number [ core { core-number \| all } ] ] ]
Display CPU usage monitoring settings.	display cpu-usage configuration [ slot slot-number [ cpu cpu-number ] ]
Display the historical CPU usage statistics in a coordinate system.	display cpu-usage history [ job job-id ] [ slot slot-number [ cpu cpu-number ] ]
Display hardware information.	display device[ flash \| usb ] [ slot slot-number \| verbose ]
Display electronic label information for the device.	display device manuinfo [ slot slot-number [ subslot subslot-number ] ]
Display electronic label information for a power module.	display device manuinfo slot slot-number power power-id
Display or save operating information for features and hardware modules.	display diagnostic-information [ hardware \| infrastructure \| l2 \| l3 \| service ] [ key-info ] [ filename ]
Display device temperature information.	display environment [ slot slot-number ]
Display the operating states of fan trays.	display fan [ slot slot-number [ fan-id ] ]
Display the packet parsing mode.	display hardware-resource [ parser ]
Display UNI operating mode information.	display hardware-resource [ uni ]
Display memory usage statistics.	display memory [ summary ] [ slot slot-number [ cpu cpu-number ] ]
Display memory alarm thresholds and statistics.	display memory-threshold [ slot slot-number [ cpu cpu-number ] ]
Display power module information.	display power [ slot slot-number [ power-id \| verbose ] ]
Display resource monitoring information.	display resource-monitor [ resource resource-name ] [ slot slot-number [ cpu cpu-number ] ]
Display job configuration information.	display scheduler job [ job-name ]
Display job execution log information.	display scheduler logfile
Display the automatic reboot schedule.	display scheduler reboot
Display schedule information.	display scheduler schedule [ schedule-name ]
Display system heath status information.	display system health [ slot slot-number ]
Display historical system heath status change information.	display system health history [ slot slot-number ]
Display system stability and status information.	display system stable state
Display system working mode information.	display system-working-mode
Display information about the transceiver module status. This command is supported only on the SFP and QSFP transceiver modules.	display transceiver status interface [ interface-type interface-number ] NOTE: This command is available only in Release 2825 and later.
Display system version information.	display version
Display startup software image upgrade records.	display version-update-record
Clear job execution log information.	reset scheduler logfile
Clear startup software image upgrade records.	reset version-update-record

‌

01-Fundamentals Configuration Guide

Configuring the device name

About this task

Procedure

About this task

Procedure

Enabling displaying the copyright statement

About this task

Procedure

About this task

Banner input methods

Disabling password recovery capability

About this task

Restrictions and guidelines

Procedure

About this task

Prerequisites

Procedure

Setting the system operating mode

About this task

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Display and maintenance commands for UNI operating mode configuration

Restrictions and guidelines

Software version and feature compatibility

Procedure

Display and maintenance commands for route asycnhronization configuration

Procedure

Monitoring CPU usage

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

Setting the temperature alarm thresholds

About this task

Procedure

About this task

Procedure

Procedure

About this task

Procedure

About this task

Procedure

Configuring uncorrectable parity error and ECC error logging for entries on forwarding chips

About this task

Software version and feature compatibility

Procedure

Specifying the number of redundant power modules

About this task

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

Restrictions and guidelines

Software version and feature compatibility

Procedure

Restrictions and guidelines

Software version and feature compatibility

Procedure

Restrictions and guidelines

Software version and feature compatibility

Procedure

Scheduling a task

Network configuration

Procedure

Verifying the configuration