AutoVNF Health Check and Automatic RecoveryThrough AutoIT
• Feature Summary and Revision History, on page 1• Feature Changes, on page 1
Feature Summary and Revision HistorySummary Data
AllApplicable Product(s) or FunctionalArea
UGPApplicable Platform(s)
Enabled - Always-onFeature Default
VNFC Health Check and Automatic Recovery through AutoVNFRelated Features in this Release
• Ultra Gateway Platform System Administration Guide
• Ultra M Solutions Guide
• Ultra Services Platform Deployment Automation Guide
Related Documentation
Revision History
ReleaseRevision Details
N6.0First introduced.
Feature ChangesAutoIT now supports the ability to monitor and auto-recover AutoVNF instances.
AutoVNF Health Check and Automatic Recovery Through AutoIT1
This functionality is enabled through configuration of the AutoVNF VNFC(s) at the time of deployment.Once enabled, AutoIT automatically monitors for faults/failures of the AutoVNF VNFC(s) for which thefunctionality is enabled. If a fault/failure is detected, AutoIT automatically attempts to auto-heal/recover(redeploy) the VNFC(s).
The Provisioning Network (floating) IP address is required to leverage the health monitoring functionality.Important
The following parameters must be configured at the VNFC-level:
Table 1: Health Check Descriptor Parameters
DescriptionTypeRequiredParameter
Enable/Disable health monitoring.boolOenabled
Health Check Frequency in seconds. UAS uses thisas health probe time, meaning every polling intervalUAS will invoke health check. Default value is 10seconds.
uint16Oprobe-frequency
Maximum number of health probe misses beforeVNFC instance is declared dead.
uint16Oprobe-max-miss
Recovery type. It can be one of the following:
• restart: Recovery only by restarting, move theVNFC instance to error after max retries
• external: Recovery performed by externalentity. No auto-recovery
• restart-then-redeploy: Restart the VM onfailure. After maximum retries, redeploy thefailed VNFC instances.
Default value is restart-then-redeploy.
choice stringOrecovery-type
Number of retries to recover the VNFC Instance.Default value is set to restart-then-redeploy.
uint16Oretry-count
Initial Bootup time for the VNFC. Default value is300 seconds.
uint16Oboot-time
Script to checkVNFC health, by default UAS ICMPscript will be used.
stringOscript
The above parameters are configured at the VNFC-level within the VNF descriptor information that is partof the deployment network service descriptor (NSD) as shown in the following example configuration:nsd <nsd_name>…vnfd <autovnf_vnfd_name>…vnfc <autovnf_vnfc_name>
AutoVNF Health Check and Automatic Recovery Through AutoIT2
AutoVNF Health Check and Automatic Recovery Through AutoITFeature Changes
health-check enabledhealth-check probe-frequency 10health-check probe-max-miss 6health-check retry-count 6health-check recovery-type restart-then-redeployhealth-check boot-time 300
…
Refer to the Cisco Ultra Services Platform NETCONF API Guide for more information on the use of theseand other parameters related to VNF configuration and deployment.
In the event that automatic recovery is not possible, an API is available to manually recover the VNFC(s).
VNFC status can be viewed by executing the show vnfr command from AutoIT. Additional details can befound in the transaction logs for the deployment.
To manually recover a failed AutoVNF VNFC, execute the following command:
recover nsd-id <nsd_name> vnfd <vnfd_name>
AutoVNF Health Check and Automatic Recovery Through AutoIT3
AutoVNF Health Check and Automatic Recovery Through AutoITFeature Changes
AutoVNF Health Check and Automatic Recovery Through AutoIT4
AutoVNF Health Check and Automatic Recovery Through AutoITFeature Changes