MQSeries.net :: View topic - BIP1536S errors when deploying in v5

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP1536S errors when deploying in v5

BIP1536S errors when deploying in v5

« View previous topic :: View next topic »

Author

Message

bdrummond

Posted: Wed Jun 15, 2005 3:34 am Post subject: BIP1536S errors when deploying in v5

Disciple

Joined: 06 May 2004
Posts: 164

Hi,

We have recently migrated our 2.1 brokers to v5.
However now we are receiving BIP1536S errors on all of the brokers where we weren't when they were v2.1.
The Config Mgr and all QMgrs associated have not been changed so all security options remain the same.

Has this happened to anyone else or does some good person know how we can resolve this..?

Cheers.

jefflowrey

Posted: Wed Jun 15, 2005 3:46 am Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Diagnostic Messages wrote:

BIP1536
Severity
30 : Severe error
Message
Configuration Manager unable to register for internal subscriptions with broker <insert_0>.
Explanation
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker <insert_0> was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker <insert_0>. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Response
Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center.

Look for errors on the Broker system. Look for additional errors on the configmgr system.

Confirm that the MQ traffic between the broker and the configmgr is operational.

Confirm that the security options specified to mqsicreateconfigmgr were actually correct, and confirm that the configMgr can properly connect to the security domain it needs to.

Confirm that the configmgr service user is fully authorized to all the mq resources on the broker queue managers.

Confirm that you have applied, *successfully*, at least FP3 of 5.0, if not FP4 or FP5.
_________________
I am *not* the model of the modern major general.

bdrummond

Posted: Wed Jun 15, 2005 3:51 am Post subject:

Disciple

Joined: 06 May 2004
Posts: 164

Thanks for the prompt reply Jeff.
I didn't mention that the actual deploy is successful and we receive this message once we have recieved the successful replies.
We are running FP4 on both the Config Mgr and Broker.

jefflowrey

Posted: Wed Jun 15, 2005 3:55 am Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

bdrummond wrote:

Okay. Check the rest of the stuff I mentioned. Or at least some of it.

The BIP error indicates that the deploy was successful. It also indicates that the configMgr doesn't have a good status for the broker - so it might not be able to control that broker properly.
_________________
I am *not* the model of the modern major general.

bdrummond

Posted: Wed Jun 15, 2005 6:56 am Post subject:

Disciple

Joined: 06 May 2004
Posts: 164

I have checked everything and all looks as though it should.
I have set up appropriate mcausers on the sender channels so permissions should not really be an issue.
What I don't really understand is that I never had this issue when the brokers were at v2.1 (???)

jefflowrey

Posted: Wed Jun 15, 2005 6:57 am Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

There are no errors in the broker's system log? Nor MQ errors on the broker machine?
_________________
I am *not* the model of the modern major general.

mayur2378

Posted: Wed Jun 15, 2005 7:04 am Post subject:

Apprentice

Joined: 26 May 2004
Posts: 47

Did u get any MQ errors. Do u have Channels between Broker QM and Config QM? If so are they Up.?

Mayur

bdrummond

Posted: Wed Jun 15, 2005 7:14 am Post subject:

Disciple

Joined: 06 May 2004
Posts: 164

The error in the 'syslog' file is as follows:

Jun 15 16:10:46 ldibmrac1 MQSIv500[1257690]: (DECL_HUB_BKRA.DECL_EOL)[8482]BIP7150E: User id 'mqadmin' not authoriz
ed to put to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'DECLCMGR' using accounting token '0000000000000000
000000000000000000000000000000000000000000000000'. : DECL_HUB_BKRA.99ac5751-0401-0000-0080-8b5ff0cbf028: /build/S50
0_P/src/DataFlowEngine/JavaNodeLibrary/ImbPubSubSubscribeMessageHandler.cpp: 524: ImbPubSubSubscribeMessageHandler:
:checkQueueAuthority: ComIbmPSControlNode: ControlNode

However, the mqadmin user is in all the appropriate groups on the ConFig Mgr (DECLCMGR) machine (Win 2000).
The sender channel to QMGR DECLCMGR also has an mca user of 'mqadmin' set up.
There are no Qmgr Errors reported on the broker machine (AIX)

fschofer

Posted: Wed Jun 15, 2005 7:37 am Post subject:

Knight

Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany

http://publib.boulder.ibm.com/infocenter/wbihelp/index.jsp

Quote:

Message BIP1536
Scenario: You have defined a Configuration Manager to run with one user ID and you have defined a broker to run on a different computer with a different user ID. When you try to deploy message flows to the broker, deployment is successful but you see the error message BIP1536.
Explanation: The Configuration Manager is unable to register for internal subscriptions with the broker because the broker is running under one ID and the Configuration Manager is running under another ID. The broker and the Configuration Manager relay internal messages back and forth via publish/subscribe. These message are carried through WebSphere MQ, which requires certain authorizations.
Solution: Do the following:
Ensure that the broker's user ID is a member of the mqm and mqbrkrs groups.
Define the broker's user ID on the computer where the Configuration Manager is running.
Define the Configuration Manager's user ID on the computer where the broker is running.
Ensure that all IDs are in lowercase so that they are compatible between computers.

jefflowrey

Posted: Wed Jun 15, 2005 7:43 am Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

bdrummond wrote:

Okay, that's telling you that the user mqadmin is not allowed to write to SYSTEM.BROKER.ADMIN.REPLY.

The permissions on the ConfigMgr machine are irrelevant at this point. Is mqadmin a member of mqm on AIX? Try using setmqaut to authorize put for mqadmin to SYSTEM.BROKER.ADMIN.REPLY.
_________________
I am *not* the model of the modern major general.

bdrummond

Posted: Wed Jun 15, 2005 7:51 am Post subject:

Disciple

Joined: 06 May 2004
Posts: 164

I have not created an 'mqadmin' user on the broker machine (AIX).
How can I run the setmqaut command for the SYSTEM.BROKER.ADMIN.REPLY queue on the broker machine when that queue does not exist...?

bdrummond

Posted: Wed Jun 15, 2005 7:54 am Post subject:

Disciple

Joined: 06 May 2004
Posts: 164

Stop Press..!!!
I have now created an mqadmin user on the broker machine and all is fine and dandy.
Just a bit confusing as I set up an mcauser of 'mqm' on the sender channel (CONFIGMGR to BROKER) yet this did not seem to work.

Oh well, at least it's working now.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP1536S errors when deploying in v5

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