9.2 Making VNFM as a Standalone VNFM
If there is a permanent loss of a VNFM, then the model can be made
into a standalone system using the CHANGE VNFM STATE REST request.
Sample Request: Request for Standalone VNFM
URL: https://<<VNFM HOST IP>>:8443/vnflcm/<<vnfm_version>>/vnfmState
Accept: application/json
Content-Type: application/json
Authorization : <Token generated after login>
{
"state": "SECONDARY",
"primaryIp": "2606:b400:605:b813::4",
"secondaryIp": "127.0.0.1"
}
Sample Request: Response for Change VNFM Request Standalone VNFM
201 Created
{
"localStateInfo": {
"state": "PRIMARY",
"primaryIp": "2606:b400:605:b813::4",
"secondaryIp": "127.0.0.1"
},
"remoteStateInfo": {
"message": "Remote IP does not exist or is LocalHost. Remote Ip: 127.0.0.1"
},
"timeStamp": "2020/07/03 14:43:31 UTC"
}
Steps to Change the Default Retry Configurations
When Change VNFM State Info Request gives a 202 response, a retry mechanism occurs to change the VNFM state. By default, the retry occurs for 10 times with a 2 min wait interval between each retry. These configurations can be changed with the following steps.
In 'dsrvnfm' user mode:
- Open
VnfmProperties
file/opt/vnfm/config/VnfmProperties
.yaml to edit the properties. - Retry Count can be modified from the following property
changeRemoteStateRetryCount
.- Min Value: 2
- Max Value: 10
- Default Value: 10
- Retry Interval can be modified from the following property
changeRemoteStateRetryInterval
. The interval is in the form of milliseconds.- Min Value: 60000
- Max Value: 300000
- Default Value: 120000