Equinix-Configured
We monitor Equinix-configured devices at the Network Edge Device Manager (NEDM) layer of the ETSI NFV stack by pinging the management interface. The management interface/VRF has restricted access and does not allow you to change the configuration. When the NEDM cannot reach the management interface, the NOC begins troubleshooting. The NOC initiates a manual recovery process if they need to recover the device. Once recovery is complete, the process reestablishes reachability with the NEDM and updates the NVFO, which updates the Fabric portal.
The recovery process deploys a new device with the Day 0 configuration for Equinix-configured devices. Next, it automatically recovers any Day 1 and Day 2..N configurations performed in the portal (L2 and L3) and reestablish connections, provided the CSP made no changes on their side.
Self-Configured (SD-WAN and non-SD-WAN)
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 L2 connections.
Any Day 1 and Day 2 configuration will also be fully restored provided that the device configuration was saved. The only exceptions are SD-WAN devices from Prisma, VMWare, and Aruba for which you will need to restore the full configuration using the vendor’s SD-WAN orchestration tool.
| Device Type | Auto/Manual Recovery Support |
|---|---|
| Equinix-configured devices created since May 2021 release | Auto recovery (recovers device default configuration + customer saved configurations) |
| Self-configured SD-WAN devices created before August 2021 release | Manual recovery |
| Self-configured SD-WAN devices created since August 2021 release except Prisma, VMWare, and Aruba | Auto recovery (recovers device default configuration + customer saved configurations) |
| All other self-configured devices | Auto recovery (recovers device default configuration + customer saved configurations) |
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.
Console
If required, console access is available for all device types to correct issues such as reachability problems caused by misconfiguration.
Restoration Time
Approximate restore time for VNF can vary depending on size of the VNF and vendor.
License Registration
It is strongly recommended to check vendor specification and licensing details after recovery. You might need to reapply the license after recovery.
Notification
You will receive notification after restoration of the device is completed.