SSO and iRules

If Kevin's answer doesn't solve it, then you can enable monitor logging and watch the log for the RECV string (see SOL12531 for info on troubleshooting monitors).

• Open the pool that is having the problem (let's call it MY_POOL)
• Make sure the monitor is active on the pool (let's call it MY_MONITOR)
• On the

  Members

  tab in the pool settings, click on one of the members (let's call it 10.0.0.1:3389)
• Enable the checkbox for

  Monitor Logging

• Open an SSH session (I use Putty to connect) to the device and log in to the shell.
  • Run the command

    cd /var/log/monitors

  • Run the command

    ls -l

  • Look for the file referencing your pool and member (most likely in our example it'd be something like

    _Common_MY_MONITOR__Common_10.0.0.1_3389.log

    )
  • Run the command

    tail -f FILENAME

    (where FILENAME is the log filename)
  • It may be visible immediately, but you should see where the monitor sends the request to the server (and you'll see the

    send

    string), and you're looking for the

    recv

    string that comes back.
  • Take that

    recv

    string and update the monitor and see if the pool member(s) show up green again.
• Go back in and disable the monitor logging for that member so you don't have excessive logging filling up space.

This should help figure it out. If your log file ever looks like it's not updating, delete the file and remove the monitor from the pool and re-add it. I've found that will kick it back on again.