| Author |
Message
|
| tanny0104 |
 Posted: Thu Jun 09, 2011 4:31 am Post subject: Find the ip MQclient connecting to from MQ server |
 |
|
Newbie
Joined: 02 Jun 2011
Posts: 7
|
Hi,
Scenario: Number of MQ clients are connecting to a MQ server which is having physical ip address and virtual ip address.
From MQ server i want to find out whether MQ clients are using physical ips or virtual ips to connect MQ server.
Is it possible to get this information from MQ server or any script can be written for the same? I cannot check/login the Mq client machines.
Please let me know if any more details or clarifications are required.
Thanks and Regards |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jun 09, 2011 4:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| tanny0104 |
| Posted: Thu Jun 09, 2011 5:00 am Post subject: |
|
|
Newbie
Joined: 02 Jun 2011
Posts: 7
|
Thanks Jeff, I looked at this param before but are the values coming under CONN attribute/parameter encoded?
As its not displaying the ip details as it is. |
|
| Back to top |
|
|
| Lieber653 |
| Posted: Thu Jun 09, 2011 5:31 am Post subject: hi |
|
|
Newbie
Joined: 09 Jun 2011
Posts: 3
|
| Try "Dis conn(*) Type(*) or Dis conn(*) Type(All)" , you should be able to see conname & pid and based on that you need to find out the source. |
|
| Back to top |
|
|
| tanny0104 |
| Posted: Thu Jun 09, 2011 5:33 am Post subject: |
|
|
Newbie
Joined: 02 Jun 2011
Posts: 7
|
I am sorry if I was not clear enough.
I do not want to identify the source. I want to identify which ip(physical or virtual) source client is using to connect MQ server.
MQ server is having physical and virtual ip.
Can this info be checked from mq server?
Please let me know if I am still not clear. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 09, 2011 5:50 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tanny0104 wrote: |
| Please let me know if I am still not clear. |
So the MQ server has 2 addresses and you want to determine which one a client has used to connect?
Or you want the address the client is connecting from?
Perhaps a little background on why you need this information would help?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Thu Jun 09, 2011 5:51 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| tanny0104 wrote: |
I am sorry if I was not clear enough.
I do not want to identify the source. I want to identify which ip(physical or virtual) source client is using to connect MQ server.
MQ server is having physical and virtual ip.
Can this info be checked from mq server?
Please let me know if I am still not clear. |
You're still not clear.
Do you know the virtual and physical IP addresses on the client? Cross reference them to the output from the DIS CONN(*) TYPE(ALL). This should tell you? Or are you trying to determine somehow from the server whether an unknown IP address is a physical or virtual address? Not sure how you would be expected to determine that.
Or am I missing something?
*EDIT* - I read Vitor's post and I see now you're trying to determine if the client is using the server's physical or virtual. A netstat should give you that info, though it won't tie directly into which channels.
Last edited by Toronto_MQ on Thu Jun 09, 2011 6:03 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jun 09, 2011 6:03 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
An easier thing to do is stop the listener, and then alter it's properties so it will only listen to the correct address (whether that's the physical or virtual, I don't know).
Then start it again.
Then you know that clients can't connect to the wrong address. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jun 09, 2011 6:03 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Also, have you considered "netstat"? |
|
| Back to top |
|
|
| gouda |
| Posted: Thu Jun 09, 2011 7:15 am Post subject: |
|
|
Apprentice
Joined: 20 May 2001
Posts: 32
Location: Germany, Nuremburg
|
Nice tool if you don't have the network people at hand:
http://planetmvs.com/freeware/tcpipm.html
You browse the netstat and can do a find.
_________________
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots.
So far, the Universe is winning.
https://en.wikiquote.org/wiki/Rick_Cook |
|
| Back to top |
|
|
| tanny0104 |
| Posted: Thu Jun 09, 2011 7:26 am Post subject: |
|
|
Newbie
Joined: 02 Jun 2011
Posts: 7
|
vitor.mqjeff
as you want elaboration regarding background-
Queue manager on MQserver can failover on two physical ips and has one virtual ip. But MQclients if point to virtual ip and Queue manager failover on second physical ip which will create problem.
Hence as i do not have control on MQ client side, I wanted to check from MQ server where QM is running if any MQclient is connecting to MQserver using its physical ip and alert them before the problem occurs.
I hope it is more clear now.
Does the netstat differentiates between physical ip connections and virtual ip connections. Any pointers will be helpful. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 09, 2011 7:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tanny0104 wrote: |
| Hence as i do not have control on MQ client side |
But in a MQ admin capacity you have (or should have) control over the connection parameters they're using, either by publishing a CCDT or by issuing an email along the lines of "if you're using the physical addresses nnn.nnn.nnn.nnn or nnn.nnn.nnn.nnn instead of the virtual address nnn.nnn.nnn.nnn then your application will not connect if we fail over. This is your fault for not reading the application connection details I publish and complaints will be ignored".
| tanny0104 wrote: |
| Does the netstat differentiates between physical ip connections and virtual ip connections. Any pointers will be helpful. |
How would it know 1 ip address is a virtual floating address and another is liked to a physical card?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 09, 2011 8:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Another, more direct, way of finding out who's using a physical address is to speak to the network & HA people, change the physical addresses of the server and modify the virtual ip to redirect to these new values.
Anyone who complains they've lost connectivity is using the physical address and can be hit upside the head with a trout wrapped in the application guidelines.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jun 09, 2011 8:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| tanny0104 wrote: |
| Does the netstat differentiates between physical ip connections and virtual ip connections. Any pointers will be helpful. |
With the correct options it will show you the source IP address of each network socket and the destination IP address of each network socket.
And, again, you can ensure that your MQ listener only attachs to the virtual IP.
Then you don't have to worry about apps connecting to the wrong address, you only have to worry about app developers complaining that MQ must be broken because they can't connect to the physical address. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 09, 2011 8:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
you can ensure that your MQ listener only attachs to the virtual IP.
Then you don't have to worry about apps connecting to the wrong address, you only have to worry about app developers complaining that MQ must be broken because they can't connect to the physical address. |
A more single handled version of what I was suggesting.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
