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 » CLUSSDR in retrying status

Post new topic  Reply to topic
 CLUSSDR in retrying status « View previous topic :: View next topic » 
Author Message
KIT_INC
PostPosted: Fri Dec 06, 2013 8:43 am    Post subject: CLUSSDR in retrying status Reply with quote

Knight

Joined: 25 Aug 2006
Posts: 589

Runing MQ 7019 under Linux
I added a Qmgr (QMESB2) to a cluster (CORP) with the full repository QMGR named QMRPU03.

I followed the steps in the manual
DEFINE CHANNEL ('TO.QMESB2') CHLTYPE(CLUSRCVR) CLUSTER('CORP') CONNAME('hostname(22392),hostname(22392)')...SSLCIPH('TRIPLE_DES_SHA_US')

DEFINE CHANNEL ('TO.QMRPU03') CHLTYPE(CLUSSDR) CLUSTER('CORP') CONNAME('rposhost1(22388)'...SSLCIPH('TRIPLE_DES_SHA_US')

I noticed the CLUSSDR channel in RETRYING status

AMQ8417: Display Channel Status details.
CHANNEL(TO.QMRPU03) CHLTYPE(CLUSSDR)
BATCHES(0) BATCHSZ(50)
:
RQMNAME( ) SHORTRTS(9)
SSLCERTI(CN=WMQ CA,OU=WMQ,O=ABC,L=Toronto,ST=ON,C=CA)
SSLKEYDA( ) SSLKEYTI( )
SSLPEER(CN=QMRPU01,OU=WMQ,O=ABC,L=Toronto,ST=ON,C=CA)
SSLRKEYS(0) STATUS(RETRYING)

I noticed the problem WAS caused by SSLPEER(CN=QMRPU01.. which should be CN=QMRPU03.... and the reason was in my CLUSSDR defintion which points to rposhost1(22388) which is a different repository Qm QMRPU01 and with the certificates containing CN=QMRPU01.

I made a mistake of not following the procedure to delete and redefine the TO.QMRPU03 cluster sender channel.
I jsut did an alter channel to change the connection name to CONNAME('rposhost3(22388)') and start the clsuter sender.

But when I display channel status, I saw the same results as before (i.e. channel in retry staus and SSLPEER still wrong.
AMQ8417: Display Channel Status details.
CHANNEL(TO.QMRPU03) CHLTYPE(CLUSSDR)
BATCHES(0) BATCHSZ(50)
:
RQMNAME( ) SHORTRTS(9)
SSLCERTI(CN=WMQ CA,OU=WMQ,O=ABC,L=Toronto,ST=ON,C=CA)
SSLKEYDA( ) SSLKEYTI( )
SSLPEER(CN=QMRPU01,OU=WMQ,O=ABC,L=Toronto,ST=ON,C=CA)
SSLRKEYS(0) STATUS(RETRYING)

I have double checked the keystore of the repository QM QMRPU03 and the certificates in there are all with CN=QMRPU03.

In order to fix the issue, I tried the follwing 2 actions with no luck.
The first action
1. remove QMESB2 from the clsuter by
- SUSPEND QMESB2 FROM THE CLSUTER 'CORP'
- STOP AND DELETE THE CLUSTER RECEIVER CHANNEL (TO.QMESB20)
- STOP AND DELETE THE CLUSTER SENDER CHANNEL (TO.QMRPU03)
- REFRESH CLUSTER ('CORP')

2. Add the QMESB2 back to the clsuter 'CORP' by
- DEFINE CLSUTER RCVR CHANNEL
- DEFINE CLUSTER SDR CHANNEL
- START THE CLSUTER SDR CHANNEL

But the display still shows the same problem, cluster sdr TO.QMRPU03 in retry and SSLPEER(CN=QMRPU01...

The second Action is adding the reset cluster on the repository Qmgr to ensure that no left over data is in the repository for QMESB2
1. remove QMESB2 from the clsuter (same step as above)
2. Issue RESET CLUSTER(CORP) QMNAME(QMESB2) ACTION(FORCEREMOVE) QUEUE(YES)
This is my sand box environment which I can do RESET CLUSTER
I saw no trace of QMESB2 doing disp clusqmgr(*) and dis chs(*)
3. Add the QMESB2 back to the clsuter (same step as above)


But the display still shows the same problem, cluster sdr TO.QMRPU03 in retry and SSLPEER(CN=QMRPU01...

Any idea what I did wrong ?
Is "SSLPEER(CN=QMRPU01,OU=WMQ,O=ABC,L=Toronto,ST=ON,C=CA)" in output of display channel status came from the certificate sent by the repository Qmgr ?
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri Dec 06, 2013 10:18 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9394
Location: US: west coast, almost. Otherwise, enroute.

A best-practice is to get the channels into RUNNING state before adding SSL. Did you?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
KIT_INC
PostPosted: Fri Dec 06, 2013 12:28 pm    Post subject: Reply with quote

Knight

Joined: 25 Aug 2006
Posts: 589

QMESB2 is just a new QMgr we added to the clsuter. We have many other Qmgrs connecting to the repository QMRPU03 working all with SSL.
There is actually one question I need help. The CLUSSDR that have problem is TO.QMRPU03. The other QMGRs in the clsuter also has a CLUSSDR with the same name TO.QMRPU03 and all are working.
There is only 1 CLUSRCVR TO.QMRPU03 on the repository Qmgr talking to multiple TO.QMRPU03 CLUSSDRs. If I turn off SSL on the TO.QMRPU03 CLUSRCVR on the repository Qmgr for this test, the other QMGR with TO.QMRPU03 CLUSSDR will fail if there is a need to reconnect.
Please correct me if I am wrong.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Dec 06, 2013 2:31 pm    Post subject: Reply with quote

Grand High Poobah

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

you need to force stop the channel to the FR.
you need to remove the cluster information and restart the channel.
you need to force stop the channel.
you need to add the cluster information and start the channel.

Tell us if this cleared the old information.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » CLUSSDR in retrying status
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.