...
- The service name given for creating the policy must match with the service name in the request
- The scope fields in the policies should match with the value in the resourceSharingLevel(non-shared/shared). Do modify the policy accordingly.
- Check the case of the attributes with the OOF request with the attribute map (camel to snake and snake to camel) in config/slicing_config.yaml, if any mismatch found modify the attribute map accordingly.
You need to restart the OOF docker container once you updated the slicing_config.yaml, you can do it using the following steps,
- Login to the worker VM where the OOF container is running. You can find the worker node by running (kubectl get pods -n onap -o wide | grep dev-oof)
- Find the container using docker ps | grep optf-osdf
- Restart the container using docker restart <container id>
CPS Configuration:
Refer CPS Configuration to setup standalone CPS and configuration of OOF and CPS.
6. Core NF Simulator Setup
...
Refer ACTN Simulator User Guide to setup ACTN-simulator or follow the below steps to launch and initialize domain controllers,
Refer Transport Slicing Configuration and Operation Guidance for NextHop details of AN &CN
Step 1. Fetch the simulator docker image
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
db.unauthenticatedperformancemeasurements.insert({
"event":{
"commonEventHeader":{
"domain":"perf3gpp",
"eventId":"95e79282-2876-4000-8192-b514ad7f399a",
"sequence":0,
"eventName":"perf3gpp_RnNode-Slicing_pmMeasResult",
"sourceName":"220",
"reportingEntityName":"",
"priority":"Normal",
"startEpochMicrosec":1651216762867,
"lastEpochMicrosec":1651216762868,
"version":"4.0",
"vesEventListenerVersion":"7.1",
"timeZoneOffset":"UTC+05:30"
},
"perf3gppFields":{
"perf3gppFieldsVersion":"1.0",
"measDataCollection":{
"granularityPeriod":900,
"measuredEntityUserName":"",
"measuredEntityDn":"220",
"measuredEntitySoftwareVersion":"r0.1",
"measInfoList":[
{
"measInfoId":{
"sMeasInfoId":"measInfoIsVal"
},
"measTypes":{
"sMeasTypesList":[
"SM.PrbUsedDl.01-3C5C90",
"SM.PrbUsedUl.01-3C5C90"
]
},
"measValuesList":[
{
"measObjInstId":"15155",
"suspectFlag":"false",
"measResults":[
{
"p":1,
"sValue":"5"
},
{
"p":2,
"sValue":"7"
}
]
},
{
"measObjInstId":"15174",
"suspectFlag":"false",
"measResults":[
{
"p":1,
"sValue":"6"
},
{
"p":2,
"sValue":"7"
}
]
},
{
"measObjInstId":"15175",
"suspectFlag":"false",
"measResults":[
{
"p":1,
"sValue":"15"
},
{
"p":2,
"sValue":"4"
}
]
},
{
"measObjInstId":"15176",
"suspectFlag":"false",
"measResults":[
{
"p":1,
"sValue":"5"
},
{
"p":2,
"sValue":"14"
}
]
},
{
"measObjInstId":"15825",
"suspectFlag":"false",
"measResults":[
{
"p":1,
"sValue":"0"
},
{
"p":2,
"sValue":"14"
}
]
}
]
}
]
}
}
}
}) |
E2E network slicing issues
If Portal UI doesn’t go up and so you cannot access SDC UI via Portal UI, you need to do the following steps in order to be authenticated for accessing SDC UI.
- Go to https://<<sdc_ip>>:<<sdc_port>/ with Google Chrome Dev
- Open Inspect and go to Application section
- On left column, open Cookies
- Add the following cookie key/value
USER_ID cs0008 for designer role
USER_ID demo for admin role
...