Contents

Managing the device· 1

Device management task list 1

Configuring the device name· 1

Configuring the system time· 1

a      Return to user view: quit 2

b     Specify a UTC time for the device: clock datetime time date· 2

Enabling displaying the copyright statement 2

Configuring banners· 3

Banner types· 3

Banner input methods· 3

Configuration procedure· 4

Setting the system operating mode· 4

Rebooting the device· 5

Configuration guidelines· 5

Rebooting devices immediately at the CLI 5

Scheduling a device reboot 6

Scheduling a task· 6

Configuration guidelines· 6

Configuration procedure· 6

Schedule configuration example· 8

Setting the port status detection timer 11

Monitoring CPU usage· 11

Setting memory alarm thresholds· 12

Configuring the temperature alarm thresholds· 14

Configuring hardware failure detection and protection· 14

Setting the table capacity mode· 15

Specifying the preferred airflow direction· 15

Verifying and diagnosing transceiver modules· 16

Verifying transceiver modules· 16

Diagnosing transceiver modules· 16

Disabling alarm traps for transceiver modules· 17

Restoring the factory-default configuration· 17

Displaying and maintaining device management configuration· 17

Managing the device

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 task list

Tasks at a glance
(Required.) Configuring the device name
(Required.) Configuring the system time
(Optional.) Enabling displaying the copyright statement
(Optional.) Configuring banners
(Required.) Setting the system operating mode
(Optional.) Rebooting the device
(Optional.) Scheduling a task
(Optional.) Setting the port status detection timer
(Optional.) Monitoring CPU usage
(Required.) Setting memory alarm thresholds
(Required.) Configuring the temperature alarm thresholds
(Optional.) Configuring hardware failure detection and protection
(Optional.) Setting the table capacity mode
(Optional.) Specifying the preferred airflow direction
(Required.) Verifying and diagnosing transceiver modules
(Optional.) Restoring the factory-default configuration

 

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

To configure the device name:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Configure the device name.	sysname sysname	The default device name is H3C.

 

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

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

·           None—Local UTC time, set by using the clock datetime command. The local UTC time is restored to the default after a reboot. After a device reboot, you must reconfigure the local UTC time.

·           NTP—NTP time source. You must configure NTP correctly. For more information about NTP and NTP configuration, see Network Management and Monitoring Configuration Guide.

On an S7500E-XS switch, system time settings are restored to the default after a reboot. After an S7500E-XS switch reboots, you must reconfigure the system time for the switch.

To configure the system time:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Specify the UTC time source.	clock protocol { none | ntp }	By default, the device uses the NTP time source. If you execute this command multiple times, the most recent configuration takes effect.
3.      (Optional.) Set the local UTC time.	a       Return to user view: quit b       Specify a UTC time for the device: clock datetime time date c       Enter system view again: system-view	Required when the local UTC time source is used.
4.      Set the time zone.	clock timezone zone-name { add | minus } zone-offset	By default, the time zone is not set. This setting must be consistent with the time zone of the place where the device resides.
5.      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. The settings must be consistent with the daylight saving time parameters of the place where the device resides.

 

Enabling displaying the copyright statement

When displaying the copyright statement is enabled, the device displays 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.

The following is a sample copyright statement:

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

* Copyright (c) 2004-2014 Hangzhou H3C Tech. Co., Ltd. All rights reserved.  *

* Without the owner's prior written consent,                                 *

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

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

To enable displaying the copyright statement:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Enable displaying the copyright statement.	copyright-info enable	By default, this feature is enabled.

 

Configuring banners

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

Banner types

The system supports the following banners:

·           Legal banner—Appears after the copyright or license 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—The device does not support this banner.

·           Shell banner—Appears for all login users.

Banner input methods

You can configure a single-line banner or a multiline banner.

·           Single-line banner.

A single-line banner must be input in the same line as the command. The start and end delimiters for the banner can be any printable character. However, they must be the same and must not be included in the banner. The input text, including the command keywords and the delimiters, cannot exceed 511 characters. Do not 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.%

·           Multiline banner.

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

To input a multiline banner, use one of the following methods:

¡  Method 1—Press Enter after the final command keyword, enter the banner as prompted, 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. Please input the password." as follows:

<System> system-view

[System] header shell

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

Have a nice day.

Please input the password.%

¡  Method 2—After you type the final command keyword, type any single printable character as the start delimiter for the banner and press Enter. Then, type the banner as prompted 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. Please input the password." as follows:

<System> system-view

[System] header shell A

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

Have a nice day.

Please input the password.A

¡  Method 3—After you type the final command keyword, type the start delimiter and part of the banner and press Enter. Then, enter the rest of the banner as prompted 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. Please input the password." as follows:

<System> system-view

[System] header shell AHave a nice day.

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

Please input the password.

A

Configuration procedure

To configure banners:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Configure the legal banner.	header legal text	By default, the device does not have a legal banner.
3.      Configure the MOTD banner.	header motd text	By default, the device does not have an MOTD banner.
4.      Configure the login banner.	header login text	By default, the device does not have a login banner.
5.      Configure the incoming banner.	header incoming text	By default, the device does not have an incoming banner.
6.      Configure the shell banner.	header shell text	By default, the device does not have a shell banner.

 

Setting the system operating mode

The device can operate in the following modes:

·           advance—Advanced mode.

·           standard—Standard mode.

In different operating modes, the device supports different features, and might have different specifications for the supported features. For example, the FCoE feature is supported only in advanced mode.

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

To set the system operating mode:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Set the system operating mode.	system-working-mode { advance | standard }	By default, the device operates in standard mode. Change to the operating mode takes effect after a reboot.

 

Rebooting the device

CAUTION: ·       A device reboot might interrupt network services. ·       To avoid configuration loss, use the save command to save the running configuration before a reboot. For more information about the save command, see Fundamentals Command Reference. ·       Before a reboot, use the display startup and display boot-loader commands to verify that the startup configuration file and startup software images are correctly specified. If a startup configuration file or software image problem exists, the device cannot start up correctly. For more information about the two display commands, see Fundamentals Command Reference.

 

The following device reboot methods are available:

·           Immediately reboot the device at the CLI.

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

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

Configuration guidelines

When you schedule a reboot, follow these guidelines:

·           The automatic reboot configuration is canceled if a master/subordinate switchover occurs.

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

Rebooting devices immediately at the CLI

Execute one of the following commands as appropriate in user view:

 

Task	Command
Reboot a member device, an interface card, or all IRF member devices.	reboot [ slot slot-number [ subslot subslot-number ] ] [ force ]

 

Scheduling a device reboot

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

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

 

Task	Command	Remarks
Specify the reboot date and time.	scheduler reboot at time [ date ]	By default, no reboot date or time is specified.
Specify the reboot delay time.	scheduler reboot delay time	By default, no reboot delay time is specified.

 

Scheduling a task

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

You can configure a non-periodic schedule or a 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.

Configuration guidelines

When you schedule a task, follow these guidelines:

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

Configuration procedure

To configure a non-periodic schedule for the device:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Create a job.	scheduler job job-name	By default, no job exists.
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 will be executed first. 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.
4.      Exit to system view.	quit	N/A
5.      Create a schedule.	scheduler schedule schedule-name	By default, no schedule exists.
6.      Assign a job to a 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 up to 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 an execution time table for the non-periodic schedule.	·          Specify the execution date and time: time at time date ·          Specify the execution days and time: time once at time [ month-date month-day | week-day week-day&<1-7> ] ·          Specify the execution delay time: time once delay time	By default, no execution time is specified for a schedule. Executing commands clock datetime, clock summer-time, and clock timezone does not change the execution time table that is already configured for a schedule.

 

To configure a periodic schedule for the device:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Create a job.	scheduler job job-name	By default, no job exists.
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 job with a smaller ID will be executed first. 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.
4.      Exit to system view.	quit	N/A
5.      Create a schedule.	scheduler schedule schedule-name	By default, no schedule exists.
6.      Assign a job to a 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 up to 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 an execution time table for the periodic schedule.	·          Execute the schedule at an interval from the specified time on: time repeating at time [ month-date [ month-day | last ] | week-day week-day&<1-7> ] ·          Execute the schedule at the specified time on every specified day in a month or week: time repeating [ at time [date ] ] interval interval-time	By default, no execution time is specified for a schedule. Executing commands clock datetime, clock summer-time, and clock timezone does not change the execution time table that is already configured for a schedule.

 

Schedule configuration example

Network requirements

As shown in Figure 1, 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 1 Network diagram

 

Scheduling procedure

# Enter system view.

<Sysname> system-view

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

[Sysname] scheduler job shutdown-Ten-GigabitEthernet1/1/1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Sysname-schedule- STOP-pc1/pc2] job shutdown-Ten-GigabitEthernet1/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 scheduling

# Display the configuration information of all jobs.

[Sysname] display scheduler job

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

 system-view

 interface ten-gigabitethernet 1/1/1

 shutdown

 

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

 system-view

 interface Ten-gigabitethernet 1/1/2

 shutdown

 

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

 system-view

 interface Ten-gigabitEthernet 1/1/1

 undo shutdown

 

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

 system-view

 interface ten-gigabitethernet 1/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-Ten-GigabitEthernet1/1/1                                 Successful

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

shutdown-Ten-GigabitEthernet1/1/2                              Successful

# Display schedule log information.

[Sysname] display scheduler logfile

Job name        : start-Ten-GigabitEthernet1/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 ten-gigabitethernet 1/1/1

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

 

Job name        : start-Ten-GigabitEthernet1/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 ten-gigabitethernet 1/1/2.

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

 

Job name        : shutdown-Ten-GigabitEthernet1/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 ten-gigabitethernet 1/1/1

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

 

Job name        : shutdown-Ten-GigabitEthernet1/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 ten-gigabitethernet 1/1/2

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

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

To set the port status detection timer:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Set the port status detection timer.	shutdown-interval time	The default setting is 30 seconds.

 

Monitoring CPU usage

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

·           Samples CPU usage at an interval of 1 minute, and compares the sample with the CPU usage threshold. If the sample is greater, the device sends a trap.

·           Samples and saves CPU usage at a configurable interval if CPU usage tracking is enabled.

To monitor CPU usage:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Set the CPU usage threshold.	monitor cpu-usage threshold cpu-threshold [ slot slot-number [ cpu cpu-number ] ]	The default CPU usage threshold is 99%.
3.      Enable CPU usage tracking.	monitor cpu-usage enable [ slot slot-number [ cpu cpu-number ] ]	By default, CPU usage tracking is enabled.
4.      Set the sampling interval for CPU usage tracking.	monitor cpu-usage interval interval-value [ slot slot-number [ cpu cpu-number ] ]	By default, the sampling interval for CPU usage tracking is 1 minute.
5.      Exit to user view.	quit	N/A
6.      Display CPU usage statistics.	display cpu-usage [ slot slot-number [ cpu cpu-number ] ]	This command is available in any view.
7.      Display CPU usage monitoring settings.	display cpu-usage configuration [ slot slot-number [ cpu cpu-number ] ]	This command is available in any view.
8.      Display the historical CPU usage statistics in a coordinate system.	display cpu-usage history [ job job-id ] [ slot slot-number [ cpu cpu-number ] ]	This command is available in any view.

 

Setting memory alarm thresholds

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

·           Samples memory usage at an interval of 1 minute, 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 a free-memory threshold is exceeded, the system generates an alarm notification or an alarm-removed notification and sends it to affected service modules or processes.

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 notification and alarm-removed notification

 

 

To set memory alarm thresholds:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Set the memory usage threshold.	memory-threshold [ slot slot-number [ cpu cpu-number ] ] usage memory-threshold	The default memory usage threshold is 100%.
3.      Set the free-memory thresholds.	memory-threshold [ 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.

 

Configuring the 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 temperature drops below the low-temperature threshold or reaches the high-temperature warning threshold, the device sends a log message and a trap.

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

To configure the temperature alarm thresholds:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Configure the temperature alarm thresholds.	temperature-limit slot slot-number hotspot sensor-number lowlimit warninglimit [ alarmlimit ]	To view the default thresholds, use the undo form of the 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. The high-temperature warning threshold must be higher than the low-temperature threshold.

 

Configuring hardware failure detection and protection

The device can automatically detect its hardware failures and take actions in response.

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

·           isolate—Shuts down the relevant ports to reduce impact from the failures.

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

·           warning—Sends traps to report the failures.

To configure hardware failure detection and protection:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
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.

 

Setting the table capacity mode

The device supports multiple table capacity modes. The capacities of the MAC address table and routing tables vary by table capacity mode.

Table 2 lists the feature highlights and application scenarios of table capacity modes.

Table 2 Table capacity modes

Table capacity mode	Feature highlights	Recommended application scenario
bridging	Increases the MAC address table size to provide higher Layer 2 packet forwarding performance.	A large MAC address table is required.
routing	Increases the IPv4 and IPv6 routing table size to provide higher Layer 3 packet forwarding performance.	A large routing table is required.
mix-bridging-routing	Increases both the MAC address table size and routing table size.	Both a large MAC address table and a large routing table are required.

 

To set the table capacity mode:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Set the table capacity mode.	switch-mode { bridging | mix-bridging-routing | routing }	The default table capacity mode is mix-bridging-routing. A table capacity mode change takes effect after a reboot. Before rebooting the switch, make sure you know the possible impact on the network.

 

Specifying the preferred airflow direction

	IMPORTANT: This feature is available only for parent devices and the following PEXs: ·       S5120-28SC-HI switches. ·       S5130-EI switches. ·       S6300 switches.

 

The device supports the following airflow directions:

·           From the port side to the power side.

·           From the power side to the port side.

Select the correct fan tray model and set the preferred airflow direction to the airflow direction of the ventilation system in the equipment room. If a fan tray is not operating correctly or has a different airflow direction than the configured one, the system sends logs.

To specify the preferred airflow direction:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Specify the preferred airflow direction.	fan prefer-direction slot slot-number { power-to-port | port-to-power }	The default preferred airflow direction is from the power side to the port side.

 

Verifying and diagnosing transceiver modules

Verifying transceiver modules

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 is written to the storage component during debugging or testing.

Install only transceiver modules that are from H3C or HP. If you install a transceiver module that is not from H3C or HP, the device will generate a log message to ask you to replace the module. For more information about log messages, see information center configuration in Network Management and Monitoring Configuration Guide.

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

 

Task	Command	Remarks
Display the key parameters of transceiver modules.	display transceiver { interface [ interface-type interface-number ] }	N/A
Display the electrical label information of transceiver modules.	display transceiver manuinfo interface [ interface-type interface-number ] }	This command cannot display information for some transceiver modules.

 

Diagnosing transceiver modules

The device provides the alarm and digital diagnosis features 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 feature, including the temperature, voltage, laser bias current, TX power, and RX power.

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

 

Task	Command	Remarks
Display transceiver alarms.	display transceiver alarm { interface [ interface-type interface-number ] }	N/A
Display the current values of the digital diagnosis parameters on transceiver modules.	display transceiver diagnosis { interface [ interface-type interface-number ] }	This command cannot display information about some transceiver modules.

 

Disabling alarm traps for transceiver modules

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

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

To disable alarm traps for transceiver modules:

 

Step	Command	Remarks
1.      Enter system view.	system-view	N/A
2.      Disable alarm traps for transceiver modules.	transceiver phony-alarm-disable	By default, alarm traps are enabled for transceiver modules.

 

Restoring the factory-default configuration

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

 

This feature performs the following tasks:

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

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

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

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

·           Deletes all license files (.ak files).

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

To restore the factory-default configuration for the device, execute the following command in user view:

 

Task	Command	Remarks
Restore the factory-default configuration for the device.	restore factory-default	This command takes effect after a device reboot.

 

Displaying and maintaining device management configuration

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 the system time, date, local time zone, and daylight saving time.	display clock
Display the copyright statement.	display copyright
Display CPU usage statistics.	display cpu-usage [ slot slot-number [ cpu cpu-number ] ]
Display CPU usage monitoring settings.	display cpu-usage configuration [ slot slot-number [ cpu cpu-number ] ]
Display historical CPU usage statistics in a chart.	display cpu-usage history [ job job-id ] [ slot slot-number [ cpu cpu-number ] ]
Display hardware information.	display device [ flash | usb ] [ slot slot-number [ subslot subslot-number ] | verbose ]
Display the electronic label information of the device.	display device manuinfo [ slot slot-number [ subslot subslot-number ] ]
Display the electronic label information of a fan.	display device manuinfo slot slot-number fan fan-id
Display the electronic label information of a power module.	display device manuinfo slot slot-number power power-id
Display or save device diagnostic information.	display diagnostic-information [ hardware | infrastructure | l2 | l3 | service ] [ filename ]
Display device temperature statistics.	display environment [ slot slot-number ]
Display the operating states of fans.	display fan [ slot slot-number [ fan-id ] ]
Display memory usage statistics.	display memory [ 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 ] ]
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 stability and status information.	display system stable state
Display table capacity mode information.	display switch-mode status
Display the current system working mode.	display system-working-mode
Display system version information.	display version
Display the startup software image upgrade history records for the master device.	display version-update-record
Clear the startup software image upgrade history records for the master device.	reset version-update-record
Clear job execution log information.	reset scheduler logfile