| Author |
Message
|
| santosh.veerlapati |
 Posted: Mon Nov 08, 2010 7:56 am Post subject: Not able to ping sender channel from mq explorer |
 |
|
Voyager
Joined: 19 Jun 2008
Posts: 87
|
Hi
We have hub-spoke configuration in our production system.
We have Central Hub at Data center, named "HubQM"(Queue manger)
located at CPBIP1IMQS01 with listener port 1415.
And we have nearly 70 spokes located at different locations and connected to HubQM.
Today, suddenly one of the spoke queue manager is not able to communicate to the HubQM , when we stop and start the sender channel it shows the status , running but when we ping on it its not able to ping and giving AMQ4054 error.
When we telnet the 1415 port of this machine from command prompt its working fine and able to telnet the remote port.
When we check the windows event logs
It displaying series of errors listed below
The response program TCP / IP encountered an error.
The response program was started but detected an error.
Examine previous error messages in the error files to determine the error encountered by the response program.
The connection to the central 'cpbip1nmon02 (192.168.52.250)' was closed.
An error occurred while receiving data from 'cpbip1nmon02 (192.168.52.250)' over TCP / IP. The remote connection to the central system terminated unexpectedly.
Communicate your system administrator.
Connection to host 'prbosiac148sg01 (10.10.148.1)' closed.
An error occurred receiving data from 'prbosiac148sg01 (10.10.148.1)' over TCP / IP. The connection to the remote host has unexpectedly terminated.
Tell the systems administrator.
actually we are not at all using the ip 192.168.52.250, and wondering how its taking this ip.
Can anybody please help me in this.
Thanks in Advance
Santosh Kumar Veerlapati |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon Nov 08, 2010 8:10 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Speak to your network people and find out whether recent changes were made to DNS etc.
And you can't ping a running 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 |
|
|
| santosh.veerlapati |
| Posted: Mon Nov 08, 2010 8:14 am Post subject: |
|
|
Voyager
Joined: 19 Jun 2008
Posts: 87
|
| Can u brefley explain me what is the DNS changes made? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 08, 2010 8:16 am Post subject: Re: Not able to ping sender channel from mq explorer |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santosh.veerlapati wrote: |
| actually we are not at all using the ip 192.168.52.250, and wondering how its taking this ip. |
If you're not using this ip, what's coded in the channel's connection name? If it's a DNS name (cpbip1nmon02) what does the DNS server say that resolves to?
When you tested with telnet, did you use the IP address or DNS name?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 08, 2010 8:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santosh.veerlapati wrote: |
| Can u brefley explain me what is the DNS changes made? |
DNS is what changes cpbip1nmon02 into a real address 123.123.123.123
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| santosh.veerlapati |
| Posted: Mon Nov 08, 2010 8:38 am Post subject: |
|
|
Voyager
Joined: 19 Jun 2008
Posts: 87
|
in the sender channel i m giving this host name
CPBIP1IMQS01
which is virtual ip of the machine on which HubQM is located.
i m able to telnet 1415 of this CPBIP1IMQS01 host name from spoke queue manger machine. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 08, 2010 8:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santosh.veerlapati wrote: |
| which is virtual ip of the machine on which HubQM is located. |
Pedantically it's the DNS name of the virtual ip of the machine.
| santosh.veerlapati wrote: |
| i m able to telnet 1415 of this CPBIP1IMQS01 host name from spoke queue manger machine. |
Then if you're certain that the telnet to that IP's 1415 port has successfully reached the receiver MCA (because it errored), and that you're issuing the telnet from the same environment that the sender MCA is running in, and that the channel's conname correctly reflects both the DNS name & the port number, then it's down to your network people to fix it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| santosh.veerlapati |
| Posted: Mon Nov 08, 2010 9:49 am Post subject: |
|
|
Voyager
Joined: 19 Jun 2008
Posts: 87
|
| thanks a lot for all u r quick replies |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Nov 08, 2010 2:31 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Pedantically an ipaddress(port) is an explicit definition of a CONNAME.
You may be able to omit the port if the receiving end of the channel is listening on 1414 - the so-called default MQ port.
You may be able to omit the ipaddress - and specify (port) only, if the receiving end is on/in the same host.
If CONNAME is something else, the ipaddress(port) must be "discoverable" via DNS or LDAP, etc..
_________________
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 |
|
|
|
|
