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 » Clustering » LOCLADDR parameter

Post new topic  Reply to topic
 LOCLADDR parameter « View previous topic :: View next topic » 
Author Message
sanvij
PostPosted: Mon Apr 05, 2004 5:37 pm    Post subject: LOCLADDR parameter Reply with quote

Novice

Joined: 21 Mar 2003
Posts: 24

Mqver is 5.3 with CSD05

Let me first explain the scenario:
1) We have 2 Sun solaris servers both having repos qmgr
2) We want to migrate the qmgr`s to a Sun cluster (HA).
3) We successfully migrated the 1 repos qmgr to a HA m/c and the MQ Cluster is fully functional
4) Let us consired the IP addresses as: Primary IP is 1, Seconday IP is 2, and Logical IP is 3

Objective:
1) We want the clussndr to have the IP of the logical m/c (in our case IP should be 3) as the local communication address for the channel .

Problem:
Although we defined the LOCLADDR parameter(a new feature in MQ5.3) to have IP 3 we dont see the parameter taking into effect .(The clussndr still treates the local IP (IP 1) as the communication IP. this was found by doing netstat -an)

IBM`s suggestion:
Opened a call with IBM they suggest to drop the clussndr channel and recreate it. But the IBM doc does not suggest so and please see the below NOTE

NOTE: The LOCLADDR parameter works perfectly fine when used on a sender channel from the same qmgr communicating to the qmgr outside the cluster

Now my questions:
1) Any one has faced similar problems?
2) Even after the restart of the qmgr the parameter did not take effect. When the qmgr can recognize on a sender channel why does not recoginze it on a clussndr channel? Is it do the cache on the cluster repos?
_________________
Sanvij
IBM Certified MQSeries Specialist
IBM Certified WebSphere MQ Solution Designer
Back to top
View user's profile Send private message
JasonE
PostPosted: Tue Apr 06, 2004 4:12 am    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

http://www-1.ibm.com/support/docview.wss?rs=0&q1=IY49334&uid=swg1IY49334&loc=en_GB&cs=utf-8&lang=

Or similar text documented internally

Quote:
The channel attribute LOCLADDR has been introduced at v5.3 in order to enable an outbound (TCP) channel to use a particular IP Address, port or port range. This is useful if the customer has more than one network card and wants a channel to use a specific one for outbound communications.
Customers need to be aware that if they add a value to the LOCLADDR field of a manually defined CLUSSDR channel, that this value will be over-written with the values in the repositories CLUSRCVR channel once communication has been established with the repository queue manager.

If a cluster wants to use LOCLADDR to get their outbound communication channels to bind to a specific IP Address, they will need to write a Channel Auto-Definition Exit in order to force the LOCLADDR value into any of their automatically defined CLUSSDR channels, as well as specifying it in the manually defined CLUSSDR channel.

It should be noted that putting an IP Address in the LOCLADDR field of a CLUSRCVR channel is not a valid thing to do unless all the queue managers reside on the same machine. This is because ANY queue manager that attempts to connect to a queue manager with an IP Address in the LOCLADDR field of its CLUSRCVR will have these values propagated to their auto-defined CLUSSDR channels.

It would however be valid to put a port number or port range in the LOCLADDR of a CLUSRCVR channel, if you wanted all the queue managers in a cluster to use a specific port or range of ports for all their outbound communications.


I make no guarantees to its accuracy though
Back to top
View user's profile Send private message
sanvij
PostPosted: Tue Apr 06, 2004 2:40 pm    Post subject: Reply with quote

Novice

Joined: 21 Mar 2003
Posts: 24

Jason,
Thanks for the reply.

So even recreating the CLUSSDR channel will not help and the only work around is using a Channel Auto-Definition Exit.

The link you provided mentions about a sample exit :568.prbnb. Is it available for reference?
_________________
Sanvij
IBM Certified MQSeries Specialist
IBM Certified WebSphere MQ Solution Designer
Back to top
View user's profile Send private message
JasonE
PostPosted: Mon Apr 26, 2004 4:03 am    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

Sorry for the delayed response... Been out for 3 weeks on holiday

Sorry - the prb link is the database holding these articles, so is internal only. Drop me a pm with your email addr and I'll send you the bits you are after.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » LOCLADDR parameter
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.