1. UUI Configuration
...
Copy subnetCapability.json to SO-API Handler pod to configure subnet capabilities at run time.
{
"AN_NF": {
"latency": 5,
"maxNumberofUEs": 200,
"maxThroughput": 90,
"termDensity": 40
},
"AN": {
"latency": 20,
"maxNumberofUEs": 100,
"maxThroughput": 150,
"termDensity": 50
},
"CN": {
"latency": 10,
"maxThroughput": 50,
"maxNumberofConns": 100
},
"TN_FH": {
"latency": 10,
"maxThroughput": 90
},
"TN_MH": {
"latency": 5,
"maxThroughput": 90
},
"TN_BH": {
"latency": 10,
"maxThroughput": 100
}
}
...
unzip policies.zip |
...
Install config DB application in a separate VM. MariaDB container should be up and running to access the config DB APIs.
Refer https://wiki.onap.org/display/DW/Config+DB+setup for configDB setup. Latest source is available at Image versions, preparation steps and useful info-Config DB Preload Info Section.
...
- Login to dcae-mongodb container and execute following commands to check if PM data was saved in DB:
- mongo
- use datalake
- db.unauthenticatedperformancemeasurements.find({})
- to load sample data:
| 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
Portal UI not working . Alternative for accessing to SDC UI .
If you cannot access to 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
This hack can be possible since SDC UI authentication mode is cookie based. So the attacker can override the cookie to force its request.