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 IndexGeneral IBM MQ SupportLOCLADDR needs to contain three ip addresses

Post new topicReply to topic
LOCLADDR needs to contain three ip addresses View previous topic :: View next topic
Author Message
NickSz
PostPosted: Wed Dec 06, 2017 7:06 am Post subject: LOCLADDR needs to contain three ip addresses Reply with quote

Novice

Joined: 26 Jul 2008
Posts: 11

Hello all,
we have eight mq appliances version 8.0.7. We are using link aggregation and vlans. We must use only one network segment per queue manager. We are using HA and this works well.
Due to firewall requirements we need to respond always on specific network zone interfaces. So we are using static routes.
In some cases we need one interface for out-bound and one for in-bound communication.
To ease this we define the standard via the environment variable MQ_LCLADDR to the out-bound address.
In some cases, where the channels are going towards inside (in-bound), we explicitly set the attribute LOCLADDR on those channels.
This works so far fine.

But if we extend this configuration and add a disaster-recovery appliance or QM to it, we need to add a third interface per LOCLADDR or MQ_LCLADDR to be able to send out from that third machine.
The documentation is not clear here and expects only two ip addresses or names but we would need three. The string length is limited to 48 characters so three ip addresses would fit (47 characters).

LOCLADDR is described here:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.con.doc/q081910_.htm

Did anybody else have been using LOCLADDR for more than two addresses in a similar config?
I am not sure if this will work as expected!

Cheers
Nicolaie
Back to top
View user's profile Send private message
zpat
PostPosted: Wed Dec 06, 2017 7:38 am Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5579
Location: UK

Quote:
Specify [,[ip-addr][(low-port[,high-port])]] multiple times for each additional local address.


Quote:
The maximum length of LOCLADDR, including multiple addresses, is MQ_LOCAL_ADDRESS_LENGTH.


Seems fairly clear to me.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
NickSz
PostPosted: Wed Dec 06, 2017 8:20 am Post subject: Reply with quote

Novice

Joined: 26 Jul 2008
Posts: 11

Thanks zpat,
but a IBM representative said that the string bellow means two ip-addresses only:
Quote:
LOCLADDR([ip-addr][(low-port[,high-port])][,[ip-addr][(low-port[,high-port])]])


And this is actually limited to 48:
Quote:
The maximum length of LOCLADDR, including multiple addresses, is MQ_LOCAL_ADDRESS_LENGTH.

Can i extend it to a bigger numeric value?
When i set it to a string it was cut off after 48 characters.
Back to top
View user's profile Send private message
exerk
PostPosted: Wed Dec 06, 2017 8:47 am Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 5756

Quote:
The maximum length of LOCLADDR, including multiple addresses, is MQ_LOCAL_ADDRESS_LENGTH.


NickSz wrote:

Can i extend it to a bigger numeric value?

No...
NickSz wrote:
When i set it to a string it was cut off after 48 characters.

...so why ask if you can extend it?
_________________
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
NickSz
PostPosted: Wed Dec 06, 2017 8:53 am Post subject: Reply with quote

Novice

Joined: 26 Jul 2008
Posts: 11

May be i am not inteligent enough to understand it?
I thought this is a forum to place queastions to?
Back to top
View user's profile Send private message
exerk
PostPosted: Wed Dec 06, 2017 9:17 am Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 5756

NickSz wrote:
I thought this is a forum to place queastions to?

It is, but you answered your own question!
_________________
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 Dec 06, 2017 9:30 am Post subject: Reply with quote

Grand Poobah

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

I think what exerk is expressing a little bit forcefully here is that IBM has not made any provision to extend that field in its length, or otherwise....
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
PeterPotkay
PostPosted: Wed Dec 06, 2017 7:43 pm Post subject: Re: LOCLADDR needs to contain three ip addresses Reply with quote

Jedi Council

Joined: 15 May 2001
Posts: 7381

NickSz wrote:
The string length is limited to 48 characters so three ip addresses would fit (47 characters).

What happens when you set it to the 3 IPs and only use up 47 characters?
On your test box, make the first IP listed a bogus one, then the 2 real ones for the 2nd and 3rd. Then test failover between the H.A. nodes, to see if the 2nd and 3rd IPs are used.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
zpat
PostPosted: Wed Dec 06, 2017 11:52 pm Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5579
Location: UK

NickSz wrote:
Thanks zpat,
but a IBM representative said that the string means two ip-addresses only


My quote was from the knowledge center. However the easiest way to prove it is to try it.

When you say "IBM rep", are you referring to L2 or L3 support?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
NickSz
PostPosted: Thu Dec 07, 2017 1:10 am Post subject: Reply with quote

Novice

Joined: 26 Jul 2008
Posts: 11

architect
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Dec 07, 2017 6:01 am Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 24648
Location: Ohio, USA

NickSz wrote:
architect


That conveys nothing.

There are a number of architects; was this one an actual IBM Hursley employee, involved in the architecting of this product? If so, was he speaking on the record and did he say how he knew so much about the implementation of the architecture after it left his area and moved into development?

Or was it a contractor who's "an IBM guy"?

There have been good suggestions on this thread. Give them a try.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
NickSz
PostPosted: Wed Dec 13, 2017 6:08 am Post subject: SOLVED Reply with quote

Novice

Joined: 26 Jul 2008
Posts: 11

Hello all,

i could finally test the szenario and prove that all thre ip-addresses are visited when i put up a queue manager and listener on a DR qm on top of a HA pair.

Thanks to all
Nicolaie
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexGeneral IBM MQ SupportLOCLADDR needs to contain three ip addresses
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.