WSS POD Decommissioning Announcement London (GGBLO2)

Duration: 1 day
Complete
Complete
After 3 months, 1 week, 1 day, 1 hour, and 58 minutes

The scheduled maintenance has been completed.

Underway
After 3 months, 1 week, 1 hour, and 58 minutes

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

Symantec will decommission the London POP, GGBLO2, on April 15, 2022. This POP was created in 2020 to facilitate easier migration from the deprecated colo-based data center network to the current Google Cloud network and is now redundant. Traffic from this POP will be redirected to the remaining London POP, GGBLO1, which is hosted in the same Google Cloud region as the POP being decommissioned. Therefore, this change will have no impact on routing or performance.

Carefully review the information below to avoid disruption of service.

Decommission Date: April 15, 2022

Ingress IP addresses • 148.64.8.164 - TO BE RETIRED APRIL 15, 2022 • 148.64.26.164 - REPLACEMENT (existing GGBLO1 ingress IP address)

Egress IP ranges: • 148.64.8.0/24 - TO BE RETIRED APRIL 15, 2022 • 148.64.26.0/24 - REPLACEMENT (existing GGBLO1 egress IP range) • 148.64.27.0/24 - REPLACEMENT (existing GGBLO1 egress IP range)

Required Action Prior to the decommission date:

• Firewall rules regulating connectivity to/from your network to WSS should be adjusted to allow traffic to pass to the replacement IP network listed above. • Third party applications that regulate connections by source IP address should be updated to accept connections from the replacement egress IP networks listed above to ensure traffic proxied through WSS can reach the application.

Failure to make these changes could prevent users from connecting to WSS, accessing third party web applications, or authenticating against the service using the Auth Connector (where applicable).

• IPsec: Customers must update their tunnel configurations to point to the replacement ingress IP address before April 15, 2022. This change can be made immediately. • WSS Agent, SEP Agent: Agent traffic will be automatically redirected to the replacement POP. No customer action is required. • Explicit proxy and proxy forwarding: Customers directing traffic to proxy.threatpulse.net will be automatically redirected to the replacement POP. No customer action is required. • Regardless of connection method, any configuration pointing to a specific POP hostname or IP address (not recommended) must be manually switched to the replacement POP prior to the decommissioning date to avoid an outage.

Please visit this KB article for a full list of IP networks used by WSS: https://knowledge.broadcom.com/external/article?legacyId=TECH242979

Technical Support Experiencing issues? Contact technical support by visiting: https://support.broadcom.com/security.

For service status and maintenance updates visit and subscribe to Broadcom Service Status: https://wss.status.broadcom.com.

Began at:

Affected components