ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Problems with RDQM setup MQ 9.2.0.0 on CentOS and RHEL 7.8

Post new topic  Reply to topic Goto page Previous  1, 2
 Problems with RDQM setup MQ 9.2.0.0 on CentOS and RHEL 7.8 « View previous topic :: View next topic » 
Author Message
fjb_saper
PostPosted: Tue Sep 01, 2020 10:39 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

@exerk
Why 3 replication sets (9 IPS) instead of one set (3 IPS) with rotating primary secondary and replication ??
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
exerk
PostPosted: Tue Sep 01, 2020 11:10 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

This was a Proof-of-Concept I set up over two years ago so I followed the KC faithfully:

Quote:
The rdqm.ini file gives the IP addresses for all of the nodes in the Pacemaker cluster. You can specify that the Pacemaker cluster uses one, two, or three IP addresses. The interface that is used for synchronous data replication is named the 'replication interface'. The interface must have sufficient bandwidth to support replication requirements given the expected workload of all the RDQMs running in the HA Group. The primary and secondary interfaces are used for the Pacemaker to monitor the system, but Pacemaker can use the replication interface for this purpose, if required.


I'm not sure what you mean by "...rotating primary secondary and replication...", sorry.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Sep 02, 2020 4:57 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

exerk wrote:

I'm not sure what you mean by "...rotating primary secondary and replication...", sorry.


Meaning that you have 3 IPS as primary, secondary and replication
Meaning that you define 3 qmgrs QM1 QM2 QM3
and preffered node is
QM1 primary
QM2 secondary
QM3 replication


_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
crashdog
PostPosted: Wed Sep 02, 2020 5:04 am    Post subject: Reply with quote

Voyager

Joined: 02 Apr 2017
Posts: 77

That's not really how it works... You have 3 nodes (VMs). Basically you only need two network cards per node, one for the floating ip and one for the replication.
The primary and alternate nics are only for the heartbeat.
The number of queue managers per node is not limited. (it used to be limited to 10 and IBM's RDQM performance tests use up to 10 qmgrs).

Cheers,
Gerhard
_________________
You win again gravity !
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Sep 02, 2020 5:42 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

crashdog wrote:
That's not really how it works... You have 3 nodes (VMs). Basically you only need two network cards per node, one for the floating ip and one for the replication.
The primary and alternate nics are only for the heartbeat.
The number of queue managers per node is not limited. (it used to be limited to 10 and IBM's RDQM performance tests use up to 10 qmgrs).

Cheers,
Gerhard

Thanks for enlightening me. I naively thought that one network card could handle both the node's ip and the floating ip...
I understand the use of an alternate card for the heartbeat.

So if I understand this right Exerk is using 3 network cards
1 for the primary traffic
1 for the heartbeat traffic
1 for the replication traffic.

Please correct me if I misunderstood this set up


_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
crashdog
PostPosted: Wed Sep 02, 2020 5:56 am    Post subject: Reply with quote

Voyager

Joined: 02 Apr 2017
Posts: 77

you got it
_________________
You win again gravity !
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Sep 02, 2020 12:06 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

crashdog wrote:
you got it

I was just a little bit surprised because usually each of those cards would be in a different subnet...
1 subnet for primary traffic
1 subnet for heartbeat
1 subnet for replications

And Exerk had them all on the same subnet... not that there's anything wrong with that...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
exerk
PostPosted: Thu Sep 03, 2020 10:04 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

fjb_saper wrote:
...And Exerk had them all on the same subnet... not that there's anything wrong with that...

It was a test installation Proof-of-Concept in a VMWare environment - not worth the hassle of creating a 'full' network infrastructure just to test out the mechanics of RDQM
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
jinyuximu
PostPosted: Tue Jun 22, 2021 4:06 am    Post subject: Reply with quote

Guest




The problem I encountered is the same as yours. I know how to do it now.
My environment is: Centos8.3 and MQ 9.2.2CD. The firewall is turned off.
I vi /etc/selinux/config and SELINUX=disabled. Then reboot 3 machines. Execute crtmqm -sx RDQM_HA1. rdqmstatus -m RDQM_HA1 is fine.



crashdog wrote:
Quote:
It works, trust me...

Not that I would ever doubt your trustworthiness but, nope same issue with REHL 7.8 and MQ 9.2.0.0 as CentOS 7.8 and MQ 9.2.0.0.

Just wondering what I could possibly be doing wrong... I've checked just about everything from drbd over corosync to pacemaker. I went over the MQ installation guide time and time again...

I guess I will try the RHEL / MQ9.2.0.0 installation on my employers system, if the issue occurs there too I guess I will just have to open a PMR.

EDIT: Is it possible to open PMRs or have any official IBM support as a "private" person ? means I don't have an MQ license. Just using the developer editions for educational purposes.

Cheers,
Gerhard
Back to top
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » Problems with RDQM setup MQ 9.2.0.0 on CentOS and RHEL 7.8
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.