Overall Infrastructure Upgrade Flow
Network Edge Infrastructure upgrade for all 27 metro locations will be upgraded during Q4 2022 and Q1 2023. This table outlines the overall flow for the upgrade of each location.
| Stage | Service Interruption | Responsibility | Description | |
|---|---|---|---|---|
| 1 | Customer notification prior to upgrade | - | Equinix | Equinix representatives will be reaching out to users to discuss upgrade details, required actions based on VNF type and possible mitigation plan. Email notifications containing upgrade details and instructions in case of failures are sent to users two weeks prior to the upgrade and a reminder notification will be sent a day before the upgrade. Users will receive two types of notification. One is for pre-upgrade notification. Another one is for RMA process described in section below. |
| 2 | Backup Configuration | - | User | It’s strongly recommended that device configuration be backed up before the upgrade to a remote location from where it can be accessed after upgrade, through a VNF interface if required. Equinix will be backing up configurations for all Equinix-Configured devices. |
| 3 | Upgrade | Yes | Equinix | Equinix performs the infrastructure upgrade. The complete upgrade is expected to take approximately 45 hours. See Service Interruption Details. Users won’t be able to create any new devices during maintenance window. Any new device request will be queued and created after the maintenance window. Status.equinix.com provides most up-to-date information and status of the infra upgrade. |
| 4 | Upgrade completion notification | - | Equinix | Email notification is sent after the upgrade containing a checklist and including instructions if an unexpected incident occurs requiring recovery flow. |
| 5 | If needed: VNF notification | Possible | User + Equinix | Some devices might require specific action to be taken post upgrade. See Troubleshooting VNF Failure. |
| 6 | If needed: open support case | Possible | User | Open a support case if unexpected incident happens after the upgrade. |
Upgrade Plan
See Network Edge Infrastructure Update Schedule for the tentative sequence in which we intend to upgrade the NE infrastructure in the 27 Network Edge locations. The Metros are listed in order of target dates. The update sequence is subject to change.
Service Interruption Details
This is a major upgrade of the infrastructure, requiring management stack and firmware upgrades to all servers. All efforts were made to minimize service interruptions for redundant and clustered deployments. However, due to the breadth of the upgrade, redundant and cluster devices in the same metro location might experience service interruptions as listed in the table below. Some customers may experience traffic degradation of approximately 3 hours.
Maintenance Window
Currently a total of 48 hours maintenance window is expected for this infrastructure upgrade. During the maintenance window, the user will not be able to create, modify, or delete any VNFs and associated Network Edge Services. If any new VNFs are ordered, the provisioning of the virtual device is queued, and the provisioning process will start after the upgrade is completed.
For Ashburn (DC), the maintenance window time is expected to be longer than other metros due to the size of the infrastructure, and it is expected to be approximately 60 hours before the Maintenance window is closed.
| Deployment Type | Impact |
|---|---|
| Single device | Single device deployments will experience a total service interruption of up to 73 minutes. Interruptions will be comprised of multiple smaller interruptions over the total upgrade period. |
| Redundant device –Single Metro | Single metro, redundant devices may experience a total service interruption of up to 20 minutes. Interruptions will be comprised of multiple interruptions over the total upgrade period due to simultaneous software process restarts. |
| Redundant device – Multiple Metros | If a primary device is installed in the upgrading metro, and a secondary device is designed to re-route traffic while the primary device is down, there will be no downtime expected during this upgrade, other than the normal router re-convergence time. |
| Cluster device | Clustered devices may experience total service interruption of up to 20 minutes. Interruptions will be comprised of multiple smaller interruptions over the total upgrade period due to simultaneous software process restarts. |
Pre-Upgrade Software Version Requirements for Prisma SD-WAN and Aruba SD-WAN
The new infrastructure management stack is incompatible with software below the versions listed in the table for Palo Alto Networks Prisma and Aruba SD-WAN. Ensure that the software is at (or above) the versions listed in the table. If the software is not updated before this infrastructure upgrade, VNFs are expected to be non-operational post upgrade.
| Vendor | VNF Type | Configuration Type | Required Software Version |
|---|---|---|---|
| Palo Alto Networks | Prisma SD-WAN | Self-configured | 5.5.3.b2 or above |
| Aruba SD-WAN | EdgeConnect | Self-configured | 8.3.3.6 or above |
Troubleshooting VNF Failure
We expect all VNFs to be operational upon the completion of the upgrade. However, we want you to be prepared to take action in the unforeseen event that your VNFs are not operational. Refer to the table below to identify your device type and follow instructions to recover your VNFs if required.
| Vendor | VNF Type | Configuration Type | Responsible Party | Action after Unexpected Failure |
|---|---|---|---|---|
| Aruba SD-WAN | EdgeConnect (Ensure VNFs are upgraded as described in Pre-Upgrade Software Version Requirements.) | Self-configured | Equinix | BYOL: Equinix will auto-recover the device without configuration. |
| Customer (Action Required) | BYOL: After recovery is complete, user will be notified to re-apply the VNF configuration from the controller. | |||
| Check Point | CloudGuard | Self-configured | Equinix | BYOL: Equinix will auto-recover the device with configuration |
| Customer (Advisory) | BYOL: After recovery is complete, user will be notified to check the license and configuration. | |||
| Cisco | CSR1000v | Equinix-configured | Equinix | Subscription: Equinix will auto-recover the device with license and configuration. BYOL: Equinix will auto-recover the devices with configuration but without license. |
| Customer (BYOL: Action Required) | Subscription: After recovery flow is complete, user will be notified to check VNF status and configuration.
BYOL: After recovery flow is complete, user must re-register BYOL license and check configuration. |
|||
| CSR1000v | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with configuration but without license. | |
| Customer (Action Required) | BYOL: After recovery flow is complete, user must re-register BYOL license and check configuration. | |||
| C8000v | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with configuration but without license. | |
| Customer (Action Required) | BYOL: After recovery flow is complete, user must re-register BYOL license and check configuration. | |||
| FTDv | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with configuration but without license. | |
| Customer (Advisory) | BYOL: After recovery flow is complete, user must re-register BYOL license and check configuration. | |||
| ASAv | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with configuration but without license. | |
| Customer (Advisory) | BYOL: After recovery flow is complete, user must re-register BYOL license and check configuration. | |||
| CSR1000v SD-WAN created after 8/6/2021 | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with configuration. | |
| Customer (Advisory) | BYOL: After recovery flow is complete, user must verify the configuration. | |||
| CSR1000v SD-WAN created before 8/6/2021 | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with configuration. | |
| Customer (Action Required) | BYOL: Customer to initiate vendor-specific replacement process. See Cisco CSR1000v SD-WAN Device Recovery Process. | |||
| F5 NGINX | NGINX Plus | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with license and configuration. |
| Customer (Advisory) | BYOL: After recovery flow is complete, user must verify the license and configuration. | |||
| Fortinet | FortiGate VM | Equinix-configured | Equinix | Subscription: Equinix will auto-recover the device with license and configuration.
BYOL: Equinix will auto-recover the devices with license and configuration. |
| Customer (Advisory) | Subscription: After recovery flow is complete, user will be notified to check VNF status and configuration.
BYOL: After recovery flow is complete, user will be notified to check license and configuration. |
|||
| FortiGate VM | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with license and configuration. | |
| Customer (Advisory) | BYOL: After recovery flow is complete, user must verify the license and configuration. | |||
| FortiGate SD-WAN | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with license and configuration. | |
| Customer (Advisory) | BYOL: After recovery flow is complete, user must verify the license and configuration. | |||
| Juniper | vSRX | Equinix-configured | Equinix | Subscription: Equinix will auto-recover the device with license and configuration. BYOL: Equinix will auto-recover the devices with license and configuration. |
| Customer (Advisory) | Subscription: After recovery flow is complete, user will be notified to check VNF status and configuration.
BYOL: After recovery flow is complete, user must verify the license and configuration. |
|||
| vSRX | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with license and configuration. | |
| Customer (Advisory) | BYOL: After recovery flow is complete, user must verify the license and configuration. | |||
| vSRX SD-WAN | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with license and configuration. | |
| Customer (Advisory) | BYOL: After recovery flow is complete, user must verify the license and configuration. | |||
| Palo Alto Networks | VM | Equinix-configured | Equinix | Subscription: Equinix will auto-recover the device with license and configuration. BYOL: Equinix will auto-recover the devices with configuration and license (with valid authcode) |
| Customer (BYOL: Action required) | Subscription: After recovery flow is complete, user will be notified to check VNF status and configuration.
BYOL: After recovery flow is complete, and if authcode does not have enough credits, then the customer will receive Pending-User-Action notification to reapply license. |
|||
| VM | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with configuration but without license. | |
| Customer (Action Required) | BYOL: After recovery flow is complete, user must re-register BYOL license and check configuration. | |||
| Prisma SD-WAN (Ensure VNFs are upgraded as described in Pre-Upgrade Software Version Requirements.) | Self-configured | Customer (Action Required) | See Post-Upgrade Software Version Requirements for Prisma SD-WAN and VMware SD-WAN Devices. | |
| Versa | VOS (FlexVNF) | Self-configured | Equinix | BYOL: Equinix will auto-recover the devices with license and configuration. |
| Customer (Advisory) | BYOL: After recovery flow is complete, user must verify the license and configuration. | |||
| VMWare | SD-WAN | Self-configured | Customer (Action Required) | See Post-Upgrade Software Version Requirements for Prisma SD-WAN and VMware SD-WAN Devices. |
Post-Upgrade Software Version Requirements for Prisma SD-WAN and VMware SD-WAN Devices
This infrastructure upgrade will result in a new internal identifier required for all devices. If this identifier is being used by an SD-WAN device to generate the serial number used in licensing/registration, you will be required to go through a vendor specific replacement process (also-know-as the RMA process).
We retain all the old serial numbers after the upgrade. However, when the VNF eventually reloads (due to reasons unrelated to this upgrade), the VNF will get a new serial number which will cause communication between the device and the SD-WAN controller to break. You will be advised to proactively address the issue by going through a vendor-specific replacement process for the devices listed in this section to generate a registration key for the new serial number. Once the key is retrieved, you can reprovision the VNF from the Network Edge Portal and all configurations will be restored from the SD-WAN controller.
For documentation about the RMA process, see:
