Ticket Details

Subject: Vancouver Router Upgrade
Category: Scheduled Maintenance
TicketID: 20240802-006
Start Time: 2024-08-13 08:00:00 EDT (2024-08-13 12:00:00 UTC)
End Time: 2024-08-13 10:30:00 EDT (2024-08-13 14:30:00 UTC)


TICKET HISTORY:

=== Updated by: Joshua Muysson on 2024-08-14 11:45:44 EDT (2024-08-14 15:45:44 UTC) ===

Closing this ticket as there's been no reported ongoing impacts.

=== Updated by: Joshua Muysson on 2024-08-13 10:23:46 EDT (2024-08-13 14:23:46 UTC) ===

All services have been restored. If there's any ongoing impacts, please let us know.

Thank you for your patience

=== Updated by: Joshua Muysson on 2024-08-13 09:18:43 EDT (2024-08-13 13:18:43 UTC) ===

We have received confirmation from the local support that it will be around 30-45 minutes for them to arrive on site.

We have extended the maintenance window to account for this travel time.

Thank you for your patience.

=== Updated by: Joshua Muysson on 2024-08-13 09:11:19 EDT (2024-08-13 13:11:19 UTC) ===

Hello All,

The upgrade has been completed and a majority of services have been restored.

However, select services are still facing ongoing impacts. We have a plan in place to repair these services and are waiting for local hands to arrive.

Impacted services:

- L2VPN-RDC-10100-13 (UBC Site)

- L2VPN-NRC-10030-57 (UBC Site)

- L2VPN-SSC:I_GCSN-10029-02 (vlan 1000)

- L2VPN-SSC:O_GCSN-10029-01 (vlan 10)

=== Updated by: Joshua Muysson on 2024-08-13 08:02:35 EDT (2024-08-13 12:02:35 UTC) ===

We are beginning the upgrade. Impacts will occur momentarily.

=== Created by: Joshua Muysson on 2024-08-01 20:27:04 EDT (2024-08-02 00:27:04 UTC) ===

We will be performing a network router firmware upgrade in Vancouver at the time listed above.

During this maintenance window we will be performing the upgrade procedure that takes at least 30 minutes to complete and requires a full restart of the equipment.
When the restart is performed, all services will go down for an expected downtime of 5-15 minutes.

During the maintenance, the following services will be impacted.

BGP peerings
- BCNet IPv4/5 R&E/CDS
- GCSN IPv4 R&E/CDS
- HE IPv6 R&E
- AEBC IPv6 R&E
- CIRA IPv6 R&E
- PEER1 IPv6 R&E
- TekSavvy IPv6 R&E
- PacificServers IPv6 R&E
- GGC IPv4/6 CDS
- Microsoft IPv4/6 CDS

Layer 2 Circuits:
- L2VPN-NRC-10030-50 (vlan 45)
- L2VPN-NRC-10030-51 (vlan 267)
- L2VPN-NRC-10030-52 (vlan 1162)
- L2VPN-NRC-10030-53 (vlan 1462)
- L2VPN-NRC-10030-54 (vlan 2267)
- L2VPN-NRC-10030-55 (vlan 268)
- L2VPN-NRC-10030-56 (vlan 310)
- L2VPN-NRC-10030-57 (vlan 1161)
- L2VPN-NRC-10030-58 (vlan 1461)
- L2VPN-NRC-10030-59 (vlan 2268)
- L2VPN-NRC-10030-60 (vlan 2310)
- L2VPN-RDC-10100-07 (vlan 107)
- L2VPN-RDC-10100-08 (vlan 108)
- L2VPN-RDC-10100-11 (vlan 12)
- L2VPN-RDC-10100-13 (vlan 400)
- L2VPN-SFU-10228-03 (vlan 2127)
- L2VPN-SFU-10228-04 (vlan 2128)
- L2VPN-SFU-10228-05 (vlan 2126)
- L2VPN-SAVI-10902-01 (vlan 300)
- L2VPN-BCNET-10252-11 (vlan 610)
- L2VPN-BCNET-10252-12 (vlan 611)
- L2VPN-BCNET-10252-13 (vlan 612)
- L2VPN-BCNET-10252-14 (vlan 450)
- L2VPN-BCNET-10252-15 (vlan 3901)
- L2VPN-BCNET-10252-16 (vlan 3921)
- L2VPN-BCNET-10252-23 (vlan 2923)
- L2VPN-BCNET-10252-24 (vlan 2924)
- L2VPN-BCNET-10252-25 (vlan 2925)
- L2VPN-PWAVE-10368-01
- L2VPN-ECONET-10108-06 (vlan 6)
- L2VPN-SSC:DFO-10029-04 (vlan 1238)
- L2VPN-SSC:NRC-10029-15 (vlan 1241)
- L2VPN-SSC:AAFC-10029-05 (vlan 610)
- L2VPN-SSC:AAFC-10029-08 (vlan 1406)
- L2VPN-SSC:AAFC-10029-09 (vlan 1306)
- L2VPN-SSC:AAFC-10029-10 (vlan 1230)
- L2VPN-SSC:AAFC-10029-13 (vlan 1235)
- L2VPN-SSC:AAFC-10029-14 (vlan 1236)
- L2VPN-SSC:CFIA-10029-16 (vlan 1233)
- L2VPN-SSC:I_GCSN-10029-02 (vlan 1000)
- L2VPN-SSC:O_GCSN-10029-01 (vlan 10)
- L2VPN-ComputeCanada-10355-02 (vlan 2951)
- L2VPN-SSC:HealthCanada-10029-11 (vlan 1239)