NetScaler: Difference between revisions
Content added Content deleted
(page created) |
(added template) |
||
Line 1: | Line 1: | ||
[[Category:Citrix]] |
|||
__TOC__ |
|||
<br /> |
|||
{{notice|This page is under Construction}} |
{{notice|This page is under Construction}} |
||
Line 21: | Line 24: | ||
*No IP to Interface mapping => Floating IP config |
*No IP to Interface mapping => Floating IP config |
||
*Why? In HA, when Primary failes, secondary takes over, no loss of Service. |
*Why? In HA, when Primary failes, secondary takes over, no loss of Service. |
||
<br /> |
|||
;References |
|||
<references/> |
|||
<br /> |
|||
<br /> |
|||
<br /> |
|||
{{DISQUS}} |
Revision as of 16:34, 21 November 2016
This page is under Construction |
- 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.
- References
{{#widget:DISQUS
|id=networkm
|uniqid=NetScaler
|url=https://aman.awiki.org/wiki/NetScaler
}}