Contents

Managing the device· 1

Device management task list 1

Configuring the device name· 1

Configuring the system time· 2

Enabling displaying the copyright statement 3

Configuring banners· 4

Banner types· 4

Banner input methods· 4

Configuration procedure· 5

Rebooting the device· 6

Rebooting devices immediately at the CLI 6

Scheduling a device reboot 6

Scheduling a task· 7

Configuration restrictions and guidelines· 7

Configuration procedure· 7

Schedule configuration example· 9

Disabling password recovery capability· 12

Setting the port status detection timer 12

Monitoring CPU usage· 13

Setting memory alarm thresholds· 13

Configuring the temperature alarm thresholds· 15

Verifying and diagnosing transceiver modules· 16

Verifying transceiver modules· 17

Diagnosing transceiver modules· 18

Restoring the factory-default configuration· 18

Displaying and maintaining device management configuration· 18

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.

The WX1800H series, WX2500H series, and WX3000H series access controllers do not support the slot keyword or the slot-number argument.

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
(Optional.) Rebooting the device
(Optional.) Scheduling a task
(Optional.) Disabling password recovery capability
(Optional.) Setting the port status detection timer
(Optional.) Monitoring CPU usage
(Required.) Setting memory alarm thresholds
(Required.) Configuring the temperature alarm thresholds
(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 device can use the locally set system time, or obtain the UTC time from an NTP source and calculate the system time.

·     When using the locally set system time, the device uses the clock signals generated by its built-in crystal oscillator to maintain the system time.

·     After obtaining the UTC time from an NTP source, the device uses the UTC time, time zone, and daylight saving time to calculate the system time. Then, the device periodically synchronizes its UTC time and recalculates the system time. For more information about NTP, see Network Management and Monitoring Configuration Guide.

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

To configure the device to use the local system time:

 

Step	Command	Remarks
1.     Enter system view.	system-view	N/A
2.     Specify the system time source.	clock protocol none	By default, the device uses the NTP time source. If you execute the clock protocol command multiple times, the most recent configuration takes effect.
3.     Return to user view.	quit	N/A
4.     Set the local system time.	clock datetime time date	N/A
5.     Enter system view.	system-view	N/A
6.     Set the time zone.	clock timezone zone-name { add | minus } zone-offset	By default, the system uses the UTC time zone. This setting must be consistent with the time zone of the place where the device resides. After a time zone change, the device recalculates the system time. To view the system time, use the display clock command.
7.     (Optional.) 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. After you set the daylight saving time, the device recalculates the system time. To view the system time, use the display clock command.

 

To configure the device to obtain the UTC time from a time source and calculate the system time:

 

Step	Command	Remarks
1.     Enter system view.	system-view	N/A
2.     Specify the system time source.	clock protocol ntp	By default, the device uses the NTP time source. If you execute the clock protocol command multiple times, the most recent configuration takes effect.
3.     Set the time zone.	clock timezone zone-name { add | minus } zone-offset	By default, the system uses the UTC time zone. This setting must be consistent with the time zone of the place where the device resides. After you set the time zone, the device recalculates the system time. To view the system time, use the display clock command.
4.     (Optional.) 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. After you set the daylight saving time, the device recalculates the system time. To view the system time, use the display clock command.

 

Enabling displaying the copyright statement

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.

The following is a sample copyright statement:

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

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

* Without the owner's prior written consent,                                 * 

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

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

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 function 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—Appears for modem users.

·     Shell banner—Appears for non-modem users.

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 entire command line, including the command keywords, the banner, and the delimiters, can have up to 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 and the delimiters can have up to 2002 characters. 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 %.

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.

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.

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

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, no legal banner is configured.
3.     Configure the MOTD banner.	header motd text	By default, no MOTD banner is configured.
4.     Configure the login banner.	header login text	By default, no login banner is configured.
5.     Configure the incoming banner.	header incoming text	By default, no incoming banner is configured.
6.     Configure the shell banner.	header shell text	By default, no shell banner is configured.

 

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:

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

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

Rebooting devices immediately at the CLI

Execute the following command in user view:

 

Task	Command
Reboot an IRF member device or all IRF member devices.	reboot [ slot slot-number ] [ force ]

 

Scheduling a device reboot

When you schedule a reboot, follow these guidelines:

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

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

To schedule a reboot, execute one 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 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.

Configuration restrictions and guidelines

When you schedule a task, follow these restrictions and guidelines:

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

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

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. A command with a smaller ID is executed first.
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. The security-audit role is mutually exclusive with any other user roles. Assigning the security-audit role removes existing user role assignments. Assigning any other user roles removes the security-audit role assignment.
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. A job with a smaller ID is executed first.
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, the PC accesses the AC through the AP. The AC acts as the DHCP server to assign IP addresses to the AP and PC. The AP is connected to the AC through Radio 1.

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

·     Enable Radio 1 at 8:00 a.m. every day.

·     Disable Radio 1 at 20:00 every day.

Figure 1 Network diagram

 

Scheduling procedure

This section describes only the scheduling procedure. For information about wireless access configuration, see WLAN Configuration Guide.

# Enter system view.

<AC> system-view

# Configure a job for disabling Radio 1.

[AC] scheduler job radio_disable

[AC-job-radio_disable] command 1 system-view

[AC-job-radio_disable] command 2 wlan ap ap1 model WA4320i-ACN

[AC-job-radio_disable] command 3 radio 1

[AC-job-radio_disable] command 4 radio disable

[AC-job-radio_disable] quit

# Configure a periodic schedule for disabling Radio 1 at 20:00 every day.

[AC] scheduler schedule stop_radio

[AC-schedule-stop_radio] job radio_disable

[AC-schedule-stop_radio] time repeating at 20:00

[AC-schedule-stop_radio] quit

# Configure a job for enabling Radio 1.

[AC] scheduler job radio_enable

[AC-job-radio_enable] command 1 system-view

[AC-job-radio_enable] command 2 wlan ap ap1 model WA4320i-ACN

[AC-job-radio_enable] command 3 radio 1

[AC-job-radio_enable] command 4 radio enable

[AC-job-radio_enable] quit

# Configure a periodic schedule for enabling Radio 1 at 8:00 a.m. every day.

[AC] scheduler schedule start_radio

[AC-schedule-start_radio] job radio_enable

[AC-schedule-start_radio] time repeating at 8:00

[AC-schedule-start_radio] quit

 Verifying the scheduling

# Display information about the AP. Verify that the value of the Admin State field is up from 8:00 to 20:00 and down outside of the time range.

[AC] display wlan ap name ap1 verbose

AP name                       : ap1

AP ID                         : 1

AP group name                 : default-group

State                         : Run

Backup Type                   : NULL

Online time                   : 0 days 2 hours 18 minutes 10 seconds

System up time                : 0 days 2 hours 19 minutes 11 seconds

Model                         : WA4320i-ACN

Region code                   : CN

Region code lock              : Disable

Serial ID                     : 210235A1BSC123000050

MAC address                   : 586a-b1fb-e2c0

IP address                    : 100.1.0.1

H/W version                   : Ver.C

S/W version                   : V700R001B64D003

Boot version                  : 7.01

Description                   : Not configured

Priority                      : 4

Echo interval                 : 10 seconds

Statistics report interval    : 50 seconds

Jumbo frame value             : 1500

MAC type                      : Local MAC & Split MAC

Tunnel mode                   : Local Bridging & 802.3 Frame & Native Frame

Discovery type                : Unknown

Retransmission count          : 3

Retransmission interval       : 5 seconds

Firmware upgrade              : Enabled

Sent control packets          : 3159

Received control packets      : 3159

Connection count              : 1

Backup Ipv4                   : Not configured

Backup Ipv6                   : Not configured

Tunnel encryption             : Disabled

LED mode                      : Normal

Radio 1:

    Basic BSSID               : 586a-b1fb-e2c0

    Admin state               : Up

    Radio type                : 802.11ac

    Antenna type              : internal

    Client dot11ac-only       : Disabled

    Client dot11n-only        : Disabled

    Channel band-width        : 20/40/80MHz

    Secondary channel offset  : SCA

    Short GI for 20MHz        : Supported

    Short GI for 40MHz        : Supported

    Short GI for 80MHz        : Supported

    Short GI for 160MHz       : Not supported

    A-MSDU                    : Enabled

    A-MPDU                    : Enabled

    LDPC                      : Not Supported

    STBC                      : Supported

    Operational VHT-MCS Set:

        Mandatory             : Not configured

        Supported             : NSS1 0,1,2,3,4,5,6,7,8,9

                                NSS2 0,1,2,3,4,5,6,7,8,9

        Multicast             : Not configured

    Operational HT MCS Set:

        Mandatory             : Not configured

        Supported             : 0, 1, 2, 3, 4, 5, 6, 7, 8, 9,

                                10, 11, 12, 13, 14, 15

        Multicast             : Not configured

    Channel                   : 149

    Max power                 : 20 dBm

    Operational rate:

        Mandatory             : 6, 12, 24 Mbps

        Multicast             : Auto

        Supported             : 9, 18, 36, 48, 54 Mbps

        Disabled              : Not configured

    Distance                  : 1 km

    ANI                       : Enabled

    Fragmentation threshold   : 2346 bytes

    Beacon interval           : 100 TU

    Protection threshold      : 2346 bytes

    Long retry threshold      : 4

    Short retry threshold     : 7

    Maximum rx duration       : 2000 ms

    Noise floor               : -102 dBm

Disabling password recovery capability

Password recovery capability controls console user access to the device configuration and SDRAM from Boot ROM menus. For more information about Boot ROM 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.

To disable password recovery capability:

 

Step	Command	Remarks
1.     Enter system view.	system-view	N/A
2.     Disable password recovery capability.	undo password-recovery enable	By default, password recovery capability is enabled.

 

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

When monitoring the 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.     Enable CPU usage tracking.	monitor cpu-usage enable [ slot slot-number ]	By default, CPU usage tracking is enabled.
3.     Set the sampling interval for CPU usage tracking.	monitor cpu-usage interval interval-value [ slot slot-number ]	By default, the sampling interval for CPU usage tracking is 1 minute.
4.     Set the CPU usage threshold.	monitor cpu-usage threshold cpu-threshold [ slot slot-number ]	By default, the CPU usage threshold is 99%.
5.     Exit to user view.	quit	N/A
6.     Display CPU usage statistics.	display cpu-usage [ summary ] [ slot slot-number ]	This command is available in any view.
7.     Display CPU usage monitoring settings.	display cpu-usage configuration [ slot slot-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 ]	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 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.

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

 

 

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 ] usage memory-threshold	By default, the memory usage threshold is 100%.
3.     Set the free-memory thresholds.	memory-threshold [ slot slot-number ] minor minor-value severe severe-value critical critical-value normal normal-value	For information about the default settings, see Fundamentals Command Reference.

 

Configuring the temperature alarm thresholds

The following matrix shows the feature and hardware compatibility:

 

Hardware series	Model	Temperature alarm compatibility
WX1800H series	WX1804H WX1810H WX1820H	Yes
WX2500H series	WX2510H WX2560H	Yes
	WX2540H	No
WX3000H series	WX3010H WX3010H-L WX3010H-X WX3024H WX3024H-L	Yes
WX3500H series	WX3508H WX3510H WX3520H WX3540H	Yes
WX5500E series	WX5510E WX5540E	Yes
WX5500H series	WX5540H WX5560H WX5580H	Yes
Access controller modules	EWPXM1MAC0F EWPXM1WCME0 EWPXM2WCMD0F LSQM1WCMX20 LSQM1WCMX40 LSUM1WCME0 LSUM1WCMX20RT LSUM1WCMX40RT	Yes

 

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 or alarming threshold, the device performs the following operations:

·     Sends log messages and traps.

·     Sets LEDs on the device panel.

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 | inflow } sensor-number lowlimit warninglimit [ alarmlimit ]	The defaults vary by temperature sensor model. To view the defaults, use the undo temperature-limit command to restore the defaults and then 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.

 

Verifying and diagnosing transceiver modules

The following matrix shows the feature and hardware compatibility:

 

Hardware series	Model	Feature compatibility
WX1800H series	WX1804H WX1810H WX1820H	No
WX2500H series	WX2510H	No
	WX2540H WX2560H	Yes
WX3000H series	WX3010H WX3010H-L WX3010H-X WX3024H WX3024H-L	Yes
WX3500H series	WX3508H WX3510H WX3520H WX3540H	Yes
WX5500E series	WX5510E WX5540E	Yes
WX5500H series	WX5540H WX5560H WX5580H	Yes
Access controller modules	EWPXM1MAC0F EWPXM1WCME0 EWPXM2WCMD0F LSQM1WCMX20 LSQM1WCMX40 LSUM1WCME0 LSUM1WCMX20RT LSUM1WCMX40RT	No

 

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. If you install a transceiver module that is not from H3C, the device will generate a log message to prompt 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 alarming 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.

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.

 

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.

 

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 command in user 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 [ summary ] [ slot slot-number ]
Display historical CPU usage statistics in a chart.	display cpu-usage history [ job job-id ] [ slot slot-number ]
Display hardware information.	display device [ cf-card ] [ slot slot-number | verbose ]
Display electronic label information for the device.	display device manuinfo [ slot slot-number ]
Display electronic label information for a fan.	display device manuinfo slot slot-number fan fan-id
Display electronic label information for a power supply.	display device manuinfo slot slot-number power power-id
Display or save device diagnostic information.	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 fans.	display fan [ slot slot-number [ fan-id ] ]
Display memory usage statistics.	display memory [ summary ] [ slot slot-number ]
Display memory alarm thresholds and statistics.	display memory-threshold [ slot slot-number ]
Display power supply information.	display power [ 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 system version information.	display version
Clear job execution log information.	reset scheduler logfile