This chapter describes how to configure basic device parameters and manage the device. You can perform the configuration tasks in this chapter in any order.

Device management tasks at a glance

All device management tasks are optional. You can perform any of the tasks in any order.

· Configuring basic parameters

¡ Configuring the device name

¡ Configuring the system time

¡ Enabling displaying the copyright statement

¡ Configuring banners

· Configuring security parameters

¡ Disabling password recovery capability

· Adjusting device capacities

¡ Setting the system operating mode

¡ Specifying load sharing modes for a service module

¡ Specifying a load sharing algorithm for a service module

¡ Specifying an operating mode for a service module

¡ Isolating a switching fabric module

¡ Setting the operating mode for an interface subcard

¡ Setting the port status detection timer

· Monitoring the device

¡ Monitoring CPU usage

¡ Setting memory alarm thresholds

¡ Setting the temperature alarm thresholds

¡ Configuring overtemperature auto shutdown

¡ Setting the card power-on control mode

¡ Configuring hardware failure detection and protection

¡ Enabling data forwarding path failure detection

¡ Displaying NSR status

· Managing resources

¡ Setting the fan operating mode

¡ Verifying and diagnosing transceiver modules

· Maintaining the device

¡ Scheduling a task

¡ Rebooting the device

¡ Restoring the factory-default configuration

Restrictions and guidelines: Device management

After being powered on, a card takes some time to start up and complete configuration and data restoration and synchronization. Before configuring the card, use the display device and display system stable state commands to verify that the card is in Normal and Stable states. Failing to follow this rule might cause configuration failures and even device exceptions.

Configuring the device name

About the device name

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

Procedure

1. Enter system view.

system-view

2. Configure the device name.

sysname sysname

The default device name is H3C.

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 or PTP source and uses the UTC time, time zone, and daylight saving time to calculate the system time. For more information about NTP and PTP, 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 NTP or PTP

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 an NTP time source.

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

Obtaining the UTC time through NTP or PTP

1. Enter system view.

system-view

2. Specify the system time source.

clock protocol { ntp | ptp } mdc mdc-id

By default, the device uses an 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 and PTP 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 copyright statement displaying

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 or modem dial-in 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 banners

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. To continue login, the user must enter Y or press Enter. To quit the process, the user must enter N. Y and N are case insensitive.

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

· Incoming banner—Appears for modem users.

· Shell banner—Appears for non-modem users.

The system displays the banners in the following order: legal banner, MOTD banner, login banner, and incoming or 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

By default, no legal banner exists.

3. Configure the MOTD banner.

header motd text

By default, no MOTD banner exists.

4. Configure the login banner.

header login text

By default, no login banner exists.

5. Configure the incoming banner.

header incoming text

By default, no incoming banner exists.

6. Configure the shell banner.

header shell text

By default, no shell banner exists.

Disabling password recovery capability

About password recovery capability

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 active MPU and access the BootWare menu while the active MPU 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.

Setting the system operating mode

About system operating modes

The device can operate in one of the following modes:

· sdn-wan—WAN SDN mode.

· standard—Standard mode.

Supported features and feature specifications vary by system operating mode. BRAS-related features are supported only in standard mode. For support information about other features, see the documents for the features. For information about BRAS-related features, see BRAS Services Configuration Guide.

Restrictions and guidelines

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

To change the system operating mode from WAN SDN to standard, identify whether a Layer 3 Ethernet interface on the device is configured with a MAC address. If yes, you must first use the undo mac-address command to restore the default for the interface.

Procedure

1. Enter system view.

system-view

2. Set the system operating mode.

system-working-mode { sdn-wan | standard }

By default, the device operates in standard mode.

Specifying load sharing modes for a service module

Restrictions and guidelines

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

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

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

If you execute the fabric load-sharing mode command multiple times, the most recent configuration takes effect.

Procedure

1. Enter system view.

system-view

2. Specify load sharing modes for a service module.

In standalone mode:

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

In IRF mode:

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

By default, load sharing for a service module is performed based on ingress interface.

Specifying a load sharing algorithm for a service module

Restrictions and guidelines

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

If a service module does not support a specified algorithm, the fabric load-sharing algorithm command displays an error message.

If you execute the fabric load-sharing algorithm command multiple times, the most recent configuration takes effect.

Procedure

1. Enter system view.

system-view

2. Specify a load sharing algorithm for a service module.

In standalone mode:

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

In IRF mode:

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

By default, no load sharing algorithm is specified for a service module.

Specifying an operating mode for a service module

Restrictions and guidelines

Contact H3C Support before configuring this feature.

This feature is supported only on the following cards:

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

· CMPE-1104 cards.

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

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

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

Procedure

1. Enter system view.

system-view

2. Specify an operating mode for a service module.

In standalone mode:

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

In IRF mode:

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

By default, the operating mode is mix-bridging-routing for a service module.

Isolating a switching fabric module

About isolating a switching fabric module

Isolating a switching fabric module isolates the module from the data plane. An isolated switching fabric module continues to communicate with the MPU, and can forward traffic immediately after the isolation is canceled. The isolation does not affect protocol packet parsing and protocol calculation on the control plane.

Restrictions and guidelines

CAUTION:

· Do not isolate the only switching fabric module of the device.

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

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

Isolate a switching fabric module only if required. If the device has multiple switching fabric modules, isolating a switching fabric module or channel decreases the forwarding bandwidth and reduces the forwarding performance.

You can isolate switching fabric modules to identify whether switching fabric modules can forward traffic correctly.

Before replacing a switching fabric module, you can isolate the module to prevent packet loss.

To use an isolated switching fabric module or channel, use the undo switch-fabric isolate command to cancel the isolation.

Procedure

1. Enter system view.

system-view

2. Isolate a switching fabric module or channel.

In standalone mode:

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

In IRF mode:

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

By default, a switching fabric module is not isolated from the forwarding plane and forwards traffic.

Setting the operating mode for an interface subcard

About operating modes for interface subcards

Some interface subcards can operate in multiple modes to provide different types of interfaces. Use this feature to set the operating mode for an interface subcard.

Restrictions and guidelines

This feature is supported only on MIC-SP4L subcards.

The following are the operating modes:

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

· oc-12-pos—Specifies the oc-12-pos mode. All interfaces on the interface subcard act as 622 Mbps POS interfaces.

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

· oc-3-pos—Specifies the oc-3-pos mode. All interfaces on the interface subcard act as 155 Mbps POS interfaces.

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

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

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

Procedure

1. Enter system view.

system-view

2. Set the operating mode for an interface subcard.

In standalone mode:

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

In IRF mode:

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

By default, a MIC-SP4L subcard operates in oc-3-pos mode.

Setting the port status detection timer

About the port status detection timer

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.

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 CPU usage monitoring

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

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

In standalone mode:

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

In IRF mode:

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

By default, the severe CPU usage alarm threshold is 99%, and the minor CPU usage alarm threshold is 79%.

3. Set the sampling interval for CPU usage tracking.

In standalone mode:

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

In IRF mode:

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

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

4. Enable CPU usage tracking.

In standalone mode:

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

In IRF mode:

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

By default, CPU usage tracking is enabled.

Setting memory alarm thresholds

About memory alarm thresholds

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

· Samples memory usage at 1-minute intervals, and compares the sample with the memory usage threshold. If the sample is greater, the device sends a trap.

· Monitors the amount of free memory space in real time. If the amount of free memory space exceeds a free-memory threshold, the system generates an alarm notification and sends it to affected service modules or processes. If the amount of free memory space drops below a free-memory threshold, the system generates an alarm-removed notification and sends it to affected service modules or processes.

For slots that support low memory, the system monitors only the amount of free low-memory space. You can use the display memory command to display memory usage information. If the LowMem field is displayed for a slot, the slot supports low memory.

As shown in Table 1 and Figure 2, the system supports the following free-memory thresholds:

· Normal state threshold.

· Minor alarm threshold.

· Severe alarm threshold.

· Critical alarm threshold.

Table 1 Memory alarm notifications and memory alarm-removed notifications

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

Figure 2 Memory alarm notifications and alarm-removed notifications

Procedure

1. Enter system view.

system-view

2. Set the memory usage threshold.

In standalone mode:

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

In IRF mode:

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

The default memory usage threshold is 100%.

3. Set the free-memory thresholds.

In standalone mode:

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

In IRF mode:

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

The defaults are as follows:

¡ Minor alarm threshold—96 MB.

¡ Severe alarm threshold—64 MB.

¡ Critical alarm threshold—48 MB.

¡ Normal state threshold—128 MB.

Setting the temperature alarm thresholds

About temperature alarm thresholds

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.

In standalone mode:

temperature-limit slot slot-number { hotspot | inflow | outflow } sensor-number lowlimit warninglimit [ alarmlimit ]

In IRF mode:

temperature-limit chassis chassis-number slot slot-number { hotspot | inflow | outflow } sensor-number lowlimit warninglimit [ alarmlimit ]

The default temperature alarm thresholds depend on the device model. To view the default temperature alarm thresholds, use the undo temperature-limit command to restore the default and execute the display environment command.

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 overtemperature auto shutdown

About overtemperature auto shutdown

When the temperature on a card reaches the shutdown temperature threshold, the overtemperature auto shutdown feature automatically shuts down the card. You can restore power supply for the cards as appropriate by using the power-off high-temp-board clear command.

Restrictions and guidelines

This feature is supported on the following cards:

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

· CMPE-1104 cards and IM-MSUX cards.

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

· Switching fabric modules.

Procedure

1. Enter system view.

system-view

2. Enable the overtemperature auto shutdown feature.

power-off high-temp-board enable

By default, the overtemperature auto shutdown feature is enabled.

3. Restore power supply for cards shut down because of overtemperature.

power-off high-temp-board clear

Setting the card power-on control mode

About card power-on control mode

When you install a service module or switching fabric module, the device calculates the following items:

· Total power reserved for fans and MPUs.

· Total maximum power of all service modules and switching fabric modules, including the newly installed module.

In strict mode, the device powers on the newly installed module only if the sum of the two items is equal to or less than the rated power of the device.

In loose mode, the device powers on the newly installed module as long as the sum of the two items is equal to or less than the rated power of the device * 1.2.

Procedure

1. Enter system view.

system-view

2. Set the card power-on control mode.

power control-mode { loose | strict }

By default, the card power-on control mode is strict.

Configuring hardware failure detection and protection

About hardware failure detection and protection

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

Specifying the actions to be taken for hardware failures

About actions for hardware failures

The device can take the following actions in response to hardware failures:

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

¡ Shuts down the relevant ports.

¡ Prohibits loading software for the relevant cards.

¡ Isolates the relevant cards.

¡ Powers off the relevant cards.

· reset—Restarts the relevant components or cards 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 hardware failures on the forwarding plane.

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

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

Enabling hardware failure protection for interfaces

About hardware failure protection for interfaces

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.

Restrictions and guidelines

Before enabling hardware failure protection on an interface, make sure a backup link is available for service continuity.

To view the status of an interface, use the display interface command.

After the failure on an interface is removed, bring the interface up by using the undo shutdown command.

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 (sending traps) in response to forwarding-plane failures.

3. Enter Ethernet interface view.

interface interface-type interface-number

4. Enable hardware failure protection for the interface.

hardware-failure-protection auto-down

By default, hardware failure protection is enabled.

Enabling hardware failure protection for aggregation groups

About hardware failure protection for aggregation groups

Hardware failure protection for aggregation groups uses the following rules upon detecting a hardware failure on an aggregation group member interface:

· Does not shut down the interface if the member interface is the only member in up state in the group.

· Shuts down the interface if the member interface is not the only member in up state in the group.

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. Enter Ethernet interface view.

interface interface-type interface-number

4. Disable hardware failure protection for the interface.

undo hardware-failure-protection auto-down

By default, hardware failure protection is enabled.

Configure this command on every member interface in the aggregation group.

5. Exit to system view.

quit

6. Enable hardware failure protection for aggregation groups.

hardware-failure-protection aggregation

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

Enabling data forwarding path failure detection

About data forwarding path failure protection

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

Procedure

1. Enter system view.

system-view

2. Enable data forwarding path failure detection.

forward-path-detection enable

By default, data forwarding path failure detection is enabled.

Displaying NSR status

About displaying NSR status

Nonstop routing (NSR) backs up protocol status and data from the active process to the standby process to ensure forwarding continuity. You can display NSR status information for all modules that support NSR.

Procedure

To display NSR status information for modules that support the NSR feature, execute the following command in any view:

display non-stop-routing status

Setting the fan operating mode

About fan operating modes

Fans can operate in either of the following modes:

· auto—Operates at an adjustable speed. The device adjusts the speed automatically based on the card temperature. As a best practice, use this mode.

· high—Operates at a higher speed to provide better cooling service.

· middle—Operates at a middle speed.

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

Procedure

1. Enter system view.

system-view

2. Set the fan operating mode.

In standalone mode:

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

In IRF mode:

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

By default, fans operate in auto mode.

Verifying and diagnosing transceiver modules

Veri fying transceiver modules

About transceiver module verification

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 transceiver module diagnosis

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 ]

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 at intervals 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 3, 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 3 Network diagram

‌

Procedure

# Enter system view.

<Sysname> system-view

# Configure a job for disabling interface GigabitEthernet 3/1/1.

[Sysna me] scheduler job shutdown-GigabitEthernet3/1/1

[Sysname-job-shutdown-GigabitEthernet3/1/1] command 1 system-view

[Sysname-job-shutdown-GigabitEthernet3/1/1] command 2 interface gigabitethernet 3/1/1

[Sysname-job-shutdown-GigabitEthernet3/1/1] command 3 shutdown

[Sysname-job-shutdown-GigabitEthernet3/1/1] quit

# Configure a job for enabling interface GigabitEthernet 3/1/1.

[Sysname] scheduler job start-GigabitEthernet3/1/1

[Sysname-job-start-GigabitEthernet3/1/1] command 1 system-view

[Sysname-job-start-GigabitEthernet3/1/1] command 2 interface gigabitethernet 3/1/1

[Sysname-job-start-GigabitEthernet3/1/1] command 3 undo shutdown

[Sysname-job-start-GigabitEthernet3/1/1] quit

# Configure a job for disabling interface GigabitEthernet 3/1/2.

[Sysname] scheduler job shutdown-GigabitEthernet3/1/2

[Sysname-job-shutdown-GigabitEthernet3/1/2] command 1 system-view

[Sysname-job-shutdown-GigabitEthernet3/1/2] command 2 interface gigabitethernet 3/1/2

[Sysname-job-shutdown-GigabitEthernet3/1/2] command 3 shutdown

[Sysname-job-shutdown-GigabitEthernet3/1/2] quit

# Configure a job for enabling interface GigabitEthernet 3/1/2.

[Sysname] scheduler job start-GigabitEthernet3/1/2

[Sysname-job-start-GigabitEthernet3/1/2] command 1 system-view

[Sysname-job-start-GigabitEthernet3/1/2] command 2 interface gigabitethernet 3/1/2

[Sysname-job-start-GigabitEthernet3/1/2] command 3 undo shutdown

[Sysname-job-start-GigabitEthernet3/1/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-GigabitEthernet3/1/1

[Sysname-schedule-START-pc1/pc2] job start-GigabitEthernet3/1/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-GigabitEthernet3/1/1

[Sysname-schedule-STOP-pc1/pc2] job shutdown-GigabitEthernet3/1/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-GigabitEthernet3/1/1

system-view

interface gigabitethernet 3/1/1

shutdown

Job name: shutdown-GigabitEthernet3/1/2

system-view

interface gigabitethernet 3/1/2

shutdown

Job name: start-GigabitEthernet3/1/1

system-view

interface gigabitethernet 3/1/1

undo shutdown

Job name: start-GigabitEthernet3/1/2

system-view

interface gigabitethernet 3/1/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-GigabitEthernet3/1/1 Successful

start-GigabitEthernet3/1/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-GigabitEthernet3/1/1 Successful

shutdown-GigabitEthernet3/1/2 Successful

# Display schedule log information.

[Sysname] display scheduler logfile

Job name : start-GigabitEthernet3/1/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 gigabitethernet 3/1/1

[Sysname-GigabitEthernet3/1/1]undo shutdown

Job name : start-GigabitEthernet3/1/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 gigabitethernet 3/1/2

[Sysname-GigabitEthernet3/1/2]undo shutdown

Job name : shutdown-GigabitEthernet3/1/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 gigabitethernet 3/1/1

[Sysname-GigabitEthernet3/1/1]shutdown

Job name : shutdown-GigabitEthernet3/1/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 gigabitethernet 3/1/2

[Sysname-GigabitEthernet3/1/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.

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

A device reboot might result in a service outage.

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

Rebooting devices 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:

In standalone mode:

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

In IRF mode:

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

Scheduling a device reboot

Restrictions and guidelines

(In standalone mode.) The automatic reboot configuration is canceled if an active/standby switchover occurs.

(In IRF mode.) The automatic reboot configuration is effective on all member devices. It will be canceled if a switchover between the global active MPU and a global standby MPU 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.

Restoring the factory-default configuration

About restoring the factory-default configuration

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.

Restrictions and guidelines

This task is disruptive.

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

(In standalone mode.) Execute display commands in any view. Execute the reset scheduler logfile 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.	display cpu-usage [ summary ] [ slot slot-number [ cpu cpu-number [ core { core-number \| all } ] ] ] display cpu-usage [ control-plane \| data-plane ] [ summary ] [ slot slot-number [ cpu cpu-number ] ]
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 CPU overload records.	display cpu-usage overload show-number [ stack-info ] slot slot-number [ cpu cpu-number ]
Display summary CPU overload information.	display cpu-usage overload summary
Display device information. The sd-card keyword is supported only on CSR05SRP1P3 cards.	display device [ cf-card \| sd-card ] [ slot slot-number [ cpu cpu-number ] [ subslot subslot-number ] \| verbose ]
Display electronic label information for the device.	display device manuinfo [ slot slot-number [ subslot subslot-number ] ]
Display electronic label information for the chassis backplane.	display device manuinfo chassis-only
Display electronic label information for a fan tray.	display device manuinfo fan fan-id
Display electronic label information for a power supply.	display device manuinfo 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 [ fan-id ]
Display the current fan operating mode and the speeds of fans.	display fan-speed
Display CPU and memory usage.	display health [ slot slot-number [ cpu cpu-number ] ]
Display hardware failure detection and fix information.	display hardware-failure-detection
Display hardware failure protection information.	display hardware-failure-protection [ aggregation \| port { auto-down \| interface-type interface-number } ]
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 supply information.	display power [ power-id ]
Display power information about power supplies and cards.	display power-information [ verbose ]
Display whether the overtemperature auto shutdown feature is enabled.	display power-off high-temp-board
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 the current operating modes of cards.	display service-mode status
Display system stability and status information.	display system stable state
Display system operating mode information.	display system-working-mode
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

‌

(In IRF mode.) Execute display commands in any view. Execute the reset scheduler logfile command in user view. Execute the reset version-update-record command in system view.

Task	Command
Display device alarm information.	display alarm [ chassis chassis-number 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.	display cpu-usage [ summary ] [ chassis chassis-number slot slot-number [ cpu cpu-number [ core { core-number \| all } ] ] ] display cpu-usage [ control-plane \| data-plane ] [ summary ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display CPU usage monitoring settings.	display cpu-usage configuration [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display the historical CPU usage statistics in a coordinate system.	display cpu-usage history [ job job-id ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display CPU overload records.	display cpu-usage overload show-number [ stack-info ] chassis chassis-number slot slot-number [ cpu cpu-number ]
Display summary CPU overload information.	display cpu-usage overload summary
Display device information. The sd-card keyword is supported only on CSR05SRP1P3 cards.	display device [ cf-card \| sd-card ] [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] [ subslot subslot-number ] ] \| verbose ]
Display electronic label information for the device.	display device manuinfo [ chassis chassis-number [ slot slot-number [ subslot subslot-number ] ] ]
Display electronic label information for a chassis backplane.	display device manuinfo chassis chassis-number chassis-only
Display electronic label information for a fan tray.	display device manuinfo chassis chassis-number fan fan-id
Display electronic label information for a power supply.	display device manuinfo chassis chassis-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 [ chassis chassis-number [ slot slot-number ] ]
Display the operating states of fan trays.	display fan [ chassis chassis-number [ fan-id ] ]
Display the current fan operating mode and the speeds of fans.	display fan-speed [ chassis chassis-number ]
Display CPU and memory usage.	display health [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] ] ]
Display hardware failure detection and fix information.	display hardware-failure-detection
Display hardware failure protection information.	display hardware-failure-protection [ aggregation \| port { auto-down \| interface-type interface-number } ]
Display memory usage statistics.	display memory [ summary ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display memory alarm thresholds and statistics.	display memory-threshold [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display power supply information.	display power [ chassis chassis-number [ power-id ] ]
Display power information about power supplies and cards.	display power-information [ chassis chassis-number ] [ verbose ]
Display whether the overtemperature auto shutdown feature is enabled.	display power-off high-temp-board
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 the current operating modes of cards.	display service-mode status chassis chassis-number
Display system stability and status information.	display system stable state
Display system operating mode information.	display system-working-mode
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 the device name

Enabling displaying the copyright statement

About copyright statement displaying

Procedure

About banners

Banner input methods

Disabling password recovery capability

About password recovery capability

Restrictions and guidelines

Procedure

About system operating modes

Restrictions and guidelines

Procedure

Specifying load sharing modes for a service module

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

Specifying an operating mode for a service module

Restrictions and guidelines

Procedure

About isolating a switching fabric module

Restrictions and guidelines

Procedure

About operating modes for interface subcards

Restrictions and guidelines

Procedure

Procedure

Monitoring CPU usage

About CPU usage monitoring

Procedure

About memory alarm thresholds

Procedure

Setting the temperature alarm thresholds

About temperature alarm thresholds

Procedure

About overtemperature auto shutdown

Restrictions and guidelines

Procedure

About card power-on control mode

Procedure

About actions for hardware failures

Procedure

About hardware failure protection for interfaces

Restrictions and guidelines

Procedure

About hardware failure protection for aggregation groups

Procedure

About data forwarding path failure protection

Procedure

About displaying NSR status

Procedure

About fan operating modes

Procedure

About transceiver module verification

Procedure

About transceiver module diagnosis

Procedure

Scheduling a task

Network configuration

Procedure

Verifying the configuration

Rebooting the device

Prerequisites

Procedure

Restrictions and guidelines

Procedure

About restoring the factory-default configuration

Restrictions and guidelines

Procedure

Display and maintenance commands for device management configuration

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy