OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

Contents

Contents
7 Troubleshooting Pointer Justification ...................................................................................7-1
7.1 Background Knowledge .............................................................................................................. 7-1 7.1.1 Mechanism of Pointer Justification.................................................................................... 7-1 7.1.2 Detection Report of Pointer Justification........................................................................... 7-3 7.1.3 Performance Events of Pointer Justification ...................................................................... 7-3 7.2 Common Faults and Causes ........................................................................................................ 7-4 7.3 Methods for Fault Locating ......................................................................................................... 7-6 7.3.1 Common Locating Methods .............................................................................................. 7-6 7.3.2 Procedures.......................................................................................................................... 7-6 7.4 Fault Handling ........................................................................................................................... 7-10 7.4.1 Checking Clock Configuration Data................................................................................ 7-10 7.4.2 Checking Ambient Temperature ...................................................................................... 7-10 7.4.3 Checking Synchronization of Interconnection Equipment .............................................. 7-11 7.4.4 Checking Connection of Optical Fibers........................................................................... 7-11 7.4.5 Checking Quality of External Clock................................................................................ 7-11 7.4.6 Checking NE Hardware Faults ........................................................................................ 7-12

Issue 06 (2006-11-20)

Huawei Technologies Proprietary

Contents

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

Figures
Figure 7-1 Generation of AU pointer................................................................................................ 7-2 Figure 7-2 System networking diagram ........................................................................................... 7-3 Figure 7-3 Flowchart of pointer justification handling..................................................................... 7-7

ii

Huawei Technologies Proprietary

Issue 06 (2006-11-20)

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

Tables

Tables
Table 7-1 Performance events of pointer justifications..................................................................... 7-4 Table 7-2 Common causes for the pointer justifications................................................................... 7-4 Table 7-3 Alarms related to the pointer justification and possible causes ........................................ 7-8

Issue 06 (2006-11-20)

Huawei Technologies Proprietary

iii

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

7 Troubleshooting Pointer Justification

7

Troubleshooting Pointer Justification

This chapter describes how to handle pointer justification of the OptiX OSN 3500/2500/1500. The main topics are: Background knowledge Common faults and causes Methods for fault locating Fault handling

7.1 Background Knowledge

The pointer justification is a specific phenomenon of the SDH network. When pointer justification appears, it indicates that there are non-synchronized NEs in the SDH network. By handling the pointer justification in time, clocks of respective NEs can be synchronous in the SDH network. Thus, the signal quality of the transmission can be ensured.

7.1.1 Mechanism of Pointer Justification

In an SDH network, there are two kinds of pointers, administrative unit pointer (AU-PTR) and tributary unit pointer (TU-PTR). There are two corresponding pointer justifications, AU pointer justification and TU pointer justification. The generation mechanism of these two kinds of pointer justification is basically the same. For details, see Chapter 1 "Generation of Alarm and Performance of SDH Service" of the OptiX OSN 3500/2500/1500 Intelligent Optical Transmission System Maintenance Manual Alarm and Performance Event.

Generation Mechanism of AU Pointer Justification

Normally, all the NEs in an SDH network are synchronous. Pointer justifications do not appear. The main reason for the AU pointer justification is that the clocks of respective NEs in the SDH network are out of synchronization. See Figure 7-1. The E1 service between NE1 and NE6 passes through the intermediate NEs at the VC-4 level. NE1 is the clock source, and the other NEs trace its clock signal west. If the clocks of NEs 2 and 3 are not synchronous, the east

Issue 06 (2006-11-20)

Huawei Technologies Proprietary

7-1

7 Troubleshooting Pointer Justification

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

optical board of NE2 and the west optical board of NE3 will fulfill the AU pointer justifications. These justifications will cause the pointer justifications of the west optical boards of NEs 1, 4, 5 and 6.

If the clock of NE2 runs faster than that of NE3, the east optical board of NE2 will execute the AU positive pointer justification. Meanwhile, the west optical board of NE3 will execute the AU negative pointer justification. If the clock of NE2 runs slower than that of NE3, the east optical board of NE2 will execute the AU negative pointer justification. Meanwhile, the west optical board of NE3 will execute the AU positive pointer justification.

T2000 NE1
W W

NE2
E W

NE3
E E W

NE4
E W

NE5
W E W

NE6

E1

E1

Figure 7-1 Generation of AU pointer

Generation Mechanism of TU Pointer Justification

For the TU pointer, the TU pointer justification does not occur in the period of adapting the E1 signals into the VC-12s until forming the STM-1 signal. If the frequency deviation lies between the E1 signal and the SDH clock, they can be synchronized by adaptation. Therefore, all the TU pointer justifications detected by the tributary board are transformed from the AU pointer justifications. The condition for the transformation is to configure the pass-through or add/drop of the VC-12. Note that the AU pointer justification is not reported after the AU is transformed into the TU pointer. See Figure 7-2. The E1 services are inserted to NE1. Parts of the services are dropped on NE2. Another part of the services passes through NE2 and is dropped on NE3. If the clocks of NE1 and NE2 are not synchronous, the AU pointer justification will occur in the west boards of NEs 1 and 2, and then are transformed into the TU pointer justification of NEs 1 and 2. The AU pointer justification of the west optical board of NE2 will cause the AU pointer justifications occurring in the west optical board of NE3. The AU pointer justifications generated in the west optical boards of NEs 2 and 3 will be directly transformed into the TU pointer justifications of NE3, too. Thus, the TU pointer justifications are reported in NEs 1, 2 and 3.

7-2

Huawei Technologies Proprietary

Issue 06 (2006-11-20)

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

7 Troubleshooting Pointer Justification

T2000 NE1
W W

NE2
E W

NE3

E1

E1

E1

Figure 7-2 System networking diagram

7.1.2 Detection Report of Pointer Justification

When this station generates the AU pointer justification, this station does report it. Instead, this station transmits the pointer justification information to the remote station through the H1 and H2 bytes. The remote station will report the event of the AU pointer justification by interpreting the H1 and H2 bytes. Thus, in remote detection mode, if the remote station reports the AU pointer justification event, it means that the pointer justification is generated in the local station. Taking Figure 7-1 for example, the clocks of NE2 and NE3 are not synchronous, but the east optical board of NE2 and the west optical board of NE3 do not detect the report of the AU pointer justification performance event. However, the pointer justification, generated in the west optical board of NE3, will be detected and reported in the west optical board of NE4. The pointer justification, generated in the east optical board of NE2, will be detected and reported in the west optical board of NE1.

Note The generation of the pointer justification is a different concept compared with the detection and report of the pointer justification. The pointer justification may not be detected and reported absolutely from where it is generated. For the AU pointer, it is generated in the upstream station, and reported in the downstream station. For the TU pointer, it is generated in the station where the AU pointer is transformed into the TU pointer, but detected and reported from the tributary board of the service termination station.

7.1.3 Performance Events of Pointer Justification

The parameters AUPJCHIGH and AUPJCLOW are generated in the multiplex section adaptation (MSA) of the line board. They respectively represent the AU positive pointer justification count and the AU negative pointer justification count. The parameters TUPJCHIGH and TUPJCLOW are generated in the higher order path adaptation (HPA) of the tributary board. They respectively represent the TU positive pointer justification count and the TU negative pointer justification count.

Issue 06 (2006-11-20)

Huawei Technologies Proprietary

7-3

7 Troubleshooting Pointer Justification

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

Table 7-1 shows the pointer justification performance events supported by the OptiX OSN 3500/2500/1500.
Table 7-1 Performance events of pointer justifications
Acronym Detailed information

AUPJCHIGH AUPJCLOW TUPJCHIGH TUPJCLOW

AU positive pointer justification count AU negative pointer justification count TU positive pointer justification count TU negative pointer justification count

7.2 Common Faults and Causes

Table 7-2 shows the common causes for the pointer justification. They can be classified into external factors, data configuration causes, and equipment causes. One or the combination of them may cause the pointer justification. Analyze them one by one with related fault locating method based on actual situations.
Table 7-2 Common causes for the pointer justifications
Category Causes

External causes

External clock signal degrade, for example, the external clock signal provided by the equipment, such as building integrated timing supply system (BITS) Misconnection of optical fibers, thus causing mutual tracing of two NEs Extra-high equipment temperature (for example, fans are not cleaned for a very long time or fans failed or the air conditioner in the equipment room failed) Unreasonable planning of the clock network (for example, the clock tracing link is too long)

Data configuration causes

Multiple independent clock sources are configured in the same SDH network Wrong configuration of the clock source level, thus cause mutual tracing of two NEs The synchronization status message (SSM) protection function is not correctly enabled. The one that shall be enabled is not enabled. The one that has been enabled is not correctly set

Equipment causes

Clock board failure or performance deterioration Line board failure or performance deterioration Cross-connect board failure or performance deterioration

7-4

Huawei Technologies Proprietary

Issue 06 (2006-11-20)

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

7 Troubleshooting Pointer Justification

7.3 Methods for Fault Locating

7.3.1 Common Locating Methods

Alarm and performance analysis Configuration modification Replacement

7.3.2 Procedures
The clock out-of-synchronization is the primary cause of pointer justification. Locate faults mainly by handling problems related to the clocks. The fault should be located following the service direction, clock tracing direction, detection report location of pointer justification and the generation location of pointer justification. Figure 7-3 shows the flowchart of locating the pointer justification.

Issue 06 (2006-11-20)

Huawei Technologies Proprietary

7-5

7 Troubleshooting Pointer Justification

Trouble shooting of Pointer justification

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

NMS 1 If any other alarm in the network? No 2 If equipment interconnection involved? No 3 If the first station has the AU pointer justification? No Note2 Handle the out-ofsynchronization between the previous NE and this NE Yes Note1 Yes If the clock of the interconnection equipment out of synchronization? No Handle the out-ofsynchronization between two upstream NE of this NE Yes Handle the out-ofsynchronization Yes Handle the alarm

4 If incorrect clock configuration? No Yes

If more than two clock synchronization sources at the same time? No

Yes

Leave only one clock synchronization source

Correctly configure the clock 5 Yes If extra-high temperature? No If the fan fault? No Handle extra-high ambient temperature 6 If optical fibers misconnected? No 7 If the external clock degraded? No 8 If the NE clock degraded? No Yes If the timing unit faulty? No If the line board faulty? No If the cross-connect unit faulty? No Go to the next step N No If the pointer justification removed? Yes Contact Huawei for technical support End Yes Replace the EXCS board Yes Replace the line board Yes Replace the EXCS board Yes Use a clock source with better clock quality Yes Correct the connection of optical fibers Yes Handle the fan fault

Figure 7-3 Flowchart of pointer justification handling

Note 1: The first station refers to the one that first reports the pointer justification in the service direction, the same as the clock direction, in the clock tracing direction. Note 2: The first station has no AU pointer justification, that is, it only has the TU pointer justification. Now we shall handle the problem of the TU pointer justification.

7-6

Huawei Technologies Proprietary

Issue 06 (2006-11-20)

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

7 Troubleshooting Pointer Justification

Checking and Analyzing Alarms

In the process of the troubleshooting, other alarms are commonly coped with first. This is because the pointer justification may appear following the alarms related to the clock, such as SYN_BAD, LTI, SYNC_C_LOS, EXT_SYN_LOS, and so on. After the alarms are cleared, the pointer justification will clear normally. Otherwise, fulfill the fault locating by following the instructions stated in the flowchart. Table 7-3 lists the alarms related to pointer justification and the causes and handling methods.
Table 7-3 Alarms related to the pointer justification and possible causes
Alarm name Possible causes Handling methods

SYN_BAD (synchronization source degrade)

1) The synchronization source being traced deteriorates. 2) The clock of this station fails.

1) Reset the priority level of the clock source. 2) If the line clock source is traced, check if there is the R_LOS alarm and solve it with appropriate methods. 3) If the tributary clock source is traced, check if there is the T_ALOS alarm and solve it with appropriate methods. 4) If the external clock is traced, check if the external clock source runs normally.

LTI (loss of synchronization source)

1) Check the clock synchronization configuration to see if a non-existing clock source is set as being traced by the 1) Optical fiber break (if the line synchronization clock source. If the clock source is being traced) configuration is incorrect, modify and 2) The external clock source stops re-download it. inputting (if the external clock 2) If the configuration is correct, check if the source is being traced). traced synchronization source is normal. If 3) The synchronization source is not, eliminate the corresponding failure to configured as being unrecoverable. make it normal. (For example, if it is 4) The SSM clock protection is configured as tracing the line clock and if enabled by mistake. there is signal loss alarm on the line, When the SSM clock protection is eliminate the signal loss alarm first. If enabled: tracing the external clock, check if the 1) Optical fiber break external clock is normal and if the external 2) The quality of the synchronization clock line is in good contact.) source is not stable; the external 3) If the traced synchronization source is clock has no input; the free-run mode normal, it can be determined that the board is active. fails. Replace the board. 3) Synchronization source configuration error 4) External clock deterioration When the SSM clock protection is not enabled:

Issue 06 (2006-11-20)

Huawei Technologies Proprietary

7-7

7 Troubleshooting Pointer Justification Alarm name Possible causes

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting Handling methods

SYNC_C_LOS (loss of synchronization source class

When the SSM clock protection is not enabled:

1) Re-set the priority level of clock source. 2) If line clock source is traced, check if 1) Optical fiber breaks (when the line there is the R_LOS alarm and solve it with appropriate methods. clock source is traced). 3) If the tributary clock source is traced, 2) The external source clock stops check if there is alarm (such as T_ALOS) inputting (when the external clock and solve it with appropriate methods. source is traced). 4) If the external clock is traced, check if the When the SSM clock protection is external clock source runs normally. enabled: 1) S1 byte switching occurs in this station. 2) The external clock (BITS) input has changed.

EXT_SYNC_LOS (loss of external clock source)

Loss of external clock source

1) Check if the input cable of the external clock is well connected. 2) Check if the equipment that provides the external clock works normally.

Common Methods for Analyzing and Locating AU Pointer Justification

In the clock tracing direction, some services consecutively pass through multiple intermediate stations in the VC-4 level. Then, the station, previous to the one that first reports the AU pointer justification, is the one whose clock is out of synchronization. This conclusion is applicable to any networks such as chain network and ring network.

Common Methods for Analyzing and Locating TU Pointer Justification

Generally, for the PDH service the network-wide clock reference source is configured as free-run or tracing the external clock. In the clock tracing direction, the first station (except the service central station), where the TU pointer justification occurs, is the station whose clock is out of synchronization. The problem may lie in the clock board or the line board that extracts the clock, or in the line board of the upstream station which transmits the signal. This conclusion is applicable to any networks such as chain network and ring network.

7-8

Huawei Technologies Proprietary

Issue 06 (2006-11-20)

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

7 Troubleshooting Pointer Justification

7.4 Fault Handling

7.4.1 Checking Clock Configuration Data
Incorrect clock configuration can result in clock out-of-synchronization. Follow the steps below to ensure the correctness of the configuration data and locate faults.
Step Operation

1 2 3 4

Check if the network is configured with more than two clock sources that result in the pointer justification. Check if the traced clock source has a low precision. For example, the precision of the access switch clock is low or there are too many tracing stations. Check if the clock protection subnet is not set. After the main clock is lost (or fiber cut), the non-protection of the clock causes the pointer justification. Check if the level of the clock source is incorrectly set. After the clock protection switching, clocks begin to trace each other, which results in the pointer justification. Check if the internal clock source of the main clock NE is configured with the clock source ID. After the clock source of a higher level is lost, the NE enters the free-run mode. Other NEs will not synchronize to the central station, this causes all the NEs in this clock subnet are in the free-run mode. Thus, the pointer justification is generated. Check if the SSM clock protection is enabled. When the clock quality deteriorates, the protection switching cannot be executed, thus generating the pointer justification. When the SSM clock protection is not enabled, the SSM quality output is set as "Disable". So, the clock quality transmitted to other NEs is unusable. The SSM will be automatically enabled after some NE is started again. Once the NE detects that the quality of all the line clock sources is unusable, it will begin to trace the internal clock. Meanwhile, it will enter the free-run mode, thus generating the pointer justification.

7.4.2 Checking Ambient Temperature

Overly high temperature of the equipment can also lead to the pointer justification. After locating the fault to a single station, check the ambient temperature of this NE.
Step Operation

1 2 3

Check the subrack fan. Check if the air filter is blocked with too much dust. Check if the air-conditioner in the equipment room works normally.

Issue 06 (2006-11-20)

Huawei Technologies Proprietary

7-9

7 Troubleshooting Pointer Justification

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

7.4.3 Checking Synchronization of Interconnection Equipment

In interconnecting the equipment of varied types or from different vendors, first check if the clocks are synchronized. Set the SDH equipment using the same clock source with other equipment. Otherwise, the pointer justification can be generated, too. The networkwide clock out-of-synchronization does not imply a problem of the transmission equipment itself. It may be a problem of an unreasonable planning of the networkwide clock synchronization. For example, the interconnecting equipment traces a clock reference source while the transmission equipment traces another, thus resulting in a certain deviation between the clocks of the two networks.

Note When the SDH is interconnected with other equipment, such as router, ATM equipment, switch, or microwave equipment, the pointer justification may occur due to the clock out-of-synchronization. The pointer justification generated during the equipment interconnection can be ignored if it does not affect services. If it is necessary to eliminate the pointer justification, the clock source shall be planned uniformly for the interconnection equipment.

7.4.4 Checking Connection of Optical Fibers

In some network protection modes (such as path protection ring), services will still be normal even if the optical fiber is mis-connected in the east and west directions. However, the clocks will trace each other, and thus pointer justification will be generated. Through the NM, insert the MS_RDI alarm for the NE that the optical fiber may be mis-connected, or query the ECC route. Operate to determine if the optical fiber is wrongly connected. If the optical fiber is wrongly connected, the pointer justification will disappear after correcting the connection.

7.4.5 Checking Quality of External Clock

Generally, check the quality of the external clock source by modifying the configuration of the clock source. Sometimes the low precision of the external clock source traced by the SDH equipment may cause the networkwide pointer justification. Also, the switching of the upper level clock source of the external BITS may cause the pointer justification to the SDH equipment. Quality factors of the external clock source, which can cause the pointer justification in the NE, include:

Low precision of the clock source

Huawei Technologies Proprietary

7-10

Issue 06 (2006-11-20)

OptiX OSN 3500/2500/1500 Maintenance Manual - Troubleshooting

7 Troubleshooting Pointer Justification

The external clock source is unavailable Power cables of the external clock deteriorate

7.4.6 Checking NE Hardware Faults

After the external causes are excluded, check if the board of the NE where the pointer justification is generated fails. Major factors that affect the NE clock quality include:

The clock board fails or its performance deteriorates. The line board fails or its performance deteriorates. The cross-connect board fails or its performance deteriorates.

In this case, the major method for locating faults is to modify the clock configuration. First, change the tracing direction of the clock. Then, based on the generation and disappearance of the pointer justification, analyze the fault and locate it to a specific board of the NE. Finally, replace the board in accordance with the actual situation. In this way, the pointer justification can be removed.

Note Among them, faults of the clock board and line board are common, especially for the clock board. After eliminating the faults of the line board and clock board, we shall consider if the cross-connect board fails. Because the clock, generated by the clock board through phase-lock, is first transmitted to the cross-connect board. After that, it is distributed to the line board or the tributary board through the cross-connect board.

Issue 06 (2006-11-20)

Huawei Technologies Proprietary

7-11