No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

An OptiX OSN 3500 NE Goes Beyond the Reach of the T2000 Due to an ECC Allocation Problem

Publication Date:  2012-07-25  |   Views:  219  |   Downloads:  0  |   Author:  SU1002230744  |   Document ID:  EKB0000387612


Issue Description

An OptiX OSN 3500 NE works properly under the management of the T2000. After being upgraded from version to version, however, the NE goes beyond the reach of the T2000. The T2000 cannot reach the NE. The engineers cannot log in to the NE through the T2000. On the NE, slots 1, 2, and 3 house the SLQ1s and slots 8 and 11 house the SL16s. The boards in slots 8 and 11 transfer the ECC information. 


Alarm Information


Handling Process

Disable the ECC bytes on the optical interfaces for the preceding three slots. Then, slots 8 and 11 obtain ECC bytes. The NE comes back within the reach of the T2000. 

Root Cause

Log in to the NE on the site. The login succeeds without any alarm. Run the command ecc-get-bdinfo to query the board information. It is found that slots 8 and 11 do not obtain any ECC but that the preceding three unused slots obtain ECC bytes. Query the ECC allocation mode. It is found that the ECC bytes are allocated by using 10 channels of D1�D3 bytes. After being upgraded and reset, the SCC reallocates the ECC bytes. In this case, the SCC allocates the ECC bytes to only the preceding three slots. Therefore, slots 8 and 11 do not obtain any ECC. As a result, the T2000 cannot reach the NE. 


By default, the OptiX OSN 3500 allocates 10 ECC bytes. After being upgrade and reset, the NE reallocates the ECC bytes. In this case, the NE may allocate an ECC to even an unused interface. To prevent the NE from allocating ECC bytes to unused interfaces, disable the ECC bytes on the unused interfaces as required.