Title | Size | Downloads |
---|---|---|
H3C Switches Quick Start Maintenance Guide-6W100-book.pdf | 170.83 KB |
- Table of Contents
- Related Documents
-
H3C Switches Quick Start Maintenance Guide
Copyright © 2022 New H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.
The information in this document is subject to change without notice.
Contents
Checking critical or minor alarms
Checking the health status of the device
Checking the CPU usage of the device
Checking the memory usage of the device
Checking the operational status of fan trays
Checking the operational status of power supplies
Checking information about temperature sensors on the device
Checking the operational status of cards and subcards
Collecting and reporting failure information
Collecting basic failure information
Collecting diagnostic information
Checking for power supply system failure
Checking for MPU failure (on modular devices)
Safety and configuration cautions and guidelines
CLI-based configuration cautions and guidelines
Preparing for maintenance
1. Obtain the network topology graph and data plan (including interfaces, VLANs, and IP addresses) and paste them at a place where it can be seen easily.
2. Prepare the tools and cables that might be required for maintenance. See Table 1.
Table 1 Tools and cables for maintenance
Item |
Description |
Cables |
· One serial console cable—Log in to the device from the console port. You can purchase a DB9-to-RJ45 console cable or USB-to-RJ45 console cable from H3C. To use a USB-to-RJ45 console cable, first download the USB-to-RJ45 console driver from the H3C official website and install it on the configuration terminal. · Two straight-through network cables—Debug management network ports or other services. · Extension cable connectors, which are used to extend cables when their length is not enough. · Optical fibers and SFP/SFP+/QSFP+/QSFP28/CFP2 transceiver modules or cables—Connect to the peer device. |
Maintenance terminal |
Typically, a maintenance terminal is a laptop used to install the serial communication software for device login. |
Auxiliary instruments and meters |
· Optical power meter—Test optical power and receiving sensitivity for fiber ports. · Hygrothermograph—Test the temperature and humidity of the environment and fan outlet. |
Other tools |
· Detachable wrench—Install, remove, or secure some service modules. · Cleaning box for optical fiber end faces. · Connector cleaning rod. · Cable tie (cable clamp). · Screwdrivers—Phillips screwdrivers and flat-head screwdrivers. · Diagonal pliers. |
3. Obtain contact information of H3C Support.
4. Access the H3C official website to apply for a user account. You can use the user account to browse or download product documents.
The command output in this document is for your reference only.
Maintaining the device
For information about the support for the commands in this section, see the command reference for the device.
To check alarms, health status, and device status, and record failure information, log in to the device through the console port, Telnet, or SSH. For how to log in to the device, see the configuration guide for the device. If you fail to log in to the device, see "Troubleshooting login failure."
Figure 1 Maintenance flow
Checking the LED status
The device provides various LEDs to indicate the operating status of different objects. If a LED indicates an abnormal state, record the failure information immediately. For how to troubleshoot and resolve the issue, see the installation guide for the switch. If the issue persists, contact H3C Support.
For information about the descriptions of the LEDs, see the installation guide or hardware information and specifications for the switch.
Checking critical or minor alarms
Only some switch models support the display alarm command. For other switch models, check the log information for alarms. For the procedure, see "Viewing log information." For more information about log information, see the configuration guide or system log messages for the switch.
If a network management system is deployed, you can also identify whether an alarm has occurred from the network management system. For more information, see the user guide for the network management system.
Viewing alarm information
Use the display alarm command to identify whether an ERROR alarm has occurred. The command output varies by switch model. The following command output uses the S12500X-AF switch series as an example.
<Sysname> display alarm
Slot CPU Level Info
- - ERROR Power 2 is faulty.
- - INFO Power 3 is absent.
- - INFO Power 4 is absent.
Table 2 Command output
Field |
Description |
Slot |
Slot where the alarm was generated. If the alarm was generated by the frame, this field displays a hyphen (-). |
Level |
Alarm severity. Possible values include ERROR, WARNING, NOTICE, and INFO, in descending order of severity. |
Info |
Detailed alarm information: · faulty—The device is starting up or is faulty. · Board is faulty—The slot is starting or faulty. · Fan n is absent—The specified fan is absent. · Fan n is faulty—The specified fan is faulty. · Power n is absent—The specified power supply is absent. · Power n is faulty—The specified power supply is faulty. · Slot n temperature is too high, above the shutdown limit—The temperature of the specified card is higher than the shutdown temperature threshold. · Slot n temperature is too high, above the high limit—The temperature of the specified card is higher than the high-temperature threshold. · Slot n temperature is too high, above the warning limit—The temperature of the specified card is higher than the high-temperature warning threshold. · Slot n temperature is too low, below the low limit—The temperature of the specified card is lower than the low-temperature threshold. |
In daily maintenance, you must handle the ERROR alarms immediately. For alarms that cannot be handled, contact H3C Support.
Viewing log information
Use the display logbuffer command to identify whether an alarm has occurred in the log buffer. For more information about log information, see the configuration guide or system log messages for the switch. The command output varies by switch model. The following command output uses the S12500X-AF switch series as an example.
<Sysname> display logbuffer
Log buffer: Enabled
Max buffer size: 1024
Actual buffer size: 512
Dropped messages: 0
Overwritten messages: 718
Current messages: 512
%Jun 17 15:57:09:578 2016 Sysname SYSLOG/7/SYS_RESTART:System restarted –
...
Table 3 Command output
Field |
Description |
Log buffer |
Status of the log buffer: · Enabled—Log messages can be output to the log buffer. · Disabled—Log messages cannot be output to the buffer. |
Max buffer size |
Maximum buffer size supported by the device. |
Actual buffer size |
Maximum buffer size configured by using the info-center logbuffer size command. |
Dropped messages |
Number of dropped messages. |
Overwritten messages |
Number of overwritten messages. |
Current messages |
Number of current messages. |
For alarms that cannot be handled, contact H3C Support.
Checking the health status of the device
Use the following commands to view the health status of the device:
· display cpu-usage
· display memory
· display fan
· display power
· display environment
Checking the CPU usage of the device
Use the display cpu-usage command to verify that the CPU usage of the device does not exceed 80%. The command output varies by switch model. The following command output uses the S12500X-AF switch series as an example.
<Sysname> display cpu-usage
Slot 1 CPU 0 CPU usage:
1% in last 5 seconds
1% in last 1 minute
1% in last 5 minutes
Table 4 Command output
Field |
Description |
1% in last 5 seconds |
Average CPU usage in the last 5 seconds. (After the device boots, the device calculates and records the average CPU usage at the interval of 5 seconds.) |
1% in last 1 minute |
Average CPU usage in the last minute. (After the device boots, the device calculates and records the average CPU usage at the interval of 1 minute.) |
1% in last 5 minutes |
Average CPU usage in the last 5 minutes. (After the device boots, the device calculates and records the average CPU usage at the interval of 5 minutes.) |
If the CPU usage is too high, wait for 5 to 10 minutes and check the CPU usage again. If the issue persists, contact H3C Support.
Checking the memory usage of the device
Use the display memory command to verify that the free memory ratio of the switch is higher than 20%. (Low memory is not supported. The following command output uses the S12500X-AF switch series as an example.)
Memory statistics are measured in KB:
Slot 0:
Total Used Free Shared Buffers Cached FreeRatio
Mem: 8149596 2351256 5798340 0 20 275784 71.1%
-/+ Buffers/Cache: 2075452 6074144
Swap: 0 0 0
Slot 1:
Total Used Free Shared Buffers Cached FreeRatio
Mem: 8149596 2180788 5968808 0 20 162472 73.2%
-/+ Buffers/Cache: 2018296 6131300
Swap: 0 0 0
Table 5 Command output
Field |
Description |
Mem |
Memory usage information. |
Total |
Total size of the physical memory space that can be allocated. The memory space is virtually divided into two parts. Part 1 is used for kernel codes, kernel management, and ISSU functions. Part 2 can be allocated and used for such tasks as running service modules and storing files. The size of part 2 equals the total size minus the size of part 1. |
Used |
Used physical memory. |
Free |
Free physical memory. |
Shared |
Physical memory shared by processes. If this field is not supported, two hyphens (--) are displayed. |
Buffers |
Physical memory used for buffers. If this field is not supported, two hyphens (--) are displayed. |
Cached Caches |
Physical memory used for caches. If this field is not supported, two hyphens (--) are displayed. |
FreeRatio |
Free memory ratio. |
-/+ Buffers/Cache |
-/+ Buffers/Cache:used = Mem:Used – Mem:Buffers – Mem:Cached, which indicates the physical memory used by applications. -/+ Buffers/Cache:free = Mem:Free + Mem:Buffers + Mem:Cached, which indicates the physical memory available for applications. |
Swap |
Memory space for swapping. |
If the free memory ratio is too low for a period of time (typically, 30 minutes), contact H3C Support.
Use the display memory command to verify that the free memory ratio of the switch is higher than 20%. (Low memory is supported. The following command output uses the S5560X-EI switch series as an example.)
<Sysname> display memory
Memory statistics are measured in KB:
Slot 1:
Total Used Free Shared Buffers Cached FreeRatio
Mem: 2036536 496116 1540420 0 1436 113644 75.7%
-/+ Buffers/Cache: 381036 1655500
Swap: 0 0 0
LowMem: 1651512 279856 1371656 -- -- -- 83.1%
HighMem: 385024 216260 168764 -- -- -- 43.8%
Table 6 Command output
Field |
Description |
Mem |
Memory usage information. |
Total |
Total size of the physical memory space that can be allocated. The memory space is virtually divided into two parts. Part 1 is used for kernel codes, kernel management, and ISSU functions. Part 2 can be allocated and used for such tasks as running service modules and storing files. The size of part 2 equals the total size minus the size of part 1. |
Used |
Used physical memory. |
Free |
Free physical memory. |
Shared |
Physical memory shared by processes. If this field is not supported, two hyphens (--) are displayed. |
Buffers |
Physical memory used for buffers. If this field is not supported, two hyphens (--) are displayed. |
Cached Caches |
Physical memory used for caches. If a memory threshold is reached, part of memory used for caches can be automatically released for other services. If this field is not supported, two hyphens (--) are displayed. |
FreeRatio |
Free memory ratio. The free memory includes the free physical memory and the part of memory used for caches that can be automatically released for other services when a memory threshold is reached. |
-/+ Buffers/Cache |
-/+ Buffers/Cache:used = Mem:Used – Mem:Buffers – Mem:Cached, which indicates the physical memory used by applications. -/+ Buffers/Cache:free = Mem:Free + Mem:Buffers + Mem:Cached, which indicates the physical memory available for applications. |
Swap |
Memory space for swapping |
LowMem |
Low memory usage information. |
HighMem |
High memory usage information. |
If the free memory ratio is too low for a period of time (typically, 30 minutes), contact H3C Support.
Checking the operational status of fan trays
Use the display fan command to verify that all present fan trays are in Normal state. The command output varies by switch model. The following command output uses the S5560X-EI switch series as an example.
<Sysname> display fan
Slot 1:
Fan 1:
State : Normal
Airflow Direction: Port-to-power
Prefer Airflow Direction: Port-to-power
Table 7 Command output
Field |
Description |
Number of the member device. |
|
Fan tray number. |
|
State |
Fan status: · Absent—The slot is not installed with a fan tray. · Normal—The fan tray is operating correctly. · Fault—The fan tray is faulty. · FanDirectionFault—The actual airflow direction is not the preferred direction. |
Actual airflow direction: · Port-to-power—From the port side to the power supply side. · Power-to-port—From the power supply side to the port side. |
|
Preferred airflow direction: · Port-to-power—From the port side to the power supply side. · Power-to-port—From the power supply side to the port side. |
If a fan tray is faulty, troubleshoot and resolve the issues as follows:
1. Verify that the fan tray is installed securely. If the fan tray is not installed securely, reinstall the fan tray.
2. Verify that the fan does not have object intrusions. If the fan got stuck, remove the objects.
3. Verify that the fan tray is clean. If the fan tray has too much dust, clean the fan tray.
4. If the fan tray still operates incorrectly, replace the fan tray.
5. If the issue persists, record the failure information immediately and contact H3C Support.
Checking the operational status of power supplies
Use the display power command to verify that all present power supplies are in Normal state when power supply management is not supported. The following command output uses the S5560X-EI switch series as an example.
<Sysname> display power
Slot 1:
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Absent -- -- -- --
2 Normal AC 0.70 56.44 39.00
Table 8 Command output
Field |
Description |
PowerID |
Power supply ID. |
State |
Power supply status: · Absent—The slot is not installed with a power supply. · Normal—The power supply is operating correctly. · Fault—The power supply is faulty. |
Mode |
Mode of the power supply: · AC—AC power supply. · DC—DC power supply. |
Current(A) |
Output current of the power supply, in amperes. This field is not supported by the device models that use built-in power supplies and displays two hyphens (--). |
Voltage(V) |
Output voltage of the power supply, in volts. This field is not supported by the device models that use built-in power supplies and displays two hyphens (--). |
Power(W) |
Output power of the power supply, in watts. This field is not supported by the device models that use built-in power supplies and displays two hyphens (--). |
If a power supply is faulty, perform the following tasks:
1. Verify that the power supply is powered on.
2. Verify that the power cord is connected securely.
3. If the power supply still operates incorrectly, replace the power supply.
4. If the issue persists, record the failure information immediately and contact H3C Support.
Use the display power command to verify that all present power supplies are in Normal state when power supply management is supported. The following command output uses the S12500X-AF switch series as an example.
<Sysname> display power
Power supply policy : Enabled
Surplus sleeping : Disabled
Power modules installed : 2
Power modules usable : 2
Total power : 4000W
Redundant power : 0W
Sleeping power : 0W
Available power : 4000W
Allocated power : 2375W
Remaining power : 1625W
PowerID State InPower(W) Current(A) Voltage(V) OutPower(W) Type
1 Normal 2000 5.80 54.00 313.20 CP2000AC
2 Absent -- -- -- -- ---
3 Normal 2000 4.40 54.00 237.60 CP2000AC
4 Absent -- -- -- -- ---
5 Absent -- -- -- -- ---
6 Absent -- -- -- -- ---
7 Absent -- -- -- -- ---
8 Absent -- -- -- -- ---
Information about reserved power:
Slot Status Power(W) Remarks
7 Normal 275 Powered on
10 Normal 170 Powered on
11 Fault 450 Powered on
12 Normal 170 Powered on
16 Normal 50 Reserved for MPU
17 Absent 50 Reserved for MPU
Power information for fans:
Fan[2]: 1200W
Table 9 Output description
Field |
Description |
Power supply policy |
Status of power supply management: · Enabled. · Disabled. |
Surplus sleeping |
Status of the surplus sleeping feature: · Enabled. · Disabled. |
Power modules installed |
Number of power supplies installed on the device. |
Power modules usable |
Number of used power supplies. The used power supplies are the power supplies in Normal and Sleeping states. |
Total power |
Total power, in watts. |
Redundant power |
Redundant power, in watts. |
Sleeping power |
Sleeping power, in watts. |
Available power |
Available power, in watts. |
Allocated power |
Used power, in watts. |
Remaining power |
Remaining power, in watts. |
PowerID |
Power supply ID. |
State |
Power supply status: · Absent—The slot is not installed with a power supply. · Normal—The power supply is operating correctly. · Fault—The power supply is faulty. · Sleeping—The power supply is sleeping. |
InPower(W) |
Input power of the power supply, in watts. If this field is not supported, two hyphens (--) are displayed. |
Current(A) |
Output current of the card, in amperes. If this field is not supported, two hyphens (--) are displayed. |
Voltage(V) |
Output voltage of the card, in volts. If this field is not supported, two hyphens (--) are displayed. |
OutPower(W) |
Output power of the power supply, in watts. If this field is not supported, two hyphens (--) are displayed. |
Type |
Power supply model. If this field is not supported, two hyphens (--) are displayed. |
Information about reserved power |
Information about reserved power on cards. |
Slot |
Slot number of the card. |
Status |
Status of the card: · Absent—The slot is not installed with a card. · Normal—The card is operating correctly. · Fault—The card is faulty or does not start up. |
Power(W) |
Reserved power on the card, in watts. |
Remarks |
Description of the reserved power: · Reserved for MPU. · Powered on—The card is powered on. · Not enough power to power it on—Reserved power is not enough for the card to be powered on. · Reserved for a non-MPU card. · Powered off—The card is powered off forcibly. |
Power information for fans |
Information about the reserved power for fans. |
Fan[x] |
Fan number. |
If a power supply is faulty, perform the following tasks:
1. Verify that the power supply is powered on.
2. Verify that the power cord is connected securely
3. Replace the power supply.
4. If the issue persists, record the failure information immediately and contact H3C Support.
Checking information about temperature sensors on the device
Use the display environment command to verify that the temperatures of temperature sensors on the device are in a normal range. The command output varies by switch model. The following command output uses the S12500X-AF switch series as an example.
<Sysname> display environment
System temperature information (degree centigrade):
-----------------------------------------------------------------------------
Slot Sensor Temperature Lower Warning Alarm Shutdown
1 hotspot 1 38 10 40 50 100
1 hotspot 2 42 10 50 80 100
Table 10 Command output
Field |
Description |
System Temperature information (degree centigrade) |
Temperature information (°C). |
sensor |
Temperature sensor: · hotspot—Hotspot sensor. · inflow—Air inlet sensor. |
Slot |
Sensor position. |
Temperature |
Current temperature. |
Lower |
Lower temperature limit. If the device does not support this field, this field displays NA. |
Warning |
Warning temperature threshold. If the device does not support this field, this field displays NA. |
Alarm |
Alarming temperature threshold. If the device does not support this field, this field displays NA. |
Shutdown |
Shutdown temperature threshold. When the sensor temperature exceeds the limit, the system shuts down automatically. If the device does not support this field, this field displays NA. |
If an exception has occurred, perform the following tasks:
1. Verify that the temperature in the equipment room is normal.
2. Verify that the device ventilation aisles are not obstructed.
3. Verify that the fan trays are operating correctly.
4. If the issue persists, record the failure information immediately and contact H3C Support.
Checking the operational status of cards and subcards
Use the display device command to verify that the present cards and subcards are in Normal state. The command output varies by switch model. The following command output uses the S12500X-AF switch series as an example.
<Sysname> display device
Slot Type State Subslot Soft Ver Patch Ver
0 LSXM1SUPB1 Master 0 S12508X-AF-0502 None
1 LSXM1SUPB1 Standby 0 S12508X-AF-0502 None
2 NONE Absent 0 NONE None
3 LSXM1TGS48C2HB1 Normal 0 S12508X-AF-0502 None
4 NONE Absent 0 NONE None
5 NONE Absent 0 NONE None
6 NONE Absent 0 NONE None
7 NONE Absent 0 NONE None
8 NONE Absent 0 NONE None
9 NONE Absent 0 NONE None
10 NONE Absent 0 NONE None
11 NONE Absent 0 NONE None
12 NONE Absent 0 NONE None
13 NONE Absent 0 NONE None
14 NONE Absent 0 NONE None
15 LSXM1SFH08D1 Normal 0 S12508X-AF-0502 None
Table 11 Command output
Field |
Description |
Type |
Hardware type of the card. |
Status |
Card status: · Standby—The card is the standby MPU. · Master—The card is the active MPU. · Absent—The slot is not installed with a card. · Fault—The card is starting up, powered off, or faulty. · Normal—The card is an interface card and is operating correctly. · Offline—The card is isolated. |
Soft Ver |
Software version of the card. |
Patch Ver |
Most recently released patch image version that is running on the card. If no patch image is installed, this field displays None. If both incremental and non-incremental patch images are running on the card, this field displays the most recently released incremental patch image version. |
If an exception has occurred, reinstall the card or subcard. If the issue persists, record the failure information immediately and contact H3C Support.
Collecting and reporting failure information
For the support for the commands in this section, see the command reference for the switch.
If an exception has occurred, first record the following failure information immediately and then report them to H3C Support:
· Symptom, time of failure, and configuration.
· Network topology information, including the network diagram, port connections, and points of failure.
· Log messages and diagnostic information.
· Steps you have taken and the result.
Collecting basic failure information
Table 12 shows the basic failure information to be collected if the device is faulty.
Table 12 Basic failure information
Item |
Collection method |
Time of failure |
Record the time when the failure occurred down to the minute. |
Symptom |
Record detailed symptom of the failure. |
Impact |
Record the failure severity and affected services. |
Networking |
Draw a network diagram, including uplink and downlink devices and connected interfaces. |
Steps you have taken |
Record the steps you have taken and the results, including output from the commands executed during the troubleshooting process. |
Collecting log information
Log information records daily information, user actions, system failures, system safety, and system debugging. It includes diagnosis monitoring log messages, diagnostic log messages, system log messages, and debug log messages.
To obtain the most recent log information, save the collected log messages to a log file.
To collect log information:
1. Save diagnostic log messages from the log buffer to a log file.
diagnostic-logfile save
By default, diagnostic log files are saved in the flash:/diagfile directory of the storage device.
2. Save system log messages from the log buffer to a log file.
logfile save
By default, system log files are saved in the flash:/logfile directory of the storage device.
3. Execute the dir command in user view to verify that the log files are generated correctly.
4. Transfer the log files to the desired destination by using FTP, TFTP, or SFTP. For more information, see the configuration guide for the switch.
Collecting diagnostic information
To collect all diagnostic information for the device, including boot configuration, current configuration, interface information, time, and system version, execute the display diagnostic-information command.
To shorten the time used for collecting diagnostic information when the device has many configurations or a long operation time, execute the display diagnostic-information key-info command to collect only key diagnostic information. Before executing the display diagnostic-information command, use the display cpu-usage and display memory commands to view the CPU usage and memory usage, respectively. If the CPU or memory usage is too high, do not execute the display diagnostic-information command until the CPU or memory usage drops below the threshold.
To collect diagnostic information:
1. Display diagnostic information for the device.
¡ Display all diagnostic information for the device.
<Sysname> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N]:n
===============================================
===============display clock===============
14:03:55 UTC Thu 01/05/2021
=================================================
===============display version===============
...
¡ Display key diagnostic information for the device.
<Sysname> display diagnostic-information key-info
Save or display diagnostic information (Y=save, N=display)? [Y/N]:n
===============================================
===============display clock===============
15:03:55 UTC Thu 01/05/2021
=================================================
===============display version===============
...
2. Save diagnostic information to a diagnostic log file.
¡ Save all diagnostic information to a diagnostic log file.
<Sysname> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N]:y
Please input the file name(*.tar.gz)[flash:/diag_Sysname_20211020-194410.tar.gz]:
Diagnostic information is outputting to flash:/diag_Sysname_20211020-194410.tar.gz.
Please wait...
Save successfully.
¡ Save key diagnostic information to a diagnostic log file.
<Sysname> display diagnostic-information key-info
Save or display diagnostic information (Y=save, N=display)? [Y/N]:y
Please input the file name(*.tar.gz)[flash:/diag_Sysname_20211020-194412.tar.gz]:
Diagnostic information is outputting to flash:/diag_Sysname_20211020-194412.tar.gz.
Please wait...
Save successfully.
By default, diagnostic log files are saved in the flash:/ directory of the storage device.
3. Execute the dir command in user view to verify that the diagnostic file is generated correctly.
4. Transfer the diagnostic file to the desired destination by using FTP, TFTP, or SFTP. For more information, see the configuration guide for the switch.
Troubleshooting login failure
CAUTION: Make sure all user services have stopped before performing the following tasks. If user services are not interrupted, collect the failure information and contact H3C Support. |
If you cannot log in to the device through Telnet or SSH, log in from the console port and modify Telnet or SSH settings. If you cannot log in to the device from the console port, use this section to troubleshoot the issue.
Checking for power supply system failure
Symptom
The LEDs on the device or cards are off and the fans on the device or cards do not operate (determined by the sound).
Solution
To resolve the issue:
1. Verify that the power supply is powered on. If the device is installed with multiple power supplies, make sure the power supply that ensures device operation is powered on.
2. Verify that the LED that indicates a normal operating state for the power supply is on. See "Checking the LED status." If the power supply is faulty, it might have issues such as output short-circuit, output overcurrent, output overvoltage, input undervoltage, and overtemperature.
3. If the power supply has an input exception, contact electricians to examine and repair the power supply system for the equipment room, rack, or cabinet. If the power supply is faulty, replace the power supply.
4. If the issue persists, contact H3C Support.
Checking for inconsistent serial communication parameter settings between the configuration terminal and the console port
Symptom
Serial communication parameter settings between the configuration terminal and the console port are inconsistent.
Solution
To resolve the issue, edit the serial communication parameter settings for the serial port on the terminal.
By default, the communication parameter settings for the console port on the device are as follows:
· Baud rate—9600.
· Data bits—8.
· Stop bits—1.
· Parity—None.
· Flow control—None.
If the communication parameter settings for the console port on the device have been changed, use the most recent settings.
Checking for MPU failure (on modular devices)
Symptom
The RUN LED for the MPU is off.
Solution
To resolve the issue:
1. Reinstall the MPU and fasten the screws to make sure the MPU is installed securely.
2. Press the RESET button, the rightmost button on the MPU, to reboot the MPU.
3. If the device has an empty MPU slot, install the MPU in the empty slot and check its operational status.
4. Replace the MPU.
Resetting the device
Power off the device and then power on the device after three minutes.
Contacting H3C Support
If the issue persists, contact H3C Support.
Safety and configuration cautions and guidelines
This section describes important information that if not understood or followed can result in undesirable situations, including bodily injury, device damage, service interruption, or service anomalies. It contains hardware safety guidelines and CLI-based configuration cautions and guidelines. Before you work on or configure your device, read the information in this section carefully.
Hardware safety guidelines
Only trained and qualified personnel are allowed to perform the operations described in this guide. For more information, see H3C Switches Safety & Configuration Cautions and Guidelines.
Table 13 Hardware safety guidelines for fixed-port switches
Category |
Guidelines |
Handling expansion modules |
Do not install or remove an expansion module during startup of the device. |
Handling transceiver modules |
Do not stare into any open apertures of operating transceiver modules or optical fiber connectors. |
Handling cables |
Network cables are used for the communication between the device and the maintenance terminal. Network cable connection or disconnection can be performed only by qualified maintenance personnel for service adjustment as scheduled and they must be aware of the impact on the network. |
Handling fan trays |
Do not install fan trays of different models on the same device. |
Do not hot swap fan trays. |
|
Do not power on the device when the device is not installed with all fan trays. |
|
Do not touch the rotating fans when replacing a fan tray. |
|
Handling power supplies |
Do not hot swap power supplies. |
Operate the power switches on the PDUs in the cabinet only when upgrading or expanding the device, replacing the components in the device, or when a severe system failure occurs. |
Table 14 Hardware safety guidelines for modular switches
Category |
Guidelines |
Handling cards |
Keep a filler panel in the unused slot. |
When the device is operating, remove the active MPU only when both MPUs are operating stably. To view system stability and status information, execute the display system stable state command. |
|
Pressing the RESET button on an MPU will reset the MPU forcibly. This operation can be performed only by qualified maintenance personnel when a severe system failure occurs. |
|
Pressing the OFL button on a fabric module will isolate the services on the module. This operation can be performed only by qualified maintenance personnel before powering off a fabric module. |
|
Handling transceiver modules |
Do not stare into any open apertures of operating transceiver modules or optical fiber connectors |
Handling cables |
Network cables are used for the communication between the device and the maintenance terminal. Network cable connection or disconnection can be performed only by qualified maintenance personnel for service adjustment as scheduled and they must be aware of the impact on the network. |
Handling fan trays |
Do not hot swap fan trays. |
Do not power on the device when the device is not installed with all fan trays. |
|
Do not touch the rotating fans when replacing a fan tray. |
|
Handling power supplies |
Do not hot swap power supplies. |
Operate the power switches on the PDUs in the cabinet only when upgrading or expanding the device, replacing the components in the device, or when a severe system failure occurs. |
|
For devices that have two power switches, to power off the device for maintenance, make sure the two power switches are both turned off. |
CLI-based configuration cautions and guidelines
Only trained and qualified personnel are allowed to do the configuration tasks described in this guide. For more information, see H3C Switches Safety & Configuration Cautions and Guidelines.
Table 15 CLI-based configuration cautions and guidelines
Feature |
Command |
Description |
Usage guidelines |
File system management |
delete [ /unreserved ] file |
Deletes a file. |
The delete /unreserved file command deletes a file permanently. The file cannot be restored. The delete file command (without /unreserved) moves a file to the recycle bin unless it is executed on the default MDC to delete a file from a non-default MDC. |
File system management |
format |
Formats a file system. |
Formatting a file system permanently deletes all files in the file system. If a startup configuration file exists in the file system, back up the file if necessary. |
Device management |
power-supply off |
Powers off a card. |
Use this command with caution. A card cannot send or receive packets after this command is executed. |
Device management |
reboot |
Reboots the device. |
A reboot might interrupt network services. Use the force keyword only when the device fails or a reboot command without the force keyword cannot perform a reboot correctly. A reboot command with the force keyword might result in file system corruption, because it does not perform data protection. |
Common interface settings |
shutdown |
Shuts down an interface. |
Use this command with caution. This command disables the interface from forwarding or receiving traffic. |
Common interface settings |
default |
Restores the default settings for an interface. |
The default command might interrupt ongoing network services. Use this command with caution. |