←Previous: main page |
CONFIGURATION REQUIREMENTS |
Next: Testing→ |
Symantec VIP services will be hosted in multiple GCP availability zones. To ensure uninterrupted connectivity from your VIP Enterprise Gateways and hosted applications to the Symantec VIP GCP-hosted cloud platform, review and update your configurations.
IP address pinning of VIP URLs could result in VIP Service disruption. Public DNS resolves traffic to the active VIP IP addresses through the domain in the URLs listed below.
|
|
|
AWS West Region Netblocks |
![]() AWS East Region Netblocks |
services-auth.vip.symantec.com services.vip.symantec.com userservices-auth.vip.symantec.com userservices.vip.symantec.com |
144.49.0.0/16 |
18.236.61.144/28 |
18.208.22.32/28 |
No VIP software updates are necessary. The VIP Enterprise Gateway(s) and Web Services WSDL files are configured to use the following globally load-balanced URLs issued by Symantec VIP. Custom applications should point to these same relevant URLs.
Testing to determine if your VIP Enterprise Gateway, custom server applications, and any other components involved can communicate with the VIP Service can be performed from the application server host and VIP Enterprise Gateway hosts within your production environment. See Testing your VIP environment for the Migration of VIP Services Platform to Google Cloud Services for testing procedures.
VIP Web Services best practice for high-availability and optimal performance
VIP Enterprise Gateway 9.9 FAQ and end-of-support announcement of 9.7 and older