About the author

Related Articles

8 Comments

  1. 1

    Gianni

    Good article and usefull!!! Im testing ipvsadm+keepalive to do similar failover/balancing.

    I have a doubt, perhaps it is a typo, u write 192.168.1.238 instead of 237?

    regards
    Gianni

    Reply
  2. 2

    viktorious

    You’re right! There was a minor mistake in the article, I’ve changed it…everything should be ok now. Thanks for your message.

    Reply
  3. 3

    ran

    hi, is it also possible to just run the pfsense from the cloud if i have a huge cloud hosting?

    Reply
    1. 3.1

      viktorious

      What scenario are you thinking about? Do you want to use pfsense as a loadbalancer for this cloud infrastructure or as VM within the cloud? For production scenarios I would recommend a supported option, pfsense is only community supported…

      Reply
  4. 4

    Abhinav

    Thanks for the wonderful article.
    We tried using pfSense for Load Balancing between 2 vSphere SSO VMs.
    It works absolutely fine if we test it using a web browser, but for some reason the Inventory Service installer doesnt like it.

    Our setup:
    SSO VM1 : 192.168.1.10
    SSO VM1 : 192.168.1.11
    Gateway for both VMs: 192.168.1.1 (LAN interface of pfSense)

    https://:7444/lookupservice/sdk works fine in web browser.

    Any thoughts ?

    Reply
    1. 4.1

      viktorious

      I presume you’re running the SSO nodes in HA mode? Maybe you will need some kind of session affinity; after the initial connection is made, I think the Inventory Service has to connect to the same node each time.

      I am wondering if this helps!

      Reply
  5. Pingback: Load balancing the vSphere Web Client | Virtual Lifestyle

  6. Pingback: vUnhandledException » VCPA-CIA Objective 1.2 – Configure vCloud Director for scalability

Leave a Reply