Keywords

duplicate cross-connection protection group IDs, different number of services, LP_UNEQ_VC12 alarm

Version Mapping

NMS	OS	Database	NE
U2000 earlier than V100R009C00SPC301	Solaris and Linux	-	-

 

Symptom

A user deactivates five trails successfully, but the error message "Different number of services.Error Code: 1090594062" is displayed indicating that errors exist on the NE.

The user deactivates the five pieces again. The operation succeeds but the error message is also reported. In addition, another five irrelevant services in use report the uneq and LP_UNEQ_VC12 alarms.

 

 

 

Problem Identification

The U2000 database contains duplicate 1+1 service protection group IDs. The U2000 V100R006C02CP3051 does not implement strong verification for duplicate protection group IDs. As a result, the U2000 provisions other services with the same protection group ID.

Cause Analysis

1.         E2E log analysis finds that when trails are deactivated, the NE management process displays the error message "Different number of services.Error Code: 1090594062."

[13:39:50.612],Info ,[T570],nmlsdh { -- SEQUENCE -- QAsnDeleteXCRsp

    ……

                objName 393238332de68192e99a86e4b89ae58aa1e6ba90efbc9a393238332de68192e99a862d382d4e31534c36342d31285344482d31292d5643342d32362d564331323a343720e4b89ae58aa1e5aebfefbc9a393238332de68192e99a862d362d4e31534c5131362d31285344482d31292d5643342d362d564331323a3539H  -- "9283-..................9283-......-8-N1SL64-1(SDH-1)-VC4-26-VC12:47.............9283-......-6-N1SLQ16-1(SDH-1)-VC4-6-VC12:59" --,

                errCode 1090594062,

                strOperDesc -- void --

            }

2.         Checking the live-network database finds that multiple 1+1 protection group services of the NE contain duplicate protection group IDs.

NE that is being checked:  9283 Phyid: 599107, Logicid: 3148791

PG ID: 268435492, xc: 8-1-24-52-->5-1-1-20---vc12, Flag: 0

PG ID: 268435492, xc: 8-1-29-62-->5-1-1-26---vc12, Flag: 0

PG ID: 268435492, xc: 8-1-24-52-->14-1-1-20---vc12, Flag: 64

PG ID: 268435492, xc: 8-1-29-62-->14-1-1-26---vc12, Flag: 64

PG ID: 268435540, xc: 11-1-2-19-->5-1-2-32---vc12, Flag: 0

PG ID: 268435540, xc: 8-1-24-15-->5-1-1-17---vc12, Flag: 0

PG ID: 268435540, xc: 11-1-2-19-->14-1-2-32---vc12, Flag: 64

PG ID: 268435540, xc: 8-1-24-15-->14-1-1-17---vc12, Flag: 64

PG ID: 268436295, xc: 8-1-26-47-->6-1-6-59---vc12, Flag: 0

PG ID: 268436295, xc: 8-1-26-33-->5-1-4-48---vc12, Flag: 0

PG ID: 268436295, xc: 8-1-26-47-->13-1-6-59---vc12, Flag: 64

PG ID: 268436295, xc: 8-1-26-33-->14-1-4-48---vc12, Flag: 64

PG ID: 268436296, xc: 8-1-26-20-->6-1-6-20---vc12, Flag: 0

PG ID: 268436296, xc: 8-1-26-34-->5-1-4-49---vc12, Flag: 0

PG ID: 268436296, xc: 8-1-26-34-->14-1-4-49---vc12, Flag: 64

PG ID: 268436296, xc: 8-1-26-20-->13-1-6-20---vc12, Flag: 64

PG ID: 268436297, xc: 11-1-10-53-->6-1-6-41---vc12, Flag: 0

PG ID: 268436297, xc: 8-1-26-35-->5-1-4-50---vc12 , Flag: 0

PG ID: 268436297, xc: 8-1-26-35-->14-1-4-50---vc12, Flag: 64

PG ID: 268436297, xc: 11-1-10-53-->13-1-6-41---vc12, Flag: 64

PG ID: 268436298, xc: 8-1-26-50-->6-1-6-62---vc12, Flag: 0

PG ID: 268436298, xc: 8-1-26-36-->5-1-4-51---vc12, Flag: 0

PG ID: 268436298, xc: 8-1-26-50-->13-1-6-62---vc12, Flag: 64

PG ID: 268436298, xc: 8-1-26-36-->14-1-4-51---vc12, Flag: 64

PG ID: 268436299, xc: 8-1-26-3-->6-1-6-3---vc12, Flag: 0

PG ID: 268436299, xc: 8-1-26-37-->5-1-4-52---vc12, Flag: 0

PG ID: 268436299, xc: 8-1-26-3-->13-1-6-3---vc12, Flag: 64

PG ID: 268436299, xc: 8-1-26-37-->14-1-4-52---vc12, Flag: 64

PG ID: 268436300, xc: 8-1-26-24-->6-1-6-24---vc12, Flag: 0

PG ID: 268436300, xc: 8-1-1-7-->5-1-1-18---vc12, Flag: 0

PG ID: 268436300, xc: 8-1-1-7-->14-1-1-18---vc12, Flag: 64

PG ID: 268436300, xc: 8-1-26-24-->13-1-6-24---vc12, Flag: 64

3.         The four services marked in red above are used as an example. The protection group IDs of the services are the same. These services are processed as one protection group, and the activation and deactivation operations are all applied to the NE synchronously.

4.         The user is deactivating the service 8-1-26-33-->5-1-4-48. In addition to the protection service 8-1-26-33-->14-1-4-48, another 1+1 protection group service, 8-1-26-47-->6-1-6-59,8-1-26-47-->13-1-6-59, is also deactivated. These two services are just the interrupted services: 8-1-26-47-->6-1-6-59 (with the 1+1 protection cross-connection as 8-1-26-47-->13-1-6-59).

Preventive Measure

Before installing the U2000 V100R006C02SPC306, perform the following operations:

1.         Upload NE data periodically.

2.         Use an E2E method to manage services and analyze and confirm errors before performing the deactivation operation. Do not process discrete services independently in the NE Explorer.

3.         Periodically use the duplicate protection group ID check script (being released) to check the live-network database. After duplicate protection groups are found, upload the protection groups or query services on the NE.

Solution

This problem has been resolved in the U2000 V100R006C02CP3061, U2000 V100R009C00CP3011, and all V200 versions at GA.

The versions that provide solutions verify services that are to be activated or deactivated. If the number of protection groups is abnormal, the U2000 displays an error message indicating that the number of services is incorrect. Customers query NE cross-connections or upload the entire NE data based on the error message. Before customers rectify the error, the U2000 does not issue any commands to deactivate services.

Suggestions and Summary

It is recommended that an E2E method be used to manage services on the live network. For errors that are reported during E2E trail management, analyze them particularly instead of ignore them.