- Table of Contents
-
- 01-Fundamentals Configuration Guide
- 00-Preface
- 01-CLI configuration
- 02-RBAC configuration
- 03-Login management configuration
- 04-FTP and TFTP configuration
- 05-File system management configuration
- 06-Configuration file management configuration
- 07-Software upgrade configuration
- 08-Emergency shell configuration
- 09-Automatic configuration
- 10-Device management configuration
- 11-Tcl configuration
- 12-Python configuration
- 13-License management
- 14-RAID management configuration (routers)
- Related Documents
-
Title | Size | Download |
---|---|---|
10-Device management configuration | 249.56 KB |
Device management tasks at a glance
Restrictions and guidelines for configuring the system time
System time configuration tasks at a glance
Setting the system time at the CLI
Obtaining the UTC time through a time protocol
Obtaining the UTC time through a cellular interface
Setting the daylight saving time
Enabling displaying the copyright statement
Disabling password recovery capability
Setting the system operating mode
Setting the operating mode for an interface module
Setting the port status detection timer
Setting memory alarm thresholds
Configuring disk usage monitoring
Configuring resource monitoring
Verifying and diagnosing transceiver modules
Diagnosing transceiver modules
Updating the modem firmware through FoTA
Restrictions and guidelines for device reboot
Rebooting devices immediately at the CLI
Restoring the factory-default configuration
Enabling PTP packet acceleration
Display and maintenance commands for device management configuration
Managing the device
About device management
This chapter describes how to configure basic device parameters and manage the device.
Device management tasks at a glance
All device management tasks are optional. You can perform any of the tasks in any order.
· Configuring basic parameters
¡ Enabling displaying the copyright statement
· Configuring security parameters
¡ Disabling password recovery capability
· Adjusting device capacities
¡ Setting the operating mode for an interface module
¡ Setting the port status detection timer
· Monitoring the device
¡ Setting memory alarm thresholds
¡ Configuring disk usage monitoring
¡ Configuring resource monitoring
· Managing resources
¡ Verifying and diagnosing transceiver modules
¡ Updating the modem firmware through FoTA
· Maintaining the device
¡ Restoring the factory-default configuration
¡ Enabling PTP packet acceleration
Configuring the device name
About this task
A device name (also called hostname) identifies a device in a network and is used in CLI view prompts. For example, if the device name is Sysname, the user view prompt is <Sysname>.
Procedure
1. Enter system view.
system-view
sysname sysname
By default, the device name is H3C.
Configuring the system ID
About this task
You can use the system ID to indicate the position or functionality of the device or any other information.
Procedure
1. Enter system view.
system-view
2. Configure the system ID.
sysid system-id
By default, the device does not have a system ID.
Configuring the system time
About the system time
Correct system time is essential to network management and communication. Configure the system time correctly before you run the device on the network.
The device can use one of the following methods to obtain the system time:
· Uses the locally set system time, and then uses the clock signals generated by its built-in crystal oscillator to maintain the system time.
· Periodically obtains the UTC time from an NTP source, and uses the UTC time, time zone, and daylight saving time to calculate the system time. For more information about NTP, see Network Management and Monitoring Configuration Guide.
The system time calculated by using the UTC time from a time source is more precise.
Restrictions and guidelines for configuring the system time
After you execute the clock protocol none command, the clock datetime command determines the system time, whether or not the time zone or daylight saving time has been configured.
If you configure or change the time zone or daylight saving time after the device obtains the system time, the device recalculates the system time. To view the system time, use the display clock command.
System time configuration tasks at a glance
To configure the system time, perform the following tasks:
1. Configuring the system time
Choose one of the following tasks:
¡ Setting the system time at the CLI
¡ Obtaining the UTC time through a time protocol
¡ Obtaining the UTC time through a cellular interface
2. (Optional.) Setting the time zone
Make sure each network device uses the time zone of the place where the device resides.
3. (Optional.) Setting the daylight saving time
Make sure each network device uses the daylight saving time parameters of the place where the device resides.
Setting the system time at the CLI
1. Enter system view.
system-view
2. Configure the device to use the local system time.
clock protocol none
The device comes with the NTP server address. By default, the device uses the NTP time source.
If you execute the clock protocol command multiple times, the most recent configuration takes effect.
3. Return to user view.
quit
4. Set the local system time.
clock datetime time date
By default, the system time is UTC time 00:00:00 01/01/2011.
CAUTION: Use this command with caution. This command changes the system time, which affects execution of system time-related features (for example, scheduled tasks) and collaborative operations of the device with other devices (for example, log reporting and statistics collection). |
Obtaining the UTC time through a time protocol
Restrictions and guidelines
If the NTP or PTP signals are lost, the device uses the clock signals generated by its built-in crystal oscillator to maintain the system time. After the NTP or PTP signals recover, the device obtains the UTC time again through NTP or PTP.
Procedure
1. Enter system view.
system-view
2. Specify the protocol for obtaining the UTC time.
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. Configure time protocol parameters.
For more information about NTP configuration, see Network Management and Monitoring Configuration Guide.
Obtaining the UTC time through a cellular interface
About this task
This feature enables the device to obtain the UTC time of a 3G or 4G modem through a cellular interface.
Restrictions and guidelines
If the 3G or 4G modem is removed or not working correctly, the device uses NTP instead. After the cellular interface operates correctly, the device obtains the UTC time again through the cellular interface.
Procedure
1. Enter system view.
system-view
2. Specify the system time source.
clock protocol controller cellular cellular-number
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. Configure 3G or 4G modem parameters. For more information, see 3G and 4G modem management in Layer 2—WAN Access Configuration Guide.
Setting the time zone
1. Enter system view.
system-view
2. Set the time zone.
clock timezone zone-name { add | minus } zone-offset
By default, the system uses the UTC time zone.
Setting the daylight saving time
1. Enter system view.
system-view
2. Set the daylight saving time.
clock summer-time name start-time start-date end-time end-date add-time
By default, the daylight saving time is not set.
Enabling displaying the copyright statement
About this task
This feature enables the device to display the copyright statement in the following situations:
· When a Telnet or SSH user logs in.
· When a console or AUX user quits user view. This is because the device automatically tries to restart the user session.
If you disable displaying the copyright statement, the device does not display the copyright statement in any situations.
Procedure
1. Enter system view.
system-view
2. Enable displaying the copyright statement.
copyright-info enable
By default, displaying the copyright statement is enabled.
Configuring banners
About this task
Banners are messages that the system displays when a user logs in.
The system supports the following banners:
· Legal banner—Appears after the copyright statement. To continue login, the user must enter Y or press Enter. To quit the process, the user must enter N. Y and N are case insensitive.
· Message of the Day (MOTD) banner—Appears after the legal banner and before the login banner.
· Login banner—Appears only when password or scheme authentication is configured.
· Incoming banner—Appears for modem users.
· Shell banner—Appears for non-modem users.
The system displays the banners in the following order: legal banner, MOTD banner, login banner, and incoming or shell banner.
Banner input methods
You can configure a banner by using one of the following methods:
· Input the entire command line in a single line.
The banner cannot contain carriage returns. The entire command line, including the command keywords, the banner, and the delimiters, can have a maximum of 511 characters. The delimiters for the banner can be any printable character but must be the same. You cannot press Enter before you input the end delimiter.
For example, you can configure the shell banner "Have a nice day." as follows:
<System> system-view
[System] header shell %Have a nice day.%
· Input the command line in multiple lines.
The banner can contain carriage returns. A carriage return is counted as two characters.
To input a banner configuration command line in multiple lines, use one of the following methods:
¡ Press Enter after the final command keyword, type the banner, and end the final line with the delimiter character %. The banner plus the delimiter can have a maximum of 1999 characters.
For example, you can configure the banner "Have a nice day." as follows:
<System> system-view
[System] header shell
Please input banner content, and quit with the character '%'.
Have a nice day.%
¡ After you type the final command keyword, type any printable character as the start delimiter for the banner and press Enter. Then, type the banner and end the final line with the same delimiter. The banner plus the end delimiter can have a maximum of 1999 characters.
For example, you can configure the banner "Have a nice day." as follows:
<System> system-view
[System] header shell A
Please input banner content, and quit with the character 'A'.
Have a nice day.A
¡ After you type the final command keyword, type the start delimiter and part of the banner. Make sure the final character of the final string is different from the start delimiter. Then, press Enter, type the rest of the banner, and end the final line with the same delimiter. The banner plus the start and end delimiters can have a maximum of 2002 characters.
For example, you can configure the banner "Have a nice day." as follows:
<System> system-view
[System] header shell AHave a nice day.
Please input banner content, and quit with the character 'A'.
A
Procedure
1. Enter system view.
system-view
2. Configure the legal banner.
header legal text
3. Configure the MOTD banner.
header motd text
4. Configure the login banner.
header login text
5. Configure the incoming banner.
header incoming text
6. Configure the shell banner.
header shell text
Disabling password recovery capability
About this task
Password recovery capability controls console user access to the device configuration and SDRAM from BootWare menus. For more information about BootWare menus, see the release notes.
If password recovery capability is enabled, a console user can access the device configuration without authentication to configure a new password.
If password recovery capability is disabled, console users must restore the factory-default configuration before they can configure new passwords. Restoring the factory-default configuration deletes the next-startup configuration files.
To enhance system security, disable password recovery capability.
(In IRF mode.) To access the device configuration without authentication, you must connect to the master device and access the BootWare menu while the master device is starting up.
Procedure
1. Enter system view.
system-view
2. Disable password recovery capability.
undo password-recovery enable
By default, password recovery capability is enabled.
Disabling USB interfaces
About this task
You can use USB interfaces to upload or download files or to connect a 3G modem. By default, all USB interfaces are enabled. You can disable USB interfaces as needed.
Hardware and feature compatibility
Hardware |
Feature compatibility |
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK |
Yes |
MSR810-LM-HK, MSR810-W-LM-HK |
No |
MSR810-LMS, MSR810-LUS |
No |
MSR810-LMS-EA, MSR810-LME |
Yes |
MSR1004S-5G |
Yes |
MSR2600-6-X1, MSR2600-15-X1 |
No |
MSR2600-10-X1 |
Yes |
MSR 2630 |
Yes |
MSR3600-28, MSR3600-51 |
No |
MSR3600-28-SI, MSR3600-51-SI |
No |
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
No |
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG |
Yes |
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1 |
Yes |
MSR 3610, MSR 3620, MSR 3640, MSR 3660 |
No |
MSR3620-DP |
Yes |
MSR3610-G, MSR3620-G |
No |
MSR3640-X1-HI |
Yes |
Hardware |
Feature compatibility |
MSR810-W-WiNet, MSR810-LM-WiNet |
Yes |
MSR830-4LM-WiNet |
Yes |
MSR830-5BEI-WiNet, MSR830-10BEI-WiNet |
Yes |
MSR830-6EI-WiNet |
No |
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet |
Yes |
MSR2600-6-WiNet |
No |
MSR2600-10-X1-WiNet |
Yes |
MSR2630-WiNet |
Yes |
MSR3600-28-WiNet |
No |
MSR3610-X1-WiNet |
Yes |
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-WiNet, MSR3660-WiNet |
No |
MSR3620-DP-WiNet |
Yes |
Hardware |
Feature compatibility |
MSR2630-XS |
Yes |
MSR3600-28-XS |
Yes |
MSR3610-XS |
Yes |
MSR3620-XS |
Yes |
MSR3610-I-XS |
Yes |
MSR3610-IE-XS |
Yes |
MSR3620-X1-XS |
Yes |
MSR3640-XS |
Yes |
MSR3660-XS |
Yes |
Hardware |
Feature compatibility |
MSR810-LM-GL |
Yes |
MSR810-W-LM-GL |
Yes |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
Yes |
MSR830-6HI-GL |
Yes |
MSR830-10HI-GL |
Yes |
MSR1004S-5G-GL |
Yes |
MSR2600-6-X1-GL |
No |
MSR3600-28-SI-GL |
No |
Prerequisites
Before using this command, use the umount command to unmount all USB partitions. For more information about this command, see Fundamentals Command Reference.
Procedure
1. Enter system view.
system-view
2. Disable USB interfaces.
usb disable
By default, all USB interfaces are enabled.
Disabling Bluetooth
About disabling Bluetooth
After you disable Bluetooth, users cannot connect to the device through Bluetooth.
Hardware and feature compatibility
Hardware |
Feature compatibility |
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK |
Yes |
MSR810-LM-HK, MSR810-W-LM-HK |
No |
MSR810-LMS, MSR810-LUS |
No |
MSR810-LMS-EA, MSR810-LME |
Yes |
MSR1004S-5G |
Yes |
MSR2600-6-X1, MSR2600-15-X1 |
No |
MSR2600-10-X1 |
Yes |
MSR 2630 |
Yes |
MSR3600-28, MSR3600-51 |
No |
MSR3600-28-SI, MSR3600-51-SI |
No |
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
No |
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG |
Yes |
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1 |
Yes |
MSR 3610, MSR 3620, MSR 3640, MSR 3660 |
No |
MSR3620-DP |
Yes |
MSR3610-G, MSR3620-G |
No |
MSR3640-X1-HI |
No |
Hardware |
Feature compatibility |
MSR810-W-WiNet, MSR810-LM-WiNet |
Yes |
MSR830-4LM-WiNet |
Yes |
MSR830-5BEI-WiNet, MSR830-10BEI-WiNet |
Yes |
MSR830-6EI-WiNet |
No |
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet |
Yes |
MSR2600-6-WiNet |
No |
MSR2600-10-X1-WiNet |
Yes |
MSR2630-WiNet |
Yes |
MSR3600-28-WiNet |
No |
MSR3610-X1-WiNet |
Yes |
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-WiNet, MSR3660-WiNet |
No |
MSR3620-DP-WiNet |
Yes |
Hardware |
Feature compatibility |
MSR2630-XS |
Yes |
MSR3600-28-XS |
Yes |
MSR3610-XS |
Yes |
MSR3620-XS |
Yes |
MSR3610-I-XS |
Yes |
MSR3610-IE-XS |
Yes |
MSR3620-X1-XS |
Yes |
MSR3640-XS |
Yes |
MSR3660-XS |
No |
Hardware |
Feature compatibility |
MSR810-LM-GL |
Yes |
MSR810-W-LM-GL |
Yes |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
Yes |
MSR830-6HI-GL |
Yes |
MSR830-10HI-GL |
Yes |
MSR1004S-5G-GL |
Yes |
MSR2600-6-X1-GL |
No |
MSR3600-28-SI-GL |
No |
Restrictions and guidelines
Use this feature with caution. After you disable Bluetooth, users cannot connect to the device through Bluetooth.
Procedure
1. Enter system view.
system-view
2. Disable Bluetooth.
bluetooth disable
By default, Bluetooth is enabled.
Setting the system operating mode
About this task
The device can operate in one of the following modes:
· standard—Standard mode.
· sd-wan—Operating mode for the SD-WAN branch scenario solution.
Supported features and feature specifications vary by system operating mode.
Hardware and feature compatibility
Hardware |
Feature compatibility |
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK |
No |
MSR810-LMS, MSR810-LUS |
No |
MSR810-LMS-EA, MSR810-LME |
No |
MSR1004S-5G |
Yes |
MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1 |
Yes |
MSR 2630 |
No |
MSR3600-28, MSR3600-51 |
No |
MSR3600-28-SI, MSR3600-51-SI |
No |
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG |
No |
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1 |
No |
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
No |
MSR3610-G, MSR3620-G |
No |
MSR3640-X1-HI |
Yes |
Hardware |
Feature compatibility |
MSR810-W-WiNet, MSR810-LM-WiNet |
No |
MSR830-4LM-WiNet |
No |
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet |
No |
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet |
Yes |
MSR2600-6-WiNet, MSR2600-10-X1-WiNet |
Yes |
MSR2630-WiNet |
No |
MSR3600-28-WiNet |
No |
MSR3610-X1-WiNet |
No |
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet |
No |
Hardware |
Feature compatibility |
MSR2630-XS |
Yes |
MSR3600-28-XS |
No |
MSR3610-XS |
No |
MSR3620-XS |
No |
MSR3610-I-XS |
No |
MSR3610-IE-XS |
No |
MSR3620-X1-XS |
No |
MSR3640-XS |
No |
MSR3660-XS |
Yes |
Hardware |
Feature compatibility |
MSR810-LM-GL |
No |
MSR810-W-LM-GL |
No |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
Yes |
MSR830-10HI-GL |
Yes |
MSR1004S-5G-GL |
Yes |
MSR2600-6-X1-GL |
Yes |
MSR3600-28-SI-GL |
No |
Restrictions and guidelines
Change to the operating mode takes effect after a system reboot.
Procedure
1. Enter system view.
system-view
2. Set the system operating mode.
system-working-mode{ sd-wan | standard }
By default, the device operates in standard mode.
Setting the operating mode for an interface module
About this task
Some interface modules can operate in multiple modes to provide different types of interfaces. Use this feature to set the operating mode for an interface module.
Hardware and feature compatibility
Hardware |
Feature compatibility |
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK |
No |
MSR810-LMS, MSR810-LUS |
No |
MSR810-LMS-EA, MSR810-LME |
No |
MSR1004S-5G |
No |
MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1 |
Yes |
MSR 2630 |
Yes |
MSR3600-28, MSR3600-51 |
Yes |
MSR3600-28-SI, MSR3600-51-SI |
Yes |
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG |
Yes |
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1 |
Yes |
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
MSR3610-G, MSR3620-G |
Yes |
MSR3640-X1-HI |
Yes |
Hardware |
Feature compatibility |
MSR810-W-WiNet, MSR810-LM-WiNet |
No |
MSR830-4LM-WiNet |
No |
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet |
No |
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet |
No |
MSR2600-6-WiNet, MSR2600-10-X1-WiNet |
Yes |
MSR2630-WiNet |
Yes |
MSR3600-28-WiNet |
Yes |
MSR3610-X1-WiNet |
Yes |
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet |
Yes |
Hardware |
Feature compatibility |
MSR2630-XS |
Yes |
MSR3600-28-XS |
Yes |
MSR3610-XS |
Yes |
MSR3620-XS |
Yes |
MSR3610-I-XS |
Yes |
MSR3610-IE-XS |
Yes |
MSR3620-X1-XS |
Yes |
MSR3640-XS |
Yes |
MSR3660-XS |
Yes |
Hardware |
Feature compatibility |
MSR810-LM-GL |
No |
MSR810-W-LM-GL |
No |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
No |
MSR830-10HI-GL |
No |
MSR1004S-5G-GL |
No |
MSR2600-6-X1-GL |
Yes |
MSR3600-28-SI-GL |
Yes |
Restrictions and guidelines
The E1 and T1 modes are supported only the HMIM-1CPOS, HMIM-2CPOS, HMIM-2E1T1, HMIM-4E1T1, HMIM-8E1T1, HMIM-2E1T1-F, HMIM-4E1T1-F, and HMIM-8E1T1-F interface modules.
For an operating mode change to take effect, you must perform one of the following tasks:
· Hot swap the interface module if the interface module supports hot swapping.
· Restart the device.
Procedure
1. Enter system view.
system-view
2. Set the operating mode for an interface module.
In standalone mode:
card-mode slot slot-number mode-name
In IRF mode:
card-mode slot slot-number subslot subslot-number mode-name
By default, an interface module operates in e1 mode.
Setting the port status detection timer
About this task
The device starts a port status detection timer when a port is shut down by a protocol. Once the timer expires, the device brings up the port so the port status reflects the port's physical status.
Procedure
1. Enter system view.
system-view
2. Set the port status detection timer.
shutdown-interval time
The default setting is 30 seconds.
Monitoring CPU usage
About this task
To monitor CPU usage, the device performs the following operations:
· Samples CPU usage at 1-minute intervals and compares the samples with the CPU usage threshold and the CPU usage recovery threshold.
¡ If a sample is greater than or equal to the CPU usage threshold, the device determines the CPU usage is high and sends traps to affected service modules and processes.
¡ If a sample decreases to or below the CPU usage recovery threshold, the device determines the CPU usage has recovered and sends traps to affected service modules and processes.
· Samples and saves CPU usage at a configurable interval if CPU usage tracking is enabled. You can use the display cpu-usage history command to display the historical CPU usage statistics in a coordinate system.
Figure 1 CPU alarms and alarm-removed notifications
Procedure
1. Enter system view.
system-view
2. Set the CPU usage alarm thresholds.
In standalone mode:
monitor cpu-usage threshold severe-threshold
In IRF mode:
monitor cpu-usage threshold severe-threshold [ slot slot-number [ cpu cpu-number ] ]
By default, the CPU usage alarm threshold is 99%.
CAUTION: If you set the severe CPU usage alarm threshold to a tool low value, the device will reach the threshold easily. Normal services will be affected. |
3. Set the sampling interval for CPU usage tracking.
In standalone mode:
monitor cpu-usage interval interval
In IRF mode:
monitor cpu-usage interval interval [ slot slot-number [ cpu cpu-number ] ]
By default, the sampling interval for CPU usage tracking is 1 minute.
4. Enable CPU usage tracking.
In standalone mode:
monitor cpu-usage enable
In IRF mode:
monitor cpu-usage enable [ slot slot-number [ cpu cpu-number ] ]
By default, CPU usage tracking is enabled.
Setting memory alarm thresholds
About memory alarm threholds
To ensure correct operation and improve memory efficiency, the system performs the following operations:
· Samples memory usage at 1-minute intervals. If the sample is equal to or greater than the memory usage threshold, the device sends a trap.
· Monitors the amount of free memory space in real time. If the amount of free memory space reaches the minor, severe, or critical alarm threshold, the system issues an alarm to affected service modules and 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 below the minor alarm threshold. |
After generating and sending a minor alarm notification, the system does not generate and send any additional minor alarm notifications until the minor alarm is removed. |
Severe alarm notification |
The amount of free memory space decreases below the severe alarm threshold. |
After generating and sending a severe alarm notification, the system does not generate and send any additional severe alarm notifications until the severe alarm is removed. |
Critical alarm notification |
The amount of free memory space decreases below the critical alarm threshold. |
After generating and sending a critical alarm notification, the system does not generate and send any additional critical alarm notifications until the critical alarm is removed. |
Critical alarm-removed notification |
The amount of free memory space increases above the severe alarm threshold. |
N/A |
Severe alarm-removed notification |
The amount of free memory space increases above the minor alarm threshold. |
N/A |
Minor alarm-removed notification |
The amount of free memory space increases above the normal state threshold. |
N/A |
Figure 2 Memory alarm notifications and alarm-removed notifications
About memory alarm threholds
To ensure correct operation and improve memory efficiency, the system performs the following operations:
· Samples memory usage at 1-minute intervals. If the sample is equal to or greater than the memory usage threshold, the device sends a trap.
· Monitors the amount of free memory space in real time. If the amount of free memory space reaches the minor, severe, or critical alarm threshold, the system issues an alarm to affected service modules and processes.
The early warning feature warns you of an approaching insufficient-memory condition.
As shown in Table 1 and Figure 2, the system supports the following free-memory thresholds:
· Sufficient-memory threshold.
· Early-warning threshold.
· Normal state threshold.
· Minor alarm threshold.
· Severe alarm threshold.
· Critical alarm threshold.
Table 2 Memory alarm notifications and memory alarm-removed notifications
Notification |
Triggering condition |
Remarks |
Early-warning notification |
The amount of free memory space decreases below the early-warning threshold. |
After generating and sending an early-warning notification, the system does not generate and send any additional early-warning notifications until the early warning is removed. |
Minor alarm notification |
The amount of free memory space decreases below the minor alarm threshold. |
After generating and sending a minor alarm notification, the system does not generate and send any additional minor alarm notifications until the minor alarm is removed. |
Severe alarm notification |
The amount of free memory space decreases below the severe alarm threshold. |
After generating and sending a severe alarm notification, the system does not generate and send any additional severe alarm notifications until the severe alarm is removed. |
Critical alarm notification |
The amount of free memory space decreases below the critical alarm threshold. |
After generating and sending a critical alarm notification, the system does not generate and send any additional critical alarm notifications until the critical alarm is removed. |
Critical alarm-removed notification |
The amount of free memory space increases above the severe alarm threshold. |
N/A |
Severe alarm-removed notification |
The amount of free memory space increases above the minor alarm threshold. |
N/A |
Minor alarm-removed notification |
The amount of free memory space increases above the normal state threshold. |
N/A |
Early-warning alarm-removed notification |
The amount of free memory space increases above the sufficient-memory threshold. |
N/A |
Figure 3 Memory alarm notifications and alarm-removed notifications
Restrictions and guidelines
If a memory alarm occurs, delete unused configuration items or disable some features to increase the free memory space. Because the memory space is insufficient, some configuration items might not be able to be deleted.
Procedure
1. Enter system view.
system-view
2. Set the memory usage threshold.
In standalone mode:
memory-threshold usage memory-threshold
In IRF mode:
memory-threshold [ slot slot-number [ cpu cpu-number ] ] usage memory-threshold
By default, the memory usage threshold is 100%.
3. Set the free-memory thresholds.
In standalone mode:
memory-threshold [ ratio ] minor minor-value severe severe-value critical critical-value normal normal-value
In IRF mode:
memory-threshold [ slot slot-number [ cpu cpu-number ] ] [ ratio ] minor minor-value severe severe-value critical critical-value normal normal-value
The default settings vary by device model. To view the default settings, use the undo memory-threshold command to restore the default settings and then execute the display memory-threshold command.
Configuring disk usage monitoring
About this task
This feature enables the device to periodically sample disk usages and compare the usages with the thresholds. If a sample is greater than or equal to the disk usage threshold, the device determines the disk usage is high.
Procedure
1. Enter system view.
system-view
2. Set the disk usage sampling interval.
monitor disk-usage interval interval
By default, the disk usage sampling interval is 300 seconds.
3. Set disk usage thresholds.
In standalone mode:
monitor disk-usage disk disk-name threshold threshold-value
In IRF mode:
monitor disk-usage [ slot slot-number ] disk disk-name threshold threshold-value
The default disk usage threshold is 90%.
Configuring resource monitoring
About this task
The resource monitoring feature enables the device to monitor the available amounts of types of resources, for example, the space for ARP entries. The device samples the available amounts periodically and compares the samples with resource depletion thresholds to identify the resource depletion status.
The device supports a minor resource depletion threshold and a severe resource depletion threshold for each supported resource type.
· If the available amount is equal to or less than the minor resource depletion threshold but greater than the severe resource depletion threshold, the resource type is in minor alarm state.
· If the available amount is equal to or less than the severe resource depletion threshold, the resource type is in severe alarm state.
· If the available amount increases above the minor resource depletion threshold, the resource type is in recovered state.
When a resource type enters severe alarm state, the device issues a severe alarm. If the resource type stays in severe alarm state, the device resends severe alarms periodically.
When a resource type enters minor alarm state, the device issues a minor alarm. If the resource type stays in minor alarm state or changes from severe alarm state to minor alarm state, the device identifies whether resending of minor resource depletion alarms is enabled. If the feature is disabled, the device does not issue additional minor alarms. If the feature is enabled, the device resends minor alarms periodically.
Resource depletion alarms can be sent to NETCONF, SNMP, and the information center to be encapsulated as NETCONF events, SNMP traps and informs, and log messages. For more information, see NETCONF, SNMP, and information center in Network Management and Monitoring Configuration Guide.
Figure 4 Resource depletion alarms and alarm-removed notifications
Procedure
1. Enter system view.
system-view
2. Set resource depletion thresholds.
In standalone mode:
resource-monitor resource resource-name cpu cpu-number { by-absolute | by-percent } minor-threshold minor-threshold severe-threshold severe-threshold
In IRF mode:
resource-monitor resource resource-name slot slot-number cpu cpu-number { by-absolute | by-percent } minor-threshold minor-threshold severe-threshold severe-threshold
The default settings vary by resource type. Use the display resource-monitor command to display the resource depletion thresholds.
3. Specify destinations for resource depletion alarms.
resource-monitor output { netconf-event | snmp-notification | syslog } *
By default, the system does not send resource depletion alarms to NETCONF, SNMP, or the information center.
4. Enable resending of minor resource depletion alarms.
resource-monitor minor resend enable
By default, resending of minor resource depletion alarms is enabled.
Verifying and diagnosing transceiver modules
Verifying transceiver modules
About this task
You can use one of the following methods to verify the genuineness of a transceiver module:
· Display the key parameters of a transceiver module, including its transceiver type, connector type, central wavelength of the transmit laser, transfer distance, and vendor name.
· Display its electronic label. The electronic label is a profile of the transceiver module and contains the permanent configuration, including the serial number, manufacturing date, and vendor name. The data was written to the transceiver module or the device's storage component during debugging or testing of the transceiver module or device.
The device regularly checks transceiver modules for their vendor names. If a transceiver module does not have a vendor name or the vendor name is not H3C, the device repeatedly outputs traps and log messages. For information about logging rules, see information center in Network Management and Monitoring Configuration Guide.
Procedure
To verify transceiver modules, execute the following commands in any view:
· Display the key parameters of transceiver modules.
display transceiver interface [ interface-type interface-number ]
· Display the electrical label information of transceiver modules.
display transceiver manuinfo { controller [ controller-type controller-number ] | interface [ interface-type interface-number ] }
Diagnosing transceiver modules
About this task
The device provides the alarm and digital diagnosis functions for transceiver modules. When a transceiver module fails or is not operating correctly, you can perform the following tasks:
· Check the alarms that exist on the transceiver module to identify the fault source.
· Examine the key parameters monitored by the digital diagnosis function, including the temperature, voltage, laser bias current, TX power, and RX power.
Procedure
To diagnose transceiver modules, execute the following commands in any view:
· Display transceiver alarms.
display transceiver alarm { controller [ controller-type controller-number ] | interface [ interface-type interface-number ] }
· Display the current values of the digital diagnosis parameters on transceiver modules.
display transceiver diagnosis { controller [ controller-type controller-number ] | interface [ interface-type interface-number ] }
Unmounting HMIM modules
About this task
If the device supports hot swapping modules, use this feature to unmount an HMIM module before removing the module from the device. If you remove an HMIM module that is not unmounted, the device might fail or be damaged.
Hardware and feature compatibility
Hardware |
Feature compatibility |
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK |
No |
MSR810-LMS, MSR810-LUS |
No |
MSR810-LMS-EA, MSR810-LME |
No |
MSR1004S-5G |
No |
MSR2600-6-X1, MSR2600-15-X1 |
Yes |
MSR2600-10-X1 |
No |
MSR 2630 |
No |
MSR3600-28, MSR3600-51 |
No |
MSR3600-28-SI, MSR3600-51-SI |
No |
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
No |
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG |
No |
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1 |
Yes |
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
MSR3610-G, MSR3620-G |
Yes |
MSR3640-X1-HI |
Yes |
Hardware |
Feature compatibility |
MSR810-W-WiNet, MSR810-LM-WiNet |
No |
MSR830-4LM-WiNet |
No |
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet |
No |
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet |
No |
MSR2600-6-WiNet |
Yes |
MSR2600-10-X1-WiNet |
No |
MSR2630-WiNet |
No |
MSR3600-28-WiNet |
No |
MSR3610-X1-WiNet |
Yes |
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet |
Yes |
Hardware |
Feature compatibility |
MSR2630-XS |
Yes |
MSR3600-28-XS |
No |
MSR3610-XS |
Yes |
MSR3620-XS |
Yes |
MSR3610-I-XS |
No |
MSR3610-IE-XS |
No |
MSR3620-X1-XS |
Yes |
MSR3640-XS |
Yes |
MSR3660-XS |
Yes |
Hardware |
Feature compatibility |
MSR810-LM-GL |
No |
MSR810-W-LM-GL |
No |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
No |
MSR830-10HI-GL |
No |
MSR1004S-5G-GL |
No |
MSR2600-6-X1-GL |
Yes |
MSR3600-28-SI-GL |
No |
Restrictions and guidelines
CAUTION: Unmounting an HMIM module stops all services provided by the module. |
An unmounted HMIM module is not visible or configurable.
Procedure
To unmount an HMIM module, execute the following command in user view:
In standalone mode:
remove subslot subslot-number
In IRF mode:
remove slot slot-number subslot subslot-number
Updating the modem firmware through FoTA
Restrictions and guidelines
CAUTION: Use this feature with caution. A modem firmware update through FoTA affects data transmission and consumes SIM card resources. |
Hardware and feature compatibility
This feature is supported only on the following devices:
· MSR810-LMS.
· MSR810-LUS.
· MSR1004S-5G.
· MSR1004S-5G-GL.
· Devices that are installed with the SIC-D4G-CNDE or SIC-4G-CNDE card.
Procedure
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular cellular-number
3. Update the modem firmware through FoTA.
firmware update fota
Scheduling a task
About task scheduling
You can schedule the device to automatically execute a command or a set of commands without administrative interference.
You can configure a periodic schedule or a non-periodic schedule. A non-periodic schedule is not saved to the configuration file and is lost when the device reboots. A periodic schedule is saved to the startup configuration file and is automatically executed periodically.
Restrictions and guidelines
· To assign a command (command A) to a job, you must first assign the job the command or commands for entering the view of command A.
· Make sure all commands in a schedule are compliant to the command syntax. The system does not check the syntax when you assign a command to a job.
· A schedule cannot contain any one of these commands: telnet, ftp, ssh2, and monitor process.
· A schedule does not support user interaction. If a command requires a yes or no answer, the system always assumes that a Y or Yes is entered. If a command requires a character string input, the system assumes that either the default character string (if any) or a null string is entered.
· A schedule is executed in the background, and no output (except for logs, traps, and debug information) is displayed for the schedule.
Procedure
1. Enter system view.
system-view
2. Create a job.
scheduler job job-name
3. Assign a command to the job.
command id command
By default, no command is assigned to a job.
You can assign multiple commands to a job. A command with a smaller ID is executed first.
4. Exit to system view.
quit
5. Create a schedule.
scheduler schedule schedule-name
6. Assign a job to the schedule.
job job-name
By default, no job is assigned to a schedule.
You can assign multiple jobs to a schedule. The jobs will be executed concurrently.
7. Assign user roles to the schedule.
user-role role-name
By default, a schedule has the user role of the schedule creator.
You can assign a maximum of 64 user roles to a schedule. A command in a schedule can be executed if it is permitted by one or more user roles of the schedule.
8. Specify the execution time for the schedule.
Choose one option as needed:
¡ Execute the schedule at specific points of time.
time at time date
time once at time [ month-date month-day | week-day week-day&<1-7> ]
¡ Execute the schedule after a period of time.
time once delay time
¡ Execute the schedule at the specified time on every specified day in a month or week.
time repeating at time [ month-date [ month-day | last ] | week-day week-day&<1-7> ]
¡ Execute the schedule periodically from the specified time on.
time repeating [ at time [date ] ] interval interval
By default, no execution time is specified for a schedule.
The time commands overwrite each other. The most recently executed command takes effect.
9. (Optional.) Set the size of the job execution log file.
scheduler logfile size value
By default, the size of the job execution log file is 16 KB.
The job execution log file stores the execution information of jobs. If the file is full, old records are deleted to make room for new records. If the size of the log information to be written to the file is greater than the file size, the excessive information is not written to the file.
Example: Scheduling a task
Network configuration
As shown in Figure 5, 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.
Procedure
# Enter system view.
<Sysname> system-view
# Configure a job for disabling interface GigabitEthernet 1/0/1.
[Sysname] scheduler job shutdown-GigabitEthernet1/0/1
[Sysname-job-shutdown-GigabitEthernet1/0/1] command 1 system-view
[Sysname-job-shutdown-GigabitEthernet1/0/1] command 2 interface gigabitethernet 1/0/1
[Sysname-job-shutdown-GigabitEthernet1/0/1] command 3 shutdown
[Sysname-job-shutdown-GigabitEthernet1/0/1] quit
# Configure a job for enabling interface GigabitEthernet 1/0/1.
[Sysname] scheduler job start-GigabitEthernet1/0/1
[Sysname-job-start-GigabitEthernet1/0/1] command 1 system-view
[Sysname-job-start-GigabitEthernet1/0/1] command 2 interface gigabitethernet 1/0/1
[Sysname-job-start-GigabitEthernet1/0/1] command 3 undo shutdown
[Sysname-job-start-GigabitEthernet1/0/1] quit
# Configure a job for disabling interface GigabitEthernet 1/0/2.
[Sysname] scheduler job shutdown-GigabitEthernet1/0/2
[Sysname-job-shutdown-GigabitEthernet1/0/2] command 1 system-view
[Sysname-job-shutdown-GigabitEthernet1/0/2] command 2 interface gigabitethernet 1/0/2
[Sysname-job-shutdown-GigabitEthernet1/0/2] command 3 shutdown
[Sysname-job-shutdown-GigabitEthernet1/0/2] quit
# Configure a job for enabling interface GigabitEthernet 1/0/2.
[Sysname] scheduler job start-GigabitEthernet1/0/2
[Sysname-job-start-GigabitEthernet1/0/2] command 1 system-view
[Sysname-job-start-GigabitEthernet1/0/2] command 2 interface gigabitethernet 1/0/2
[Sysname-job-start-GigabitEthernet1/0/2] command 3 undo shutdown
[Sysname-job-start-GigabitEthernet1/0/2] quit
# Configure a periodic schedule for enabling the interfaces at 8:00 a.m. every Monday through Friday.
[Sysname] scheduler schedule START-pc1/pc2
[Sysname-schedule-START-pc1/pc2] job start-GigabitEthernet1/0/1
[Sysname-schedule-START-pc1/pc2] job start-GigabitEthernet1/0/2
[Sysname-schedule-START-pc1/pc2] time repeating at 8:00 week-day mon tue wed thu fri
[Sysname-schedule-START-pc1/pc2] quit
# Configure a periodic schedule for disabling the interfaces at 18:00 every Monday through Friday.
[Sysname] scheduler schedule STOP-pc1/pc2
[Sysname-schedule-STOP-pc1/pc2] job shutdown-GigabitEthernet1/0/1
[Sysname-schedule-STOP-pc1/pc2] job shutdown-GigabitEthernet1/0/2
[Sysname-schedule-STOP-pc1/pc2] time repeating at 18:00 week-day mon tue wed thu fri
[Sysname-schedule-STOP-pc1/pc2] quit
Verifying the configuration
# Display the configuration information of all jobs.
[Sysname] display scheduler job
Job name: shutdown-GigabitEthernet1/0/1
system-view
interface gigabitethernet 1/0/1
shutdown
Job name: shutdown-GigabitEthernet1/0/2
system-view
interface gigabitethernet 1/0/2
shutdown
Job name: start-GigabitEthernet1/0/1
system-view
interface gigabitethernet 1/0/1
undo shutdown
Job name: start-GigabitEthernet1/0/2
system-view
interface gigabitethernet 1/0/2
undo shutdown
# Display the schedule information.
[Sysname] display scheduler schedule
Schedule name : START-pc1/pc2
Schedule type : Run on every Mon Tue Wed Thu Fri at 08:00:00
Start time : Wed Sep 28 08:00:00 2011
Last execution time : Wed Sep 28 08:00:00 2011
Last completion time : Wed Sep 28 08:00:03 2011
Execution counts : 1
-----------------------------------------------------------------------
Job name Last execution status
start-GigabitEthernet1/0/1 Successful
start-GigabitEthernet1/0/2 Successful
Schedule name : STOP-pc1/pc2
Schedule type : Run on every Mon Tue Wed Thu Fri at 18:00:00
Start time : Wed Sep 28 18:00:00 2011
Last execution time : Wed Sep 28 18:00:00 2011
Last completion time : Wed Sep 28 18:00:01 2011
Execution counts : 1
-----------------------------------------------------------------------
Job name Last execution status
shutdown-GigabitEthernet1/0/1 Successful
shutdown-GigabitEthernet1/0/2 Successful
# Display schedule log information.
[Sysname] display scheduler logfile
Job name : start-GigabitEthernet1/0/1
Schedule name : START-pc1/pc2
Execution time : Wed Sep 28 08:00:00 2011
Completion time : Wed Sep 28 08:00:02 2011
--------------------------------- Job output -----------------------------------
<Sysname>system-view
System View: return to User View with Ctrl+Z.
[Sysname]interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1]undo shutdown
Job name : start-GigabitEthernet1/0/2
Schedule name : START-pc1/pc2
Execution time : Wed Sep 28 08:00:00 2011
Completion time : Wed Sep 28 08:00:02 2011
--------------------------------- Job output -----------------------------------
<Sysname>system-view
System View: return to User View with Ctrl+Z.
[Sysname]interface gigabitethernet 1/0/2
[Sysname-GigabitEthernet1/0/2]undo shutdown
Job name : shutdown-GigabitEthernet1/0/1
Schedule name : STOP-pc1/pc2
Execution time : Wed Sep 28 18:00:00 2011
Completion time : Wed Sep 28 18:00:01 2011
--------------------------------- Job output -----------------------------------
<Sysname>system-view
System View: return to User View with Ctrl+Z.
[Sysname]interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1]shutdown
Job name : shutdown-GigabitEthernet1/0/2
Schedule name : STOP-pc1/pc2
Execution time : Wed Sep 28 18:00:00 2011
Completion time : Wed Sep 28 18:00:01 2011
--------------------------------- Job output -----------------------------------
<Sysname>system-view
System View: return to User View with Ctrl+Z.
[Sysname]interface gigabitethernet 1/0/2
[Sysname-GigabitEthernet1/0/2]shutdown
Rebooting the device
About device reboot
The following device reboot methods are available:
· Schedule a reboot at the CLI, so the device automatically reboots at the specified time or after the specified period of time.
· Immediately reboot the device at the CLI.
During the reboot process, the device performs the following operations:
a. Resets all of its chips.
b. Uses the BootWare to verify the startup software package, decompress the package, and load the images.
c. Initializes the system.
· Power off and then power on the device. This method might cause data loss, and is the least-preferred method.
Using the CLI, you can reboot the device from a remote host.
Restrictions and guidelines for device reboot
For data security, the device does not reboot while it is performing file operations.
Rebooting devices immediately at the CLI
Prerequisites
Perform the following steps in any view:
1. Verify that the next-startup configuration file is correctly specified.
display startup
For more information about the display startup command, see Fundamentals Command Reference.
2. Verify that the startup image files are correctly specified.
display boot-loader
If one main startup image file is damaged or does not exist, you must specify another main startup image file before rebooting the device.
For more information about the display boot-loader command, see Fundamentals Command Reference.
3. Save the running configuration to the next-startup configuration file.
save
To avoid configuration loss, save the running configuration before a reboot.
For more information about the save command, see Fundamentals Command Reference.
Procedure
To reboot the device immediately at the CLI, execute one of the following commands in user view:
In standalone mode:
reboot [ slot subslot-number ] [ force ]
In IRF mode:
reboot [ slot slot-number [ subslot subslot-number ] ] [ force ]
CAUTION: · A device reboot might result in service interruption. Use this command with caution. · Use the force keyword to reboot the device only when the system is faulty or fails to start up normally. A forced device reboots might cause file system damage. Before using the force keyword to reboot the device, make sure you understand its impact. |
Scheduling a device reboot
Restrictions and guidelines
(In IRF mode.) The automatic reboot configuration takes effect on all member devices. It will be canceled if a master/subordinate switchover occurs.
The device supports only one device reboot schedule. If you execute the scheduler reboot command multiple times, the most recent configuration takes effect.
Procedure
To schedule a reboot, execute one of the following commands in user view:
· scheduler reboot at time [ date ]
· scheduler reboot delay time
By default, no device reboot time is specified.
CAUTION: A device reboot might result in service interruption. Use this command with caution. |
Restoring the factory-default configuration
About this task
If you want to use the device in a different scenario or you cannot troubleshoot the device by using other methods, use this task to restore the factory-default configuration.
This task does not delete .bin files and license files.
Restrictions and guidelines
Procedure
To restore the factory-default configuration for the device, execute the following command in user view:
restore factory-default
CAUTION: This command restores the device to the factory default settings. Use this command with caution. |
Enabling PTP packet acceleration
About PTP packet acceleration
Enabling PTP packet acceleration improves PTP packet forwarding speed and reduces PTP packet transmission delay and jitter.
Hardware and feature compatibility
Hardware |
Feature compatibility |
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK |
No |
MSR810-LMS, MSR810-LUS |
No |
MSR810-LMS-EA, MSR810-LME |
No |
MSR1004S-5G |
No |
MSR2600-6-X1, MSR2600-15-X1 |
Yes |
MSR2600-10-X1 |
No |
MSR 2630 |
No |
MSR3600-28, MSR3600-51 |
No |
MSR3600-28-SI, MSR3600-51-SI |
No |
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
No |
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG |
Yes |
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1 |
Yes |
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3660 |
No |
MSR 3640 |
Yes |
MSR3610-G, MSR3620-G |
No |
MSR3640-X1-HI |
Yes |
Hardware |
Feature compatibility |
MSR810-W-WiNet, MSR810-LM-WiNet |
No |
MSR830-4LM-WiNet |
No |
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet |
No |
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet |
No |
MSR2600-6-WiNet |
Yes |
MSR2600-10-X1-WiNet |
No |
MSR2630-WiNet |
No |
MSR3600-28-WiNet |
No |
MSR3610-X1-WiNet |
Yes |
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet |
No |
Hardware |
Feature compatibility |
MSR2630-XS |
Yes |
MSR3600-28-XS |
No |
MSR3610-XS |
Yes |
MSR3620-XS |
No |
MSR3610-I-XS |
Yes |
MSR3610-IE-XS |
Yes |
MSR3620-X1-XS |
Yes |
MSR3640-XS |
Yes |
MSR3660-XS |
Yes |
Hardware |
Feature compatibility |
MSR810-LM-GL |
No |
MSR810-W-LM-GL |
No |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
No |
MSR830-10HI-GL |
Yes |
MSR1004S-5G-GL |
No |
MSR2600-6-X1-GL |
Yes |
MSR3600-28-SI-GL |
No |
Procedure
1. Enter system view.
system-view
2. Enable PTP packet acceleration.
ptp acceleration enable
By default, PTP packet acceleration is disabled.
Display and maintenance commands for device management configuration
IMPORTANT: · Support for the display device, display fan, display environment, and display system-working-mode commands depends on the device model. For more information, see device management in Fundamentals Command Reference. · Support for the cf-card, harddisk, sd-card, and usb keywords in the display device command depends on the device model. For more information, see device management in Fundamentals Command Reference. |
Execute display commands in any view. Execute the reset scheduler logfile command in user view. Execute the reset version-update-record command in system view.
Task |
Command |
Display device alarm information. |
In standalone mode: display alarm [ slot slot-number ] In IRF mode: display alarm [ slot slot-number ] |
Display the system time, date, time zone, and daylight saving time. |
display clock |
Display the copyright statement. |
display copyright |
Display CPU usage statistics. |
In standalone mode: display cpu-usage [ summary ] [ cpu cpu-number [ core { core-number | all } ] ] display cpu-usage [ control-plane | data-plane ] [ summary ] In IRF mode: display cpu-usage [ summary ] [ slot slot-number [ cpu cpu-number [ core { core-number | all } ] ] ] display cpu-usage [ control-plane | data-plane ] [ summary ] [ slot slot-number [ cpu cpu-number ] ] |
Display CPU usage monitoring settings. |
In standalone mode: display cpu-usage configuration In IRF mode: display cpu-usage configuration [ slot slot-number [ cpu cpu-number ] ] |
Display the historical CPU usage statistics in a coordinate system. |
In standalone mode: display cpu-usage history [ job job-id ] In IRF mode: display cpu-usage history [ job job-id ] [ slot slot-number [ cpu cpu-number ] ] |
Display hardware information. |
In standalone mode: display device [ cf-card | harddisk | sd-card | usb ] [ slot subslot-number | verbose ] In IRF mode: display device [ cf-card | harddisk | sd-card | usb ] [ slot slot-number [ subslot subslot-number ] | verbose ] |
Display electronic label information for the device. |
In standalone mode: display device manuinfo In IRF mode: display device manuinfo [ slot slot-number ] |
Display or save operating information for features and hardware modules. |
display diagnostic-information [ hardware | infrastructure | l2 | l3 | service ] [ key-info ] [ filename ] |
Display device temperature information. |
In standalone mode: display environment In IRF mode: display environment [ slot slot-number ] |
Display the operating states of fan trays. |
In standalone mode: display fan [ fan-id ] In IRF mode: display fan [ slot slot-number [ fan-id ] ] |
Display memory usage statistics. |
In standalone mode: display memory [ summary ] In IRF mode: display memory [ summary ] [ slot slot-number [ cpu cpu-number ] ] |
Display memory alarm thresholds and statistics. |
In standalone mode: display memory-threshold In IRF mode: display memory-threshold [ slot slot-number [ cpu cpu-number ] ] |
Display power supply information. |
In standalone mode: display power [ verbose ] In IRF mode: display power [ slot slot-number [ verbose ] ] |
Display power supply management information. |
In standalone mode: display power-supply [ verbose ] In IRF mode: display power-supply [ slot slot-number ] [ verbose ] |
Display resource monitoring information. |
In standalone mode: display resource-monitor [ resource resource-name ] [ cpu cpu-number ] In IRF mode: display resource-monitor [ resource resource-name ] [ slot slot-number [ cpu cpu-number ] ] |
Display job configuration information. |
display scheduler job [ job-name ] |
Display job execution log information. |
display scheduler logfile |
Display the automatic reboot schedule. |
display scheduler reboot |
Display schedule information. |
display scheduler schedule [ schedule-name ] |
Display system stability and status information. |
display system stable state |
Display system working mode information. |
display system-working-mode |
Display system version information. |
display version |
Display startup software image upgrade records. |
display version-update-record |
Clear job execution log information. |
reset scheduler logfile |
Clear startup software image upgrade records. |
reset version-update-record |