AX working with VMWare 'View'

Posted by LynnS

A customer asked if we can work with their VMWARE 'View' product. I've not had any time yet to research this, but I wanted to ask if anyone has any idea what this product is/does and if the AX is compatible with it in any way. This came up in a conversation about VMWARE VCenter working with our axAPI. Thanks!

Comments

  • edited February 2014
    Posted by ddesmidt

    I haven't personally tested it, but AX has the functionalities required to load balance VMware View.

    There are multiple ways to configure VMView.

    Case1:
    VMView not using PCoIP (use SSL) + AX configured with no SSL Offload (end-to-end SSL)

    On VMware Manager servers:
    . Keep default "Require SSL for client connections"
    . Configure external URL with "https:// vmview.example.com" (with "vmview.example.com" = AX-VIP)
    . Uncheck "direct connection to desktop"

    On AX:
    . VIP x.x.x.x
    . port 443 type https
    - Service Group with "View_Managers_servers:443"
    - Create aFleX for persistence based on the cookie JSESSIONID (see http://www.a10networks.com/vadc/index.php/forums/topic/aflex-for-individual-server-cookie-persist/)
    - Client-SSL-Template with your certificate for "https:/vmview.example.com"
    - Server-SSL-Template with default

    Case2:
    VMView not using PCoIP (use SSL) + AX configured with SSL Offload (SSL up to AX only)

    On VMware Manager servers:
    . Uncheck default "Require SSL for client connections" (under View Manager Administrator tool - View Configuration - Global Settings - Edit"
    . Configure external URL with "https:// vmview.example.com" (with "vmview.example.com" = AX-VIP)
    . Uncheck "direct connection to desktop"
    . Restart the View Connection Server service (as explained in the www.vmware.com/pdf/view-46-administration.pdf)

    On AX:
    . VIP x.x.x.x
    . port 443 type https
    - Service Group with "View_Managers_servers:80"
    - Create aFleX for persistence based on the cookie JSESSIONID (see http://www.a10networks.com/vadc/index.php/forums/topic/aflex-for-individual-server-cookie-persist/)
    - Client-SSL-Template with your certificate for "https:/vmview.example.com"
    - No Server-SSL-Template

    Case3:
    VMView using PCoIP + AX configured with no SSL Offload (end-to-end SSL).
    In that case only authentication/authorization/accounting packets are received and load balanced by AX to VMView Managers servers. Then clients access directly their desktops.

    On VMware Manager servers:
    . Keep default "Require SSL for client connections"
    . Configure external URL with "https:// vmview.example.com" (with "vmview.example.com" = AX-VIP)
    . Check "direct connection to desktop"

    On AX:
    . VIP x.x.x.x
    . port 443 type https
    - Service Group with "View_Managers_servers:443"
    - Create aFleX for persistence based on the cookie JSESSIONID (see http://www.a10networks.com/vadc/index.php/forums/topic/aflex-for-individual-server-cookie-persist/)
    - Client-SSL-Template with your certificate for "https:/vmview.example.com"
    - Server-SSL-Template with default

    Case4:
    VMView using PCoIP + AX configured with SSL Offload (SSL up to AX only).
    In that case only authentication/authorization/accounting packets are received and load balanced by AX to VMView Managers servers. Then clients access directly their desktops.

    On VMware Manager servers:
    . Uncheck default "Require SSL for client connections" (under View Manager Administrator tool - View Configuration - Global Settings - Edit"
    . Configure external URL with "https:// vmview.example.com" (with "vmview.example.com" = AX-VIP)
    . Check "direct connection to desktop"
    . Restart the View Connection Server service (as explained in the www.vmware.com/pdf/view-46-administration.pdf)

    On AX:
    . VIP x.x.x.x
    . port 443 type https
    - Service Group with "View_Managers_servers:80"
    - Create aFleX for persistence based on the cookie JSESSIONID (see http://www.a10networks.com/vadc/index.php/forums/topic/aflex-for-individual-server-cookie-persist/)
    - Client-SSL-Template with your certificate for "https:/vmview.example.com"
    - No Server-SSL-Template

    If you plan to test it yourself, come back to us with the results :-)
Sign In or Register to comment.