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 » General Discussion » Connectivity test

Post new topic  Reply to topic
 Connectivity test « View previous topic :: View next topic » 
Author Message
RichA
PostPosted: Thu Jul 02, 2009 2:03 am    Post subject: Connectivity test Reply with quote

Centurion

Joined: 14 Mar 2002
Posts: 102

Ok, does anyone know how to talk to a queue manager over telnet?
Up until a few weeks ago a response from a telnet request was sufficient to prove TCP communication between boxes. There was a change in the network, now it's not.
So for other services it's not so much a problem, with http we can use wget or a get within a telnet session. Similar with ftp, proving we're hitting the target server for those protocols is faily easy without having to involve a whole host of network/firewall engineers.
The best I can come up with for proving the MQ connection is an MQ ping, the customer wants to know if there's something more basic at a lower level that can be done without having to set up channels.
Any ideas?
Back to top
View user's profile Send private message MSN Messenger
exerk
PostPosted: Thu Jul 02, 2009 2:12 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Even the telnet is using a channel...
_________________
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
View user's profile Send private message
RichA
PostPosted: Thu Jul 02, 2009 2:14 am    Post subject: Reply with quote

Centurion

Joined: 14 Mar 2002
Posts: 102

No, the telnet is using a listener
Back to top
View user's profile Send private message MSN Messenger
exerk
PostPosted: Thu Jul 02, 2009 2:16 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Sorry, I should have qualified my statement: not a WMQ channel was meant, but not said.
_________________
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
View user's profile Send private message
shashivarungupta
PostPosted: Thu Jul 02, 2009 2:19 am    Post subject: Re: Connectivity test Reply with quote

Grand Master

Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.

RichA wrote:
Ok, does anyone know how to talk to a queue manager
over telnet?
Up until a few weeks ago a response from a telnet request was sufficient to prove TCP communication between boxes. There was a change in the network, now it's not.
So for other services it's not so much a problem, with http we can use wget or a get within a telnet session. Similar with ftp, proving we're hitting the target server for those protocols is faily easy without having to involve a whole host of network/firewall engineers.
The best I can come up with for proving the MQ connection is an MQ ping, the customer wants to know if there's something more basic at a lower level that can be done without having to set up channels.
Any ideas?


telnet IPAddress Port

e.g.
telnet x.x.x.x 7414
On pressing "Enter" after each telnet command, it shows "Connecting to x.x.x.x " and a blank screen appears instantly.

That means there is a connectivity(either direct or through firewalls).
_________________
*Life will beat you down, you need to decide to fight back or leave it.
Back to top
View user's profile Send private message Send e-mail
exerk
PostPosted: Thu Jul 02, 2009 2:24 am    Post subject: Re: Connectivity test Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

shashivarungupta wrote:
telnet IPAddress Port

e.g.
telnet x.x.x.x 7414
On pressing "Enter" after each telnet command, it shows "Connecting to x.x.x.x " and a blank screen appears instantly.

That means there is a connectivity(either direct or through firewalls).


I think the poster knows that...

RichA wrote:
...Up until a few weeks ago a response from a telnet request was sufficient to prove TCP communication between boxes. There was a change in the network, now it's not...

_________________
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
View user's profile Send private message
RichA
PostPosted: Thu Jul 02, 2009 2:34 am    Post subject: Reply with quote

Centurion

Joined: 14 Mar 2002
Posts: 102

There's now something to proxy the requests, this results in a TCP response regardless of whether we're hitting the target machine or not.
The blank screen is a windows thing, no idea if it's the same, it probably is, but I can issue GET / HTTP/1.1 to check a response from an http server. If I'm hitting the proxy device, but not the server it just times out.
I would like a similar test for MQ, my current bet is that there isn't one, or if there is then nobody's going to tell me what it is because it could probably be used for nefarious purposes.
Back to top
View user's profile Send private message MSN Messenger
exerk
PostPosted: Thu Jul 02, 2009 2:43 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Nothing that I'm aware of, but how about setting up a client connection using the MQSERVER variable, going to the SYSTEM.DEF.SVRCONN (which will of course have a 'null' user specified), as when you get MQRC 2035, you'll know for certain you've hit it.
_________________
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
View user's profile Send private message
RichA
PostPosted: Thu Jul 02, 2009 2:46 am    Post subject: Reply with quote

Centurion

Joined: 14 Mar 2002
Posts: 102

Not a bad idea, I'll go with that one. Thanks
Back to top
View user's profile Send private message MSN Messenger
gbaddeley
PostPosted: Thu Jul 02, 2009 4:36 pm    Post subject: Re: Connectivity test Reply with quote

Jedi Knight

Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia

RichA wrote:
Ok, does anyone know how to talk to a queue manager over telnet?
Up until a few weeks ago a response from a telnet request was sufficient to prove TCP communication between boxes. There was a change in the network, now it's not....


Are you telnetting to the standard telnet port 23 or the MQ listener port (default 1414, but could be almost anything) ? The networking folk may have blocked port 23 (eg. to switch from using telnet to ssh as the required logon method).
_________________
Glenn
Back to top
View user's profile Send private message
RichA
PostPosted: Thu Jul 02, 2009 11:14 pm    Post subject: Reply with quote

Centurion

Joined: 14 Mar 2002
Posts: 102

The MQ port of course. The problem was that whatever the device they've changed/put on the network responds to telnet requests so we were getting false positives, we thought we were connecting to the MQ server, but when we were trying channel communication it was failing. After much faffing around and getting network engineers from all over the place we found out we weren't even connecting to the destination server (I actually knew this a lot earlier because the destination machine wasn't showing an established connection, but you know network types, it's always the applications at fault and vice versa)
Anyway the client connection should be enough, I'm expecting a 2393 or 2035 as ererk speculated.
Might be a problem if they want to get rid of the sample apps or anything that's going to act as a client.
Back to top
View user's profile Send private message MSN Messenger
fjb_saper
PostPosted: Fri Jul 03, 2009 12:11 am    Post subject: Reply with quote

Grand High Poobah

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

RichA wrote:
The MQ port of course. The problem was that whatever the device they've changed/put on the network responds to telnet requests so we were getting false positives, we thought we were connecting to the MQ server, but when we were trying channel communication it was failing. After much faffing around and getting network engineers from all over the place we found out we weren't even connecting to the destination server (I actually knew this a lot earlier because the destination machine wasn't showing an established connection, but you know network types, it's always the applications at fault and vice versa)
Anyway the client connection should be enough, I'm expecting a 2393 or 2035 as ererk speculated.
Might be a problem if they want to get rid of the sample apps or anything that's going to act as a client.


If you are using MQIPT (and possibly an http/https proxy) in between, make sure somebody looks at the logs and errors for mqipt on that machine....

We also check that the openssl -client will pull the correct certificate from the partner machine, thus making sure the certs will match...

Have fun
_________________
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 » General Discussion » Connectivity test
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.