
Chapter 4: Configuring the High-Level Network
4-158
The monitors themselves must be configured with the grouping in mind. For
example, if the dest values of both monitors were set to *:*, then both
monitor instances would try to ping the default port 80. This would both
defeat the purpose of the HTTPS monitor and cause an automatic failure,
since two monitors would be trying to ping the same address and port
simultaneously.
Instead, monitor my_http should be given a dest value of *:* and monitor
my_https should be given a dest value of *:443. This causes only the
my_http monitor instances to default to 80. The my_https monitor
instances are forced to the explicit port 443, avoiding a conflict as shown in
Figure 4.75.
Using wildcards to specify addresses
The wildcard * can be used to specify addresses. A wildcard address
association creates instances of the monitor for all nodes load balanced by
the BIG-IP:
b node * monitor use my_tcp_echo:
A wildcard with a port association creates instances of the monitor for every
node configured to service that port:
b node *:80 monitor use my_http:
To associate a monitor using the Configuration utility
1. In the navigation pane, click Monitors.
The Network Monitors screen opens.
2. Click one of three tabs:
• If you are associating the monitor with a node (the IP address
plus the port) click the Node Associations tab.
• If you are associating the monitor with a node address only (the
IP address minus the port), click the Node Address Associations
tab.
• If you are associating the monitor with a port only (the port minus
the IP address), click the Port Associations tab.
3. Regardless of the selection you made in step 2, a dialog box appears
with the boxes Choose Monitor and Monitor Rule. Type the
monitor name or select one from the list.
MONITOR my_http and https_443
|
+- NODE 11.12.11.20:80 UP
| |
| +- my_http
| | 11.12.11.20:80 up enabled
| |
| +- https_443
11.12.11.20:443 up enabled
Figure 4.75 Use of a monitor rule
Comentarios a estos manuales