Unsolved
This post is more than 5 years old
5 Posts
0
24386
February 2nd, 2012 13:00
Unable to ping group IP from specific computer
Weird issue here. I think I know what's happening, but I just cannot figure out how to fix it.
We have our SAN network on a different segment that our production LAN with a Windows 2008 server acting as a router between the two segments.
We recently replaced that box with a new one with a new IP address.
Now, from my workstation (located on the production lan segment, I cannot ping the SAN group IP. I can ping each NIC okay, just not the group IP. I can also ping the group IP from other authorized systems fine... just not my specific IP. Just to add to the confusion, if I change the IP on my workstation, it works okay.
My guess is that the SAN group IP is trying to find me through the old IP addy of the server/router.
* I did change the group gateway to the new address
* I did change the default gateway on the SAN switches
DELL-Joe S
7 Technologist
•
729 Posts
0
February 2nd, 2012 13:00
To use ping and/or traceroute from the PS Aarray,
telnet/ssh to one of the eth interfaces (do not use the group ip, if you have more than one array member, do telnet into each member to perform the test)
login as groupadmin, and at the groupname prompt:
Ping:
to ping out of each of the specific ETH port interfaces add the switch to choose the interface IP as shown below:
ping "-I "
(that is a –I as in Capital letter “eye”, and don't forget the quotes after ping and at the end of the argument string).
Test all IP combinations (eth0, eth1, eth2, etc.)
Traceroute:
To traceroute out each of the specific ETH port interface add a switch to choose the interface IP as shown below (note the cli command is "support traceroute"):
GrpName>support traceroute "-s [ETH port source IP] [destinationIP]"
(don't forget the quotes after support traceroute and at the end of the argument string).
Ensure to test each ETH interface combination
Test all IP combinations (eth0, eth1, eth2, etc.)
From the Windows Server, Windows ping uses a –S to specify the interface to use.
-joe
michaelt73
5 Posts
0
February 2nd, 2012 16:00
Hi Joe. Thanks for the response.
I can ping from all 4 interfaces okay... just not from the group ip addy.
This is also the case with traceroute where I get "***" when trying to ping my workstation IP from the group IP addy. If I traceroute from one of the eth interfaces, it works fine.
DELL-Joe S
7 Technologist
•
729 Posts
0
February 3rd, 2012 08:00
Is the workstatation on the SAN subnet or a subnet that is passed through the gateways (router) server?
From the array, test the ping/traceroute to a system (one of the host systems) on the SAN subnet, what is your results?
Also, if you can, from a system on the SAN subnet, test to see if it can ping/traceroute the group IP.
Post your results.
Also, verify the following:
Make sure that the WKA (well known address, a.k.a. the Group IP), is listed and associated with one of the interfaces of the group lead array (if you only have one array member, then that is the group lead, if you have more than one array member in the group, look in the GUI event log for a “login or logout” event, for that event, look in the “Member” column, you will see what array responded, this is the group lead member, and the one you need to telnet into):
Login as grpadmin
at the groupname prompt, type:
Groupname> Support exec “ifconfig –a”
In the output, you should see one of the interfaces has this entry (your IP’s will be listed, I have x’ed out the example for security), the line we are looking for is the one that starts with “inet alias”
eth0: flags=8043 mtu 9000
address: 00:xx:xx:xx:xx:xx
media: Ethernet none (1000baseT full-duplex)
status: active
inet 172.xx.xx.3 netmask 0xffff0000 broadcast 172.xx.xxx.xxx
this line -->>inet alias 172.xx.xx.2 netmask 0xffff0000 broadcast 172.xx.xxx.xxx
inet6 fexx::xx:xxx:xxxx:xxxx prefixlen 64
report back your findings.
-joe