Hello, everyone!
This post will tell you one issue for The SCC Is Reset Due to Service Deactivation on an OptiX OSN 3500 NE.
Problem description:
On an OptiX OSN 3500 NE, when the engineers deactivate services, the SCC is reset.
Handling procedure:
1. Check the returned NE data by using the database detection tool and find the following two errors:
ERROR: CheckMultiPtrPair[0x9310000] Attr[0x331F005] Pair[0x4D312101] Src[0x197][0x2]
Dst[0x10][0x4A7] NOT Match
ERROR: CheckSinglePtrPair[0x9310000] Attr[0x331F004] Pair[0x4D312102] Src[0x1E2][0x2]
Dst[0x10][0x4A7] NOT Match
2. These two errors indicate the following information:
? Pointers FromCCOP and ToCCOP through which VC12TP points to CrossConn exist.
? Pointers ToTP and FromTP through which CrossConn points back to VC12TP do not exist.
Query the SBOL of cross-connection No. 1192, [0x10][0x4A7], and find that the cross-connection points to four TPs. Normally, a cross-connection points up to two TPs.
3. Analyze further the problem:
VC12TPs [0x197][0x2] and [0x1E2][0x2] originally function as a pair of source and sink TPs. Now, however, they are two source TPs. This indicates that cross-connection No. 1192 is allocated twice to different services.
An XCID can be allocated to only a noactive cross-connection object. The engineers suspect that the problem results from the status transient of cross-connection No. 1192. That is, the cross-connection changes from active or adding to noactive transiently during the warm reset of the SCC and is then allocated to another service.
4. Try reproducing the problem. Modify a service to noactive manually and then configure the service again. The service is configured successfully. Then, delete the service. During the deletion, the NE is reset and reports the same errors.
5. Summarize the root cause of the problem. The memory transient of the SCC during the warm reset causes the cross-connection to change from active or adding to nonactive. After finding that the service does not exist, the engineers configure the service again. When the engineers delete the service, the NE finds two copies of the service in the database. Therefore, the pointer cannot point to the proper address and becomes a void pointer. As a result, a warm reset of the SCC is caused.
Root cause:
The memory transient of the SCC during the warm reset causes the cross-connection to change from active or adding to nonactive.
Solution:
To avoid the problem in emergency cases, reset the SCC and download the NE data again.
To solve the problem, replace the SCC that has the memory problem with a normal one.
That's all, I welcome everyone to leave a message and exchange in the comment area!
Thank you！
