25. September 2016

    Configure the Health Check for vRealize Operations Manager with NSX Load Balancer

    Create Service Monitor

    Name SM-HTTPS-vRealize-Operations-Manager-WebUI
    Type: HTTPS
    Expected: 200
    Method: GET
    URL: /casa/sysadmin/slice/online_state
    Receive: {"slice_online_state":"ONLINE"
    Extension:

    header="Host: vROPs-node01.lab.local"

    authorization=admin:MY_PASSWORD


    Important information:

    Since NSX version 6.2.0, there is no need to escape special characters.

    In previous versions, you have to escape it in any statements, which were written in the haproxy.conf. Escape character is "\" without quotes. Check my post "Escape characters are not needed anymore" .

     

    e.g. passoword: MY!STRONG!Password

    authorization=admin:MY\!STRONG\!Password

     

    e.g. URL: /index.php?target=Main&action=statusCheck

    "/index.php?target=Main\&action=statusCheck"

     

    VMware forgot to put this information into the change log.

    Associate Service Monitor to your pool

    Check status of your pool

    lb01.lab.local-0> show service loadbalancer pool VP-vRealize-Operations-Manager-WebUI

    -----------------------------------------------------------------------

    Loadbalancer Pool Statistics:

     

    POOL VP-vRealize-Operations-Manager-WebUI

    |  LB METHOD leastconn

    |  LB PROTOCOL L7

    |  Transparent disabled

    |  SESSION (cur, max, total) = (0, 57, 11969)

    |  BYTES in = (48357944), out = (546704250)

       +->POOL MEMBER: VP-vRealize-Operations-Manager-WebUI/vrops-node01, STATUS: UP

       |  |  HEALTH MONITOR = BUILT-IN, SM-HTTPS-vRealize-Operations-Manager-WebUI:L7OK

       |  |  |  LAST STATE CHANGE: 2017-03-18 13:09:46

       |  |  SESSION (cur, max, total) = (0, 57, 2508)

       |  |  BYTES in = (6243758), out = (74202528)

       +->POOL MEMBER: VP-vRealize-Operations-Manager-WebUI/vrops-node02, STATUS: UP

       |  |  HEALTH MONITOR = BUILT-IN, SM-HTTPS-vRealize-Operations-Manager-WebUI:L7OK

       |  |  |  LAST STATE CHANGE: 2017-03-18 13:09:46

       |  |  SESSION (cur, max, total) = (0, 16, 9459)

       |  |  BYTES in = (42114186), out = (472501722)

     

    Troubleshooting issues

    Please see my next blog entry, how you could trouble shoot issues if health check fails.

    1. Check written configuration

    2. Set up packet capture

    Tags: NSX, vrealize, operations, loadbalancer, load, balancer, health, check, service monitor, load balancer

    Kommentar schreiben

    Kommentare: 0