Scenario: The primary content switching vServer has gone down. To troubleshoot, a Citrix Administrator has issued the following command:
> show csvserver CSV
CSV (10.1.100.100:443) -- HTTPS Type: CONTENT
State: UP
Last state change was at Mon Jun 29 15:20:43 2020
Time since last state change: 1 day, 06:47:58 610
Client Idle Timeout: 180 sec
Down state flush: ENABLED
Disable Primary vServer On Down: DISABLED
Appflow logging: ENABLED
Port Rewrite: DISABLED
State Update: DISABLED
Default: Content Precedence: URL
vServer IP and Port insertion: OFF
Persistence: NONE redirect: http://www.site1.com/mysite1/maintenance
Backup: vServer--LB--2
Listen Policy: NONE
IcmpResponse: PASSIVE
RHIstate: PASSIVE
Traffic Domain: 0
Based on this output, where will the subsequent request be redirected?
Forcing the node to stay secondary works on both standalone and secondary nodes. On a standalone node, you must use this option before you can add a node to create an HA pair. When you add the new node, the existing node stops processing traffic and becomes the secondary node. The new node becomes the primary node.
On a standalone node, you must use this option before you can add a node to create an HA pair. When you add the new node, the existing node continues to function as the primary node, and the new node becomes the secondary node.
Louis
1 days agoFabiola
3 days agoCherrie
11 days ago