8.1 Change VNFM State

The VNFM state can be changed using the CHANGE VNFM STATE' POST REST request.

Sample Request: Change VNFM Request

URL: https://<<VNFM HOST IP>>:8443/vnflcm/v1/vnfmState

Accept: application/json

Content-Type: application/json

X-Token : <Token generated after login>

{

  "state": "SECONDARY",

  "primaryIp": "2606:b400:605:b813::4",

  "secondaryIp": "2606:b400:605:b813::7"

}

Sample Request: Responses for Change VNFM State

201 Created
  "localStateInfo": {

    "state": "SECONDARY",

    "primaryIp": "2606:b400:605:b813::4",

    "secondaryIp": "2606:b400:605:b813::7"

  },

  "remoteStateInfo": {

    "state": "PRIMARY",

    "primaryIp": "2606:b400:605:b813::7",

    "secondaryIp": "2606:b400:605:b813::4"

  },

  "timeStamp": "2020/07/03 10:35:29 UTC"

}


202 Accepted

{

  "localStateInfo": {

    "state": "SECONDARY",

    "primaryIp": "2606:b400:605:b813::4",

    "secondaryIp": "2606:b400:605:b813::7"

  },

  "remoteStateInfo": null,

  "timeStamp": "2020/07/03 10:35:29 UTC"

}

Note:

• The 201 response indicates that the request is complete.
• The 202 response indicates that the request is accepted for processing. The VNF retries to update the state for the configured amount of time. Use the LCM operation ID to determine the status of the request.
  • If the request is complete, then the LCM operation status changes to COMPLETED.
  • If the request fails, then the VNFM state changes to TRASIENT and the LCM operation status changes to FAILED. In this case, the user must re-trigger the CHANGE VNFM request after resolving the reason for failure.