Non-default vSytems support only the display cpu-usage configuration and display memory-threshold commands. For more information about vSystem, see Virtual Technologies Configuration Guide.

When the system is not stable, do not perform any operation on the device (such as active and standby switchover or device reboot). To determine whether the system is in stable state, execute the display system stable state command.

Device management tasks at a glance

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

· Configuring basic parameters

¡ Configuring the device name

¡ Configuring the system ID

¡ Configuring the system time

¡ Enabling displaying the copyright statement

¡ Configuring banners

· Configuring security parameters

¡ Disabling password recovery capability

¡ Disabling BootWare menu access

· Adjusting device capacities

¡ Setting the port status detection timer

¡ Enabling flows to be hashed across CPU cores based on the inner-layer fields of packets

· Monitoring the device

¡ Enabling FPGA chips to send high-priority packets to the CPU

¡ Monitoring CPU usage

¡ Monitoring CPU core usage

¡ Monitoring CPU status

¡ Setting memory alarm thresholds

¡ Monitoring DMA memory

¡ Configuring resource monitoring

¡ Setting the temperature alarm thresholds

· Managing resources

¡ Verifying and diagnosing transceiver modules

¡ Enabling USB interfaces on service modules from providing power

¡ Enabling a switching fabric module to distribute traffic to multiple IRF interface modules

¡ Enabling IRF physical interface splitting

¡ Configuring CRC error check on inner interfaces of service modules

· Maintaining the device

¡ Scheduling a task

¡ Locating devices

¡ Rebooting the device

¡ Restoring the factory-default configuration

¡ Enabling the device to register with the China Mobile management platform

¡ Enabling the device to register with the China Telecom esurfing management platform

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

2. Configure the device name.

sysname sysname

By default, the device name is H3C.

By default, the device name is NEC.

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.

This feature is supported only on the default context. All contexts on the device use the same system time.

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

2. (Optional.) Setting the time zone

Make sure each network device uses the time zone of the place where the device resides.

3. (Optional.) Setting the daylight saving time

Make sure each network device uses the daylight saving time parameters of the place where the device resides.

Setting the system time at the CLI

1. Enter system view.

system-view

2. Configure the device to use the local system time.

clock protocol none

By default, the device uses NTP to obtain the UTC time on the default context.

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:

This command changes the system time, which affects the 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). Before executing this command, make sure you fully understand its impact on your live network.

‌

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 context context-id

By default, the device uses the NTP time source specified on the default context.

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.

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 time zone is GMT+08:00.

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 user quits user view. This is because the device automatically tries to restart the user session.

If you disable displaying the copyright statement, the device does not display the copyright statement in any situations.

Procedure

1. Enter system view.

system-view

2. Enable displaying the copyright statement.

By default, displaying the copyright statement is enabled.

Configuring banners

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

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

· Shell banner—Appears before the user enters user view.

The system displays the banners in the following order: legal banner, MOTD banner, login banner, and shell banner.

Banner input methods

You can configure a banner by using one of the following methods:

· Input the entire command line in a single line.

The banner cannot contain carriage returns. The entire command line, including the command keywords, the banner, and the delimiters, can have a maximum of 511 characters. The delimiters for the banner can be any printable character but must be the same. You cannot press Enter before you input the end delimiter.

For example, you can configure the shell banner "Have a nice day." as follows:

<System> system-view

[System] header shell %Have a nice day.%

· Input the command line in multiple lines.

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

To input a banner configuration command line in multiple lines, use one of the following methods:

¡ Press Enter after the final command keyword, type the banner, and end the final line with the delimiter character %. The banner plus the delimiter can have a maximum of 1999 characters.

For example, you can configure the banner "Have a nice day." as follows:

<System> system-view

[System] header shell

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

Have a nice day.%

¡ After you type the final command keyword, type any printable character as the start delimiter for the banner and press Enter. Then, type the banner and end the final line with the same delimiter. The banner plus the end delimiter can have a maximum of 1999 characters.

For example, you can configure the banner "Have a nice day." as follows:

<System> system-view

[System] header shell A

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

Have a nice day.A

¡ After you type the final command keyword, type the start delimiter and part of the banner. Make sure the final character of the final string is different from the start delimiter. Then, press Enter, type the rest of the banner, and end the final line with the same delimiter. The banner plus the start and end delimiters can have a maximum of 2002 characters.

For example, you can configure the banner "Have a nice day." as follows:

<System> system-view

[System] header shell AHave a nice day.

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

Procedure

1. ‍Enter system view.

system-view

2. Configure the legal banner.

header legal text

3. Configure the MOTD banner.

header motd text

4. Configure the login banner.

header login text

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

Restrictions and guidelines

This feature is supported only on the default context.

To access the device configuration without authentication, you must connect to the active MPU and access the BootWare menu while the MPU is starting up.

In an IRF fabric, the password-recovery enable command will not take effect when used directly for password recovery. You must first split the IRF fabric, clear the authentication password from the BootWare menu, and then re-access the system to rebuild the IRF fabric. For more information about IRF, see IRF configuration in Virtual Technologies Configuration Guide.

Procedure

1. ‍Enter system view.

system-view

2. Disable password recovery capability.

undo password-recovery enable

By default, password recovery capability is enabled.

Disabling BootWare menu access

About this task

By default, anyone can press Ctrl+B during device startup to access the BootWare menu, load software, and manage storage media. To prevent unauthorized access, disable BootWare menu access.

Restrictions and guidelines

This feature is supported only on the default context.

Procedure

To disable BootWare menu access, execute the following command in user view:

undo bootrom-access enable

By default, access to the BootWare menu is enabled.

Setting the load mode for MPUs

About this task

The device supports the following MPU load modes:

· load-balance—The MPUs share the load to process and forward packets.

· load-single—Only the active MPU processes and forwards packets. The standby MPUs back up data and monitor the status of the active MPU.

Restrictions and guidelines

This feature is supported only on the default context.

A single-MPU device supports only the load-single mode. If you set the MPU load mode to load-balance, the device automatically switches to load-single mode.

Procedure

1. Enter system view.

system-view

2. Set the load mode for MPUs.

In standalone mode:

xbar { load-balance | load-single }

In IRF mode:

xbar chassis chassis-number { load-balance | load-single }

By default, MPUs operate in load-balance mode.

Enabling forwarding acceleration for a card

About this task

Enabling forwarding acceleration improves forwarding performance.

Restrictions and guidelines

IMPORTANT:

Use this feature under the guidance of H3C Support. Enabling this feature on multiple cards might cause traffic bursts on switching fabric modules and result in packet loss.

‌

This feature is supported only on the default context.

The configuration for a card takes effect after the card reboots.

Procedure

1. Enter system view.

system-view

2. Enable forwarding acceleration for a card.

In standalone mode:

accelerate slot slot-number

In IRF mode:

accelerate chassis chassis-number slot slot-number

By default, forwarding acceleration is disabled for all cards.

Setting the port status detection timer

About this task

On a network enabled with loopback detection or STP, the device starts a port status detection timer when a port is shut down by a protocol. Once the timer expires, the system restores the port to its real physical status. You can use this task to set the port status detection timer.

Procedure

1. Enter system view.

system-view

2. Set the port status detection timer.

shutdown-interval time

The default setting is 30 seconds.

Enabling flows to be hashed across CPU cores based on the inner-layer fields of packets

About this task

To hash QinQ, GRE, IPinIP, and PPPoE packets across CPU cores based on their inner-layer fields such as their inner source IP and destination IP, perform this task.

Procedure

1. Enter system view.

system-view

2. Enable the device to hash flows across CPU cores based on the inner-layer fields of packets.

hardware forwarding hash-inner enable

By default, the device does not hash flows across CPU cores based on the inner-layer fields of packets.

Enabling FPGA chips to send high-priority packets to the CPU

Restrictions and guidelines

The sending of high-priority packets from the FPGA chips to the CPU on the service module might cause packet loss on the FPGA chips. You need to disable the FPGA chips from sending high-priority packets to the CPU as needed.

Procedure

To enable the FPGA chips to send high-priority packets to the CPU, execute one of the following commands in user view:

In standalone mode:

archer high-priority to-cpu enable chip chip-number slot slot-number subslot-number cpu cpu-number

In IRF mode:

archer high-priority to-cpu enable chip chip-number chassis chassis-number slot slot-number subslot-number cpu cpu-number

By default, the FPGA chips send high-priority packets to the CPU.

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 (recovery threshold supported)

‌

Procedure

1. ‍Enter system view.

system-view

2. Set the CPU usage alarm thresholds.

In standalone mode:‌

monitor cpu-usage threshold severe-threshold recovery-threshold recovery-threshold [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

monitor cpu-usage threshold severe-threshold recovery-threshold recovery-threshold [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

The CPU usage alarm thresholds vary by service module type. To view the default CPU usage thresholds, execute the undo monitor cpu-usage threshold command to restore the default, and then execute the display cpu-usage configuration command.

CAUTION:

If you set the severe CPU usage alarm threshold to a too 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 [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

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

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

4. Enable CPU usage tracking.

‌In standalone mode:

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

In IRF mode:

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

By default, CPU usage tracking is enabled.

Monitoring CPU core usage

About this task

The device samples CPU core usage at 5-second intervals and calculates the average value during each CPU core usage statistics interval. If the value during an interval is greater than the CPU core usage threshold, the device issues an alarm and logs the event.

Restrictions and guidelines

As a best practice, set this argument to a multiple of the sampling interval, which is fixed at 5 seconds. If you do not do so, the actual statistics interval is the biggest multiple of the sampling interval that is smaller than the setting. For example, if you set this argument to 12 seconds, the actual statistics interval is 10 seconds.

Procedure

1. Enter system view.

system-view

2. Set CPU core usage statistics intervals.

In standalone mode:‌

monitor cpu-usage statistics-interval interval slot slot-number cpu cpu-number core core-id-list

In IRF mode:

monitor cpu-usage statistics-interval interval chassis chassis-number slot slot-number cpu cpu-number core core-id-list

By default, the CPU core usage statistics interval is 60 seconds.

3. Set CPU core alarm resending intervals.

In standalone mode:‌

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

In IRF mode:

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

By default, the CPU core alarm resending interval is 300 seconds.

Monitoring CPU status

About CPU status monitoring

This feature enables the device to monitor the following items:

· Whether the CPUs are receiving or sending packets correctly.

· Whether the PCI buses are operating correctly.

If the device detects an error, it generates a log message and issues an alarm.

Procedure

1. Enter system view.

system-view

2. Enable CPU forwarding status monitoring in the outbound direction.

monitor cpu-tx-status

By default, CPU forwarding status monitoring is disabled in the outbound direction.

3. Enable CPU forwarding status monitoring in the inbound direction.

monitor cpu-rx-status

By default, CPU forwarding status monitoring is disabled in the inbound direction.

4. Enable PCI bus monitoring.

monitor cpu-pci-status

By default, PCI bus monitoring is disabled.

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.

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

This feature is supported only on the default context.

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.

The system will restart a card if one of the following conditions is met:

· After a critical alarm occurs, the remaining free-memory value has been smaller than the critical alarm threshold for 30 seconds.

· The interval between two consecutive critical alarms is shorter than 30 seconds.

· The critical alarm has occurred three times within three minutes.

· After a critical alarm occurs, the system will periodically sample free memory space and predict if the free memory space will be exhausted within 30 seconds. If the prediction result indicates that the free memory space will be exhausted within 30 seconds, the system will restart the card.

Once the free memory space reaches the early warning, minor, severe, or critical alarm threshold, the device will display the current memory usage information when you log in to the device through console or Telnet login, or execute every command.

Procedure

1. ‍Enter system view.

system-view

2. Set the memory usage threshold.

‌In standalone mode:

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

In IRF mode:

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

By default, the memory usage threshold is 90%.

3. Set the free-memory thresholds.

In standalone mode:‌

memory-threshold [ slot slot-number [ cpu cpu-number ] ] [ ratio ] minor minor-value severe severe-value critical critical-value normal normal-value [ early-warning early-warning-value secure secure-value ]

In IRF mode:

memory-threshold [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ ratio ] minor minor-value severe severe-value critical critical-value normal normal-value [ early-warning early-warning-value secure secure-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.

Monitoring DMA memory

About this task

To ensure correct operation of services that use Direct Memory Access (DMA) memory, the system monitors the amount of free DMA memory space regularly. If the amount of free DMA memory space decreases to or below the alarm threshold, the system generates a notification that the DMA memory space is insufficient. If the amount of free DMA memory space increases above the normal state threshold, the system generates a notification that the DMA memory space is sufficient.

DMA memory alarm notifications are sent to NETCONF, SNMP, and the information center to be encapsulated as NETCONF events, SNMP traps and informs, and log messages. For more information about NETCONF, SNMP, and information center, see Network Management and Monitoring Configuration Guide.

Procedure

1. ‍Enter system view.

system-view

2. Set the DMA memory thresholds.

In standalone mode:‌

memory-threshold dma [ slot slot-number [ cpu cpu-number ] ] [ ratio ] critical critical-value normal normal-value

In IRF mode:

memory-threshold dma [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ ratio ] critical critical-value normal normal-value

The default settings vary by device model.

3. Set the DMA memory alarm resending interval.

In standalone mode:‌

monitor resend memory-threshold dma critical-interval critical-interval [ slot slot-number [ cpu cpu-number ] ]

undo monitor resend memory-threshold dma critical-interval [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

monitor resend memory-threshold dma critical-interval critical-interval [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

undo monitor resend memory-threshold dma critical-interval [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

The default settings vary by device model.

Configuring resource monitoring

Monitoring the total inbound bandwidth usage

About this task

If the total inbound traffic remains greater than or equal to the total inbound bandwidth usage threshold for the specified duration, the device sends an alarm. If the alarm state persists, the device resends the alarm at 5-second intervals.

Restrictions and guidelines

This feature is supported only on the default context.

Procedure

1. Enter system view.

system-view

2. Set the total inbound bandwidth usage threshold.

monitor resource-usage bandwidth inbound threshold threshold-value [ duration duration-value ]

By default, the total inbound bandwidth usage threshold is not set. The bandwidth usage alarm feature is disabled.

Monitoring the aggregate interface usage

About this task

When the number of created Layer 2 or Layer 3 aggregate interfaces reaches the aggregate interface usage threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 3-hour intervals.

Procedure

1. Enter system view.

system-view

2. Set aggregate interface usage thresholds.

monitor resource-usage { bridge-aggregation | route-aggregation } threshold threshold-value

By default, no aggregate interface usage thresholds are set. The aggregate interface usage alarm feature is disabled.

Monitoring the inner interface throughput

About this task

When the inner interface throughput reaches the threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 10-minute intervals.

Restrictions and guidelines

This feature is supported only on the default context.

Procedure

1. Enter system view.

system-view

2. Set the inner interface throughput threshold.

monitor resource-usage blade-throughput threshold threshold-value

By default, the inner interface throughput threshold is not set. The inner interface throughput alarm feature is disabled.

Monitoring the number of contexts

About this task

This feature monitors both the total number of contexts created on the device and the number of contexts in each security engine group.

When the total number of contexts created on the device reaches the global context usage threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 6-hour intervals.

After you enable monitoring of the number of contexts in each security engine group, the device regularly monitors the number of contexts in each security engine group.

The device supports a minor alarm threshold and a severe alarm threshold.

· When the number of contexts in a security engine group increases to or above the minor alarm threshold, the security engine group enters minor alarm state and issues a minor alarm.

· When the number of contexts in a security engine group increases to or above the severe alarm threshold, the security engine group enters severe alarm state and issues a severe alarm.

· When the number of contexts in a security engine group decreases below the severe alarm threshold, the team enters minor alarm state and issues a severe-alarm-removed notification.

· When the number of contexts in a security engine group decreases below the minor alarm threshold, the team issues a minor-alarm-removed notification.

· If the security engine group stays in minor alarm state, the device resends minor alarms at 6-hour intervals. If the security engine group stays in severe alarm state, the device resends severe alarms at 6-hour intervals.

For more information about security engine groups, see context configuration in Virtual Technologies Configuration Guide.

Restrictions and guidelines

This feature is supported only on the default context.

The alarm thresholds for security engine groups are fixed and cannot be changed. You can view the thresholds by reading alarm messages.

Procedure

1. Enter system view.

system-view

2. Set the global context usage threshold.

monitor resource-usage context threshold threshold-value

By default, the global context usage threshold is not set. The global context usage alarm feature is disabled.

3. Enable monitoring of the number of contexts in each security engine group.

monitor resource-usage blade-controller-team context

By default, monitoring of the number of contexts in each security engine group is disabled.

Monitoring the number of NAT mappings

About this task

When the number of NAT mappings reaches the NAT mapping threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 3-hour intervals.

In the current software version, this feature counts only static NAT mappings and effective NAT server mappings. To display the status of NAT server mappings, execute the display nat server command.

Procedure

1. Enter system view.

system-view

2. Set the NAT mapping threshold.

monitor resource-usage nat threshold threshold-value

By default, the NAT mapping threshold is not set. The NAT mapping alarm feature is disabled.

Monitoring the QACL resource usage

About this task

When the QACL resource usage reaches the QACL resource usage threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 3-hour intervals.

Restrictions and guidelines

This feature is supported only on the default context.

Procedure

1. Enter system view.

system-view

2. Set the QACL resource usage threshold.

monitor resource-usage qacl threshold threshold-value

By default, the QACL resource usage threshold is not set. The QACL resource usage alarm feature is disabled.

Monitoring the number of security policy rules

About this task

When the number of created security policy rules reaches the security policy rule usage threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 6-hour intervals.

Procedure

1. Enter system view.

system-view

2. Set security policy rule usage thresholds.

monitor resource-usage security-policy { ip | ipv6 } threshold threshold-value

By default, no security policy rule thresholds are set. The security policy rule alarm feature is disabled.

Monitoring the number of sessions

About this task

When the number of sessions reaches the session usage threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 10-minute intervals.

Procedure

1. Enter system view.

system-view

2. Set the session usage threshold.

In standalone mode:‌

monitor resource-usage session-count [ slot slot-number cpu cpu-number ] threshold threshold-value

In IRF mode:

monitor resource-usage session-count [ chassis chassis-number slot slot-number cpu cpu-number ] threshold threshold-value

By default, no session usage thresholds are set. The session usage alarm feature is disabled.

Monitoring the session establishment rate

About this task

When the session establishment rate reaches the threshold, the device sends an alarm. If the alarm state persists, the device resends the alarm at 10-minute intervals.

Procedure

1. Enter system view.

system-view

2. Set the session establishment rate threshold.

In standalone mode:‌

monitor resource-usage session-rate [ slot slot-number cpu cpu-number ] threshold threshold-value

In IRF mode:

monitor resource-usage session-rate [ chassis chassis-number slot slot-number cpu cpu-number ] threshold threshold-value

By default, no session establishment rate thresholds are set. The session establishment rate alarm feature is disabled.

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

‌

Restrictions and guidelines

This feature is supported only on the default context.

Procedure

1. Enter system view.

system-view

2. Set resource depletion thresholds.

In standalone mode:‌

resource-monitor resource resource-name slot slot-number cpu cpu-number by-percent minor-threshold minor-threshold severe-threshold severe-threshold

In IRF mode:

resource-monitor resource resource-name chassis chassis-number slot slot-number cpu cpu-number 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, resource depletion alarms are sent to NETCONF, SNMP, and 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.

Setting the temperature alarm thresholds

About this task

The device monitors its temperature based on the following thresholds:

· Low-temperature threshold.

· High-temperature warning threshold.

· High-temperature alarming threshold.

When the device temperature drops below the low-temperature threshold or reaches the high-temperature warning or alarming threshold, the device performs the following operations:

· Sends log messages and traps.

· Sets LEDs on the device panel.

Restrictions and guidelines

This feature is supported only on the default context.

Procedure

1. ‍Enter system view.

system-view

2. Configure the temperature alarm thresholds.

In standalone mode:

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

In IRF mode:

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

The defaults vary by temperature sensor model. To view the defaults, execute the undo temperature-limit and display environment commands in turn.

The high-temperature alarming threshold must be higher than the high-temperature warning threshold, and the high-temperature warning threshold must be higher than the low-temperature threshold.

Configuring hardware failure detection and protection

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

Specifying the actions to be taken for hardware failures

About this task

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

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

¡ Shuts down the relevant ports.

¡ Prohibits loading software for the relevant cards.

¡ Isolates the relevant cards.

¡ Powers off the relevant cards.

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

· warning—Sends traps to report the failures.

Restrictions and guidelines

You can configure this feature only on the default context. However, the configuration takes effect on all contexts.

Procedure

1. Enter system view.

system-view

2. Specify the action to be taken in response to a type of hardware failures.

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

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

Enabling hardware failure protection for interfaces

About this task

After you enable hardware failure protection on an interface, the system automatically shuts down the interface when it detects a hardware failure on the interface. An interface shut down this way is in Protect Down state.

Restrictions and guidelines

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

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

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

Procedure

1. Enter system view.

system-view

2. Set the action to be taken in response to failures on the forwarding plane to isolate.

hardware-failure-detection forwarding isolate

By default, the system takes the action of warning (sending traps) in response to forwarding-plane failures.

This command is supported only on the default context.

3. Enter Ethernet interface view.

interface interface-type interface-number

4. Enable hardware failure protection for the interface.

hardware-failure-protection auto-down

By default, hardware failure protection is enabled.

Enabling hardware failure protection for aggregation groups

About this task

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

· Shuts down the interface if the undo hardware-failure-protection auto-down command is executed on the interface, and the interface is not the only member in up state in the group.

· Does not shut down the interface if the undo hardware-failure-protection auto-down command is executed on the interface, and the interface is the only member in up state in the group.

· Shuts down the interface if the hardware-failure-protection auto-down command is executed on the interface, no matter whether the interface is the only member in up state in the group.

Procedure

1. Enter system view.

system-view

2. Set the action to be taken in response to failures on the forwarding plane to isolate.

hardware-failure-detection forwarding isolate

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

This command is supported only on the default context.

3. (Optional.) Disable hardware failure protection for a member interface in the aggregation group.

a. Enter Ethernet interface view.

interface interface-type interface-number

b. Disable hardware failure protection for the interface.

undo hardware-failure-protection auto-down

By default, hardware failure protection is enabled.

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

c. Exit to system view.

quit

4. Enable hardware failure protection for aggregation groups.

hardware-failure-protection aggregation

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

This command is supported only on the default context.

Configuring fault monitoring

About this task

Fault monitoring enables the system to monitor the health status of cards in real time. If a hardware fault occurs on a card, the system will attempt to recover the card by restarting it. By default, if the fault still persists after the card restarts three times consecutively at intervals of equal to or shorter than 30 minutes, the system will immediately isolate the faulty card.

Restrictions and guidelines

The device supports only restarting faulty service subcards and does not isolate faulty service subcards.

Procedure

1. Enter system view.

system-view

2. Enable fault monitoring and set the number of card restarts before the device isolates a faulty card.

monitor fault reboot-number reboot-number

By default, fault monitoring is enabled and the number of card restarts before the device isolates a faulty card is set to three.

Configuring electronic label monitoring

About this task

This feature allows the system to monitor the electronic label status of cards at the specified periods. If an electronic label of a card is found to be missing, the system will generate a log message and a trap.

Hardware and feature compatibility

series	Models	Feature compatibility
M9000 series	M9006, M9010, M9014, M9016-V	Yes
M9000-S series	M9008-S, M9008-S-V	Yes
M9000-AK series	M9000-AK001	Yes
M9000-AI-E series	M9000-AI-E4	Yes
M9000-AI-E series	M9000-AI-E8, M9000-AI-E16	Yes
M9000-X series	M9000-X06, M9000-X06-B, M9000-X06-B-G, M9000-X06-G, M9000-X10	Yes
M9000-AI-X series	M9000-AI-X06, M9000-AI-X10	Yes
M9000-CN series	M9000-CN04	No

Procedure

1. Enter system view.

system-view

2. Enable electronic label monitoring and specify the monitoring period.

monitor manuinfo period period-value

By default, electronic label monitoring is disabled.

Configuring auto card recovery from a fault

About this task

This feature enables a card to automatically restart to recover from a fault when the fault duration reaches the threshold. By default, a card will restart if the duration of a fault on the card reaches 120 minutes. By default, a faulty card first performs three warm restarts. If the fault persists, the faulty card will perform one cold restart.

Procedure

1. ‍Enter system view.

system-view

2. Enable a card to automatically restart to recover from a fault.

monitor fault-timer reboot enable

By default, a card can automatically restart to recover from a fault.

3. Configure the minimum fault duration on a card that can trigger card restarts.

monitor fault-timer reboot-duration duration-value

By default, the minimum fault duration on a card that can trigger card restarts is 120 minutes.

4. Specify the number of warm restarts for a faulty card.

monitor fault-timer warm-reboot warm-reboot-number

By default, the number of warm restarts for a faulty card is three.

Configuring GOLD notifications

About this task

Configure this feature to enable or disable types of notifications sent by GOLD.

Procedure

1. Enter system view.

system-view

2. Enable GOLD notifications.

By default, GOLD notifications are enabled.

Configuring health value reporting on check items of GOLD

About this task

The device periodically executes a series of checks to monitor its health status. Use this command to customize the check items whose health values will be reported. You can execute the display system health command to the health values reported for the specified check items.

Procedure

1. Enter system view.

system-view

2. Enable health value reporting on check items of GOLD.

By default, health value reporting on check items of GOLD is enabled.

Configuring fault recovery by GOLD

About this task

Enable this feature to automatically perform fault recovery on faulty modules. In the current software version, this feature supports only faulty recovery on errors that occur on a subcard port that connects to an interface switch module. When GOLD detects errors on a subcard port connected to an interface switch module three times consecutively, GOLD will restart the interface switch module to perform fault recovery.

Procedure

1. Enter system view.

system-view

2. Enable fault recovery by GOLD.

gold recover-action [ fmea-port ] enable

By default, fault recovery by GOLD is enabled.

Monitoring FPGA NICs for packet loss events

About this task

Use this feature to monitor NICs for packet loss events when you troubleshoot packet loss issues or optimize network performance. By monitoring packet loss events on NICs, this feature helps you accurately identify the cause of issues, such as network congestion, hardware failure, or misconfiguration.

This feature detects packet loss events on each applicable NIC regularly at specified detection intervals.

· When the number of consecutive packet loss events detected on a NIC reaches the specified logging threshold within a logging interval, the device generates a diagnostic log.

· When the number of consecutive packet loss events detected on a NIC reaches the specified alarm threshold within an alarm interval, the device sends an SNMP notification.

Restrictions and guidelines

This feature is available only if the device has security service modules such as Blade VI modules.

Procedure

1. Enter system view.

system-view

2. Enable FPGA NIC packet loss logging on a card.

monitor pktdrop-nic [ interval value ] [ log [ interval value ] [ threshold value ] ] [ trap [ interval value ] [ threshold value ] ] enable

By default, the device checks each NIC for packet loss every 15 seconds. If five consecutive packet loss events occur within 30 minutes (1800 seconds), the device generates a diagnostic log.

Managing power supply

About power supply management

Power modules might have problems such as overload overcurrent, overvoltage, overtemperature, and short circuit. Some power modules use a hardware protection measure, for example, powering off the device, to protect the entire device from being damaged. The hardware protection measure helps protect the device but causes service outage. The power supply management feature can minimize service outage while protecting the device against overload problems.

The power supply management feature constantly monitors the available power and the system loads. If a potential power supply overload problem is found, this feature takes protective measures immediately to remove requirements for power supply hardware protection. Examples of protective measures include sending a notification, starting redundant power modules, and powering off certain interface modules.

Restrictions and guidelines

This feature is supported only on the default context.

Enabling power supply management

1. Enter system view.

system-view

2. Enable power supply management.

In standalone mode:

power-supply policy enable

In IRF mode:

power-supply policy chassis chassis-number enable

The default setting varies by device model.

Powering on or off a card

About this task

You can manually power on or off cards. To view the power module status, use the display power-supply command.

Restrictions and guidelines

To power on or power off a card, you must enable power supply management first.

(In IRF mode.) To avoid IRF split, do not power off an interface module that contains the only active IRF physical interface on a member device.

Powering on a card

To power on a card, execute one of the following commands in user view:

In standalone mode:

power-supply on slot slot-number [ subslot subslot-number ]

In IRF mode:

power-supply on chassis chassis-number slot slot-number [ subslot subslot-number ]

Support for this command depends on the device model.

Powering off a card

To power off a card, execute one of the following commands in user view:

In standalone mode:

power-supply off slot slot-number [ subslot subslot-number ]

In IRF mode:

power-supply off chassis chassis-number slot slot-number [ subslot subslot-number ]

Support for this command depends on the device model.

CAUTION:

Execute this command with caution. A card will not send or receive packets after you power off it.

‌

Setting the fan operating mode

About this task

Fans can operate in either of the following modes:

· Low-temperature mode—Operates at a higher speed to provide better cooling service.

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

Procedure

1. Enter system view.

system-view

2. Set the fan operating mode.

In standalone mode:

fan auto-control-mode { low-temperature | silence }

In IRF mode:

fan auto-control-mode chassis chassis-number { low-temperature | silence }

By default, fans operate in low-temperature mode.

Verifying and diagnosing transceiver modules

Veri fying 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 electronic label information of transceiver modules.

display transceiver manuinfo 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 interface [ interface-type interface-number ]

· Display the current values of the digital diagnosis parameters on transceiver modules.

display transceiver diagnosis interface [ interface-type interface-number ]

Enabling alarm for third-party transceiver modules

About this task

Upon installation of a transceiver module, the system reads vendor information from it to determine whether it is a third-party transceiver module. If it is a third-party module, the device sends a notification and a log message to notify the user of replacing it with an H3C transceiver module. You can use display transceiver manuinfo to obtain vendor information for a transceiver module.

Restrictions and guidelines

This feature is supported only on the default context.

Procedure

1. Enter system view.

system-view

2. Enable alarm for third-party transceiver modules.

transceiver third-party alarm enable

By default, alarm is enabled for third-party transceiver modules.

Enabling USB interfaces on service modules from providing power

About this task

Loops might exist in a scenario that has the following conditions:

· A PFC is connected to a blade module on the device through the USB interface.

· The interface modules on the device are connected to transceiver modules on the PFC.

To resolve this issue, enable USB interfaces on service modules to provide power.

Procedure

1. Enter system view.

system-view

2. Enable USB interfaces on service modules to provide power.

hardware usb power-on

By default, USB interfaces on service modules can provide power.

Enabling a switching fabric module to distribute traffic to multiple IRF interface modules

About this task

In this section, the term "IRF interface modules" refers to interface modules that have IRF physical interfaces. The term "non-IRF interface modules" refers to interface modules that do not have IRF physical interfaces.

By default, traffic from a non-IRF interface module can be forwarded to multiple switching fabric modules. However, the switching fabric modules forward the traffic to only one IRF interface module. After you execute this command for switching fabric modules, the switching fabric modules can forward the traffic to multiple IRF interface modules to implement load balancing.

Procedure

1. Enter system view.

system-view

2. Enable a switching fabric module to distribute traffic to multiple IRF interface modules.

stack load-sharing fabric-slot-based chassis chassis-number slot slot-number

By default, a switching fabric module can distribute traffic to only one IRF interface module..

Enabling IRF physical interface splitting

About this task

Use this feature in scenarios where an interface module has multiple types of IRF physical interfaces. You can enable IRF physical interface splitting on the interface module to improve the usage of high-speed physical interfaces.

Procedure

1. Enter system view.

system-view

2. Enable IRF physical interface splitting.

stack port split chassis chassis-number slot slot-number

By default, IRF physical interface splitting is disabled.

Configuring CRC error check on inner interfaces of service modules

About this task

The system checks the inner interface (an HG or XE port) of a service module for CRC errors per second. A CRC error threshold exceeded event occurs if the number of CRC errors detected in a second exceeds the CRC error threshold. If the maximum number of consecutive CRC error threshold exceeded events have occurred on the inner interface of a service module, the system takes action on that service module as configured.

To tune the CRC error check configuration, perform this task.

To view the CRC error check configuration for the inner interfaces of service modules, execute the display crc-error configuration command.

Restrictions and guidelines

This feature takes effect only on security modules that use FPGA processors.

The CRC error check settings for XE ports apply only to Blade V security modules.

Procedure

1. Enter system view.

system-view

2. Specify the action to take on a service module when the maximum number of consecutive CRC error threshold exceeded events have occurred on its inner interface.

monitor crc-error { higig-port | xe-port } action { ignore | reboot | isolate }

By default, a service module reboots when the maximum number of consecutive CRC error threshold exceeded events have occurred on its inner interface.

The isolate action is not available for Blade VI security service modules.

3. Set the threshold for CRC errors per second on the inner interfaces of service modules.

monitor crc-error { higig-port | xe-port } threshold threshold-value

By default, the threshold for CRC errors per second on the inner interfaces of service modules is 50.

4. Set the maximum number of consecutive CRC error threshold exceeded events on the inner interface of a service module before the system takes action.

monitor crc-error { higig-port | xe-port } times times

By default, the system takes action if a maximum of 300 consecutive CRC error threshold exceeded events have occurred on the inner interface of a service module.

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.

Locating devices

About device locating

The device provides LEDs for device locating. The locator blink blink-time command flashes the LEDs quickly for a specified period of time unless you execute the locator blink stop command.

Restrictions and guidelines

This feature is supported only on the default context.

Starting LED flashing

To start LED flashing, execute one of the following commands in user view:

‌In standalone mode:

locator blink blink-time

‌In IRF mode:

locator [ chassis chassis-number ] blink blink-time

Stopping LED flashing

To stop LED flashing, execute one of the following commands in user view:

‌In standalone mode:

locator blink stop

‌In IRF mode:

locator [ chassis chassis-number ] blink stop

Isolating switching fabric modules

About this task

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

Restrictions and guidelines

CAUTION:

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

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

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

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

Procedure

1. ‍Enter system view.

system-view

2. Isolate a switching fabric module or channel.

In standalone mode:

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

In IRF mode:

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

By default, a switching fabric module is not isolated and can forward traffic.

CAUTION:

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

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

· Carefully examine the states of the modules before you decide to isolate a switching fabric module.

‌

Suppressing removal interrupt signals from switching fabric modules

About this task

Typically, removing a switching fabric module triggers one removal interrupt signal. Upon receiving the signal, the system switches traffic on the switching fabric module to other switching fabric modules to ensure service continuity. Upon hardware failure or signal interference, however, removal interrupt signals might be frequently triggered. To prevent the interrupt signals from affecting system operation, use this feature to suppress the interrupt signals.

Procedure

1. Enter system view.

system-view

2. Suppress removal interrupt signals from switching fabric modules.

switch-fabric removal-signal-suppression

By default, removal interrupt signals from switching fabric modules are not suppressed.

CAUTION:

Use this command with caution. This command might result in packet loss and service outage.

‌

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 slot-number ] [ force ]

In IRF mode:

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

CAUTION:

· Execute this command with caution. A device reboot might result in service interruption.

· 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 standalone mode.) The automatic reboot configuration is canceled if an active/standby switchover occurs.

(In IRF mode.) The automatic reboot configuration is effective on all member devices. It will be canceled if a switchover between the global active MPU and a global standby MPU occurs.

The device supports only one device reboot schedule. If you execute the scheduler reboot command multiple times, the most recent configuration takes effect.

Procedure

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

· scheduler reboot at time [ date ]

· scheduler reboot delay time

By default, no device reboot time is specified.

CAUTION:

This task enables the device to reboot at a scheduled time, which causes service interruption. Before configuring this task, make sure you fully understand its impact on your live network.

‌

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

This feature is supported only on the default context.

Procedure

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

restore factory-default

CAUTION:

Use this command with caution. This command restores the device to the factory default settings.

‌

Enabling the device to register with the China Mobile management platform

About this task

To be monitored from the China Mobile management platform, the device needs to register with that platform. After this task is configured, the device will register with the China Mobile management platform automatically. The information sent from the device will be displayed on the platform.

Procedure

1. Enter system view.

system-view

2. Enable the device to register with the China Mobile management platform.

auto-register cmcc device-management enable

By default, the device is disabled from registering with the China Mobile management platform.

Enabling the device to register with the China Telecom esurfing management platform

About this task

To be monitored from the China Telecom esurfing management platform, the device needs to register with that platform. After this task is configured, the device will register with the China Telecom esurfing management platform automatically. The information sent from the device will be displayed on the platform.

Procedure

1. Enter system view.

system-view

2. Enable the device to register with the China Telecom esurfing management platform.

auto-register telecom device-management enable

By default, the device is disabled from registering with the China Telecom esurfing management platform.

Resetting the health check results of check items

About this task

This feature resets the health check result of the specified check items to Normal(0), which indicates the health status is normal.

Procedure

1. Enter system view.

system-view

2. Reset the health check results of check items on the device

In standalone mode:

reset-health-value { chip-error | fmea-blade | fmea-port | hg-packet-drop | hg-packet-loss | hg-packet-tamper | hg-port-down | parity-error | port-drop } slot slot-number cpu cpu-number

In IRF mode:

reset-health-value { chip-error | fmea-blade | fmea-port | hg-packet-drop | hg-packet-loss | hg-packet-tamper | hg-port-down | parity-error | port-drop } chassis chassis-number slot slot-number cpu cpu-number

Display and maintenance commands for device management configuration

‌

IMPORTANT:

Support for the display device manuinfo fan, and display device manuinfo power commands depends on the device model. For more information, see device management in Fundamentals Command Reference.

‌

IMPORTANT:

Non-default vSystems do not support some of the display and maintenance commands. For information about vSystem support for these commands, see the device management command reference. For more information about vSystem, see Virtual Technologies Configuration Guide.

‌

Execute display commands in any view. Execute the reset scheduler logfile and display disk-information commands 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 [ cpu cpu-number ] ] In IRF mode: display alarm [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display information about active alarms.	display alarm active [ verbose ]
Display information about historical alarms that have been cleared	display alarm history [ verbose ]
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 ] [ slot slot-number [ cpu cpu-number [ core { core-number \| all } ] ] ] display cpu-usage [ control-plane \| data-plane ] [ summary ] [ slot slot-number [ cpu cpu-number ] ] In IRF mode: display cpu-usage [ summary ] [ chassis chassis-number slot slot-number [ cpu cpu-number [ core { core-number \| all } ] ] ] display cpu-usage [ control-plane \| data-plane ] [ summary ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display CPU usage monitoring settings.	‌In standalone mode: display cpu-usage configuration [ slot slot-number [ cpu cpu-number ] ] In IRF mode: display cpu-usage configuration [ chassis chassis-number 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 ] [ slot slot-number [ cpu cpu-number ] ] In IRF mode: display cpu-usage history [ job job-id ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display hardware information.	‌In standalone mode: display device [ slot slot-number [ cpu cpu-number ] [ subslot subslot-number ] \| verbose ] In IRF mode: display device [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] [ subslot subslot-number ] ] \| verbose ]
Display electronic label information for the device.	In standalone mode:‌ display device manuinfo [ slot slot-number [ cpu cpu-number ] [ subslot subslot-number ] ] In IRF mode: display device manuinfo [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] [ subslot subslot-number ] ] ]
Display electronic label information for the chassis backplane.	In standalone mode: display device manuinfo chassis-only In IRF mode: display device manuinfo chassis chassis-number chassis-only
Display electronic label information for a fan tray.	‌In standalone mode: display device manuinfo fan fan-id ‌In IRF mode: display device manuinfo chassis chassis-number fan fan-id
Display electronic label information for a power module.	‌In standalone mode: display device manuinfo power power-id ‌In IRF mode: display device manuinfo chassis chassis-number power power-id
Display or save operating information for features and hardware modules.	display diagnostic-information [ hardware \| infrastructure \| l2 \| l3 \| service ] [ context context-name ] [ key-info ] [ filename ]
Collect disk information.	In standalone mode:‌ display disk-information [ slot slot-number [ cpu cpu-number ] ] In IRF mode: display disk-information [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display device temperature information.	In standalone mode: display environment [ slot slot-number ] In IRF mode: display environment [ chassis chassis-number [ slot slot-number ] ]
Display the operating states of fan trays.	‌In standalone mode: display fan [ fan-id ] ‌In IRF mode: display fan [ chassis chassis-number [ fan-id ] ]
Display memory usage statistics.	‌In standalone mode: display memory [ summary ] [ slot slot-number [ cpu cpu-number ] ] In IRF mode: display memory [ summary ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display DMA memory usage statistics.	In standalone mode:‌ display memory dma [ slot slot-number [ cpu cpu-number ] ] In IRF mode: display memory dma [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display memory alarm thresholds and statistics.	‌In standalone mode: display memory-threshold [ slot slot-number [ cpu cpu-number ] ] In IRF mode: display memory-threshold [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display DMA memory alarm information.	In standalone mode:‌ display memory-threshold dma [ slot slot-number [ cpu cpu-number ] ] In IRF mode: display memory-threshold dma [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Display power module information.	‌In standalone mode: display power [ power-id ] ‌In IRF mode: display power [ chassis chassis-number [ power-id ] ]
Display resource monitoring information.	In standalone mode:‌ display resource-monitor [ resource resource-name ] [ slot slot-number [ cpu cpu-number ] ] In IRF mode: display resource-monitor [ resource resource-name ] [ chassis chassis-number 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 information about active/standby MPU switchovers.	In standalone mode: display switchover In IRF mode: display switchover [ chassis chassis-number ]
Display system heath status information.	In standalone mode: display system health In IRF mode: display system health [ chassis chassis-number ] display display system health [ chassis chassis-number ]
Display historical system heath status change information.	In standalone mode: display system health history In IRF mode: display system health history[ chassis chassis-number ]
Display system stability and status information.	display system stable state [ context { context-id \| all } ]
Display system version information.	display version
Display startup software image upgrade records.	display version-update-record
Display voltage information.	In standalone mode:‌ display voltage [ slot slot-number ] In IRF mode: display voltage [ chassis chassis-number [ slot slot-number ] ]
Clear job execution log information.	reset scheduler logfile
Clear startup software image upgrade records.	reset version-update-record

‌

Task	Command
Display the enabling status of check items detected by GOLD.	display gold health
Display the enabling status information of fault recovery by GOLD.	display gold recover-action
Display enabling status information of GOLD notifications.	display gold trap
Display information about fault monitoring on the device.	display monitor fault
Display health check configuration for ports on interface subcards.	display monitor fmea-port
Display information about auto card recovery from a fault through card restarts.	display monitor fault-timer
Display information about electronic label monitoring.	display monitor manuinfo

‌

NOTE:

· Executing the display cpu-usage, display cpu-usage configuration, display cpu-usage history, or display memory command on a context displays information for the context.

· The display device command displays device information about the physical devices, whether you execute the command on the default context or on a non-default context.

‌

NOTE:

The following commands are supported only on the default context:

· display alarm

· display bootrom-access

· display device manuinfo chassis-only

· display memory-threshold

· display version-update-record

· reset scheduler logfile

· reset version-update-record

‌

01-Fundamentals Configuration Guide

Configuring the device name

About this task

About this task

Procedure

Restrictions and guidelines

Procedure

Enabling displaying the copyright statement

About this task

Procedure

About this task

Banner input methods

Disabling password recovery capability

About this task

Restrictions and guidelines

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Setting the load mode for MPUs

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

Procedure

About this task

Procedure

Restrictions and guidelines

Procedure

Monitoring CPU usage

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About CPU status monitoring

Procedure

About memory alarm threholds

About memory alarm threholds

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

Monitoring the number of contexts

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

Setting the temperature alarm thresholds

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines