| Author |
Message
|
| hilltops |
 Posted: Mon Apr 10, 2006 5:29 am Post subject: Conname parameter for clustered channels |
 |
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
I defined a clustered sender channel specifying an IP address for the conname attribute on Linux. This channel passes thru a firewall to the repos queue managers on zSeries.
When I issue a DISPLAY CHANNEL(TO.REPOS.QM) command the channel attributes are display with the correct IP I specified for the conname. However, when I issue a DISPLAY CHS(TO.REPOS.QM) command, the conname attribute now has the hostname instead of the IP.
I am unable to start this channel and I reckon this is the problem. Is this correct and what's happening here? |
|
| Back to top |
|
 |
| wschutz |
| Posted: Mon Apr 10, 2006 6:05 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
and when you do an "host" of the name that shows on the dis chs, do you get a different IP address than what you specified in the define?
_________________
-wayne |
|
| Back to top |
|
|
| hilltops |
| Posted: Mon Apr 10, 2006 6:20 am Post subject: |
|
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
| From the Linux box I can ping or telnet the zSeries box using the IP but not hostname. |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Apr 10, 2006 6:57 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Of course, you don't normally start a cluster channel, they start as needed by the qmgr itself. Why are you trying to manually start it? And when you do, are there any errors in AMQERR01.LOG ?
You didn't really answer my question about using the "host" command.
_________________
-wayne |
|
| Back to top |
|
|
| hilltops |
| Posted: Mon Apr 10, 2006 7:12 am Post subject: |
|
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
I issued the command "host MVSC.SYSTEMS.UK.COMP" but the command timeout
The entry in the error log is as follows:
10/04/06 13:36:25
AMQ9203: A configuration error for TCP/IP occurred.
EXPLANATION:
Error in configuration for communications to host 'MVSC.SYSTEMS.UK.COMP.
Allocation of a TCP/IP conversation to host 'MVSC.SYSTEMS.UK.COMP' was not
possible.
ACTION:
The configuration error may be one of the following:
1.If the communications protocol is LU 6.2, it may be that one of the
transmission parameters (Mode, or TP Name) is incorrect. Correct the error
and try again. The mode name should be the same as the mode defined on host
'MVSC.SYSTEMS.UK.COMP'. The TP name on 'MVSC.SYSTEMS.UK.COMP' should be
defined.
2.If the communications protocol is LU 6.2, it may be that an LU 6.2 session
has not been established. Contact your systems administrator.
3.If the communications protocol is TCP/IP, it may be that the host name
specified is incorrect. Correct the error and try again.
4.If the communications protocol is TCP/IP, it may be that the host name
specified cannot be resolved to a network address. The host name may not be
in the nameserver.
"AMQERR01.LOG" 2321L, 90136C |
|
| Back to top |
|
|
| hilltops |
| Posted: Mon Apr 10, 2006 7:38 am Post subject: |
|
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
The following may be significant. The QM on the Linux box joined the cluster before 'somewhat' using a sender channel defined with the hostname MVSC.SYSTEM.UK.COMP. I say somewhat because I am not sure if this QM's connectivity with the repos QMs were fully functional.
The QM was removed from the cluster, the channels deleted and recreated using the IP address instead. Is it possible that the repos QM has retained knowledge of itself with respect to the new QM as the hostname instead of the IP address and passes this on to the new QM when it rejoins? |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Apr 10, 2006 10:21 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Well, it does sound like the IP address is getting cached in some repository. I did a quick test on V6 and can't reproduce your problem. What version of MQ and CSD level?
_________________
-wayne |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Apr 10, 2006 11:53 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| hilltops wrote: |
The following may be significant. The QM on the Linux box joined the cluster before 'somewhat' using a sender channel defined with the hostname MVSC.SYSTEM.UK.COMP. I say somewhat because I am not sure if this QM's connectivity with the repos QMs were fully functional.
The QM was removed from the cluster, the channels deleted and recreated using the IP address instead. Is it possible that the repos QM has retained knowledge of itself with respect to the new QM as the hostname instead of the IP address and passes this on to the new QM when it rejoins? |
To know what is really being used you need to check the channel status.
Yes stuff gets cached in the repository and it may take some time to replace... especially if channels are running on the old definition.
If you can and it is possible (depends on your environment) make the FR a partial refresh repos(yes), make it a full again. You should probably start with the FR that has no direct connection to the qmgr you changed the channel on. This way the new def gets propagated from the connected FR to the unconnected FR a little bit faster.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| hilltops |
| Posted: Tue Apr 11, 2006 12:30 am Post subject: |
|
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
| I am using version 5.3 CSD10. |
|
| Back to top |
|
|
| GMcCarthy |
| Posted: Thu Apr 13, 2006 7:05 am Post subject: |
|
|
Centurion
Joined: 06 Nov 2001
Posts: 113
Location: Melville NY
|
With cluster channels, the CONNAME on the CLUSRCVR is used. Make sure your CONNAME on the CLUSSDR and CLUSRCVR are the same.
The CONNAME specified on a cluster-receiver channel definition is used throughout the cluster to identify the network address of the queue manager. Take care to select a value for the CONNAME parameter that resolves throughout your WebSphere MQ cluster. Do not use a generic name. Remember that the value specified on the cluster-receiver channel takes precedence over any value specified in a corresponding cluster-sender channel.
_________________
Regards,
Gina
IBM Certified MQSeries Specialist |
|
| Back to top |
|
|
|
|
