Login
- Table of Contents
-
- 01-Fundamentals Configuration Guide
- 00-Preface
- 01-CLI Configuration
- 02-Login Management Configuration
- 03-FTP and TFTP Configuration
- 04-File System Management
- 05-Configuration File Management Configuration
- 06-Software Upgrade Configuration
- 07-ISSU Configuration
- 08-Device Management Configuration
- 09-Automatic Configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 08-Device Management Configuration | 260.6 KB |
Contents
Changing and displaying the system time
Enabling displaying the copyright statement
Configuring the exception handling method
Configuring the system working mode·
Scheduling a job in the non-modular approach
Scheduling a job in the modular approach·
Scheduled job configuration example
Configuring a detection interval
Configuring temperature thresholds for a card
Isolating and diagnosing a card
Configuring in-service hardware failure diagnosis and failure protection
Configuring the load mode for the active MPU and the standby MPU
Configuring the size of the buffer shared by all interfaces on a service card
Configuring automatic speed adjustment mode for fans
Clearing unused 16-bit interface indexes
Enabling automatic forwarding path check
Verifying and diagnosing transceiver modules
Introduction to transceiver modules
Diagnosing transceiver modules
Displaying and maintaining device management
Device management includes monitoring the operating status of devices and configuring their running parameters.
|
|
NOTE: · The switch operates in IRF or standalone (the default) mode. For more information about the IRF mode, see IRF Configuration Guide. · Storage media include Flash, compact Flash (CF), and universal serial bus (USB). Flash is exemplified in this document. · The configuration tasks in this document are all optional and independent from one another. |
Configuring the device name
A device name identifies a device in a network and works as the user view prompt at the CLI. 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 |
Optional. By default, the device name is H3C. |
Changing and displaying the system time
Changing the system time
The system time, displayed by system time stamp, is determined by the configured relative time, time zone, and daylight saving time. To view the system time, use the display clock command. The system time should be precise to make sure that the switch can work with other devices.
To configure the system time:
|
Step |
Command |
Remarks |
|
1. Set the time and date. |
clock datetime time date |
Optional. Available in user view. |
|
2. Enter system view. |
system-view |
N/A |
|
3. Set the time zone. |
clock timezone zone-name { add | minus } zone-offset |
Optional. Universal time coordinated (UTC) time zone by default. |
|
4. Set a daylight saving time scheme. |
·
Set a non-recurring scheme: ·
Set a recurring scheme: |
Optional. Use either command. By default, daylight saving time is disabled and the UTC time zone applies. |
Displaying the system time
The system time is determined by the commands clock datetime, clock timezone and clock summer-time. If these three commands are not configured, the display clock command displays the original system time. If you combine these three commands in different ways, the system time is displayed in the ways as shown in Table 1. The following describes the parameters in the configuration column:
· 1 indicates date-time has been configured with the clock datetime command.
· 2 indicates time-zone has been configured with the clock timezone command and the offset time is zone-offset.
· 3 indicates daylight saving time has been configured with the clock summer-time command and the offset time is summer-offset.
· [1] indicates the clock datetime command is an optional configuration, which can be either executed or not executed.
· The default system time is 2005/1/1 1:00:00 in the example.
Table 1 System time configuration
|
Configuration |
System time configured |
Example |
|
1 |
date-time |
Configure: clock datetime 1:00 2007/1/1 System time configured: 01:00:00 UTC Mon 01/01/2007 |
|
2 |
The original system time ± “zone-offset” |
Configure: clock timezone zone-time add 1 System time configured: 02:00:00 zone-time Sat 01/01/2005 |
|
1 and 2 |
date-time ± zone-offset |
Configure: clock datetime 2:00 2007/2/2 and clock timezone zone-time add 1 System time configured: 03:00:00 zone-time Fri 02/02/2007 |
|
[1], 2 and 1 |
date-time |
Configure: clock timezone zone-time add 1 and clock datetime 3:00 2007/3/3 System time configured: 03:00:00 zone-time Sat 03/03/2007 |
|
3 |
If the original system time is not in the daylight saving time range, the system time configured is the original system time. |
Configure: clock summer-time ss one-off 1:00 2006/1/1 1:00 2006/8/8 2 System time configured: 01:00:00 UTC Sat 01/01/2005 |
|
If the original system time is in the daylight saving time range, the system time configured is the original system time + “summer-offset”. |
Configure: clock summer-time ss one-off 00:30 2005/1/1 1:00 2005/8/8 2 System time configured: 03:00:00 ss Sat 01/01/2005 If the original system time + “summer-offset” is not in the daylight saving time range, the system time configured is the original system time. After this configuration, if you disable the daylight saving, the system time becomes the system time minus “summer-offset”. |
|
|
1 and 3 |
If “date-time” is not in the daylight saving time range, the system time configured is “date-time”. |
Configure: clock datetime 1:00 2007/1/1 and clock summer-time ss one-off 1:00 2006/1/1 1:00 2006/8/8 2 System time configured: 01:00:00 UTC Mon 01/01/2007 |
|
If “date-time” is in the daylight saving time range, the system time configured is “date-time” + “summer-offset”. |
Configure: clock datetime 8:00 2007/1/1 and clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 System time configured: 10:00:00 ss Mon 01/01/2007 If “date-time” + “summer-offset” is not in the daylight saving time range, the system time configured is “date-time”. After this configuration, if you disable the daylight saving, the system time becomes the system time minus “summer-offset”. |
|
|
[1], 3 and 1 |
If “date-time” is not in the daylight saving time range, the system time configured is “date-time”. |
Configure: clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 and clock datetime 1:00 2008/1/1 System time configured: 01:00:00 UTC Tue 01/01/2008 |
|
“date-time” is in the daylight saving time range: If the value of “date-time”
- “summer-offset” is not in the summer-time range, the
system time configured is “date-time” - “summer-offset”; |
Configure: clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 and clock datetime 1:30 2007/1/1 System time configured: 23:30:00 UTC Sun 12/31/2006 |
|
|
Configure: clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 and clock datetime 3:00 2007/1/1 System time configured: 03:00:00 ss Mon 01/01/2007 |
||
|
2 and 3 or 3 and 2 |
If the value of the original system time ± “zone-offset” is not in the summer-time range, the system time configured is the original system time ± “zone-offset”. |
Configure: clock timezone zone-time add 1 and clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 System time configured: 02:00:00 zone-time Sat 01/01/2005 |
|
If the value of the original system time ± “zone-offset” is in the summer-time range, the system time configured is the original system time ± “zone-offset” + “summer-offset”. |
Configure: clock timezone zone-time add 1 and clock summer-time ss one-off 1:00 2005/1/1 1:00 2005/8/8 2 System time configured: 04:00:00 ss Sat 01/01/2005 |
|
|
1, 2 and 3 or 1, 3 and 2 |
If the value of “date-time”±”zone-offset” is not in the summer-time range, the system time configured is “date-time”±”zone-offset”. |
Configure: clock datetime 1:00 2007/1/1, clock timezone zone-time add 1 and clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 System time configured: 02:00:00 zone-time Mon 01/01/2007 |
|
If the value of “date-time”±”zone-offset” is in the summer-time range, the system time configured is “date-time”±”zone-offset”+”summer-offset”. |
Configure: clock datetime 1:00 2007/1/1, clock timezone zone-time add 1 and clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 System time configured: 04:00:00 ss Mon 01/01/2007 |
|
|
[1], 2, 3 and 1 or [1], 3, 2 and 1 |
If “date-time” is not in the daylight saving time range, the system time configured is “date-time”. |
Configure: clock timezone zone-time add 1, clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 and clock datetime 1:00 2007/1/1 System time configured: 01:00:00 zone-time Mon 01/01/2007 |
|
“date-time” is in the daylight saving time range: If the value of “date-time”-”summer-offset”
is not in the summer-time range, the system time configured is “date-time”-”summer-offset”; |
Configure: clock timezone zone-time add 1, clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 and clock datetime 1:30 2008/1/1 System time configured: 23:30:00 zone-time Mon 12/31/2007 |
|
|
Configure: clock timezone zone-time add 1, clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 and clock datetime 3:00 2008/1/1 System time configured: 03:00:00 ss Tue 01/01/2008 |
Enabling displaying the copyright statement
The device by default displays the copyright statement when a Telnet or SSH user logs in, or when a console user quits user view. You can disable or enable the function as needed. The following is a sample copyright statement:
**************************************************************************
* Copyright (c) 2004-2011 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 copyright statement. |
copyright-info enable |
Optional Enabled by default |
Configuring banners
Introduction to banners
Banners are messages that the system displays when a user connects to the device to perform login authentication, and start interactive configuration.
Banner types
The system supports the following types of banners:
· Legal banner appears after the system displays the copyright or license statement for a user attempting to log in. To continue authentication or 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 displays the greeting message, and appears after the legal banner and before the login banner. Support for this banner depends on the device model.
· Login banner appears only when password or scheme login authentication has been configured.
· Incoming banner appears for Modem dial-in users and the shell banner appears for users that use any other access method to access the CLI.
Message input modes
The system supports single-line input and multiple-line input for configuring a banner.
· Single-line input:
In single-line input mode, all banner information comes after the command keywords in the same line. The start and end characters of the input text must be the same but are not part of the banner information. The input text, together with the command keywords, cannot exceed 510 characters. In this mode, do not press Enter after typing the banner information. For example, to configure a banner like “Have a nice day.” use the following command:
<System> system-view
[System] header shell %Have a nice day.%
· Multiple-line input:
In multiple-line input mode, you can press Enter to separate the banner information in multiple lines. In this case, up to 2000 characters can be typed.
Use one of the following methods to implement multi-line input mode:
¡ Method I—Press the Enter key after the command keywords, type the banner information, and finish with the % character. The % character is not part of the banner information. For example, to configure a banner like “Have a nice day. Please input the Password.”, use the following commands:
<System> system-view
[System] header shell
Please input banner content, and quit with the character '%'.――System prompt
Have a nice day.
Please input the Password.%
¡ Method II—Type a character after the command keywords at the first line, and press Enter. Type the banner information, and finish with the character you typed at the first line. The start character and the end character are not part of the banner information. For example, to configure a banner like “Have a nice day. Please input the Password.”, use the following commands:
<System> system-view
[System] header shell A
Please input banner content, and quit with the character 'A'.――System prompt
Have a nice day.
Please input the Password.A
¡ Method III—Type multiple characters after the command keywords at the first line (with the first and last characters being different), and press the Enter key. Type the banner information, and finish with the first character you typed at the first line. The first input character at the first line and the end character are not part of the banner information. For example, to configure a banner like “Have a nice day. Please input the Password.”, use the following commands:
<System> system-view
[System] header shell AHave a nice day.
Please input banner content, and quit with the character 'A'.――System prompt
Please input the Password.A
Configuration procedure
To configure a banner:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Configure the incoming banner. |
header incoming text |
Optional |
|
3. Configure the login banner. |
header login text |
Optional |
|
4. Configure the legal banner. |
header legal text |
Optional |
|
5. Configure the shell banner. |
header shell text |
Optional |
|
6. Configure the MOTD banner. |
header motd text |
Optional |
Configuring the exception handling method
In standalone mode, when the system detects any software abnormality on the active main processing unit (MPU), it handles the situation with one of the following methods:
· reboot—The device automatically reboots the failed active MPU to recover from the error condition.
· maintain—The device stays in the error condition so you can collect complete data, including error messages, for diagnosis. In this approach, you must manually reboot the device.
To configure the exception handling method:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Configure the exception handling method of the MPUs. |
system-failure { maintain | reboot } |
Optional. By default, an MPU reboots when an exception occurs to it. |
|
|
NOTE: The system always reboots a line processing unit (LPU) or the auxiliary CPU system when an exception occurs to them. |
In IRF mode, when the system detects any software abnormality on the active MPU on an IRF member device, it handles the situation with one of the following two methods:
· reboot—The device automatically reboots the failed active MPU to recover from the error condition.
· maintain—The device stays in the error condition so you can collect complete data, including error messages, for diagnosis. In this approach, you must manually reboot the device.
To configure the exception handling method:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Configure the exception handling method of the MPUs. |
system-failure { maintain | reboot } |
By default, an MPU reboots when an exception occurs to it. |
|
|
NOTE: · The system always reboots an LPU or the auxiliary CPU system when an exception occurs to them. · The exception handling method is effective only for the failed card, and does not influence the functions of other cards or the IRF fabric. |
Rebooting the switch
You can reboot the switch in one of the following ways to recover from an error condition:
· Reboot the switch immediately at the CLI.
· At the CLI, schedule a reboot to occur at a specific time and date or after a delay.
· Power off and then re-power on the switch. This method might cause data loss and hardware damage, and is the least preferred method.
Reboot at the CLI enables easy remote device maintenance.
|
|
CAUTION: · Device reboot can interrupt network services. · To avoid data loss, use the save command to save the current configuration before a reboot. · Use the display startup and display boot-loader commands to check that you have correctly set the startup configuration file and the main system software image file. If the main system software image file has been corrupted or does not exist, the device cannot reboot. You must re-specify a main system software image file, or power off the device and then power it on so the system can reboot with the backup system software image file. |
To reboot a switch, perform one of these commands in user view:
|
Task |
Command |
Remarks |
|
Reboot a switch. |
·
Reboot a card, or the whole system immediately
(in standalone mode):
·
Reboot a card, a member switch, or the whole
system immediately (IRF mode): |
Use either command. |
To schedule a device reboot, perform one of the following commands in user view:
|
Task |
Command |
Remarks |
|
Schedule a reboot. |
·
Schedule a reboot to occur at a specific time
and date: ·
Schedule a reboot to occur after a delay: |
Use either approach. The scheduled reboot function is disabled by default. |
|
|
NOTE: · The system displays the alert “REBOOT IN ONE MINUTE” one minute before the reboot. · If the device has only one MPU, rebooting the MPU causes the device to reboot. If the device has two MPUs, rebooting the active MPU causes the active MPU to reboot and an active/standby switchover. You cannot use the reboot command to reboots a standby MPU. To reboot a standby MPU, use the slave restart command (see High Availability Command Reference). · For data security, if you are performing file operations at the reboot time, the system does not reboot. |
Configuring the system working mode
In different system working modes, the system adjusts the hardware resources to meet the requirements of different services. The switch has the following system working modes:
· advance—Advanced mode
· bridgee—Enhanced L2 mode
· routee—Enhanced L3 mode
· standard—Standard mode
· advance hybrid—Advanced hybrid mode
· bridgee hybrid—Enhanced L2 hybrid mode
· routee hybrid—Enhanced L3 hybrid mode
· standard hybrid—Standard hybrid mode
Among the working modes, advance hybrid, bridgee hybrid, routee hybrid, and standard hybrid can be called the hybrid mode.
To configure the system working mode:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Configure the system working mode. |
system working mode { { advance | bridgee | routee | standard } [ hybrid ] } |
By default, the system working mode is standard. |
|
|
NOTE: · H3C recommends you to restart the switch immediately to make this configuration take effect. · An IRF member switch cannot operate in hybrid mode; meanwhile, a switch operating in hybrid mode can operate in standalone mode instead of IRF mode. |
|
System working mode |
EB card |
EC card |
EF card |
Service base card |
OAA card |
|
standard |
Supported |
Supported |
Supported |
Not supported |
Supported |
|
bridgee |
Not supported |
Supported |
Supported |
Not supported |
Supported |
|
routee |
Not supported |
Supported |
Supported |
Not supported |
Supported |
|
advance |
Not supported |
Not supported |
Supported |
Not supported |
Not supported |
|
standard hybrid |
Supported |
Supported |
Supported |
Supported |
Supported |
|
bridgee hybrid |
Not supported |
Supported |
Supported |
Supported |
Supported |
|
routee hybrid |
Not supported |
Supported |
Supported |
Supported |
Supported |
|
advance hybrid |
Not supported |
Not supported |
Supported |
Supported |
Not supported |
|
|
NOTE: · An EB card has a silkscreen ended with EB, for example, LSR1GP48LEB1. An EC or EF card has a silkscreen ended with EC or EF. · A service base card refers to the card with the silkscreen LSR1LN1BNL1 or LSR1LN2BNL1. · For more information about OAA card models, see OAA Configuration Guide. |
The default values of some commands vary with system working modes. The following table illustrates the details.
|
Command |
Working mode and default value |
|||||||
|
standard |
bridgee |
routee |
advance |
standard hybrid |
bridgee hybrid |
routee hybrid |
advance hybrid |
|
|
multicast-vlan ipv6 entry-limit limit |
511 |
4095 |
4095 |
4095 |
511 |
1024 |
1024 |
1024 |
|
multicast-vlan entry-limit limit |
2047 |
4096 |
16384 |
30720 |
2047 |
4096 |
16384 |
16384 |
|
mac-table limit mac-limit-num |
Not supported |
131072 |
65536 |
131072 |
Not supported |
131072 |
65536 |
131072 |
|
multicast forwarding-table route-limit limit |
2047 |
4096 |
16384 |
30720 |
2047 |
4096 |
13824 |
13824 |
|
mld group-limit limit |
2048 |
8192 |
8192 |
8192 |
2048 |
8192 |
8192 |
8192 |
|
ip verify source max-entries number |
1536 |
7680 (without the acl ipv6 enable command) 3584 (with the acl ipv6 enable command) |
7680 (without the acl ipv6 enable command) 3584 (with the acl ipv6 enable command) |
32256 (without the acl ipv6 enable command) 15872 (with the acl ipv6 enable command) |
1536 |
7680 (without the acl ipv6 enable command) 3584 (with the acl ipv6 enable command) |
7680 (without the acl ipv6 enable command) 3584 (with the acl ipv6 enable command) |
32256 (without the acl ipv6 enable command) 15872 (with the acl ipv6 enable command) |
|
ip verify source max-entries number |
1536 |
3584 |
3584 |
15872 |
1536 |
3584 |
3584 |
15872 |
|
|
NOTE: The default parameters that do not vary with different system working modes are not listed in the above table. |
Scheduling jobs
You can schedule a job to automatically run a command or a set of commands without administrative interference. The commands in a job are polled every minute. When the scheduled time for a command is reached, the job automatically executes the command. If a confirmation is required while the command is running, the system automatically enters Y or Yes. If characters are required, the system automatically enters a default character string or an empty character string when no default character string is available.
Job configuration approaches
You can configure jobs in a non-modular or modular approach. Use the non-modular approach for a one-time command execution and use non-modular approach for complex maintenance work.
Table 2 A comparison of non-modular and modular approaches
|
Comparison item |
||
|
Configuration method |
Configure all elements in one command |
Separate job, view, and time settings |
|
Can multiple scheduled jobs be configured? |
No |
Yes |
|
Can a job contain multiple commands? |
No If you use the schedule job command repeatedly, only the last configuration takes effect. |
Yes You can use the time command in job view to configure commands to be executed at different time points. |
|
Supported views |
User view and system view. In the schedule job command, shell represents user view, and system represents system view. |
All views. In the time command, monitor represents user view. |
|
Supported commands |
Commands in user view and system view |
Commands in all views |
|
Can a job be repeatedly executed? |
No |
Yes |
|
Can a job be saved? |
No |
Yes |
|
Can a job be backed up to the standby MPUs? |
No |
Yes |
Configuration guidelines
· To have a job successfully run a command, check that the specified view and command are valid. The system does not verify their validity.
· The configuration interface, view, and user status that you have before job execution restores even if the job has run a command that changes the user interface (for example, telnet, ftp, and ssh2), the view (for example, system-view and quit), or the user status (for example, super).
· The jobs run in the background without displaying any messages except log, trap and debugging messages.
· In the modular approach:
¡ Every job can have only one view and up to 10 commands. If you specify multiple views, the one specified last takes effect.
¡ Input a view name in its complete form. Most commonly used view names include monitor for user view, system for system view, GigabitEthernetx/x/x for Ethernet interface view, and Vlan-interfacex for VLAN interface view.
¡ The time ID (time-id) must be unique in a job. If two time and command bindings have the same time ID, the one configured last takes effect.
Scheduling a job in the non-modular approach
To schedule a job, perform one of the following commands in user view:
|
Task |
Command |
Remarks |
|
Schedule a job. |
· Schedule a job to run a command at a specific time: · Schedule a job to run a command after a delay: |
Use either command. NOTE: · If you execute the schedule job command repeatedly, the last configuration takes effect. · Changing the system time can affect the execution time of the job set by the schedule job at command but not the schedule job delay command. |
Scheduling a job in the modular approach
To configure a scheduled job:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Create a job and enter job view. |
job job-name |
N/A |
|
3. Specify the view in which the commands in the job run. |
view view-name |
You can specify only one view for a job. The job executes all commands in the specified view. |
|
4. Add commands to the job. |
· Configure a command to run at a specific time and date: · Configure a command to run at a specific time: · Configure a command to run after a delay: |
Use any of the commands. NOTE: Changing the system time can affect the execution time of the job set by the time at command but not the time delay command. |
Scheduled job configuration example
Network requirements
Configure scheduled jobs on the device to enable interfaces GigabitEthernet 3/0/1, GigabitEthernet 3/0/2, and GigabitEthernet 3/0/3 at 8:00 and disabled them at 18:00 on working days every week, to control the access of the PCs connected to these interfaces.
Figure 1 Network diagram
Configuration procedure
# Enter system view.
<Sysname> system-view
# Create scheduled job pc1, and enter its view.
[Sysname] job pc1
# Configure the job to be executed in the view of GigabitEthernet 3/0/1.
[Sysname-job-pc1] view GigabitEthernet 3/0/1
# Configure the device to start GigabitEthernet 3/0/1 at 8:00 on working days every week.
[Sysname-job-pc1] time 1 repeating at 8:00 week-day mon tue wed thu fri command undo shutdown
# Configure the device to shut down GigabitEthernet 3/0/1 at 18:00 on working days every week.
[Sysname-job-pc1] time 2 repeating at 18:00 week-day mon tue wed thu fri command shutdown
[Sysname-job-pc1] quit
# Create scheduled job pc2, and enter its view.
[Sysname] job pc2
# Configure the job to be executed in the view of GigabitEthernet 3/0/2.
[Sysname-job-pc2] view GigabitEthernet 3/0/2
# Configure the device to start GigabitEthernet 3/0/2 at 8:00 on working days every week.
[Sysname-job-pc2] time 1 repeating at 8:00 week-day mon tue wed thu fri command undo shutdown
# Configure the device to shut down GigabitEthernet 3/0/2 at 18:00 on working days every week.
[Sysname-job-pc2] time 2 repeating at 18:00 week-day mon tue wed thu fri command shutdown
[Sysname-job-pc2] quit
# Create scheduled job pc3, and enter its view.
[Sysname] job pc3
# Configure the job to be executed in the view of GigabitEthernet 3/0/3.
[Sysname-job-pc3] view GigabitEthernet 3/0/3
# Configure the device to start GigabitEthernet 3/0/3 at 8:00 on working days every week.
[Sysname-job-pc3] time 1 repeating at 8:00 week-day mon tue wed thu fri command undo shutdown
# Configure the device to shut down GigabitEthernet 3/0/3 at 18:00 on working days every week.
[Sysname-job-pc3] time 2 repeating at 18:00 week-day mon tue wed thu fri command shutdown
[Sysname-job-pc3] quit
# Display information about scheduled jobs.
[Sysname] display job
Job name: pc1
Specified view: GigabitEthernet3/0/1
Time 1: Execute command undo shutdown at 08:00 Mondays Tuesdays Wednesdays Thursdays Fridays
Time 2: Execute command shutdown at 18:00 Mondays Tuesdays Wednesdays Thursdays Fridays
Job name: pc2
Specified view: GigabitEthernet3/0/2
Time 1: Execute command undo shutdown at 08:00 Mondays Tuesdays Wednesdays Thursdays Fridays
Time 2: Execute command shutdown at 18:00 Mondays Tuesdays Wednesdays Thursdays Fridays
Job name: pc3
Specified view: GigabitEthernet3/0/3
Time 1: Execute command undo shutdown at 08:00 Mondays Tuesdays Wednesdays Thursdays Fridays
Time 2: Execute command shutdown at 18:00 Mondays Tuesdays Wednesdays Thursdays Fridays
Configuring a detection interval
Some protocols may shut down ports under specific circumstances. For example, MSTP automatically shuts down a port that receives configuration messages after the BPDU guard function is enabled on the port. Then, the switch enables a detection timer and detects the status of the port. If the port is still down when the detection timer times out, the switch will automatically bring up the port.
To configure a detection interval:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Configure a detection interval. |
shutdown-interval time |
Optional 30 seconds by default |
Configuring temperature thresholds for a card
You can set the temperature threshold to monitor the temperature of a card.
The switch supports lower temperature threshold, warning temperature threshold, and alarming temperature threshold.
· When the card temperature drops below the lower temperature threshold, the device logs the event and outputs a log message and a trap.
· When the card temperature reaches the warning threshold, the device logs the event and outputs a log message and a trap.
· When the card temperature reaches the alarming threshold, the device logs the event and outputs a log message and a trap repeatedly, and alerts users through the LED on the device panel.
To configure temperature thresholds for a card:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Configure temperature thresholds for a card. |
·
In standalone mode: ·
In IRF mode: |
Optional. Use either command. |
Isolating and diagnosing a card
When the switch detects a card failure or upgrades the logic of the CPU daughter card on an LPU, you can isolate the faulty card or the CPU daughter card to prevent it from forwarding data packets. This operation allows for convenient on-site diagnosis or upgrading while causing no interference on the operation of the system and services of other cards.
After isolating a card, you can use the test diag-offline command to collect the diagnosis information of the card.
To isolate and diagnose a card:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Isolate a card. |
·
In standalone mode: ·
In IRF mode: |
Use either command. No card is isolated by default. |
|
3. Diagnose the card problem. |
·
In standalone mode: ·
In IRF mode: |
Use either command. The diagnosis information will be displayed and saved in logs under the root directory of the flash. Each log is named in the format of diag_slot_time, where slot indicates the location of the card and time indicates when the diagnosis operation is performed. |
|
|
CAUTION: · The active MPU cannot be isolated. If the standby MPU is isolated, the load mode of the active MPU becomes load-single. · Before upgrading the logic of an LPU, keep the LPU offline. · No other commands but the test diag-offline command can be executed for an isolated card. Otherwise, the configuration cannot take effect. |
|
|
NOTE: · You can use the display device command to view whether a card is isolated, that is, whether the card is in the offline state. · When you execute the test diag-offline command, the path where the diagnosis information is saved is also displayed following the diagnosis information on the terminal. For example, you can see flash:/diag_slot3_20080522_103458.txt. · H3C recommends you to send the diagnosis information to qualified engineers for analysis. |
Powering on/off a card
When the power supply is not sufficient, the switch automatically adjusts power supply to the cards according to a specific mechanism. You can also use the display power-supply command to view the power supply conditions of the cards, and power on or power off some cards to adjust the available power according to the actual network services.
To power on a card, perform one of these commands in user view:
|
Task |
Command |
Remarks |
|
Power on a card. |
· In standalone mode: · In IRF mode: |
Optional. Use either command. The specified card cannot be the MPU. |
To power off a card, perform one of these commands in user view:
|
Task |
Command |
Remarks |
|
Power off a card. |
· In standalone mode: · In IRF mode: |
Optional. Use either command. The specified card cannot be the MPU. |
Configuring in-service hardware failure diagnosis and failure protection
A hardware failure may cause traffic forwarding failures and service interruption. To improve the automatic failure detection and handling capabilities of the switch, you can configure in-service hardware failure diagnosis and failure protection.
The in-service hardware failure diagnosis and failure protection feature covers:
· In-service hardware failure detection for chips, cards, and the forwarding service, and automatic fix actions taken for the detected failures.
· Failure protection for ports. When a hardware failure is detected on a port, the switch automatically shuts down the port.
· Failure protection for aggregation groups. When a hardware failure is detected on a member port of an aggregation group, if the member port is not configured with the hardware-failure-protection auto-down command but it is not the last up port in the aggregation group, the port is shut down automatically; if the member port is not configured with the command and it is the last UP port in the aggregation group, the port will not be shut down; if the member port is configured with the command, the port is shut down automatically no matter whether it is the last UP port in the aggregation group.
|
|
NOTE: Because hardware failure protection is enabled on member ports of an aggregation group, use the undo hardware-failure-protection auto-down command to disable this feature for the member ports of all aggregation groups before you enable hardware failure protection for the aggregation groups. |
To configure in-service hardware failure diagnosis and failure protection:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Enable in-service hardware failure detection and configure fix actions taken in case of hardware failures.. |
hardware-failure-detection { chip | board | forwarding } { off | warning | reset | isolate } |
The fix actions taken in case of hardware failures include: · off—Takes no action. · warning—Sends warning messages. · reset—Resets the failed card. · isolate—Shuts down the failed port, isolates the failed card, prohibits the failed card from loaded, or powers off the failed card to reduce the impact of the failure to the system. By default, the fix action taken for all hardware failures is warning. |
|
3. Enable hardware failure protection for aggregation groups. |
hardware-failure-protection aggregation |
Optional. Disabled by default. This command is effective only when the fix action is configured as isolate. |
|
4. Enter Ethernet interface view. |
interface interface-type interface-number |
N/A |
|
5. Configure hardware failure protection for the port. |
hardware-failure-protection auto-down |
Optional. Enabled by default. This command is effective only when the fix action is configured as isolate. |
|
|
CAUTION: Before configuring the hardware-failure-protection auto-down command on a port, make sure that a backup link exists to avoid service interruption in case the port is shut down. |
The hardware-failure-protection aggregation and hardware-failure-protection auto-down command do not take effect on a port in either of the following cases:
· The port is configured with the loopback { external | internal } command.
· The port is configured with the port up-mode command.
· The port is configured as an IRF physical port.
|
|
NOTE: · If a port is automatically shut down due to hardware failure protection, its status displayed with the display interface command is Protect DOWN. To bring up the port, use the undo shutdown command on the port. · If a card is isolated or its software is not allowed to be loaded due to hardware failure fix operations, you can unplug the card and then plug it in to recover the card status. · After configuring in-service diagnosis and failure protection, you can use the display hardware-failure-detection command to check the running information of the feature. · For information about IRF physical ports, see IRF Configuration Guide. |
Configuring the load mode for the active MPU and the standby MPU
The following load modes are available for the active MPU and standby MPU:
· load-balance mode: Load ( for processing and forwarding packets) is balanced between the active MPU and standby MPU.
· load-single mode: The active MPU processes and forwards packets, whereas the standby MPU only backs up data and monitors the state of the active MPU.
To configure the load mode for the active MPU and standby MPU:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Configure the load mode. |
·
Configure the load mode for the active MPU and
standby MPU (in standalone mode): ·
Configure the load mode for the active MPUs
and standby MPUs on member devices (in IRF mode): |
Optional Use either command. load-balance mode by default |
|
|
NOTE: · The load-balance mode is valid only when both the active MPU and standby MPU are in their slots. If only the active MPU is available, the active MPU will automatically switch to the load-single mode after the load-balance mode is configured. · The models of the active MPU and standby MPU must be consistent; otherwise, the standby MPU cannot start normally. |
Configuring the size of the buffer shared by all interfaces on a service card
A service card uses a buffer with a fixed size to buffer the packets received and sent. A buffer comprises multiple storage units. It is divided into two areas: fixed buffer and shared buffer. The fixed buffer is allocated to the interfaces according to a certain algorithm, and the shared buffer is shared by all interfaces. When the traffic of an interface becomes heavy, and the fixed buffer cannot provide sufficient memory, the shared buffer provides temporary memory for the interface.
By default, the fixed buffer and the shared buffer contain a fixed number of storage units. You can configure the number of storage units in the shared buffer as needed. Because the total number of storage units in a buffer is fixed, the number of storage units in the fixed buffer will change after your configuration. You can tune the shared buffer area depending on traffic patterns. If transient large traffic bursts occur on some interfaces, you can expand the shared buffer to accommodate the bursts to prevent traffic loss. If transient small traffic bursts often occur on the interfaces, you can decrease the shared buffer so that each port can get more dedicated buffer memory.
To set the size in blocks of the receive or transmit buffer shared by all interfaces on a service card:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Set the size in blocks of the receive or transmit buffer shared by all interfaces on a service card. |
·
In standalone mode: ·
In IRF mode: |
Optional. By default, the size in blocks of the shared receive buffer is 1024, and that of the shared transmit buffer is 4608. |
Configuring automatic speed adjustment mode for fans
You can configure either of the following automatic speed adjustment modes for fans as required:
· Low temperature mode: In this mode, the fans operate at a high speed to ensure low temperature for the switch.
· Silent mode: In this mode, the fans operate at a low speed with low noise, but the temperature is a little higher than that in lower temperature mode. This mode is suitable for a noise-sensitive environment.
To configure the automatic speed adjustment mode, perform one of these commands in system view:
|
Task |
Command |
Remarks |
|
Configure the automatic speed adjustment mode. |
·
In standalone mode: ·
In IRF mode: |
Use either command. The switch operates in low temperature mode by default. |
Clearing unused 16-bit interface indexes
The device must maintain persistent 16-bit interface indexes and keep one interface index match one interface name for network management. After deleting a logical interface, the device retains its 16-bit interface index so the same index can be assigned to the interface at interface re-creation.
To avoid index depletion causing interface creation failures, you can clear all 16-bit indexes that have been assigned but not in use. The operation does not affect the interface indexes of the interfaces that have been created but the indexes assigned to re-recreated interfaces might change.
To clear unused 16-bit interface indexes:
|
Task |
Command |
Remarks |
|
Clear unused 16-bit interface indexes. |
reset unused porttag |
Available in user view |
|
|
CAUTION: A confirmation is required when you execute this command. If you fail to make a confirmation within 30 seconds or enter N to cancel the operation, the command is executed. |
Enabling automatic forwarding path check
When the switch is operating, traffic forwarding exceptions might occur due to hardware failures or other reasons. You can enable automatic forwarding path check so that the switch gives prompts when a forwarding exception occurs. According to the prompts, you can troubleshoot the problem.
To enable automatic forwarding path check:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Enable automatic forwarding path check. |
forward-path check { enable | disable } |
Enabled by default |
Above the configuration, if a forwarding exception occurs, the switch gives prompts, for example:
%Aug 20 14:55:54:973 2010 H3C DIAG/3/ERROR: -Slot=8; Forwarding fault: slot 5 to slot 8
%Aug 20 14:55:55:084 2010 H3C DIAG/3/ERROR: -Slot=6; Forwarding fault: slot 6 to slot 6
The output shows that a forwarding exception exists between the cards in slot 8 and slot 5, and an exception in internal data forwarding exists on the card in slot 6.
Verifying and diagnosing transceiver modules
Introduction to transceiver modules
Table 3 lists the commonly used transceiver modules. They can be further divided into optical transceivers and electrical transceivers based on transmission medium.
Table 3 Commonly used transceiver modules
|
Transceiver type |
Application environment |
Whether can be an optical transceiver |
Whether can be an electrical transceiver |
|
SFP (Small Form-factor Pluggable) |
Generally used for 100M/1000M Ethernet interfaces or POS 155M/622M/2.5G interfaces |
Yes |
Yes |
|
SFP+ (Enhanced 8.5 and 10 Gigabit Small Form-factor Pluggable) |
Generally used for 10G Ethernet interfaces |
Yes |
Yes |
|
XFP (10-Gigabit small Form-factor Pluggable) |
Generally used for 10G Ethernet interfaces |
Yes |
No |
Verifying transceiver modules
You can verify the genuineness of a transceiver module in the following ways:
· 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.
To identify transceiver modules:
|
Task |
Command |
Remarks |
|
Display key parameters of the transceiver modules. |
display transceiver interface [ interface-type interface-number ] [ | { begin | exclude | include } regular-expression ] |
Available for all transceiver modules |
|
Display transceiver modules’ electrical label information. |
display transceiver manuinfo interface [ interface-type interface-number ] [ | { begin | exclude | include } regular-expression ] |
Available for H3C customized transceiver modules only |
|
|
NOTE: If the Vendor Name field in the prompt information of the display transceiver command is H3C, it indicates that is the module is an H3C-customized transceiver module. |
Diagnosing transceiver modules
The device provides the alarm function and digital diagnosis function for transceiver modules. When a transceiver module fails or inappropriately work, you can check for alarms present on the transceiver module to identify the fault source or 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:
|
Task |
Command |
Remarks |
|
Display alarms present on transceiver modules. |
display transceiver alarm interface [ interface-type interface-number ] [ | { begin | exclude | include } regular-expression ] |
Available for all transceiver modules |
|
Display the present measured values of the digital diagnosis parameters for transceiver modules. |
display transceiver diagnosis interface [ interface-type interface-number ] [ | { begin | exclude | include } regular-expression ] |
Available for H3C customized transceiver modules only |
Displaying and maintaining device management
For diagnosis or troubleshooting, you can use separate display commands to collect running status data module by module, or use the display diagnostic-information command to bulk collect running data for multiple modules.
|
Task |
Command |
Remarks |
|
Display alarm information (standalone mode). |
display alarm [ slot slot-number ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display alarm information (IRF mode). |
display alarm [ chassis chassis-number slot slot-number ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the system version information. |
display version [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the system time information. |
display clock [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display clipboard information. |
display clipboard [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display or save statistics of the running status of multiple modules. |
display diagnostic-information [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the configuration of the shared buffer on a service card (standalone mode). |
display buffer-manage configuration [ slot slot-number ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the configuration of the shared buffer on a service card (IRF mode). |
display buffer-manage configuration [ chassis chassis-number slot slot-number ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the statistics of the CPU usage (standalone mode). |
display cpu-usage [ slot slot-number [ cpu cpu-number ] ] [ | { begin | exclude | include } regular-expression ] display cpu-usage entry-number [ offset ] [ verbose ] [ slot slot-number [ cpu cpu-number ] ] [ from-device ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the statistics of the CPU usage (IRF mode). |
display cpu-usage [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ | { begin | exclude | include } regular-expression ] display cpu-usage entry-number [ offset ] [ verbose ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ from-device ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display history statistics of the CPU usage in a chart (standalone mode). |
display cpu-usage history [ task task-id ] [ slot slot-number [ cpu cpu-number ] ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display history statistics of the CPU usage in a chart (IRF mode). |
display cpu-usage history [ task task-id ] [ chassis chassis-number slot slot-number ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display device information (standalone mode). |
display device [ cf-card ] [ slot slot-number [ subslot subslot-number ] | verbose ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display device information (IRF mode). |
display device [ cf-card ] [ [ chassis chassis-number ] [ slot slot-number ] [ subslot subslot-number ] | verbose ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display electrical label information of the switch (standalone mode). |
display device manuinfo [ slot slot-number ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display electrical label information of an member switch (IRF mode). |
display device manuinfo [ chassis chassis-number [ slot slot-number ] ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the electrical label information of the specified chassis backplane (standalone mode). |
display device manuinfo chassis-only [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the electrical label information of the specified chassis backplane (IRF mode). |
display device manuinfo chassis chassis-number chassis-only [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the electrical label information of the specified fan (standalone mode). |
display device manuinfo fan fan-id [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the electrical label information of the specified fan (IRF mode). |
display device manuinfo chassis chassis-number fan fan-id [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the electrical label information of the specified power module (standalone mode). |
display device manuinfo power power-id [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the electrical label information of the specified power module (IRF mode). |
display device manuinfo chassis chassis-number power power-id [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the temperature information of the switch (standalone mode). |
display environment [ slot slot-number ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the temperature information of an member switch (IRF mode). |
display environment [ chassis chassis-number [ slot slot-number ] ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the operating state of fans in the switch (standalone mode). |
display fan [ fan-id ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the operating state of fans in an IRF member switch (IRF mode). |
display fan [ chassis chassis-number ] [ fan-id ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the automatic speed adjustment mode of fans in the switch (standalone mode). |
display fan auto-control-mode [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the automatic speed adjustment mode of fans in an IRF member switch (IRF mode). |
display fan auto-control-mode chassis chassis-number [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display hardware failure detection and fix operation records. |
display hardware-failure-detection [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display hardware failure protection information. |
display hardware-failure-protection [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the usage of the memory of the switch (standalone mode). |
display memory [ slot slot-number [ cpu cpu-number ] ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the usage of the memory of an IRF member switch (IRF mode). |
display memory [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the power state of the switch (standalone mode). |
display power-supply [ verbose ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the power state of an IRF member switch (IRF mode). |
display power-supply [ chassis chassis-number ] [ verbose ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the configuration of the scheduled job configured by the schedule job command. |
display schedule job [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the reboot time of the switch. |
display schedule reboot [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display brief information about the hardware configuration file. |
display system config file [ file-url ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the system working mode. |
display system working mode [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the configuration of scheduled jobs configured by the job command. |
display job [ job-name ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the load mode of the current active MPU and standby MPU (standalone mode). |
display xbar [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
Display the load mode of the current active MPU and standby MPU (IRF mode). |
display xbar [ chassis chassis-number ] [ | { begin | exclude | include } regular-expression ] |
Available in any view |
|
|
NOTE: The display commands discussed above are for the global configuration. For the display command for specific protocol and interface, see corresponding sections. |
