Configurations kept independent in High Availability
Setting up High Availability only requires a single line of configuration on each node add ha node <node ID> <IP Address> (the node IDs don't need to be unique).
- NSIPs
- Interface configurations
- Hostnames
Note
Any configuration changes made outside of these areas should be done only on the primary. The risk with not following this is that the command run on the secondary will not be propagated, and hence will be lost during the next sync/propagation.
Get Troubleshooting NetScaler now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
