The Brocade ADX offers two methods for binding multiple ports to a single healthcheck ; via the use of a port profile or by using healthcheck element groups.<\/p>\n
The main caveat when using a port profile is that you can only bind a non well-known port to the healthcheck of a well known port.
\nAnd also that the configuration for the port is global across the ADX.<\/p>\n
Within this article we will focus on the configuration steps for configuring healthcheck elements.<\/p>\n
The configuration is pretty standard. You configure your healthchecks and assign them to your real servers.
\nThe key command, however, is ‘hc-track-port 80 443’. This command instructs the ADX to track the health status of the master port (in this case 80) and bind the health to a secondary port (in this case port 443).
\nThis ensures if the master port goes down traffic is also not sent to the secondary port.<\/p>\n
healthck 192.168.100.1-hc tcp\r\n\u00a0 dest-ip 192.168.100.1\r\n\u00a0 port http\r\n\u00a0 protocol http\r\n\u00a0 protocol http url \"GET \/healthcheck.html\"\r\n\u00a0 l7-check\r\n!\r\n healthck 192.168.100.2-hc tcp\r\n\u00a0 dest-ip 192.168.100.2\r\n\u00a0 port http\r\n\u00a0 protocol http\r\n\u00a0 protocol http url \"GET \/healthcheck.html\"\r\n\u00a0 l7-check\r\n!\r\n server real web1_192.168.100.1 192.168.100.1\r\n\u00a0port http\r\n\u00a0port http healthck 192.168.100.1-hc\r\n\u00a0port http keepalive\r\n\u00a0port http url \"GET \/\"\r\n\u00a0port ssl\r\n\u00a0port ssl keepalive\r\n\u00a0hc-track-port 80 443\r\n!\r\nserver real web2_192.168.100.2 192.168.100.2\r\n\u00a0port http\r\n\u00a0port http healthck 192.168.100.2-hc\r\n\u00a0port http keepalive\r\n\u00a0port http url \"GET \/\"\r\n\u00a0port ssl\r\n\u00a0port ssl keepalive\r\n\u00a0hc-track-port 80 443<\/pre>\nGotcha<\/strong><\/h2>\n
Based on the configuration above consider the following scenario. Port 80 is marked as failed for a real server after the port failed its healthcheck. However when running a ‘show server bind’ you notice that ssl is still showing as active even though you have grouped these 2 ports via the use of the ‘hc-track-port’ command.<\/p>\n
SSH@ADX# show hc-track-port-state\r\nReal Server\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 track-port\u00a0\u00a0 state<\/pre>\nweb1_192.168.100.1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 80 443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 DOWN
\nweb2_192.168.100.2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 80 443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ACTIVE<\/p>\nBased on this output, you can see that the group is marked as ‘DOWN’. Meaning that the ADX will not send any traffic to either port 80 or 443, even though the port shows as active within ‘show server bind’.<\/p>\n","protected":false},"excerpt":{"rendered":"