The following fixes were tested on scenario 2 (e.g. External NSSMFs), non-shared slice.
We tested the use case with the following OOM configuration:
- oom Honolulu with the following changes:
- SO
- bpmn-infra at 1.9.0 (in order to fix UUI Slicing Management Section issue)
- SO
or
- oom master from 09-02-2021 (it should be good all version with AAI v23 enabled) with the following changes:
- AAI (v23 schema should be enabled):
- aai-schema-service 1.8.6
- aai-traversal at 1.8.0
- SO
- api handler infra at 1.8.1
- nssmf-adapter at 1.8.0
- bpmn-infra at 1.8.0
- SDNC
- sdnc-image version 2.1.1
- For specifics on Transport Slicing Configuration and Operation Guidance, refer to: Transport Slicing Configuration and Operation Guidance.
- AAI (v23 schema should be enabled):
For configuration, we used the instructions reported in points 2, 3, 4, 5, 6, 7 at Install Minimum Scope for Option 1
For onboarding phase, plese use this guide Template Design for Option2 with the following fix:
- Fill in the "Service Role" field with the value "ONAP_internal" (in the General section, in SDC ) for the resources: Tn_ONAP_internal_BH
- Fill in the "Service Role" field with the value "huawei" (in the General section, in SDC ) for the resources: EmbbCn_External, EmbbAn_NF
- Fill in the "Service Role" field with the value "option2" (in the General section, in SDC ) for the resources: EmbbNst_O2
- Fill in the "Service Type" field with the value "embb" (in the General section, in SDC ) for the resources: Tn_ONAP_internal_BH, EmbbAn_NF, EmbbCn_External, CST_O2
- Fill in the "Vendor Name" field with the value "huawei" (in the General section, in SDC ) for the resources: EmbbCn_External_AR, EmbbAn_NF_AR
Issue | Brief description of resolution | Components affected | Workaround | Jira(s) | Status |
---|---|---|---|---|---|
ServiceProfile (Onboarding phase) | ServiceProfile_O2 in the wiki misses the step "Declare ar-invariant and ar-uuid as Input" and fill the Activity Factor param with a value (i.e. 20) (Point 14 of Template Design for Option2) | DOCS | Declare them as input | ||
AAI Distribution Fails (Onboarding phase) | Distribution fails into AAI for the resources SliceProfileXXX (missing Allotted Resource service model) | AAI | Add Slice_AR (the allotted resource componing each SliceProfile) as | ||
NST Selection | OOF returns always an empty solution array | OOF | - OPTFRA-764Getting issue details... STATUS | FIXED | |
NSI Selection | Camel_to_snake/snake_to_camel schema is wrong | OOF | You will need to change several params into slicing_config.yaml file inside OOF container A working slicing_config.yaml is : You need to restart the OOF docker container once you updated the slicing_config.yaml, you can do it using the following steps,
| ||
NSI Selection | Policies from WIKI page are wrong. The NSI selection response from OOF does not contain all information in order to create the Slice Management Task properly | DOCS/POLICY | new policies must be used
| ||
NSI Selection | subnetCapability.json file is wrong and it should be updated | DOCS/SO | Point 4 of Install Minimum Scope for Option 1 change subnetCapability.json file as following: { "AN": { "latency": 5, "maxNumberofUEs": 10, "maxThroughput": 150, "termDensity": "50" }, "CN": { "latency": 1, "maxThroughput": 5, "maxNumberofConns": 6000 }, "TN_FH": { "latency": 10, "maxThroughput": "100" }, "TN_MH": { "latency": 5, "maxThroughput": "50" }, "TN_BH": { "latency": 10, "maxThroughput": 100 }, "AN_NF": { "latency": 5, "maxNumberofUEs": 100, "maxThroughput": "150", "termDensity": "50" } } | ||
UUI does not display "CommunicationService" and"SlicingResouce Management" items | In the UUI, in "5G Slicing Management" Section, "Communication Service" and "Slicing Resource Management" items are not retrieved from AAI returning 500 Server error with message: "5G slicing order query failed! | MSB | You should add a new service for MSB.
| ||
Netconf device not mounted to SDN-R | While starting the Netconf servers (Honeycomb), the device mount should happen automatically. org.onap.ransim.rest.client.RestClient.sendMountRequestToSdnr(RestClient.java:241)||Exc in post {} | RANSimulator | Username and password to connect with SDN-R need be configured properly. Refer gerrit.onap Code Review - integration/simulators/ran-simulator.git/blob - ransim/docker/docker-compose.yml | Fixed | |
Certificate error in RansimController |
| RANSimulator | Use the jssecacerts cert from sdnc container (var/custom-certs) and place it in ransim package under ransim/docker/config/ransim. It needs to be replaced as it expires over time. or 1.Download the SDNR cacerts from browser. 2.Import the cacerts into RANsim keytool -import -noprompt -trustcacerts -alias SNDC -file <certsfile> -keystore /ransim/docker/config/ransim/jssecacerts -storepass changeit
| Fixed | |
Maven CPS compilation error | Maven compilation fails withe the following error message: mvn --release invalid flag | CPS/CPS-TBDMT | Use the following java version linked to maven : b@ranvm:~/cps/cps-tbdmt$ java -version openjdk version "13.0.1" 2019-10-15 OpenJDK Runtime Environment (build 13.0.1+9) OpenJDK 64-Bit Server VM (build 13.0.1+9, mixed mode, sharing) |
Information about simulators used in the use case:
- External RAN Simulator: External RAN NSSMF
- External Core Simulator: External Core NSSMF Simulator Use Guide
- Transport Simulator: not used
14 Comments
Rajendra Prasad Mishra
Hi,
Can you provide a workaround for the below issues mentioned above.
Policies from WIKI page are wrong. The NSI selection response from OOF does not contain all information in order to create the Slice Management Task properly
Question: Where do we copy these ZIP files ? is this the link with details Optimization Policy Creation Steps
Aniello Paolo Malinconico
Hi Rajendra Prasad Mishra, I have uploaded a working slicing_config.yaml file, containing the camel to snake mapping.
For policies, you can follow this guide Optimization Policy Creation Steps using the policies.zip file uploaded here.
Thanks,
Aniello
Elangovan Thanasekaran
Hi Aniello Paolo Malinconico ,
We are getting below response from OOF during NSI selection.
NSI oofResponse is: {"requestId": "1f232a34-01fe-4e1f-b892-7d8853e51a06", "transactionId": "1f232a34-01fe-4e1f-b892-7d8853e51a06", "requestStatus": "error", "statusMessage": "[Parameter 'exp_data_rate_dl' undefined in path demands > NSTO1[1] > filtering_attributes > service_profile > exp_data_rate_dl > value]"}
Please let us know if any other configuration or policy needs to be updated for resolving this error.
Thanks in advance.
Regards,
Elangovan T
Aniello Paolo Malinconico
Hi, is it shared or non-shared scenario?
Thanks,
Aniello
Elangovan Thanasekaran
Hi Aniello Paolo Malinconico ,
It is for non-shared scenario.
Regards,
Elangovan T
Aniello Paolo Malinconico
I think you have not used the latest policies.zip file uploaded here .
I have checked the policies.zip file and there are no occurrences of "exp_data_rate_dl" param ....
Can you check?
Aniello
Elangovan Thanasekaran
Hi Aniello Paolo Malinconico ,
I can see the entry for exp_data_rate_dl as below in the optimization_nsi_non_shared.json file in policies.zip folder.
exp_data_rate_dl{
"minimizeLatency_{{ service_name }}": {
"metadata": {
"policy-id": "minimizeLatency_{{ service_name }}",
"policy-version": 1
},
.....
}
Regards,
Elangovan T
Aniello Paolo Malinconico
Hi,
I have now downloaded Policies.zip and the optimization_non_shared.json policy is the following:
Elangovan Thanasekaran
Hi,
Can you please attach that policies.zip folder in this comment section.
Thank you.
Regards,
Elangovan T
Aniello Paolo Malinconico
Here https://wiki.onap.org/download/attachments/93011642/policies.zip?version=2&modificationDate=1630660200000&api=v2
Elangovan Thanasekaran
Hi Aniello Paolo Malinconico ,
Thank you so much for sharing the latest policies.zip file. This resolved all the "undefined" errors from OOF.
Currently we are getting empty solutions list from OOF for NSI selection response. Can you please let us know if you have any information on this.
NSI oofResponse is: {"requestId": "9fd98f41-dbec-4414-81c0-3d32f2e99e81", "transactionId": "9fd98f41-dbec-4414-81c0-3d32f2e99e81", "requestStatus": "completed", "statusMessage": "", "solutions": []}
Regards,
Elangovan T
Aniello Paolo Malinconico
If I remember well, for non-shared case, OOF response is an empty solution . So it should be a good response.
Thanks,
Aniello
Elangovan Thanasekaran
Hi Aniello Paolo Malinconico ,
As per the existing logs attached, this is the expected response from OOF is below. existingNSI flag will be false and newNSISolution having sliceProfiles. But we are getting empty solutions response.
Address: http://so-bpmn-infra.onap:8081/mso/WorkflowMessage/NSISelectionResponse/a1184d10-dc23-49c5-ba53-061cad228af7
Encoding: UTF-8
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[*/*], accept-encoding=[gzip,deflate], Authorization=[Basic YXBpaEJwbW46cGFzc3dvcmQxJA==], connection=[Keep-Alive], Content-Length=[1037], content-type=[application/json], cookie=[JSESSIONID=3DA86F2C813894FB2DEF8EA99067496F], host=[so-bpmn-infra.onap:8081], user-agent=[Apache-HttpClient/4.5.13 (Java/11.0.8)]}
Payload: {"requestId": "a1184d10-dc23-49c5-ba53-061cad228af7", "transactionId": "a1184d10-dc23-49c5-ba53-061cad228af7", "requestStatus": "completed", "statusMessage": "", "solutions": [{"existingNSI": false, "newNSISolution": {"sliceProfiles": [{"latency": 20, "sNSSAI": "01-63459CBE", "sST": "embb", "activityFactor": "20", "pLMNIdList": "39-00", "survivalTime": "10", "maxNumberofUEs": 200, "resourceSharingLevel": "shared", "uEMobilityLevel": "stationary", "expDataRateDL": 1440000, "expDataRateUL": 1200000, "maxNumberofPDUSession": 12000, "domainType": "AN"}, {"latency": 10, "sNSSAI": "01-63459CBE", "maxBandwidth": 1000, "pLMNIdList": "39-00", "sST": "embb", "resourceSharingLevel": "shared", "domainType": "TN_BH"}, {"latency": 5, "sNSSAI": "01-63459CBE", "sST": "embb", "activityFactor": "20", "resourceSharingLevel": "shared", "pLMNIdList": "39-00", "survivalTime": "10", "maxNumberofUEs": 200, "uEMobilityLevel": "stationary", "expDataRateDL": 1440000, "expDataRateUL": 1200000, "maxNumberofPDUSession": 12000, "domainType": "CN"}]}}]}
Can you please confirm if this something related to NSI policy.
Regards,
Elangovan T
Aniello Paolo Malinconico
Hi,
you are right... OOF NSI response should not return an empty array .
Can you see this JIRA https://jira.onap.org/projects/OPTFRA/issues/OPTFRA-970 ? In the comment section, I had a similar issue (no solution returned) and it was a mismatch type of an NSTO1 param during SDC onboarding ...
Let me know if solved.
Regards,
Aniello