{"id":954,"date":"2015-11-20T22:29:59","date_gmt":"2015-11-20T22:29:59","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2015\/11\/20\/brocade-adx-multiple-health-checks-on-a-per-domain-basis\/"},"modified":"2021-07-31T16:17:34","modified_gmt":"2021-07-31T16:17:34","slug":"brocade-adx-multiple-health-checks-on-a-per-domain-basis","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Loadbalancers\/Brocade\/brocade-adx-multiple-health-checks-on-a-per-domain-basis.html","title":{"rendered":"Brocade ADX – Multiple Health-checks on a Per Domain Basis"},"content":{"rendered":"
Now lets consider the following scenario. The client has multiple domains. Traffic is going to all domains on HTTP. However, these domains are under a single virtual server and each domain requires a separate health-check.<\/p>\n
In order to achieve this configuration port-aliasing is used. What is port-aliasing, you may ask ?
\nWithin the ADX various configuration options can be assigned on a per port basis on the real server. Port-aliasing allows you to map a different port against your real port i.e port 80.<\/p>\n
Below is a summary of the configuration elements within our example,<\/p>\n
Domain<\/strong><\/td>\nAlias Port<\/strong><\/td>\n | Group id<\/strong><\/td>\n | Port-Policy<\/strong><\/td>\n<\/tr>\n | Domain1<\/td>\n | 81<\/td>\n | 1<\/td>\n | DOMAIN1<\/td>\n<\/tr>\n | Domain2<\/td>\n | 82<\/td>\n | 2<\/td>\n | DOMAIN2<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n | \n Table of Contents<\/p>\n |