Diiference between HTTPS & HTTPS_443 monitors

https_443 can assign to wildcard (any) port pool member because port number is hardcoded in the monitor. 🙂

root@(B6900-R69-S5)(cfg-sync Standalone)(Active)(/Common)(tmos) list ltm monitor https https_443
ltm monitor https https_443 {
    cipherlist DEFAULT:+SHA:+3DES:+kEDH
    compatibility enabled
    defaults-from https
    destination *:https
    interval 5
    ip-dscp 0
    send "GET /\r\n"
    time-until-up 0
    timeout 16
}

https_443 can assign to wildcard (any) port pool member because port number is hardcoded in the monitor. 🙂

root@(B6900-R69-S5)(cfg-sync Standalone)(Active)(/Common)(tmos) list ltm monitor https https_443
ltm monitor https https_443 {
    cipherlist DEFAULT:+SHA:+3DES:+kEDH
    compatibility enabled
    defaults-from https
    destination *:https
    interval 5
    ip-dscp 0
    send "GET /\r\n"
    time-until-up 0
    timeout 16
}

The difference between HTTPS and HTTPS_443 monitors is in Alias Service Port. Alias Service Port * All Ports - for HTTPS monitor. Alias Service Port HTTPS - for HTTPS_443 monitor.

e.g.

root@(B6900-R69-S5)(cfg-sync Standalone)(Active)(/Common)(tmos) create ltm pool foo members add { 1.1.1.1:any }

root@(B6900-R69-S5)(cfg-sync Standalone)(Active)(/Common)(tmos) modify ltm pool foo monitor https
01070622:3: The monitor /Common/https has a wildcard destination service and cannot be associated with a node that has a zero service.

root@(B6900-R69-S5)(cfg-sync Standalone)(Active)(/Common)(tmos) modify ltm pool foo monitor https_443

root@(B6900-R69-S5)(cfg-sync Standalone)(Active)(/Common)(tmos) list ltm pool foo
ltm pool foo {
    members {
        1.1.1.1:any {
            address 1.1.1.1
            session monitor-enabled
            state checking
        }
    }
    monitor https_443
}