Cloud SWG backup sites, hostnames and VIPs for fixed locations
Article ID: 400758
Updated On:
Products
Issue/Introduction
What are the backup sites and their hostnames for explicit proxy, SEP Web and Cloud Access Protection and/or proxy forwarding methods?
What are the backup site VIPs for IPSec connections?
What is the optimal backup site for my primary site?
Environment
Explicit, SEP Web and Cloud Access protection, Proxy Forwarding and IPSec Access methods
Cause
Users accessing Cloud SWG via SEP Web and Cloud Access protection, Explicit or Proxy Forwarding access methods connecting to non-optimal Cloud SWG site.
Users accessing Cloud SWG via IPSec are unable to access the Internet since no backup IPSec tunnel is established.
Resolution
The following guide contains a table with the following:
- The most optimal backup site for every Cloud SWG site.
- A backup hostname for Explicit and Proxy Forwarding which resolves to the backup Cloud SWG site.
- A VIP for each backup Cloud SWG site for IPSec tunnels.
More about hostnames:
Each primary site listed has a hostname for its designated backup site based on the name of the primary site. This allows CloudSWG administrators to add a backup hostname to configurations where a primary hostname is used in configurations for explicit or proxy forwarding access methods, without knowing the actual designated backup site.
WARNING*: These options should only be used by experienced individuals who understand the implications of manual traffic redirection. Manual data center selection may result in poor performance, reduced fault tolerance, and invalidation of relevant SLA claims.
For the six hostnames per primary data center, there are equivalent backup hostnames:
| Primary site | Backup site |
| [site codename]-vip[1-6].threatpulse.net | [site codename]-backup-vip[1-6].threatpulse.net |
Where:
- [site codename] is a codename from the table below.
- [1-6] is a number 1 through 6 for each of the available six IP addresses.
Example:
|
Primary site hostname |
Backup site hostname |
|
gjptk1-vip1.threatpulse.net gjptk1-vip2.threatpulse.net gjptk1-vip3.threatpulse.net gjptk1-vip4.threatpulse.net gjptk1-vip5.threatpulse.net gjptk1-vip6.threatpulse.net |
gjptk1-backup-vip1.threatpulse.net gjptk1-backup-vip2.threatpulse.net gjptk1-backup-vip3.threatpulse.net gjptk1-backup-vip4.threatpulse.net gjptk1-backup-vip5.threatpulse.net gjptk1-backup-vip6.threatpulse.net |
NOTE CHINESE HOSTNAMES:
CloudSWG sites ACNSH and ACNBJ are in China and will use a different format. They will use <hostname>.wss.broadcom.cn instead of <hostname>.threatpulse.net. Examples: acnsh1-vip1.threatpulse.net and acnsh1-backup-vip1.threatpulse.net. This hostname change is necessary due to Chinese regulations which Symantec/Broadcom must abide by. The Chinese hosts will also have the six different VIPs as explained in the example above for Tokyo (gjptk1).
Cloud SWG sites, backup hostnames and backup VIPs:
|
Primary site |
Backup site hostname (Explicit and/or Proxy Forwarding) |
Backup site VIP (IPSec) |
Backup site |
|
Americas |
|||
|
Bogota, Columbia (GCOBO) |
gcobo1-backup-vip1.threatpulse.net |
34.95.130.164 |
Sao Paolo, Brazil (GBRSP) |
|
Buenos Aires, Argentina (GARBA) |
garba1-backup-vip1.threatpulse.net |
199.116.174.164 |
Bogota, Columbia (GCOBO) |
|
Columbia, South Carolina (GUSCO) |
gusco1-backup-vip1.threatpulse.net |
170.176.240.164 |
Washington, DC (GUSAS) |
|
Dallas, Texas (GUSDA) |
gusda1-backup-vip1.threatpulse.net |
199.247.42.164 |
Des Moines, Iowa (GUSDM) |
|
Des Moines, Iowa (GUSDM) |
gusdm1-backup-vip1.threatpulse.net |
170.176.240.164 |
Washington, DC (GUSAS) |
|
Las Vegas, Nevada (GUSLV) |
guslv1-backup-vip1.threatpulse.net |
199.19.248.164 |
Los Angeles, California (GUSLA) |
|
Los Angeles, California (GUSLA) |
gusla1-backup-vip1.threatpulse.net |
168.149.133.164 |
Las Vegas, Nevada (GUSLV) |
|
Mexico City, Mexico (GMXMC) |
gmxmc1-backup-vip1.threatpulse.net |
168.149.128.164 |
Dallas, Texas (GUSDA) |
|
Montreal, Canada (GCAMO) |
gcamo1-backup-vip1.threatpulse.net |
168.149.130.164 |
Toronto, Canada (GCATO) |
|
Portland, Oregon (GUSPO) |
guspo1-backup-vip1.threatpulse.net |
168.149.133.164 |
Las Vegas, Nevada (GUSLV) |
|
Sao Paolo, Brazil (GBRSP) |
gbrsp1-backup-vip1.threatpulse.net |
199.116.174.164 |
Bogota, Columbia (GCOBO) |
|
Toronto, Canada (GCATO) |
gcato1-backup-vip1.threatpulse.net |
199.19.253.164 |
Montreal, Canada (GCAMO) |
|
Washington, DC (GUSAS) |
gusas1-backup-vip1.threatpulse.net |
168.149.137.164 |
Columbia, South Carolina (GUSCO) |
|
APAC |
|||
|
Auckland, New Zealand (GNZAU) |
gnzau1-backup-vip1.threatpulse.net |
168.149.190.164 |
Melbourne, Australia (GAUME) |
|
Beijing, China (ACNBJ) |
acnbj1-backup-vip1.wss.broadcom.cn |
40.72.119.208 |
Shanghai, China (ACNSH) |
|
Delhi, India (GINDE) |
ginde1-backup-vip1.threatpulse.net |
148.64.4.164 |
Mumbai, India (GINMU) |
|
Hong Kong, China (GCNHK) |
gcnhk1-backup-vip1.threatpulse.net |
103.246.37.164 |
Singapore (GSGRS) |
|
Jakarta, Indonesia (GIDJK) |
gidjk1-backup-vip1.threatpulse.net |
103.246.37.164 |
Singapore (GSGRS) |
|
Melbourne, Australia (GAUME) |
gaume1-backup-vip1.threatpulse.net |
148.64.2.164 |
Sidney, Australia (GAUSY) |
|
Mumbai, India (GINMU) |
ginmu1-backup-vip1.threatpulse.net |
168.149.182.164 |
Delhi, India (GINDE) |
|
Osaka, Japan (GJPOS) |
gjpos1-backup-vip1.threatpulse.net |
223.29.216.164 |
Tokyo, Japan (GJPTK) |
|
Seoul, South Korea (GKRSE) |
gkrse1-backup-vip1.threatpulse.net |
98.158.245.164 |
Osaka, Japan (GJPOS) |
|
Shanghai, China (ACNSH) |
acnsh1-backup-vip1.wss.broadcom.cn |
52.131.103.144 |
Beijing, China (ACNBJ) |
|
Singapore (GSGRS) |
gsgrs1-backup-vip1.threatpulse.net |
103.246.38.164 |
Hong Kong, China (GCNHK) |
|
Sidney, Australia (GAUSY) |
gausy1-backup-vip1.threatpulse.net |
168.149.190.164 |
Melbourne, Australia (GAUME) |
|
Taipei, Taiwan (GTWTA) |
gtwta1-backup-vip1.threatpulse.net |
103.246.37.164 |
Singapore (GSGRS) |
|
Tokyo, Japan (GJPTK) |
gjptk1-backup-vip1.threatpulse.net |
98.158.245.164 |
Osaka, Japan (GJPOS) |
|
EMEA |
|||
|
Abu Dhabi, UAE (GAEAD) |
gaead1-backup-vip1.threatpulse.net |
148.64.17.164 |
Dammam, Saudi Arabia (GSADA) |
|
Amsterdam, the Netherlands (GNLAM) |
gnlam1-backup-vip1.threatpulse.net |
199.247.38.164 |
Frankfurt, Germany (GDEFR) |
|
Ankara, Turkey (GTRAN) |
gtran1-backup-vip1.threatpulse.net |
185.180.49.164 |
Milan, Italy (GITMO) |
|
Brussels, Belgium (GBEBR) |
gbebr1-backup-vip1.threatpulse.net |
199.116.172.1 |
Paris, France (GFRVE) |
|
Bucharest, Romania (GROBU) |
grobu1-backup-vip1.threatpulse.net |
185.180.49.164 |
Milan, Italy (GITMO) |
|
Copenhagen, Denmark (GDKCP) |
gdkcp1-backup-vip1.threatpulse.net |
199.247.38.164 |
Frankfurt, Germany (GDEFR) |
|
Dammam, Saudi Arabia (GSADA) |
gsada1-backup-vip1.threatpulse.net |
185.180.49.164 |
Milan, Italy (GITMO) |
|
Dover, England (GGBDO) |
ggbdo1-backup-vip1.threatpulse.net |
148.64.26.164 |
London, England (GGBLO) |
|
Dublin, Ireland (GIEDU) |
giedu1-backup-vip1.threatpulse.net |
148.64.24.164 |
Dover, England (GGBDO) |
|
Frankfurt, Germany (GDEFR) |
gdefr1-backup-vip1.threatpulse.net |
98.158.252.164 |
Amsterdam, the Netherlands (GNLAM) |
|
Helsinki, Finland (GFIHE) |
gfihe1-backup-vip1.threatpulse.net |
199.247.38.164 |
Frankfurt, Germany (GDEFR) |
|
Johannesburg, South Africa (GZASO) |
gzaso1-backup-vip1.threatpulse.net |
185.180.49.164 |
Milan, Italy (GITMO) |
|
London, England (GGBLO) |
ggblo1-backup-vip1.threatpulse.net |
148.64.24.164 |
Dover, England (GGBDO) |
|
Madrid, Spain (GESTO) |
gesto1-backup-vip1.threatpulse.net |
185.180.49.164 |
Milan, Italy (GITMO) |
|
Milan, Italy (GITMO) |
gitmo1-backup-vip1.threatpulse.net |
199.19.249.164 |
Madrid, Spain (GESTO) |
|
Oslo, Norway (GNOOS) |
gnoos1-backup-vip1.threatpulse.net |
98.158.252.164 |
Amsterdam, the Netherlands (GNLAM) |
|
Paris, France (GFRVE) |
gfrve1-backup-vip1.threatpulse.net |
148.64.24.164 |
Dover, England (GGBDO) |
|
Stockholm, Sweden (GSESK) |
gsesk1-backup-vip1.threatpulse.net |
199.247.38.164 |
Frankfurt, Germany (GDEFR) |
|
Tel Aviv, Israel (GILTA) |
gilta1-backup-vip1.threatpulse.net |
185.180.49.164 |
Milan, Italy (GITMO) |
|
Warsaw, Poland (GPOWA) |
gpowa1-backup-vip1.threatpulse.net |
199.247.38.164 |
Frankfurt, Germany (GDEFR) |
|
Zurich, Switzerland (GCHZU) |
gchzu1-backup-vip1.threatpulse.net |
199.247.38.164 |
Frankfurt, Germany (GDEFR) |
Feedback
