NfpData
This type contains information used to create or modify NFP instance parameters for the update of an existing VNFFG instance. It shall comply with the provisions defined in Table 6.5.3.38-1.
{
"nfpInfoId": "string",
"nfpName": "string",
"description": "string",
"cpGroup": [
{
"cpPairInfo": [
{
"vnfExtCpIds": [
"string"
],
"pnfExtCpIds": [
"string"
],
"sapIds": [
"string"
]
}
],
"forwardingBehaviour": "string",
"forwardingBehaviourInputParameters": {
"algortihmName": "string",
"algorithmWeights": [
0
]
}
}
],
"nfpRule": {
"etherDestinationAddress": "string",
"etherSourceAddress": "string",
"etherType": "string",
"vlanTag": [
"string"
],
"protocol": "string",
"dscp": "string",
"sourcePortRange": {
"lowerPort": 0,
"upperPort": 0
},
"destinationPortRange": {
"lowerPort": 0,
"upperPort": 0
},
"sourceIpAddressPrefix": "string",
"destinationIpAddressPrefix": "string",
"extendedCriteria": [
{
"startingPoint": 0,
"length": 0,
"value": "string"
}
]
}
}Human readable name for the NFP. It shall be present for the new NFP, and it may be present otherwise. It shall be present for the new NFP, and it may be present otherwise.
Human readable description for the NFP. It shall be present for the new NFP, and it may be present otherwise. It shall be present for the new NFP, and it may be present otherwise.
Group(s) of CPs and/or SAPs which the NFP passes by. Cardinality can be 0 if only updated or newly created NFP classification and selection rule which applied to an existing NFP is provided. At least a CP or an nfpRule shall be present. When multiple identifiers are included, the position of the identifier in the cpGroup value specifies the position of the group in the path.