{"id":915,"date":"2014-08-11T11:19:10","date_gmt":"2014-08-11T03:19:10","guid":{"rendered":"http:\/\/www.thunder-link.com\/blog\/?p=915"},"modified":"2023-04-12T14:00:16","modified_gmt":"2023-04-12T06:00:16","slug":"cautions-for-service-configuration-failure-on-osn-9500","status":"publish","type":"post","link":"https:\/\/www.thunder-link.com\/blog\/cautions-for-service-configuration-failure-on-osn-9500\/","title":{"rendered":"Cautions for Service Configuration Failure on OSN 9500"},"content":{"rendered":"

[Problem Description]<\/strong>
\nTrigger conditions:
\nTwo lower order cross-connection protection groups are configured on an OptiX OSN<\/a> 9500. If any of the following operations is performed, the problem occurs.<\/p>\n

\"Huawi
\n<\/a>
\n1. Configure lower order services, or convert ordinary lower order services to lower order SNCP.
\n2. Run commands or perform operations on the NMS to adjust concatenated timeslots.<\/p>\n

3. Download configurations from the NMS.<\/p>\n

Symptoms:
\n1. Lower order services fail to be configured. The error code “38735” is returned, indicating that the verification services on the matrix algorithm submodule fail to be connected.
\n2. After service configuration, the system control board may be reset.
\n3. The system control board is frequently reset when perform concatenated timeslot adjustment operations on the NMS or running commands.<\/p>\n

Identification method:
\nOptiX OSN 9500 NEs are configured with two lower order cross-connection protection groups. Note that only OSN 9500 NEs with a V100R6 version or later can be configured with two lower order cross-connection protection groups.<\/p>\n

Scenario 1:
\nLower order services fail to be configured. The error code “38735” is returned, indicating that the verification services on the matrix algorithm submodule fail to be connected. Alternatively, the system control board may be warm reset.
\nScenario 2:
\nThe system control board is frequently reset when perform concatenated timeslot adjustment operations on the NMS or running commands.]<\/p>\n

[Root Cause]<\/strong>
\nDuring concatenated timeslot adjustment, higher order concatenation needs to be established between two cross-connection protection groups to search and allocate concatenated lower order TU timeslots for lower order cross-connections. The algorithm for allocating concatenated lower order timeslots has defects. Therefore, invalid lower order timeslots are allocated in some specific scenarios, resulting in array subscript violation and memory access exception in further allocation. As a result, NEs are abnormally reset.
\nAs for the service configuration failure that occurs after configuration downloading from the NMS, it is mainly caused by the defects in the algorithm for allocating concatenated lower order TU timeslots. Therefore, invalid TU timeslots are allocated, and they will fail in the lower order algorithm verification when functioning as service sinks<\/p>\n

[Impact and Risk]<\/strong>
\n1. Lower order services may fail to be configured. There is a low probability that the system control boards are reset.
\n2. Lower order resources cannot be optimized by adjusting concatenated timeslots. Otherwise, NEs may be frequently reset.
\n3. Configurations may fail to be downloaded from the NMS.
\n4. If an NE is faulty, the system control board may fail to be started after warm reset or active\/standby switching.
\n5. This problem does not affect:<\/p>\n