mark a node down in one pool only?

Can you define what you mean by a "node"? In terms of the BIG-IP the top level object is a Virtual Server. The VS has an attribute of a single default pool that it serves traffic to. A pool can contain many pool members.

 

 

A Node is most typically referred to as a backend server ip address. A Pool Member is a combination of a node's IP address and a specific port on that node.

 

 

I'm a bit confused by your statement about a node servicing two or more pools. If you mean to use Virtual Server instead of node, a Virtual Server has only one pool as an attribute. Of course you can override this with iRules, but it's not part of the core configuration.

 

 

I'm sure the answer is yes to your question as you have full control of enabling/disabling objects at all levels (ie. a single pool member within a pool). But, if you disable the one and only pool to a virtual server, there will be no where to send the traffic to.

 

 

If you could clarify your question with your specific configuration, we can let you know how to get it done and what methods to use.

 

 

-Joe

sorry for not being clear. i will explain what i think i am trying to do which may spur more questions from you. if you like i could then explain overall my issue but i tend to ramble and dont want to muddy up the post.

 

 

by node i do mean backend server. i was thinking of having one vip that is serviced by four pools (using an irule to determine which pool to use). these four pools would have four nodes in each pool. furthermore, these nodes are in all four of the pools. basically the same four nodes in all four pools. am i making sense? then with icontrol, i need to make a determination on a backend service state and drop one of these nodes from only one of the pools. i wasnt sure if icontrol could do that or would it just down the node (backend server) all together causing it to drop from all four pools. like i said this may not seem to make much sense of why i am doing that but i can explain further if it would help. (i suspect at some point i will anyways seeing that i will most likely be looking for more help as i go down this road)

 

 

thanks and i hope that clarifies my question somewhat.

In v9.x and higher you can define the same IP:port combo in several pools, and each is as a unique configuration object (Pool:IP:port) whose status can be managed independently of peer instances of the same service.

 

 

For instance, if you have a webserver hosting 2 apps on port 80, and you want to maintain their individual statuses, you would define 2 pools containing the same members. Typical scenario would involve applying a monitor to each pool that tests only the application it serves. When one monitor marks a server down in one pool, the corresponding pool member in another pool is unaffected - its status is managed by a different monitor.

 

 

iControl can manage the status of such pool members independently as well using pool member-specific functions.

 

 

hth

 

/deb

 

good deal. that answers the question. thanks.

 

now on to the irule to determine which pool to use.. it will require reading into the packet.

 

 

thanks again