Citrix (Netscaler) configuration for PSM Load Balancer

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Citrix (Netscaler) configuration for PSM Load Balancer

L3 Networker

Hi All,

 

I would like to share the following information regarding the configuration of the Citrix (Netscaler) Load Balancer for PSM.

 

Citrix ADC Load Balance Config for CyberArk PSM

 

Certainly, many customers use this Load Balancer model and it would be useful to integrate the official documentation.

 

 

Nino

1 accepted solution

Accepted Solutions

L2 Linker

Hi Guys, sorry i took down the site due to hosting issue, I'm happy to see it helped few, posting the content here. NS CLI commands

 

## Add PSM Backend Servers ## add server PSM-01 x.x.x.x -comment cyberark add server PSM-02 x.x.x.x -comment cyberark ## Create RDS Health Monitor & PSM Health Monitor ## add lb monitor CyberArk-PSMHealth-monitor HTTP-ECV -send "GET /psm/api/health" -recv PASS -LRTM DISABLED -interval 30 -resptimeout 10 -destPort 443 -secure YES -sslProfile ns_default_ssl_profile_backend add lb monitor CyberArk-RDSHealth-monitor USER -scriptName nsrdp.pl -dispatcherIP 127.0.0.1 -dispatcherPort 3013 -LRTM DISABLED -interval 30 -resptimeout 10 ## Create TCP Service Group, bind backend servers and health monitors with service group monitor threshold/weight of 2 ## add serviceGroup CyberArkPSM-TCP3389-SG TCP -maxClient 0 -maxReq 0 -cip DISABLED -usip NO -useproxyport YES -cltTimeout 9000 -svrTimeout 9000 -CKA NO -TCPB NO -CMP NO -monThreshold 2 -downStateFlush DISABLED -comment "SM: CyberArk PSM Service Group" bind serviceGroup CyberArkPSM-TCP3389-SG PSM-01 3389 bind serviceGroup CyberArkPSM-TCP3389-SG PSM-02 3389 bind serviceGroup CyberArkPSM-TCP3389-SG -monitorName CyberArk-PSMHealth-monitor bind serviceGroup CyberArkPSM-TCP3389-SG -monitorName CyberArk-RDSHealth-monitor ## Create LB TCP VIP ## add lb vserver CyberarkPSM_TCP3389_VS TCP x.x.x.x 3389 -persistenceType NONE -cltTimeout 9000 bind lb vserver CyberarkPSM_TCP3389_VS CyberArkPSM-TCP3389-SG

Couple of things to call out, the PSM monitor presumes the PSM Health Check backend server setup is configured with ResponseMode of Classic. Notice the PSM monitor has the destPort override of 443, without it service group port would be used causing the probe to fail. Also the monThreshold for the service group set to 2, both health checks need to pass for ADC to mark the backend server as up.

 

Hope this helps more. if there questions please reach out.

View solution in original post

7 REPLIES 7

L7 Applicator

Thanks for sharing this!

-Matt

L0 Member

Link is not reach able

 

L7 Applicator

hey @Antonino Bambino​ 

It seems the link is now broken. Can you update it?

-Matt

L6 Presenter

Hi all,

 

unfortunately the site is offline.

 

I'm trying to track down the site manager to get some information.

 

Nino

hello

did you find the information?

 

I am having a problem with my client about this configuration.

L2 Linker

Hi Guys, sorry i took down the site due to hosting issue, I'm happy to see it helped few, posting the content here. NS CLI commands

 

## Add PSM Backend Servers ## add server PSM-01 x.x.x.x -comment cyberark add server PSM-02 x.x.x.x -comment cyberark ## Create RDS Health Monitor & PSM Health Monitor ## add lb monitor CyberArk-PSMHealth-monitor HTTP-ECV -send "GET /psm/api/health" -recv PASS -LRTM DISABLED -interval 30 -resptimeout 10 -destPort 443 -secure YES -sslProfile ns_default_ssl_profile_backend add lb monitor CyberArk-RDSHealth-monitor USER -scriptName nsrdp.pl -dispatcherIP 127.0.0.1 -dispatcherPort 3013 -LRTM DISABLED -interval 30 -resptimeout 10 ## Create TCP Service Group, bind backend servers and health monitors with service group monitor threshold/weight of 2 ## add serviceGroup CyberArkPSM-TCP3389-SG TCP -maxClient 0 -maxReq 0 -cip DISABLED -usip NO -useproxyport YES -cltTimeout 9000 -svrTimeout 9000 -CKA NO -TCPB NO -CMP NO -monThreshold 2 -downStateFlush DISABLED -comment "SM: CyberArk PSM Service Group" bind serviceGroup CyberArkPSM-TCP3389-SG PSM-01 3389 bind serviceGroup CyberArkPSM-TCP3389-SG PSM-02 3389 bind serviceGroup CyberArkPSM-TCP3389-SG -monitorName CyberArk-PSMHealth-monitor bind serviceGroup CyberArkPSM-TCP3389-SG -monitorName CyberArk-RDSHealth-monitor ## Create LB TCP VIP ## add lb vserver CyberarkPSM_TCP3389_VS TCP x.x.x.x 3389 -persistenceType NONE -cltTimeout 9000 bind lb vserver CyberarkPSM_TCP3389_VS CyberArkPSM-TCP3389-SG

Couple of things to call out, the PSM monitor presumes the PSM Health Check backend server setup is configured with ResponseMode of Classic. Notice the PSM monitor has the destPort override of 443, without it service group port would be used causing the probe to fail. Also the monThreshold for the service group set to 2, both health checks need to pass for ADC to mark the backend server as up.

 

Hope this helps more. if there questions please reach out.

Hi @Siva M​,

 

thanks for update.

 

I posted the link to your article because I had some requests and I was also interested in learning more about the topic.

 

Nino

  • 1 accepted solution
  • 1382 Views
  • 7 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!