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 » IBM MQ Installation/Configuration Support » Channel outgoing (IP) address on Solaris

Post new topic  Reply to topic Goto page 1, 2  Next
 Channel outgoing (IP) address on Solaris « View previous topic :: View next topic » 
Author Message
hmh
PostPosted: Mon Apr 03, 2006 3:12 am    Post subject: Channel outgoing (IP) address on Solaris Reply with quote

Apprentice

Joined: 31 Mar 2006
Posts: 29
Location: Germany

Hello,

this is my first posting in this forum.
My question is.
It is possible to configure a SDR-Channel to another QMGR on a specified IP-Address?
My problem is, that I have to use another IP than the default of the Solaris-System, because I have to use a logical IP while this is only allowed by the firewall.

Kind regards
Michael
_________________
Michael Hoppe
63067 Offenbach

+49 (0)170 / 9629 131
http://www.hmhcs.de
Back to top
View user's profile Send private message Visit poster's website
Vitor
PostPosted: Mon Apr 03, 2006 3:20 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Are you talking about a normal sender channel? You can specify any address you like in that for the target of the channel and it's resolved & routed by the magic of IP.

Please also post what version of MQ you're using. Please also correct me f I've misunderstood your question.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Apr 03, 2006 3:57 am    Post subject: Reply with quote

Grand High Poobah

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

I would not use the IP address just because of the problem you are describing.

You should be able to use a DNS name. The address resolution then happens in the network layer.

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
happyj
PostPosted: Mon Apr 03, 2006 4:06 am    Post subject: Reply with quote

Voyager

Joined: 07 Feb 2005
Posts: 87

Have a look at the LOCLADDR channel parameter in the intercommunications manual
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Apr 03, 2006 4:12 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

happyj wrote:
Have a look at the LOCLADDR channel parameter in the intercommunications manual


Providing hmh isn't using 5.3. That parameter is new in 6.0 (hence my question about version).
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
hmh
PostPosted: Mon Apr 03, 2006 4:16 am    Post subject: Reply with quote

Apprentice

Joined: 31 Mar 2006
Posts: 29
Location: Germany

Vitor wrote:
Are you talking about a normal sender channel? You can specify any address you like in that for the target of the channel and it's resolved & routed by the magic of IP.

Please also post what version of MQ you're using. Please also correct me f I've misunderstood your question.


Hi,

sorry, but my question might be a little wrong.

I have a sender channel and I reached the destination QMGR with the IP/DNS defined in CONAME of the SDR-Channel.
My problem is, that the firewall blocked my packets, because these are send via the first interface of the SUN, but allowed is only the logical IP of the second interface.
The connection works, if the IP of the primary interface is open on the FW, but I want that MQ will use the locigal IP as senderaddress so the FW will block the primary interface.

My Version is MQ 5.3.11.

Kind regards
Michael
_________________
Michael Hoppe
63067 Offenbach

+49 (0)170 / 9629 131
http://www.hmhcs.de
Back to top
View user's profile Send private message Visit poster's website
jefflowrey
PostPosted: Mon Apr 03, 2006 4:31 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Vitor wrote:
happyj wrote:
Have a look at the LOCLADDR channel parameter in the intercommunications manual


Providing hmh isn't using 5.3. That parameter is new in 6.0 (hence my question about version).


Ummm.

It's valid in v5.3.. http://publibfp.boulder.ibm.com/epubs/html/csqzaj09/csqzaj0910.htm#HDRDEFCH

Quote:
LOCLADDR(string)
Local communications address for the channel. Use this parameter if you want a channel to use a particular IP address, port, or port range for outbound communications. This might be useful in recovery scenarios where a channel is restarted on a different TCP/IP stack.

This parameter is valid only for channels with a transport type (TRPTYPE) of TCP. If TRPTYPE is not TCP, the data is ignored and no error message is issued. The value is the optional IP address and optional port or port range used for outbound TCP/IP communications. The format for this information is as follows:


LOCLADDR([ip-addr][(low-port[,high-port])])


where ip-addr is specified in dotted decimal or alphanumeric form, and low-port and high-port are port numbers enclosed in parentheses. All are optional.

Table 2 shows how the LOCLADDR parameter can be used:

Table 2. Examples of how the LOCLADDR parameter can be used
LOCLADDR Meaning
9.20.4.98 Channel binds to this address locally
9.20.4.98(1000) Channel binds to this address and port 1000 locally
9.20.4.98(1000,2000) Channel binds to this address and uses a port in the range 1000 to 2000 locally
(1000) Channel binds to port 1000 locally
(1000,2000) Channel binds to port in range 1000 to 2000 locally

This parameter is valid only for channels with a channel type (CHLTYPE) of SDR, SVR, RQSTR, CLNTCONN, CLUSSDR, or CLUSRCVR.

Note:
Even though this parameter is similar in form to CONNAME, it should not be confused with it. The LOCLADDR parameter specifies the characteristics of the local communications, whereas the CONNAME parameter specifies how to reach a remote queue manager.


_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Apr 03, 2006 4:36 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

It's a double dose of sackcloth and ashes for me tonight.

I'll also cancel the purging and beating with hazel twigs; I just don't deserve it....

Apologies for spreading confusion and misinformation on the forum.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Apr 03, 2006 4:39 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Vitor wrote:
It's a double dose of sackcloth and ashes for me tonight.

I'm sure, however, you still know the difference between the MQMD and the transmission header...

_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Apr 03, 2006 4:39 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

hmh wrote:

Hi,

sorry, but my question might be a little wrong.

I have a sender channel and I reached the destination QMGR with the IP/DNS defined in CONAME of the SDR-Channel.
My problem is, that the firewall blocked my packets, because these are send via the first interface of the SUN, but allowed is only the logical IP of the second interface.
The connection works, if the IP of the primary interface is open on the FW, but I want that MQ will use the locigal IP as senderaddress so the FW will block the primary interface.

My Version is MQ 5.3.11.

Kind regards
Michael


Ignore me, listen to everyone else and look up LOCLADDR as recommended.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Apr 03, 2006 4:43 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

jefflowrey wrote:
Vitor wrote:
It's a double dose of sackcloth and ashes for me tonight.

I'm sure, however, you still know the difference between the MQMD and the transmission header...


At this moment, I'm not counting on it. I dread to think what my coffee was spiked with this morning (though I have a list of suspects in mind) but there's some really dodgy information coming out of my head and poluting this forum.

Of course, there's the alarming posibility my coffee wasn't spiked....

Transmission header - that's got the mcd information in it, right?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
hmh
PostPosted: Mon Apr 03, 2006 5:38 am    Post subject: Reply with quote

Apprentice

Joined: 31 Mar 2006
Posts: 29
Location: Germany

happyj wrote:
Have a look at the LOCLADDR channel parameter in the intercommunications manual


Thanks a lot.

This was ist.

alter channel(CHANNELNAME) CHLTYPE(SDR) +
LOCLADDR('logical address')

Michael
_________________
Michael Hoppe
63067 Offenbach

+49 (0)170 / 9629 131
http://www.hmhcs.de
Back to top
View user's profile Send private message Visit poster's website
xxx
PostPosted: Mon Apr 03, 2006 7:30 am    Post subject: Reply with quote

Centurion

Joined: 13 Oct 2003
Posts: 137

9.20.4.98(1000,2000) Channel binds to this address and uses a port in the range 1000 to 2000 locally

based on the same topic, can some explain how the above works ?

i.e on what port can listner be started based on the above numbers ?
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Apr 03, 2006 7:37 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Localaddr has nothing to do with listeners. Listener ports are used to bind reciever channels - and the documentation clearly says that LOCALADDR is not valid for RCVRs. It's only valid for CLUSRCVrs because CLUSRCVrs are used as models for CLUSSDRs .
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
xxx
PostPosted: Mon Apr 03, 2006 7:49 am    Post subject: Reply with quote

Centurion

Joined: 13 Oct 2003
Posts: 137

Jeff thanks for the reply,

I was confused with the conname and locaaddress, the doucmentation says excatly not to be ! the more I look the more I get confused,

9.20.4.98(1000) Channel binds to this address and port 1000 locally
9.20.4.98(1000,2000) Channel binds to this address and uses a port in the range 1000 to 2000 locally


So for a simple Sender , recevier channles , why there is a range ?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Channel outgoing (IP) address on Solaris
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.