To identify a fault effectively, you must determine whether the fault exists in the UPCC.

The basic rules for identifying a fault are as follows:

• Checking alarms and then components

  To identify a fault effectively, you are advised to check the alarm information and then analyze whether the fault is caused by a component accordingly.

• Identifying networks and then NEs

  Generally, a carrier network consists of several sub-networks. When a service is interrupted, identify the faulty network and then the faulty network element (NE) in the faulty network.

• Identifying configuration errors and then hardware failures

  After identifying that the UPCC is faulty, identify software failures and configuration errors that can be fixed on the M2000 and then board, optical module, and link failures on site.

• Analyzing common problems and then individual problems

  When analyzing a UPCC service failure, analyze the common problems such as active/standby switchover failure and resource overuse, and then the specific service failure.

• Analyzing major logs and then minor logs

  After collecting the UPCC log information, analyze the major log information such as interface Up/Down status, active/standby switchover, and number of discarded packets, and then the minor log information such as command configuration and subscriber operation.