For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

giltjr's avatar
giltjr
Icon for Nimbostratus rankNimbostratus
Jun 20, 2012

Log which monitor failed for which pool.

O.K. I have issued the command 'b db bigd.lognodestatuschange enable' and it did not do what I need. After reading more about that command it will tell you which monitor failed if you have multiple monitors for the same pool. Not what we have.

 

 

What I have is:

 

 

POOL1: NODE1:9080 NODE2:9080 -- HTTP MONITOR1

 

 

POOL2: NODE1:9080 NODE2:9080 -- HTTP MONITOR2

 

 

Although they are on the same server and use the same port, POOL1 is used when user goes into application 1 and POOL2 is used when they go into application 2.

 

 

I can see in the log "Pool member NODE1:9080 monitor status down" and then a few seconds later "up". But I don't know which monitor failed.

 

 

Is there away, without writing a custom script, to get the F5 to log which monitor or pool failed. I looked and I can't seem to find anyway to do this.

 

1 Reply

  • giltjr's avatar
    giltjr
    Icon for Nimbostratus rankNimbostratus
    O.K. My misunderstanding.

     

     

    For some reason I was expecting the monitor name on the standard "Pool member addr:port monitor status down|up". I see now that there is a separate message that show which monitor failed.