11 Heal VNF

Using the Heal VNF operation, you can request for healing a VNFC instance. Auto-healing is not supported by VNFM. Only Orchestrator-triggered healing is supported.

Heal VNF accepts a single VNFC name per healing request. Only one server is healed at a certain point of time per each (DSR/SDS) NOAM topology to avoid complete state down. When there are concurrent healing requests for multiple VNFCs from the same system topology, the requests are arranged in a queue and are processed in the same sequence as they are positioned in the queue.

Heal VNF Resource only supports the following VNFs with DSR/SDS version 8.5.0.1.0 or later:

• DSR Network OAM
• DSR DR Network OAM
• DSR Signaling
• SDS Network OAM
• SDS DR Network OAM
• SDS Signaling

Heal VNF supports the following DSR/SDS alarms:

Table 11-1 DSR/SDS Alarms

Alarm ID	Alarm Name	Healing Action
32306	Server RAM Shortage Error	Server Reboot
32307	Server Swap Space Shortage Error	Server Reboot
31101	DB Replication To Slave Failure	Server Reboot
31283	Lost Communication with server	Server Reboot
31114	DB Replication over SOAP has failed	Server Reboot
31233	HA Path Down	Server Reboot
31107	DB Merge From Child Failure	Server Reboot

Note:

• Server Reboot and Application Restart are the only supported healing tasks.
• Heal Operation does not support recreation of any VNF/VNFC.
• When a VNFM state is changed as a part of Geo Redundancy, then all the healing operations waiting in the queue are discarded.

Sample Request for Heal VNF Request

URL: https://<<VNFM HOST IP>>:8443/vnfm/v1/vnf_instances/< VNF ID received from create request>/heal

Accept: application/json
{
  "cause": "merging alarms",
  "additionalParams": {
      "vnfcName": "heal1-SNO00",
      "noamVip": "10.75.189.34",
      "username": "root",
      "password": "xxxx"
  }
}

Sample Response for Heal VNF Request

Response Code : 202
{
     location: https://localhost:8443/vnflcm/v1/vnf_lcm_op_occs/lcmOp-fb21f9d3-43ad-46cd-a03f-7220bb36a5c6  
     date: Tue, 29 Jan 2019 10:39:24 GMT  
     content-length: 0  content-type:
     application/xml 
}