I have a strange networking issue. Pinging a SAN cluster environment from 1 remote location. We have 4 remote locations that connect to our main office. Here we have a SAN cluster environment. We have a location that is different then to other two. One connects thru an nvpn network the other two connect thru a VPN concentrator.
The SAN is connected to the LAN switches. There are 3 network cables in total for the SAN cluster. I have 1 cable in a different switch. The switches are not cluster.
The weird case is that I can ping from the trouble location other servers in the same network as the SAN except the actual SAN. Here is a tracert example:
C:\Documents and Settings\adminbla>tracert 172.16.5.33
Tracing route to [172.16.5.33] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.2.99.2 2 24 ms 26 ms 27 ms x.x.x.37 (external address 2 of them in x) 3 340 ms 336 ms 301 ms x.x.x.58 4 311 ms 347 ms 306 ms servername.domainname.com [172.16.5.33]
Trace complete.
C:\Documents and Settings\TPGRoot>tracert 172.16.5.70
Tracing route to san03.domainname.com [172.16.5.70] over a maximum of 30 hops:
1 3 ms <1 ms <1 ms 10.2.99.1 2 <1 ms <1 ms <1 ms 10.2.99.2 3 27 ms 339 ms 267 ms x.x.x.x (external address 1 of them) 4 * * * Request timed out. 5 * * * Request timed out. 6 ^C
Well I need to have this location be able to reach the SAN server. The mystery to me is why they cannot ping the 3 SAN machines while they can reach all other servers in the same network. I will put tomorrow the SAN machines in the same switch it is the only thing I can think of for now. I also wonder why the way to the SAN network from the remote office has two internal IP address to get to this location and not the other servers have one internal IP address hence are connecting fine. From over there they should all come here in the same way. Where do I check in the remote location?
Okay this is what I found. The entries In the DNS server are correct. I looked at the 2 SAN servers I found that one of the when you run Ipconfig has two ip address while the other has just its own. The DNS entries for the SAN servers didn't seem consistent. One SAN had two DNS servers while the other just one. M
Yes I managed to solve this issue by entering a static route in each SAN server. As it turned out the heart beat of each server had a NIC to NIC address scheme of 10.x.x.x. that was similar to the one from the remote trouble location. when I run route print it will show me a host for that network that was causing me trouble. Thanks, for your help.