Troubleshooting hardware failures

For more information about the LEDs on the device, see H3C RA5300[5300-X][5300-AC] Routers Hardware Information and Specifications.

System failures

No display or garbled display on the configuration terminal

Symptom

The configuration terminal does not have a display or has garbled display when the device is powered on.

Common causes

The following are the common causes for this type of issue:

·     The power system is operating incorrectly.

·     The MPU is operating incorrectly.

·     The console cable is not connected to the console port on the MPU.

·     Configuration terminal parameters are incorrect.

·     The console cable has exceptions.

Troubleshooting flow

Figure 1 shows the troubleshooting flowchart:

Figure 1 Troubleshooting flow

 

Solution

1.     Verify that the power system is operating correctly.

If the power system is operating incorrectly, see the power failure troubleshooting section to resolve the issue.

2.     Verify that the MPU is operating correctly.

If the MPU is operating incorrectly, see the MPU failure troubleshooting section to resolve the issue.

3.     Verify that the console cable is correctly connected to the console port on the MPU.

4.     Verify that the console cable is correctly connected to the console port and the specified serial port on the configuration terminal. Verify that the following settings are configured for the terminals:

¡     Baud rate—9600.

¡     Data bits—8.

¡     Parity—None.

¡     Stop bits—1.

¡     Flow control—None.

Verify that the terminal is VT100. The serial port settings depend on the device model.

5.     Replace the console cable.

6.     If the issue persists, collect the following information and contact Technical Support:

¡     Results of each step.

¡     The configuration file, log messages, and alarm messages.

Related alarm and log messages

Alarm messages

N/A

Log messages

N/A

Unexpected device reboot

Symptom

The device reboots unexpectedly.

Common causes

This type of issue is typically caused by startup file exceptions.

Troubleshooting flow

Figure 2 shows the troubleshooting flowchart:

Figure 2 Flowchart for troubleshooting unexpected reboot of a device

 

Solution

1.     Identify whether the device can enter command line state after it reboots.

If the device can enter command line mode, execute the display diagnostic-information command to collect diagnostic information. Then, export the device data and send it to H3C technical support for help.

When you execute the display diagnostic-information command, you can specify the key-info keyword to collect only critical diagnostic information and reduce collection time.

2.     Verify that the startup file is normal.

If the device cannot enter command line mode, connect it via the console port and reboot it again. If BootWare reports a CRC error or fails to locate the startup file, use the BootWare menu to reload the startup file and set it as the current startup file. During the BootWare loading process, BootWare automatically sets this file as the current startup file.

3.     If the issue persists, collect the following information and contact Technical Support:

¡     Results of each step.

¡     The configuration file, log messages, and alarm messages.

Related alarm and log messages

Alarm messages

N/A

Log messages

N/A

Voltage anomaly alarm

Symptom

The system outputs an alarm message for abnormal voltage, for example:

DEV/4/VOLTAGE_HIGH: Voltage is greater than the high-voltage alarm threshold on chasiss 1 slot 16 voltage sensor 1.

DEV/4/VOLTAGE_LOW: Voltage is less than the low-voltage alarm threshold on chasiss 1 slot 16 voltage sensor 24.

Common causes

This type of issue is typically caused by hardware failures.

Troubleshooting flow

Figure 3 shows the troubleshooting flowchart:

Figure 3 Flowchart for troubleshooting voltage anomaly

 

Solution

Execute the display voltage command to check voltage sensor readings on the device. Contact technical support if you find any abnormalities.

Related alarm and log messages

Alarm messages

N/A

Log messages

·     VOLT_HIGH

·     VOLT_LOW

·     VOLT_NORMAL

Memory anomaly alarm

Symptom

The system outputs an alarm message for abnormal memory usage, for example:

DIAG/1/MEM_EXCEED_THRESHOLD: Memory minor threshold has been exceeded.

Common causes

This type of issue is typically caused by memory leakage.

Troubleshooting flow

Figure 4 shows the troubleshooting flowchart:

Figure 4 Flowchart for troubleshooting high memory usage

 

Solution

1.     Check the usage of each memory module.

2.     Execute the display system internal kernel memory pool command in probe view to check the memory usage. Identify memory modules with abnormal or continuously increasing usage.

<Sysname> system-view

[Sysname] probe

[Sysname-probe] display system internal kernel memory pool slot 1

Active    Number  Size     Align Slab Pg/Slab ASlabs  NSlabs Name

9126      9248    64       8     32   1       289     289    kmalloc-64

105       112     16328    0     2    8       54      56     kmalloc-16328

14        14      2097096  0     1    512     14      14     kmalloc-2097096

147       225     2048     8     15   8       12      15     kmalloc-2048

7108      7232    192      8     32   2       226     226    kmalloc-192

22        22      524232   0     1    128     22      22     kmalloc-524232

1288      1344    128      8     21   1       64      64     kmalloc-128

0         0       67108808 0     1    16384   0       0      kmalloc-67108808

630       651     4096     8     7    8       93      93     kmalloc-4096

68        70      131016   0     1    32      68      70     kmalloc-131016

1718      2048    8        8     64   1       31      32     kmalloc-8

1         1       16777160 0     1    4096    1       1      kmalloc-16777160

2         15      2048     0     15   8       1       1      sgpool-64

0         0       40       0     42   1       0       0      inotify_event_cache

325       330     16328    8     2    8       165     165    kmalloc_dma-16328

0         0       72       0     30   1       0       0      LFIB_IlmEntryCache

0         0       1080     0     28   8       0       0      LFIB_IlmEntryCache

0         0       1464     0     21   8       0       0      MFW_FsCache

1         20      136      0     20   1       1       1      L2VFIB_Ac_cache

0         0       240      0     25   2       0       0      CCF_JOBDESC

0         0       88       0     26   1       0       0      NS4_Aggre_TosSrcPre

0         0       128      0     21   1       0       0      IPFS_CacheHash_cachep

---- More ----

View the values in the Number and Size columns. If you find that the memory usage of a block is continuously increasing, it indicates that the block is being constantly used.

¡     An increase in the usage of some memory blocks can be normal, so you must determine whether the increase is truly abnormal. Number*Size represents the amount of memory used by a module. Identifying whether the memory usage is normal might require monitoring the rate of memory growth and the amount of memory used over time.

¡     Some memory leaks might be slow, so a longer period (even several weeks) of observation and comparison might be needed.

3.     Collecting information and contacting Technical Support

As a best practice, contact Technical Support to collect failure information.

For correct failure location, do not restart the device.

Related alarm and log messages

Alarm messages

N/A

Log messages

·     MEM_ALERT

·     MEM_EXCEED_THRESHOLD

·     MEM_BELOW_THRESHOLD