| Author |
Message
|
| shashivarungupta |
 Posted: Wed Feb 25, 2009 10:26 pm Post subject: Cluster Monitoring ? |
 |
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
Hi Folk,
Could you please help me with cluster monitoring.
I mean to say do you have some unix/aix/java related scripts/programs that can help in monitoring the cluster and its objects.
I am using IBM MQ v6.0.2.4
Any suggestion or any link will be thankful.
Thank
Varun Gupta  |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Wed Feb 25, 2009 10:41 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
MQSeries cluster monitoring or hardware cluster monitoring?
MQ cluster monitoring does not differ much vom the "normal" mq monitoring, you need to monitor queues and channels, in case of clustering there is also SYSTEM.CLUSTER* that should be monitored, as well als cluster channel status.
There are lots of treads here related to monitoring and the related tools, the search button is your friend.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Wed Feb 25, 2009 10:45 pm Post subject: RE |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
Thanks Sir.
I meant to say MQ Cluster Monitoring.
Ya. I got the point, as monitoring the system cluster queues and channels.
Any thing else that you would like to suggest while monitoring the mq cluster that I should takecare of.
Appreciate your help.
Thank
Varun |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 26, 2009 1:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
One tip - remember "the cluster" is not an entity; it's the queue managers which make it up that you're monitoring.
Somewhat obvious but a lot of people seem to overlook it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Pavan Kumar PNV |
| Posted: Wed Mar 18, 2009 3:50 am Post subject: |
|
|
Acolyte
Joined: 03 Feb 2007
Posts: 66
|
1. Check for any temporary objects in the output of dis clusqmgr(*). That is a sign of a cluster that needs cleanup done.
_________________
_____________
Pavan Pendyala
http://pavanz.blogspot.com |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Mar 18, 2009 4:08 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Pavan Kumar PNV wrote: |
| 1. Check for any temporary objects in the output of dis clusqmgr(*). That is a sign of a cluster that needs cleanup done. |
This indicates the cluster was not cleanly functioning in the first place, i.e. a communication/definition issue is/was extant, and should have been addressed at the time. Clusters shouldn't need a 'cleanup', they should be properly managed all the time.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Wed Mar 18, 2009 4:10 am Post subject: RE |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| Pavan Kumar PNV wrote: |
| 1. Check for any temporary objects in the output of dis clusqmgr(*). That is a sign of a cluster that needs cleanup done. |
This displays all the queue managers that are the part of that cluster. It'll show the info. with the channel name. As:
display clusqmgr(*)
1 : display clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(EAIDVBR1) CHANNEL(TO.EAIDVBR1)
CLUSTER(CLSTR.EAIDV)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(EAIDVGW1) CHANNEL(TO.EAIDVGW1)
CLUSTER(CLSTR.EAIDV)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(EAIDVGW2) CHANNEL(TO.EAIDVGW2)
CLUSTER(CLSTR.EAIDV)
No temporary objects is shown.
And even when we REFRESH CLUSTER it do the needful that means it removes all the temp. objects and modifies the status of repository queue managers.
So I dont know ..that would help. |
|
| Back to top |
|
|
| Pavan Kumar PNV |
| Posted: Wed Mar 18, 2009 4:12 am Post subject: |
|
|
Acolyte
Joined: 03 Feb 2007
Posts: 66
|
Agreed - adding this as a monitoring event will notify you as and when the error is occuring presenting you an oppurtunity to fix it right away.
_________________
_____________
Pavan Pendyala
http://pavanz.blogspot.com |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 18, 2009 4:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Pavan Kumar PNV wrote: |
| Agreed - adding this as a monitoring event will notify you as and when the error is occuring presenting you an oppurtunity to fix it right away. |
No - monitoring the channels will notify you that an error is occuring. This will only show you that the initial set up of the cluster is wrong (or in rare circumstances that the cluster has broken some hours if not days after the event).
Using this monitor has no value.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Wed Mar 18, 2009 4:22 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| Quote: |
| ..adding this as a monitoring event will notify you as and when the error is occuring presenting you an oppurtunity to fix it right away. |
Until you have a running setup of cluster or clusters, I don't think there is any logic to have a monitoring script/program to monitor that.
Ya ofcourse you can check manually why the initial stage of cluster setup is not working as desired. In that case for example you can check the cluster channels. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 18, 2009 5:40 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I'd suggest reading the WMQ Clusters manual, and the WMQ Monitoring manual.
_________________
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 |
|
|
|
|
