NetScaler
This page is under Construction |
Basics
- A Netscaler is deployed in front of Server farm & functions as a Transparent Proxy between Client & server without requiring any client-side Configuration.
#ship #show connectiontable
#config ns OR #set ns config -Ipaddress <IP> -netmask <mask>
#add ns ip <IP> <subnet mask> -mgmtAccess [Enabled|Disabled] -type MIP
- Adding Virtual Server automatically creates a VIP
- VLAN tagging does not propagate in NS HA Pairs
- Can create null routes to prevent routing loops
- 2 interfaces should not be plugged into same port or vlan unless using link aggregation
- No IP to Interface mapping => Floating IP config
- Why? In HA, when Primary failes, secondary takes over, no loss of Service.
- When the Backend Application expects request for a specific Hostname or redirect you to that hostname, Netscaler should be configured as below:
- Configure the VIP for the same Hostname - Use URL Transformation to achieve the same
- References
{{#widget:DISQUS
|id=networkm
|uniqid=NetScaler
|url=https://aman.awiki.org/wiki/NetScaler
}}