If a server_ping doesn’t work its typically:

- Wrong address or (default) route (typo)

- Bad cabling or wrong interface plugged in

- Wrong switch or router config

- A misunderstanding about control station interfaces versus data mover interfaces

Rainer

Just to clarify, the ports seem to be working fine on the DM since I can ping other addresses in the same subnet with server_ping, at first I though that we had a firewall issue or bad IPs but after configuring my laptop with the same parameters using the same cable... well lets just say that I am here still scratching my head.

The NX4 is new, so we are not using any trunking, I´ll see if we can take a tcpdump.

Thank you.

Well – there could be the rare case of the port being defective – but typically it’s a config error

If you use trunking/teaming try turning off reflect mode

You can also take a tcpdump and see whats going on on that interface

HI Rainer,

Its not a wrong address I´m sure of that, the cabling is good because I got to a point that the cable was unplugged from the data mover and connected directly to my laptop, I configured my network card the same way I did with the NX4 and it worked fine, I was able to reach the DNS.

About the misunderstanding CS nic with DM nic, well I use server 2 cge0 and cge1 so I dont think we got that confused.

Thanks.

I´m sure that the netmask is OK,  I have no idea how to set the default route but I see that one was created after I created the interface, not sure if I have to create one with other parameters.

you could also try to set a host static route just to your DNS servers.

Well – if you can ping other hosts on that same subnet as the DNS server then most likely its not a Celerra problem

Maybe your DNS server is multi-homed and sending the replies to a wrong interface or doesn’t have a routing to the data mover

Double check if you have really set the netmask and the default route correctly on the data mover

Hi,

could you please post the output of :

$ server_route server_2 -l

and

$ server_ifconfig server_2 -a

You can hide any information you think it's confidential. I just want to better understand the network setup on your environment.

Gustavo Barreto.

Most likely what you see is the network route and not the default route

The default route doesn’t get created automatically (unless it was setup with CSA)

Set a default route with the GUI or “server_route server_2 -add default x.x.x.x” and most likely things will start to work

Rainer

Hi,

Are you able to ping the default gateway 172.18.1.1. Using the DM interface.

server_ping server_2 172.18.1.1.

If you are able to reach the gateway, you can add default gateway. Which will surely help you reaching the DM interface.

If you are not able to reach gateway, assuming your physical connection are fine. Then it must you network configuration issue on switch.

Also, confirm the port used on the switch is a access port or trunk port.

If it is trunk port, make sure you add the correct Vlan ID to the interface.

Naveen

In addition to all of the suggestions above and continuing with Naveenkumar's comment about VLAN ID's, similarly if you aren't configured to use VLAN Tagging make sure that the Celerra Interface VLAN ID is set to zero/blank.  Even if you have a VLAN associated with the switch port, in this scenario you would not set that VLAN ID on the Celerra Interface.

As soon as we get back  I´ll run the command, what we are planning on doing this Monday is adding new IPs on the same subnet as the DNS, I agree on all suggestions about the routing not being correctly configured.

Thank all of you for your fast response, I'll let you know my findings as soon as I can get my hands on the array again.

Hi Corona,

Do you have any update on this?

Regards,

Naveen

Guys first of all thank you for your fast response, at the end we decided not to troubleshoot any more and simply add IPs with the same subnet as the domain and it worked as expected. I compared the routing whit another NAS boxes we have and they looked a like so not sure what went wrong.

Thank you all.