This section guides you in applying new Application Delivery Controller (ADC) configurations on Thunder using PowerShell scripts. These PowerShell scripts make Thunder aXAPI calls over the HTTPS protocol.
PowerShell is required to execute the PowerShell script. For more information, see Prerequisites.
Table 8 provides an overview of the different supported Thunder configurations. These configurations are optional. You can choose to apply them based on your specific use cases. For more information, see Deployment Templates.
Configuration |
Description |
|||
---|---|---|---|---|
Applies a new vThunder instance password.
|
||||
Applies an SLB configuration for inbound traffic, outbound traffic, policies, server grouping, and routing to destination virtual servers. |
||||
Applies an SLB configuration automatically whenever backend app/web servers are autoscaled. When the backend web/app servers are in a Virtual Machine Scale Set (VMSS) group within the Azure cloud, autoscale-in or autoscale-out of server triggers a defined webhook for SLB configuration, applying or removing virtual server configuration in Thunder. |
||||
Applies an A10 license to the vThunder instance.
|
||||
Applies a server connection certificate configuration. An SSL certificate is a digital certificate that authenticates a website's identity and enables an encrypted connection. SSL stands for Secure Sockets Layer, a security protocol that creates an encrypted link between a web server and a web browser. Applies server connection certificate configurations. A Secure Sockets Layer (SSL) certificate is a digital certificate that verifies a website's identity and facilitates an encrypted connection. SSL is a security protocol that establishes an encrypted link between a web server and a web browser. |
||||
Applies a high availability configuration. These configurations automatically synchronize Thunder configurations between the active and standby Thunder instances. In the event of a failover, it designates the other Thunder instance as active to ensure uninterrupted traffic routing. For this functionality, it is essential for both Thunder instances to have identical resources and configurations. |
||||
Applies a disaster recovery configuration using a global server load balancer across any two regions or locations, whether same cloud, hybrid-cloud or on-premise. It requires a minimum of two Thunder instances in each region or location —one acting as the master controller and the other as a site device. Multiple site devices can be configured but it is recommended to have minimum of three site devices for seamless failover and effective disaster recovery. For a configuration with three Thunders instances, the recommended setup includes one as the master controller and the other two as a site device. Ensure that both regions have identical set of resources. To create and install three thunder instances in one region use Thunder-3NIC-3VM template. Same template can be used to install in another region. |