MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » August 2014

Re: Fw: telnet



fixed

Smells like a possible VLAN issue. Can 10.10.1.195 ping the gateway for that network? If not then definitely a VLAN issue. If Yes then not likely.

Also can the 10.10.6.48 partition ping ITs gateway? That's also important.

Are there routes on both servers that cover the other server. If that's the default route that's OK but routes must exist BOTH ways.

If the above is correct then what is the router device and are it's routes correct?

If this stuff had just been moved in the last minutes then I would say flush your arp caches but they would have long aged out by now. Stupid question though, you don't use any static ARP entries do you? (read: LandMine :-) )



- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 8/1/2014 8:47 AM, rob@xxxxxxxxx wrote:
*This message was transferred with a trial version of CommuniGate(r) Pro*
I am trying to talk to my network guy but he doesn't start until 10:30.
Not an urgent, critical OMG issue (update: it is causing issues with BRMS
networking) but I want to get it resolved.
I do not want finger pointing. If it's my issue and not the networking
guy's I want to get it fixed on my end.

I moved a couple of lpars from our 10.10.1.x subnet to our 10.10.6.x
subnet at the same time as I moved them from Power 6 to Power 8.
The new addresses were all determined by the network guy.

GDIHQ2(10.10.1.195) will not talk to MAILTWO(10.10.6.48)
GDISYS2(10.10.6.129) will talk to MAILTWO(10.10.6.48)

Not a DNS resolution issue.

From GDISYS2(10.10.6.48)
ping mailtwo
Verifying connection to host system MAILTWO.dekko-1 at address
10.10.6.48.
PING reply 1 from 10.10.6.48 took 0 ms. 256 bytes. TTL 64.
PING reply 2 from 10.10.6.48 took 0 ms. 256 bytes. TTL 64.
PING reply 3 from 10.10.6.48 took 0 ms. 256 bytes. TTL 64.
PING reply 4 from 10.10.6.48 took 0 ms. 256 bytes. TTL 64.
PING reply 5 from 10.10.6.48 took 0 ms. 256 bytes. TTL 64.
Round-trip (in milliseconds) min/avg/max = 0/0/0.
Connection verification statistics: 5 of 5 successful (100 %).
TRACEROUTE MAILTWO
Probing possible routes to MAILTWO.dekko-1 (10.10.6.48) using *ANY
interface.
1 mailtwo (10.10.6.48) 0.101 0.058 0.043

From GDIHQ2(10.10.1.195):
ping mailtwo
Verifying connection to host system MAILTWO.dekko-1 at address
10.10.6.48.
No response from host within 1 seconds for connection verification 1.
No response from host within 1 seconds for connection verification 2.
No response from host within 1 seconds for connection verification 3.
No response from host within 1 seconds for connection verification 4.
No response from host within 1 seconds for connection verification 5.
Connection verification statistics: 0 of 5 successful (0 %).
TRACEROUTE MAILTWO
Probing possible routes to MAILTWO.dekko-1 (10.10.6.48) using *ANY
interface.
1 gdslan-v1.dekko-1 (10.10.1.1) 0.804 0.785 0.690
2 * * *
3 * * *
4 * * *
Last request at level 4 ended. (I aborted it after several seconds)


From GDIHQ2(10.10.1.195)
PING '10.10.6.1'
Verifying connection to host system 10.10.6.1.
PING reply 1 from 10.10.6.1 took 0 ms. 256 bytes. TTL 255.
PING reply 2 from 10.10.6.1 took 0 ms. 256 bytes. TTL 255.
PING reply 3 from 10.10.6.1 took 0 ms. 256 bytes. TTL 255.
PING reply 4 from 10.10.6.1 took 0 ms. 256 bytes. TTL 255.
PING reply 5 from 10.10.6.1 took 0 ms. 256 bytes. TTL 255.
Round-trip (in milliseconds) min/avg/max = 0/0/0.
Connection verification statistics: 5 of 5 successful (100 %).
PING '10.10.6.129'
Verifying connection to host system 10.10.6.129.
PING reply 1 from 10.10.6.129 took 0 ms. 256 bytes. TTL 63.
PING reply 2 from 10.10.6.129 took 0 ms. 256 bytes. TTL 63.
PING reply 3 from 10.10.6.129 took 0 ms. 256 bytes. TTL 63.
PING reply 4 from 10.10.6.129 took 0 ms. 256 bytes. TTL 63.
PING reply 5 from 10.10.6.129 took 0 ms. 256 bytes. TTL 63.
Round-trip (in milliseconds) min/avg/max = 0/0/0.
Connection verification statistics: 5 of 5 successful (100 %).
PING '10.10.6.48'
Verifying connection to host system 10.10.6.48.
No response from host within 1 seconds for connection verification 1.
No response from host within 1 seconds for connection verification 2.
No response from host within 1 seconds for connection verification 3.
No response from host within 1 seconds for connection verification 4.
No response from host within 1 seconds for connection verification 5.
Connection verification statistics: 0 of 5 successful (0 %).

From MAILTWO(10.10.6.48)
ping '10.10.1.1'
Verifying connection to host system 10.10.1.1.
No response from host within 1 seconds for connection verification 1.
No response from host within 1 seconds for connection verification 2.
No response from host within 1 seconds for connection verification 3.
No response from host within 1 seconds for connection verification 4.
No response from host within 1 seconds for connection verification 5.
Connection verification statistics: 0 of 5 successful (0 %).
> ping '10.17.1.1'
Verifying connection to host system 10.17.1.1.
PING reply 1 from 10.17.1.1 took 1 ms. 256 bytes. TTL 250.
PING reply 2 from 10.17.1.1 took 1 ms. 256 bytes. TTL 250.
PING reply 3 from 10.17.1.1 took 1 ms. 256 bytes. TTL 250.
PING reply 4 from 10.17.1.1 took 1 ms. 256 bytes. TTL 250.
PING reply 5 from 10.17.1.1 took 1 ms. 256 bytes. TTL 250.
Round-trip (in milliseconds) min/avg/max = 1/1/1.
Connection verification statistics: 5 of 5 successful (100 %)

MAILTWO:
Route destination . . . . . . . . . . : *DFTROUTE
Subnet mask . . . . . . . . . . . . . : *NONE
Type of service . . . . . . . . . . . : *NORMAL
Next hop . . . . . . . . . . . . . . . : 10.10.6.1
Preferred binding interface . . . . . : 10.10.6.48

GDIHQ2:
Route destination . . . . . . . . . . : *DFTROUTE
Subnet mask . . . . . . . . . . . . . : *NONE
Type of service . . . . . . . . . . . : *NORMAL
Next hop . . . . . . . . . . . . . . . : 10.10.1.1
Preferred binding interface . . . . . : *NONE
Route destination . . . . . . . . . . : 10.17.252.0
Subnet mask . . . . . . . . . . . . . : 255.255.254.0
Type of service . . . . . . . . . . . : *NORMAL
Next hop . . . . . . . . . . . . . . . : 10.10.252.1
Preferred binding interface . . . . . : 10.10.252.192
Note: Should the next hop of 10.10.1.1 have a preferred binding interface
of 10.10.1.195?

GDISYS2:
Route destination . . . . . . . . . . : *DFTROUTE
Subnet mask . . . . . . . . . . . . . : *NONE
Type of service . . . . . . . . . . . : *NORMAL
Next hop . . . . . . . . . . . . . . . : 10.10.6.1
Preferred binding interface . . . . . : *NONE
Route destination . . . . . . . . . . : 10.17.252.0
Subnet mask . . . . . . . . . . . . . : 255.255.254.0
Type of service . . . . . . . . . . . : *NORMAL
Next hop . . . . . . . . . . . . . . . : 10.10.252.1
Preferred binding interface . . . . . : 10.10.252.193
Note: Should the next hop of 10.10.6.1 have a preferred binding interface
of 10.10.6.129?

Rob Berendt






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact