@Hello Al
I have a project to be submitted.
Here's the scenario.
I have 2 RSA Authentication Managers in Prod. Right now, our privilege access management is pointing to primary RSA AM, and when I am doing maintenance I have to manually switch RADIUS authentication to secondary. To overcome with this problem I am looking to create F5 VIP which will then point to both primary & secondary AM as failover.
I am little confused with few question and not sure about the answers
Virtual Server FQDN: rsa-prod.abc.om
Virtual IP Address: 20.20.20.1
Protocol: ? ------------------------
Service Port 1812 TCP.
Persistence (default & Fallback): ? ------------- Source_addr or Universal Persistance?
Monitor Type: ? ---------------------
Send String: -------------------------
Receive String: UP
Member server hostname: rsa1-prod.abc.com & rsa2-prod.abc.com
Member IP: 10.10.10.1 & 10.10.10.2
Service Port: 1812
Priority Group: Disabled
Load Balancing Method: Round Robin
If this has been accomplished in your environment would you help me fill the blanks please.
Virtual Server FQDN / URL | Virtual IP Address | Protocol | Service Port (TCP) | HTTPS Redirect | Persistance (default & fallback) | Montor Type | Freq. (Secs) | TOut (secs) | Send String | Receive String | Username | Password | Member Server (Hostname) | Member IP Address | Service Port | Priority Group | Load Balancing Method | Monitor Failure Action |
Jai Pagare,
Great question! OK, RSA SecurID Access community, can anyone help Jai out?
Regards,
Erica