Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 03-Hardware resource management configuration | 183.59 KB |
Hardware resource management tasks at a glance
Configuring CPU usage tracking
Configuring CPU diagnostic troubleshooting
Displaying CPU usage monitoring information
Setting memory alarm thresholds
Configuring memory diagnostic troubleshooting
Displaying memory usage monitoring information
Specifying the allocation mode for MDB resources
Displaying the MDB resources allocation mode
Configuring resource monitoring
Displaying resource monitoring information
Setting the temperature alarm thresholds
Displaying device temperature information
Configuring hardware failure detection and protection
Specifying the actions to be taken for hardware failures
Enabling hardware failure protection for aggregation groups
Power supply management tasks at a glance
Enabling power supply management
Specifying the number of redundant power modules
Specifying the exception monitoring mode for power modules
Enabling power module sleeping
Setting the port status detection timer
Verifying and diagnosing transceiver modules
Diagnosing transceiver modules
Specifying an ITU channel number for a transceiver module
Configuring transceiver monitoring
Configuring consistency error logging for software and hardware forwarding entries
Configuring parity error and ECC error logging for entries on forwarding chips
Configuring uncorrectable parity error and ECC error logging for entries on forwarding chips
Setting the port speed mode for the device
Enabling or disabling port licensing
Displaying device hardware information
Displaying device hardware electronic label information
Displaying device hardware alarm information
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.
¡ Configuring CPU usage tracking
¡ Configuring CPU diagnostic troubleshooting
¡ Displaying CPU usage monitoring information
¡ Setting memory alarm thresholds
¡ Configuring memory diagnostic troubleshooting
¡ Displaying memory usage monitoring information
¡ Configuring resource monitoring
¡ Displaying resource monitoring information
· Monitoring device temperature
¡ Setting the temperature alarm thresholds
¡ Displaying device temperature information
· Configuring hardware failure detection and protection
¡ Specifying the actions to be taken for hardware failures
¡ Enabling hardware failure protection for aggregation groups
¡ Enabling power supply management
¡ Specifying the number of redundant power modules
¡ Specifying the exception monitoring mode for power modules
¡ Enabling power module sleeping
· 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
· Configuring transceiver monitoring
· Configuring consistency error logging for software and hardware forwarding entries
· Configuring parity error and ECC error logging for entries on forwarding chips
· Configuring uncorrectable parity error and ECC error logging for entries on forwarding chips
· Setting the port speed mode for the device
· Displaying device hardware information
· Displaying device hardware electronic label information
· Displaying device hardware alarm information
· Displaying information about active alarms
· Displaying information about historical alarms
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
Procedure
1. Enter system view.
system-view
2. Set the CPU usage alarm thresholds.
monitor cpu-usage threshold severe-threshold [ minor-threshold minor-threshold recovery-threshold recovery-threshold ] [ slot slot-number [ cpu cpu-number ] ]
By default, the severe CPU usage alarm threshold is 99%, the minor CPU usage alarm threshold is 79%, and the CPU usage recovery threshold is not specified.
|
|
CAUTION: If you set the severe CPU usage alarm threshold to a too low value, the device will reach the threshold easily. Normal service processing will be affected. |
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.
Configuring CPU diagnostic troubleshooting
CPU diagnostic troubleshooting detects whether CPU usage is normal. If CPU usage exceeds alarm thresholds or suddenly increases, this feature helps you to locate CPU usage issues. For more information about CPU diagnostic troubleshooting, see diagnostic troubleshooting in Intelligent O&M Configuration Guide.
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 [ 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 cores
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 ] ]
The resending interval is 300 seconds for minor CPU core usage alarms and 60 seconds for severe CPU core usage alarms.
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.
You can use the display memory command to display memory usage information.
As shown in Table 1 and Figure 2, the system supports the following free-memory thresholds:
· Normal state threshold.
· Minor alarm threshold.
· Severe alarm threshold.
· Critical alarm threshold.
Table 1 Memory alarm notifications and memory alarm-removed notifications
|
Notification |
Triggering condition |
Remarks |
|
Minor alarm notification |
The amount of free memory space decreases to or below the minor alarm threshold. |
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 2 Memory alarm notifications and alarm-removed notifications
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
The default settings are as follows:
¡ Minor alarm threshold—1024 MB.
¡ Severe alarm threshold—768 MB.
¡ Critical alarm threshold—512 MB.
¡ Normal state threshold—1280 MB.
Configuring memory diagnostic troubleshooting
Memory diagnostic troubleshooting detects whether free memory space is normal. If free memory space exceeds alarm thresholds or suddenly decreases, this feature helps you to locate memory space issues. For more information about memory diagnostic troubleshooting, see diagnostic troubleshooting in Intelligent O&M Configuration Guide.
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 MDB resources
Specifying the allocation mode for MDB resources
About this task
You can specify the routing or normal allocation mode for MDB resources. The MAC address table, ARP table, and routing table capacities vary by the resource allocation mode.
Restrictions and guidelines
For the configuration to take effect, restart the device.
Procedure
1. Enter system view.
system-view
2. Specify the allocation mode for MDB resources.
hardware-resource mdb { normal | routing }
By default, the routing allocation mode is specified for MDB resources.
Displaying the MDB resources allocation mode
To display the MDB resources allocation mode, execute the following command in any view:
display hardware-resource [ mdb ]
Monitoring resource usage
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 about NETCONF and SNMP, see Network Management and Monitoring Configuration Guide. For more information about information center, see "Configuring the information center."
Figure 3 Resource depletion alarms and alarm-removed notifications
Procedure
1. Enter system view.
system-view
2. Set resource depletion thresholds.
resource-monitor resource resource-name slot slot-number cpu cpu-number { by-absolute | by-percent } minor-threshold minor-threshold severe-threshold severe-threshold
The default settings vary by resource type. Use the display resource-monitor command to display the resource depletion thresholds.
3. Specify destinations for resource depletion alarms.
resource-monitor output { netconf-event | snmp-notification | syslog } *
By default, 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.
Displaying resource monitoring information
To display resource monitoring information, execute the following command in any view:
display resource-monitor [ resource resource-name ] [ slot slot-number [ cpu cpu-number ] ]
Monitoring device temperature
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.
Procedure
1. Enter system view.
system-view
2. Configure the temperature alarm thresholds.
temperature-limit 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.
Displaying device temperature information
To display device temperature information, execute the following command in any view:
display environment [ slot slot-number ]
Configuring hardware failure detection and protection
The device can automatically detect hardware failures on components, the device, 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 device.
¡ Isolates the device.
¡ Powers off the device.
· reset—Restarts the relevant components or the device to recover from failures.
· warning—Sends traps to report the failures.
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 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 interface is not the only member in up state in the group.
· Does not shut down the interface if 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 warning action in response to forwarding-plane failures.
3. Enable hardware failure protection for aggregation groups.
hardware-failure-protection aggregation
By default, hardware failure protection is disabled for aggregation groups.
Enabling chip reset
About this task
This task enables the system to reset a chip when an alarm indicating that the chip is faulty is generated.
Procedure
1. Enter system view.
system-view
2. Enable chip reset.
monitor chipblock reset [ logging ]
By default, chip reset is enabled.
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 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.
Power supply management tasks at a glance
To manage power supply, perform the following tasks:
1. Enabling power supply management
2. (Optional.) Specifying the number of redundant power modules
To avoid overload problems, you can install redundant power modules.
Enabling power supply management
1. Enter system view.
system-view
2. Enable power supply management.
power-supply policy enable
By default, power supply management is enabled.
Specifying the number of redundant power modules
About this task
To avoid overload problems, you can install redundant power modules. For example, if the device requires a minimum of N power modules to operate correctly, you can install M power modules (M > N). The M power modules operate in load balance mode. When a power module fails, the load is rebalanced among the other power modules.
After you specify the number of redundant power modules, the device compares the maximum power consumption of a newly added card with the remaining power.
· If the remaining power is sufficient for the card, the device powers on the card.
· If the power is insufficient, the device does not power on the card. You can add power modules or scale the number of redundant power modules down.
Restrictions and guidelines
This feature takes effect only if power supply management is enabled.
Procedure
1. Enter system view.
system-view
2. Specify the number of redundant power modules.
power-supply policy redundant module-count
By default, the number of redundant power supplies is 0.
Specifying the exception monitoring mode for power modules
Restrictions and guidelines
The enhanced exception monitoring mode for the power modules occupies lots of system resources.
Procedure
1. Enter system view.
system-view
2. Specify the exception monitoring mode for the power modules.
power-exception-monitor { normal | enhanced }
By default, the normal exception monitoring mode applies to the power modules.
Enabling power module sleeping
About this task
This feature enables the device to monitor the remaining power in real time.
· If the remaining power is greater than the power of a power module, the device places the power module into sleeping state.
· When the remaining power becomes insufficient, the device wakes up a sleeping power module.
Restrictions and guidelines
This feature is supported only on switches that are compatible with the PSR2400-54A, PSR2400-54D, or PSR3000-54A power module.
This feature takes effect only when power supply management is enabled.
Power modules in sleeping state cannot act as the backup power modules. When an operating power module fails or is removed, the device might not be able to operate correctly.
To view the operating status of power modules, execute the display power command.
Procedure
1. Enter system view.
system-view
2. Enable power module sleeping.
power-supply surplus-power enable
Verifying power supply
Displaying power module information
To display power module information, execute the following command in any view:
display power [ slot slot-number [ power-id ] ]
Displaying electronic label information for a power module
To display electronic label information for a power module, execute the following command in any view:
display device manuinfo slot slot-number power power-id
Monitoring fans
Displaying fan information
Perform display tasks in any view.
· Display fan tray operating status information.
display fan [ slot slot-number [ fan-id ] ]
· Display electronic label information for a fan tray.
display device manuinfo slot slot-number 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.
Procedure
1. Enter system view.
system-view
2. Set the port status detection timer.
shutdown-interval time
The default is 30 seconds.
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 ]
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 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 ] ]
Configuring transceiver monitoring
About this task
After transceiver monitoring is enabled, the device samples the parameters of transceiver modules periodically, including the input power and output power of transceiver modules. If a sampled value reaches the alarm threshold, the device generates a log to notify users.
Procedure
1. Enter system view.
system-view
2. Enable transceiver monitoring.
transceiver monitor enable [ grey | tunable ]
By default, transceiver monitoring is disabled
3. Set the transceiver monitoring interval.
transceiver monitor interval interval
By default, the transceiver monitoring interval is 600 seconds.
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.
Starting LED flashing
To start LED flashing, execute one of the following commands in user view:
locator [ slot slot-number ] blink blink-time
Stopping LED flashing
To stop LED flashing, execute one of the following commands in user view:
locator [ slot slot-number ] blink stop
Configuring consistency error logging for software and hardware forwarding entries
About this task
To forward packets, the device generates hardware forwarding entries in forwarding chips and software forwarding entries in memory at the same time. The device automatically detects whether the hardware forwarding entries and the software forwarding entries are consistent.
The consistency error logging for software and hardware forwarding entries enables the device to collect statistics for consistency errors between software and hardware forwarding entries periodically. If the number of consistency errors reaches or exceeds the logging threshold, the device generates a log message.
Procedure
1. Enter system view.
system-view
2. Set the logging threshold for consistency errors between software and hardware forwarding entries.
parity-error consistency-check threshold value
By default, the logging threshold is 10.
3. Enable consistency error logging for software and hardware forwarding entries.
parity-error consistency-check log enable
By default, consistency error logging is enabled for software and hardware forwarding entries.
Configuring parity error and ECC error logging for entries on forwarding chips
About this task
The device automatically detects parity errors and ECC errors in entries on forwarding chips. The parity error and ECC error logging feature collects parity errors and ECC error statistics periodically, and generates a log message if the number of parity errors and ECC errors reaches or exceeds the logging threshold.
Procedure
1. Enter system view.
system-view
2. Set the parity error and ECC error statistics period for entries on forwarding chips.
parity-error monitor period value
By default, the parity error and ECC error statistics period for entries on forwarding chips is 60 seconds.
3. Set the parity error and ECC error logging threshold for entries on forwarding chips.
parity-error monitor threshold value
By default, the parity error and ECC error logging threshold for entries on forwarding chips is 5000.
4. Enable parity error and ECC error logging for entries on forwarding chips.
parity-error monitor log enable
By default, parity error and ECC error logging is disabled for entries on forwarding chips.
Configuring uncorrectable parity error and ECC error logging for entries on forwarding chips
About this task
The device automatically detects parity errors and ECC errors in entries on forwarding chips and tries to correct the error when an error is detected. The uncorrectable parity error and ECC error logging feature enables the device to collect statistics for uncorrectable parity errors and ECC errors periodically. If the number of uncorrectable parity errors and ECC errors reaches or exceeds the logging threshold, the device generates a log message.
Uncorrectable parity errors and ECC errors in entries on forwarding chips might affect system services. To remove the errors from the entries on forwarding chips, you can enable automatic system reboot upon generation of an uncorrectable parity error and ECC error log.
Procedure
1. Enter system view.
system-view
2. Set the statistics period for uncorrectable parity error and ECC errors for entries on forwarding chips.
parity-error unrecoverable period value
By default, the statistics period for uncorrectable parity error and ECC errors for entries on forwarding chips is 60 seconds.
3. Set the logging threshold for uncorrectable parity errors and ECC errors for entries on forwarding chips.
parity-error unrecoverable threshold value
By default, the logging threshold is 1 for uncorrectable parity errors and ECC errors for entries on forwarding chips.
4. Enable uncorrectable parity error and ECC error logging for entries on forwarding chips.
parity-error unrecoverable log enable
By default, uncorrectable parity error and ECC error logging is enabled for entries on forwarding chips
5. (Optional.) Enable automatic system reboot upon generation of an uncorrectable parity error and ECC error log.
parity-error unrecoverable reboot
By default, the device reboots upon generation of an uncorrectable parity error and ECC error log.
Setting the port speed mode for the device
Restrictions and guidelines
For a new port speed mode to take effect, restart the device.
Porcedure
1. Enter system view.
system-view
2. Set the port speed mode for the device.
hardware-resource port-speed { high | low } [ slot slot-number ]
By default, the device operates in low port speed mode.
Verifying the port speed mode for the device
To display the port speed mode for the device, execute the following command in any view:
display hardware-resource [ port-speed ]
Enabling or disabling port licensing
Restrictions and guidelines
To use license-based features, you need to install the licenses on the device. You can perform this task to have the installed licenses take effect.
For an enabling status change to take effect, restart the device.
Procedure
1. Enter system view.
system-view
2. Configure the enabling status of port licensing.
hardware-resource smartman { enable | disable }
By default, port licensing is disabled. That is, the installed licenses do not take effect on the ports of the device.
Verifyinport licensing
To display the port licensing status information, execute the following command in any view:
display hardware-resource [ smartman ]
Displaying device hardware information
To display device hardware information, execute the following command in any view:
display device [ flash | 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 ]
Displaying information about active alarms
Restrictions and guidelines
When a power module, CPU, or fan tray on the device is operating abnormally, you can use the display alarm command to view alarm information. To view historical alarms that have been cleared, use the display alarm history command. To view active alarms that have not been cleared, use the display alarm active command.
Procedure
To display information about active alarms, execute the following command in any view:
display alarm active
Displaying information about historical alarms
Restrictions and guidelines
When a power module, CPU, or fan tray on the device is operating abnormally, you can use the display alarm command to view the alarm information. To view historical alarms that have been cleared, use the display alarm history command. To view active alarms that have not been cleared, use the display alarm active command.
Procedure
To display information about historical alarms, execute the following command in any view:
display alarm history [ verbose ]
