ADC

Static route advertisement to upstream routers

February 12, 2026

Contributed by:

To reduce the high costs associated with using external cloud routers or ALBs for NetScaler cluster deployments, a more efficient solution has been validated for Google VPC. While standard VPC routers are natively available, they are limited to static routing and lack support for dynamic protocols like ECMP. NetScaler addresses this issue by introducing automated static route management through the Cluster Control Owner (CCO). By ensuring the number of VPC routes matches the number of active cluster nodes, the CCO can automatically delete routes when a node fails or add them when a node is joined, providing a seamless and cost-effective traffic distribution method within the cloud environment.

To configure static route advertisement to upstream routers, perform the following steps:

Enable the gcpstaticroutes feature. By default, this feature is disabled.

> set cloud gcpstaticroutes -status ENABLED / DISABLE
<!--NeedCopy-->

Add route profiles.
```
> add cloud routes <name>  -routesVpcNetwork [-vipSubnet <ip_addr[/prefix]|ipv6_addr[/prefix]>] [-vipVpcNetwork ]

```
In the command:
- RoutesVpcNetwork – VPC name in GCP where routes must be installed.
- VipSubnet – The subnet for which routes must be installed in CIDR notation.
- VipVpcNetwork – VPC name from which subnets are picked up and installed as routes.
Note:

You can either use –vipSubnet option for single subnet CIDR or –vipVpcNetwork option where VPC name is used. All subnets are under given VPC are installed as routes.

Example:
```
> add cloud routes profileP5 -routesVpcNetwork target-vpc -vipsubnet 80.0.0.0/24 

> add cloud routes profileP4 -routesVpcNetwork target-vpc -vipvpcNetwork vip1-vpc-name 

```
Push the routes to the GCP cloud console.
```
> apply cloud routes

```
If you change cloud routes profile, run the apply cloud routes command to update cloud routes in the GCP.
Clear and remove all cloud routes profile. After clear command, run apply cloud routes for the changes to reflect in GCP.
```
> clear cloud routes

```

Run show Cloud Routes command.

> show cloud routes
<!--NeedCopy-->

Example:

> sh cloud routes 
1) Name: profile_p1 RoutesVpcNetwork: target-vpc VipSubnet: 90.0.0.0/2 
2) Name: profile_p4 RoutesVpcNetwork: target-vpc VipVpcNetwork: vip1-vpc-name
<!--NeedCopy-->

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

NetScaler Secure Deployment Guide

Static route advertisement to upstream routers

February 12, 2026

Contributed by:

February 12, 2026

Contributed by:

Static route advertisement to upstream routers

In this article