Details
-
Type:
CR
-
Status:
Pending Design Session
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Component/s: FN
-
Labels:None Labels
-
Customer:OMAN-Tel
-
Product:NEP
Description
As we discussed, we are encountering an issue with the Gaming ADD-ON scenario for orders where no trail is available. These orders are failing with the following error:
CVlan Reservation failed - Couldn't find active node while calling reserveCvlanIp API.
Currently, the NEP system attempts to extract active node details from the trail when calling this API. Since these specific orders lack trail data, they are being interrupted.
Recommendation: I suggest implementing a fallback logic. If the trail is unavailable, NEP should automatically pull the active node details from the ONU view. This will ensure the API call succeeds and prevents the CVlan reservation error.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header />
<SOAP-ENV:Body>
<ns3:reserveCvlanIp xmlns:ns3="http://server.api.nep.mobinets.com/">
<subscriberNumber>24546987</subscriberNumber>
</ns3:reserveCvlanIp>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>"
nep_fn_ui.2026-01-14.1.log:2026-01-14 10:54:33.415 [https-jsse-nio-8450-exec-6] DEBUG
org.apache.http.wire - http-outgoing-78
<
< "
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:reserveCvlanIpResponse xmlns:ns2="http://server.api.nep.mobinets.com/">
<return>
<cvlanIp></cvlanIp>
<responseCode>5</responseCode>
<responseMessage>CVlan Reservation failed - Couldn't find active node</responseMessage>
<svlanIp></svlanIp>
</return>
</ns2:reserveCvlanIpResponse>
</soap:Body>
</soap:Envelope>
Thank U!!!

As discussed, the issue is clearly related to Gaming ADD-ON orders where no trail information exists. In such cases, NEP fails to retrieve the active node from the trail, which causes the `reserveCvlanIp` API call to fail with the error "Couldn't find active node".
To unblock the flow, we agree with the proposed approach:
Kindly proceed with uploading and updating the related process to cover both *activation* and *termination* scenarios for subscribers without trail data.
releasing patch 3.7.0.1416