Specifications

Chapter 4: Configuring the High-Level Network
4-154
This has the effect of disabling all instances of the monitor, as shown in
Figure 4.71.
To disable a monitor instance, use the bigpipe monitor instance
<addr:port> disable command:
b monitor instance <addr:port> disable
Disabled monitors and instances may be re-enabled as follows:
b monitor <name> enable
b monitor instance <addr:port> enable
To delete a monitor with no node associations from the
command line
You can delete a monitor if it has no existing node associations and no
references in a monitor rule. To delete a monitor, use the bigpipe monitor
<name> delete command:
b monitor my_http delete
If the monitor has instances, the instances must first be deleted using the
bigpipe node <addr:port> monitor delete command. (Refer to Showing
and deleting associations, on page 4-159.)
Associating the monitor with a node or nodes
Now that your monitor exists, the final step is to associate it with the nodes
to be monitored. This creates an instance of the monitor for each node. At
the command line, association is done using bigpipe node command:
b node <addr_list> monitor use <name>
For example, to associate monitor http with nodes 11.12.11.20:80,
11.12.11.21:80, and 11.12.11.22:80, the bigpipe node command would be
as follows:
b node 11.12.11.20:80 11.12.11.21:80 11.12.11.22:80 monitor use http
+- NODE 11.12.11.20:80 UP
| |
| +- http
| 11.12.11.20:80 up disabled
|
+- NODE 11.12.11.21:80 UP
| |
| +- http
| 11.12.11.21:80 up disabled
|
+- NODE 11.12.11.22:80 UP
|
+- http
11.12.11.22:80 ip disabled
Figure 4.71 All monitor instances disabled