Huawei S Series Switch Routine Maintenance Steps Explained

The Huawei S series (S5700, S7700, S12700 and others) is deployed in large numbers across enterprise campuses and data centres. The purpose of routine maintenance is not to rush repairs once a fault has occurred, but to identify hidden risks in advance. The following is an inspection workflow that can be put into practice directly.

1. Preparation before maintenance

• Confirm the maintenance window and avoid business peak periods
• Back up the current configuration (see below) and the version information
• Prepare an out-of-band management channel so that an operating error does not leave you locked out
• Record key metrics before maintenance to serve as a baseline

2. Overall device status check

```

display version // version, uptime, patch information

display device // whether boards and subcards are Normal

display power // power module status

display fan // fan speed and status

display temperature // temperature at each monitoring point

```

Key points to watch:

• Whether all boards are Normal and none are Offline
• Whether power is supplied redundantly and whether there is a single-feed alarm
• Whether the air inlet temperature remains persistently high (a sign of cooling or environmental problems)

3. Resource utilisation check

```

display cpu-usage // CPU utilisation

display memory-usage // memory utilisation

```

CPU or memory sustained above 70% requires further analysis. A persistently high level may indicate abnormal traffic, a loop or an excessive number of table entries, and is a precursor to a potential fault.

4. Interface and link check

```

display interface brief // status, speed and duplex of each interface

display interface GigabitEthernet 0/0/1 // detailed information for a single interface

```

Key points to watch:

• Whether there are unexpected down interfaces
• Whether CRC / error packet counts keep growing (usually pointing to cables, optical modules or interference)
• Whether speed and duplex are negotiated consistently with the peer
• Whether the transmit and receive optical power of optical interfaces is within specification

5. Log and alarm check

```

display logbuffer // log buffer

display trapbuffer // alarm buffer

```

Work through the alarms along the timeline, focusing on:

• Repeated port up/down events (an unstable link)
• Temperature, fan and power alarms
• Authentication, ARP and routing anomalies

6. Configuration and version management

```

display current-configuration // currently running configuration

display saved-configuration // saved configuration

```

Recommended actions:

• Export the current configuration as a backup, labelled with the date and version
• Compare the running configuration with the saved configuration for consistency
• Check whether NTP time synchronisation is working (inaccurate time strips the logs of any troubleshooting value)
• Verify that the log server and SNMP alarm reporting are available

7. Environmental and physical checks

• Clean the air inlet filters and remove dust from the rack
• Check cable bundling and the completeness of labels
• Confirm that the rack airflow path is not obstructed
• Check earthing and power distribution status

8. Wrap-up after maintenance

1. Save the configuration: `save`

2. Record a maintenance report: items checked, problems found, how they were handled, outstanding issues

3. Update the device asset and maintenance records

Recommended maintenance intervals

The value of routine maintenance lies in the "trend". A single set of figures is only a snapshot; only continuous records show whether a device is heading towards failure.

Note: This article is provided for technical exchange and experience sharing. Always refer to the original manufacturer's technical documentation and the conditions of your own environment. Maintenance and change operations should be carried out by qualified engineers.