Contents

Managing hardware resources· 1

Hardware resource management tasks at a glance· 1

Monitoring CPU usage· 1

Configuring CPU usage alarm·· 1

Configuring CPU usage tracking· 3

Displaying CPU usage monitoring information· 3

Monitoring CPU core usage· 4

Configuring CPU cores· 4

Specifying the number of CPU cores as control cores· 4

Displaying information about CPU core allocation· 5

Monitoring memory usage· 5

Setting memory alarm thresholds· 5

Displaying memory usage monitoring information· 6

Monitoring device temperature· 7

Displaying device temperature information· 7

Monitoring fans· 7

Displaying fan information· 7

Setting the port status detection timer 7

Setting the operating mode for an interface card· 7

Verifying and diagnosing transceiver modules· 8

Verifying transceiver modules· 8

Diagnosing transceiver modules· 8

Enabling alarm for third-party transceiver modules· 9

Specifying an ITU channel number for a transceiver module· 9

Displaying device hardware information· 10

Displaying device hardware electronic label information· 10

Displaying device hardware alarm information· 10

Managing hardware resources

This chapter describes routine device hardware resource management tasks, including monitoring CPU and memory usage, displaying power supply and fan operating status, and configuring basic device operating parameters.

Hardware resource management tasks at a glance

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

·     Monitoring CPU usage

¡     Configuring CPU usage alarm

¡     Configuring CPU usage tracking

¡     Displaying CPU usage monitoring information

·     Monitoring CPU core usage

·     Configuring CPU cores

¡     Specifying the number of CPU cores as control cores

¡     Displaying information about CPU core allocation

·     Monitoring memory usage

¡     Setting memory alarm thresholds

¡     Displaying memory usage monitoring information

·     Monitoring device temperature

¡     Displaying device temperature information

·     Monitoring fans

¡     Displaying fan information

·     Setting the port status detection timer

·     Verifying and diagnosing transceiver modules

¡     Verifying transceiver modules

¡     Diagnosing transceiver modules

·     Specifying an ITU channel number for a transceiver module

·     Displaying device hardware information

·     Displaying device hardware electronic label information

·     Displaying device hardware alarm information

Monitoring CPU usage

Configuring CPU usage alarm

About this task

The device samples CPU usage at 1-minute intervals, and compares the samples with CPU usage thresholds to identify the CPU usage status and send alarms or notifications accordingly.

The device supports the following CPU usage thresholds:

·     Minor threshold—If the CPU usage increases to or above the minor threshold but is less than the severe threshold, the CPU usage enters minor alarm state. The device sends minor alarms periodically until the CPU usage increases above the severe threshold or the minor alarm is removed.

·     Severe threshold—If the CPU usage increases above the severe threshold, the CPU usage enters severe alarm state. The device sends severe alarms periodically until the severe alarm is removed.

·     Recovery threshold—If the CPU usage decreases below the recovery threshold, the CPU usage enters recovered state. The device sends a recovery notification.

CPU usage alarms and notifications 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 about NETCONF and SNMP, see Network Management and Monitoring Configuration Guide. For more information about information center, see "Configuring the information center."

Figure 1 CPU alarms and alarm-removed notifications

‌

Figure 2 CPU alarms and alarm-removed notifications

‌

Procedure

1.     Enter system view.

system-view

2.     Set the CPU usage alarm thresholds.

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

By default, the CPU usage alarm threshold is 99%.

3.     Set the CPU usage alarm resending intervals.

monitor resend cpu-usage { minor-interval minor-interval | severe-interval severe-interval } * [ slot slot-number [ cpu cpu-number ] ]

By default, the minor CPU usage alarm resending interval and severe CPU usage alarm resending interval are 300 seconds and 60 seconds, respectively.

Configuring CPU usage tracking

About this task

After you enable CPU usage tracking, the system samples CPU usage at intervals and saves the samples to a buffer. You can use the display cpu-usage history command to view the recent CPU usage.

Procedure

1.     Enter system view.

system-view

2.     Set the sampling interval for CPU usage tracking.

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

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

3.     Enable CPU usage tracking.

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

By default, CPU usage tracking is enabled.

Displaying CPU usage monitoring information

Perform display tasks in any view.

·     Display CPU usage monitoring settings.

display cpu-usage configuration [ slot slot-number [ cpu cpu-number ] ]

·     Display the current CPU usage statistics.

display cpu-usage [data-plane ] [ summary ] [ slot slot-number [ cpu cpu-number ] [ core { core-number | all } ] ]

·     Display the historical CPU usage statistics in a coordinate system.

display cpu-usage history [ job job-id ] [ slot slot-number [ cpu cpu-number ] ]

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 a CPU core usage threshold, the device issues an alarm and logs the event.

Restrictions and guidelines

As a best practice, set the CPU core usage statistics interval to an integer multiple of 5. If you set the interval to a non-integer multiple of 5, the effective statistics interval is the integer multiple of 5 that is close to and smaller than the value you set. For example, if you set this argument to 18 seconds, the effective statistics interval is 15 seconds.

Procedure

1.     Enter system view.

system-view

2.     Set CPU core alarm resending intervals.

monitor resend cpu-usage core-interval { minor-interval minor-interval | severe-interval severe-interval } * [ slot slot-number [ cpu cpu-number ] ]

By default, the minor CPU core alarm resending interval is 300 seconds and the severe CPU core alarm resending interval is 60 seconds.

Configuring CPU cores

Specifying the number of CPU cores as control cores

About this task

Control cores are used for the system services on the control plane. Typically, all services are running in one CPU core. If services need a large amount of computing, such as for a VPN with device networking, using only one CPU core might affect computing speed. In this case, you can use this feature to increase the number of control cores. Data cores are used for packet forwarding and VM cores are used on VMs.

You can use display core allocation to obtain information about CPU core allocation.

Restrictions and guidelines

The total number of CPU cores that are allocated must be equal to or smaller than the total number of CPU cores on the device.

For the configuration to take effect, restart the slot where CPU cores reside.

Procedure

1.     Enter system view.

system-view

2.     Specify the number of CPU cores allocated as control cores.

allocate core slot slot-number control-core core-count

By default, the number of CPU cores allocated as control cores is 1.

Displaying information about CPU core allocation

To display information about CPU core allocation, execute the following command in any view:

display core allocation slot slot-number

 

Monitoring memory usage

Setting memory alarm thresholds

About this task

To ensure correct operation and improve memory efficiency, the system 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 3, the system supports the following free-memory thresholds:

·     Normal state threshold.

·     Minor alarm threshold.

·     Severe alarm threshold.

·     Critical alarm threshold.

Table 1 Memory alarm notifications and memory alarm-removed notifications

Notification	Triggering condition	Remarks
Minor alarm notification	The amount of free memory space decreases to or below the minor alarm threshold.	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 to or 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 to or 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 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.

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.

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 ]

The default settings are as follows:

¡     Minor alarm threshold—256 MB.

¡     Severe alarm threshold—192 MB.

¡     Critical alarm threshold—128 MB.

¡     Normal state threshold—320 MB.

Displaying memory usage monitoring information

Perform display tasks in any view.

·     Display memory usage information.

display memory [ summary ] [ slot slot-number [ cpu cpu-number ] ]

·     Display memory alarm thresholds and statistics.

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

Monitoring device temperature

Displaying device temperature information

To display device temperature information, execute the following command in any view:

display environment [ slot slot-number ]

Monitoring fans

Displaying fan information

Perform display tasks in any view.

·     Display fan tray operating status information.

display fan [ fan-id ] [ verbose ]

·     Display electronic label information for a fan tray.

display device manuinfo fan fan-id

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. If the port has been in down state before the timer expires, the device will set the port status to the port's physical status. This feature sets 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.

Setting the operating mode for an interface card

About this task

Some interface cards can operate in multiple modes to provide different types of interfaces. Use this feature to set the operating mode for an interface card.

Restrictions and guidelines

For the new setting to take effect, you must perform one of the following tasks to activate the setting:

·     Restart the device.

·     Hot swap the interface card if the interface card supports hot swapping.

Procedure

1.     Enter system view.

system-view

2.     Set the operating mode for an interface card.

card-mode slot slot-number subslot subslot-number mode-name

Supported operating modes depend on the card model.

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 "Configuring the information center."

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

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.

Specifying an ITU channel number for a transceiver module

About this task

ITU numbers and identifies fiber signals by wavelength and frequency. A transceiver module sends signals of a specific wavelength and frequency based on the specified ITU channel number.

This feature is required in dense wavelength division multiplexing scenarios.

Restrictions and guidelines

This feature is supported only on the HPE X130 10G SFP+ LC LH80 Tunable Transceiver (JL250A) module.

This feature is supported only on the SFP-XG-LH80-Tunable transceiver module.

The ITU channel number is saved in a register on the transceiver module. It is not saved to the configuration file.

Procedure

1.     Enter system view.

system-view

2.     Enter Ethernet interface view.

interface interface-type interface-number

3.     Specify an ITU channel number.

itu-channel channel-number

By default, the ITU channel number is 1.

Displaying ITU channel information

To display ITU channel information for transceiver modules, execute the following command in any view:

display transceiver itu-channel interface [ interface-type interface-number [ supported-channel ] ]

Displaying device hardware information

To display device hardware information, execute the following command in any view:

display device [ flash | harddisk | usb ] [ slot slot-number [ subslot subslot-number ] | verbose ]

Displaying device hardware electronic label information

To display hardware electronic label information for the device, execute the following command in any view:

display device manuinfo [ slot slot-number [ subslot subslot-number ] ]

Displaying device hardware alarm information

To display device hardware alarm information, execute the following command in any view:

display alarm [ slot slot-number ]