Forum Discussion

Angel_Martinez_'s avatar
Angel_Martinez_
Icon for Nimbostratus rankNimbostratus
Apr 26, 2010

Is possible to have a MQSeries Monitor ¿?

Hi

 

 

I have been reading here and also at AskF5 but I haven't found a real solution for MQSeries monitoring.

 

 

We've several Virtual Server for MQSeries and all of them are working properly with a FastL4 Profile, but the deliver is some times wrong because I only have a easy L4 TCP Monitor for the pool and the queue is stoped or just not working and of course the syn, syn-ack, ack secuence is ok.

 

 

So, is there anyone working with MQSeries + a L7 Monitor ?

 

 

Do you have any clue how to monitor from BigIP to the MQSeries Pool ?

 

 

Thank you!

 

 

BIGIP: 6800

 

LTM: (9.4.3 HF4 and 9.4.8 HF2)

 

config
design
  • Angel_Martinez_'s avatar
    Angel_Martinez_
    Icon for Nimbostratus rankNimbostratus
    Apr 27, 2010
    Yes I managed!

     

     

     

    1. Add in the MQServer .ssh/authorized_keys2 the BigIP id_rsa.pub

     

    2. cut & pastel:

     

     

    [root@bigroitb:Active] .ssh cat /usr/bin/monitors/mqping.sh

     

    !/bin/bash

     

    MQPING=/usr/bin/dspmq

     

    MQUSER=root

     

    NODE_IP=$1

     

    NODE_PORT=$2

     

    IP=`echo $NODE_IP | sed 's/::ffff://'`

     

     

    STATUS=`ssh -l $MQUSER $IP $MQPING | awk '{ print $2 }'`

     

     

    case "$STATUS" in

     

    *Running*)

     

    echo "Up"

     

    ;;

     

    *)

     

    esac

     

     

    3. Set up your monitor:

     

     

    [root@bigroitb:Active] .ssh b monitor MQPING list

     

    monitor MQPING {

     

    defaults from external

     

    run "mqping.sh"

     

    }

     

     

    4. Set up your pool:

     

    - a TCP monitor for checking the Listener

     

    - b MQPING monitor for checking that the queue is "Running"

     

     

    [root@bigroitb:Active] .ssh b pool pool_mq list

     

    pool pool_mq {

     

    monitor all MQPING and tcp

     

    members 10.64.112.109:1414

     

    }

     

     

     

    Remember, at first time ssh needs to accept the key exchange: "The authenticity of host '10.64.112.109 (10.64.112.109)' can't be established.

     

    RSA key fingerprint is c6:d3:e4:45:9d:fe:cb:34:0c:e7:3a:6a:53:b2:26:af.

     

    Are you sure you want to continue connecting (yes/no)?"

     

     

  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Apr 27, 2010
    Great work!

     

     

    If you are more interested in usability than security, you could use a flag on ssh to ignore a change in the remote host key:

     

     

    ssh -o 'StrictHostKeyChecking no' 1.1.1.1

     

     

    This would make a great Codeshare example:

     

     

    http://devcentral.f5.com/wiki/default.aspx/AdvDesignConfig/codeshare

     

     

    Aaron