| Author |
Message
|
| ourtown |
 Posted: Sat Sep 14, 2013 2:13 am Post subject: F5 BigIP and clustered Multi-Instance Queue Managers |
 |
|
Acolyte
Joined: 05 Feb 2002
Posts: 67
Location: Somerset, NJ
|
Can anyone point to some better documentation than Deploying the BIG-IP LTM with IBM WebSphere MQ - F5 from www.f5.com
We have multiple MQClients coming through the F5 and 2 Multi-Instance Queue Managers running active-passive on 2 Linux Servers
Our network guys can configure the F5 to connect to one box but they have problems in rerouting when QM1 or QM2 move to the other server
_________________
Brian S. Crabtree
WBI Consultant |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Sat Sep 14, 2013 8:02 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
This Technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21606845
Talks about this from the MQ Client perspective.
What I haven't found is doc that talks about it from an MQ Server to MQ Server perspective. But if the partner QM is at a supported version of MQ, that partner QMs' Sender Channel's CONNAME parameter can list both the primary and secondary IP address of your Multi Instance QM's servers.
What is the issue you are having? Is it for the MQ Clients trying to connect or partner QMs?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Sep 14, 2013 11:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Generally, there's no signal that flows from the MI qmgr to anyone who's listening during or after failover - MI assumes that anyone connected to the qmgr will have both IP addresses and be able to reconnect themselves based on a connection failure.
MQ Service objects are excellent choices for moving a virtual IP address around during MI failover. |
|
| Back to top |
|
|
| ourtown |
| Posted: Sun Sep 15, 2013 2:32 am Post subject: |
|
|
Acolyte
Joined: 05 Feb 2002
Posts: 67
Location: Somerset, NJ
|
Hi Peter
What I was really looking for was some success stories
Jeff's suggestion is fine as a workaround
F5 BIG-IP looks very useful for adding the missing VIP to MQMI, allowing MQClient reconnection for applications that can't reconnect and allowing access to MQ across zones or for DR or Cloud
The F5 can monitor the Listener and detect where it is but we havent successfully configured this yet
There seems to be a basic pathing error in the F5 so that the incoming F5 IP doesnt always map to the outgoing MQ connection
We keep getting 2538 errors - no path found - we can telnet but not MQClient so the F5 is mapping the port but the final connection to the MQ Server is bad
_________________
Brian S. Crabtree
WBI Consultant |
|
| Back to top |
|
|
| ourtown |
| Posted: Sun Sep 15, 2013 8:46 am Post subject: |
|
|
Acolyte
Joined: 05 Feb 2002
Posts: 67
Location: Somerset, NJ
|
Problem resolved
F5 configured - everything works now - F5 detects the MQMI failover
Now to enable SSL :)
_________________
Brian S. Crabtree
WBI Consultant |
|
| Back to top |
|
|
| niswanger |
| Posted: Tue Aug 25, 2015 8:31 am Post subject: |
|
|
Newbie
Joined: 25 Aug 2015
Posts: 1
|
@ourtown
Could you please share how you got MI to work with F5's LTM? Would be very curious about the load balancing type and the health monitor you chose to use.
Thank you,
Roy Niswanger |
|
| Back to top |
|
|
| sijtom0703 |
| Posted: Wed Aug 26, 2015 5:35 am Post subject: |
|
|
Voyager
Joined: 28 May 2011
Posts: 84
Location: USA
|
I am curious about the logic that worked for the below line. Is F5 checking the queue manager status before failover??
| Quote: |
| F5 detects the MQMI failover |
|
|
| Back to top |
|
|
|
|
