Solved!
Go to SolutionD
dbreveard1
21 Posts
0
1366
January 30th, 2010 09:00
Celerras cannot access other subnets
I have an NS120 (Kalamazoo, Mi) and an NX4 (Boise, Id) that are unable to ping each other.. The IP addresses for the Celerras are 10.10.10.51/24 and 172.16.204.31/16. I have a site to site VPN configured between the facilities. Communications between the sites is functional. I can ping servers on one side from servers on the other side. I can access my vCenter servers at each location from the other location. This is just and EMC to EMC issue. I need this resolved to be able to setup replication between the EMC SANs. The IP addresses that I listed were Control Station IPs. I am NOT an EMC guy so maybe I am going this incorrectly. Any help would be greatly appreciated.
dbreveard1
21 Posts
477
0
Posted January 30th, 2010 09:00
I understand the networking and routing aspect of it, but I was unsure as to whether the CS would control the routing for the DM or not. Now that you have provided this information, I will see if I can configure it. I was also unaware that I needed to login as root to make those changes to the networking. Thank you. If this works, I will award points.dbreveard1
21 Posts
477
0
Posted January 30th, 2010 09:00
Yes, but that did not resolve the issue. I set the route 0.0.0.0 0.0.0.0 172.16.254.1 (default gw for all devices on that network) and still cannot access devices on other networks. Shoud I set the route to use the IP of the EMC interface instead of the default gateway for the network. Again, I am not an EMC guy so this has me a little confused.dbreveard1
21 Posts
477
0
Posted January 30th, 2010 10:00
Thanks to your information I have one side up and going. I am trying to figure out why the other side wont function properly when the same rules are applied. I am going to continue working with this. Once it is complete, I will award points. If it turns out to be a networking issue this side I will still award you the points. Unfortunately I am working on this from home so I cannot physically check the connections.no - the DM is an extra machine and has its own IP stack
the CS doesnt control it - its merely where the config is maintained and the commands are entered - but these just talk to the DM to configure it
(since the DMs dont have internal disks or a login shell)
if you login to Celerra Manager as nasadmin it will show the control station networking - but you wont be able to change it
this is so that admins take care and not shoot themselves in the foot by changing the interface they are working through
if the control station admin interface (eth3 normally) gets screwed up then you better start looking for that serial cable :-)
Rainer
dbreveard1
21 Posts
477
0
Posted January 30th, 2010 13:00
Your steps to perform worked to get the devices talking. I had an issue with access rules on my ASA that was preventing me from pinging from device to another. I will award you points for this. Thank you again.dbreveard1
21 Posts
314
0
Posted January 30th, 2010 14:00
I am having other issues with the replication now. I have posted another topic about it. Can you answer this question for me: Can Celerras replicate if they have different software versions?Rainer_EMC
6 Operator
•
8645 Posts
477
1
Posted January 30th, 2010 14:00
you're welcome
glad it worked
if you do have a firewall in front of the Celerra you also want to take a look at the security manual that lists which ports are used by the Celerra for what purpose
Rainer
ral67_xyz
147 Posts
477
0
Posted January 30th, 2010 09:00
Hi,
first thing you need to take in mind is that the control station and the data mover networking are two different setups.
For Celerra Replicator to work both the CS's need to see each other and both DM's need to.
The DM doesnt "route" through the CS or vice versa - both have to have working networking
You can use Celerra Manager to configure both - you just need to login as root (not nasadmin)
the CS networking is configurable under the control station tab
the DM networking is configuruable under data mover -> networking
Then you need to check routing tables for both - netstat for CS and server_netstat for DM
and test with ping for CS and server_ping for DM
for a default route the destination must the next-hop routers interface on the network that the CS (or DM) is directly conneted to.
I would suggest to talk to your networking people - they should be more familiar with IP adresses and routing tables
Rainer