{"id":606,"date":"2011-12-02T07:55:46","date_gmt":"2011-12-02T07:55:46","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2011\/12\/02\/brocade-adx-match-list-port-policy\/"},"modified":"2021-07-24T18:23:44","modified_gmt":"2021-07-24T18:23:44","slug":"brocade-adx-match-list-port-policy","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Loadbalancers\/Brocade\/brocade-adx-match-list-port-policy.html","title":{"rendered":"Brocade ADX – Match-list Port Policy"},"content":{"rendered":"

A match-list provides the ability to content match string based values and mark the application (layer 7) based health-check as either up or down.
When assigning a match-list health-check the match-list is assigned to a port policy. This port policy is then assigned to the virtual server.<\/p>\n

Steps<\/strong><\/h3>\n

1. First we enable Layer 7 health-checks on the webserver<\/p>\n

server real webserver1
  port http keepalive<\/p>\n

2. When next create a match-list which will bring up the health-check if the string ALIVE is found within the content received from the HTTP \/GET that is issues under the port policy.<\/p>\n

http match-list matchlist1
  default down
  up simple “ALIVE” log<\/p>\n

3. A port policy is created and assigned the port http and configuring to perform a HTTP GET \/  and content-match against our previous match-list.<\/p>\n

server port-policy ppolicy1
  port http
  protocol http url “GET \/”
  protocol http content-match matchlist1<\/p>\n

3. Finally the port policy is assigned to the virtual server.<\/p>\n

server virtual VIP_192.168.1.100
  port http use-port-policy ppolicy1<\/p>\n

Show Commands<\/strong><\/h3>\n

The following show commands are especially useful in confirm the status and troubleshooting match-list based health-checks.<\/p>\n