Device Recovery
We monitor self-configured devices at the Virtualized Infrastructure Manager (VIM) layer of the ETSI NFV stack using OpenStack APIs. Monitoring at this layer is required because there are no AAA restrictions to prohibit you from changing the management interface, so the management interface must have no impact on monitoring or recovery. In this case, if the API returns any status other than active, an automatic recovery process starts.
The automatic recovery process deploys a new device with the Day 0 configuration. Once the process recovers the device, it also restores any Layer 2 connections.
Any Day 1 and Day 2 configuration will also be fully restored provided that the device configuration was saved.
| Device Type | Auto/Manual Recovery Support |
|---|---|
| Self-configured SD-WAN devices created before August 2021 release | Manual recovery |
| Self-configured SD-WAN devices created since August 2021 release except Palo Alto, Arista, and Aruba. See SD-WAN Devices | Auto recovery (recovers device default configuration + customer saved configurations) |
| All other self-configured devices | Auto recovery (recovers device default configuration + customer saved configurations) |
If required, console access is available for all device types to correct issues such as reachability problems caused by misconfiguration.
Approximate restore time for VNF can vary depending on size of the VNF and vendor. You will receive notification after restoration of the device is completed.
License Registration
It is strongly recommended to check vendor specification and licensing details after recovery. You might need to reapply the license after recovery.
SD-WAN Devices
SD-WAN devices from Palo Alto, Arista, and Aruba do not support automatic device recovery. To recover these devices, use the Manual Device Replacement process and restore the full configuration using the vendor’s SD-WAN orchestration tool.
CSP Configuration
You control CSP configuration and recovery. However, if you recover a failed device on the NFV platform, the CSP connection automatically reestablishes peering, provided the CSP made no changes on their side of the connection.