| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Channel error between SunSolaris and AS400 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Pete |
 Posted: Tue Feb 01, 2005 10:06 am Post subject: Channel error between SunSolaris and AS400 |
 |
|
Apprentice
Joined: 25 Nov 2003
Posts: 43
|
Hi All,
I think this is an underlying network issue but I hope someone will respond to confirm I'm not missing something obvious...
I have a SunSolaris and AS400 server both running WQ5.1 server, with bi-directional communication over sender-receiver channel pairs (standard MQ setup) which works fine.
I need to change the IP address of the AS400 server from 3.123.123.123 to 172.123.123.123. Network changes have been made and I am able to ping both adresses from the Solaris command line.
When I change the MQ sender channel configuration from 3.123.123.123 to 172.123.123 I cannot successfully start the sender channel with error:
| Quote: |
01/02/05 02:57:25 PM
AMQ9202: Remote host '172.123.123.123 (1414)' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host '172.123.123.123
(1414)' was not successful. However the error may be a transitory one and it
may be possible to successfully allocate a TCP/IP conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
145 (X'91'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host
'172.123.123.123 (1414)' was not running. If this is the case, perform the
relevant operations to start the TCP/IP listening program, and try again. |
From speaking to the network adminstrator I understand the 3.123.123.123 is a direct connection whereas the 172.123.123.123 undergoes a network address translation to 10.xxx.xxx.xxx (not sure of the full address yet).
My question is: am I correct in thinking that MQSeries will work fine if using network address translation i.e. aslong as there is a valid TCP/IP network the channels will run, therefore is the problem more likely a network issue such as routing problem or firewall issue?
I am aware that 5.1 is no longer in support, however the client is not looking to upgrade and I don't believe this is the issue here.
Also, if anyone can point me in the direction of the TCP/IP return codes on a Solaris server that would be much appreciated.
Anyhelp appreciated,
Regards,
Pete |
|
| Back to top |
|
 |
| bbburson |
| Posted: Tue Feb 01, 2005 12:31 pm Post subject: Re: Channel error between SunSolaris and AS400 |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
| Pete wrote: |
| Also, if anyone can point me in the direction of the TCP/IP return codes on a Solaris server that would be much appreciated. |
From /usr/include/sys/errno.h on a Solaris machine:
| Code: |
| #define ETIMEDOUT 145 /* Connection timed out */ |
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Feb 01, 2005 12:35 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
And a timed out error likely indicates either an incorrect NAT mapping or an intentional port blocking for port 1414 (or failure to intentionally unblock) in the NAT rules.
At least in the situation you describe.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Feb 01, 2005 3:08 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If you want a better feel if it will work, do a command line telnet, rather than a command line ping. Lots of times the network guys / firewall guys will not allow pings, but will allow telnet, or vice versa. An MQ channel looks more like a telnet session than a ping. If the telnet fails, you know its not an MQ problem.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Feb 01, 2005 5:28 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
And you can always telnet to the MQ Listening port. It thows an error to the log, but it shows that the connection has been made to the correct box and the correct port. Especially if the firewall guys don't like you to use telnet and block that as well.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Pete |
| Posted: Wed Feb 02, 2005 6:57 am Post subject: |
|
|
Apprentice
Joined: 25 Nov 2003
Posts: 43
|
All,
Thanks very much for your replies. I'm now waiting for the network teams to make there changes....
Thanks again,
Pete |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
