1) yes

2) yes

So if I cannot ping the default gateway how do I asssign a route for the default gateway?

Without an interface a data mover cannot talk IP to the outside world.

Same as on every other system running TCP/IP you need an interface to create a default route

The internal network between the CS and DM is strictly internal – it is not routed for good reasons

So NFS/NTP/… on the CS uses the CS interface eth3 – the similar services on the DM need an interface on the DM

So I create an interface and use that interface's default gateway to create a gateway route?

Do i have to create a route for the dns and ntp servers?

You need to create an interface that is in the same subnet as the default gateway

do you have to assign an ip address to a windows server to be able to get it on the network ? Yes ..same concept there.

unless all your clients will be on the same network as your interface,  you need to specify default gateway.

So if I have to get the DNS and NTP servers to communicate with the data mover then I have to create an interface?

And I have to assign a default gateway for this interface which are both in the same subnet and with the same vlan id?

I did not understand your question Dynamox. So I created an interface within the same subnet as the default gateway and with the same vlan id. I used one of the fsn network devices that I created but I am still unable to ping the default gateway or create a route to the DNS or NTP server. It says fails to connect to default gateway. What could be the other issues that I can troubleshoot. I have asked the network team to check the connectivity between the MAC addressses of the NIC cards and the default gateway.

the default gateway has a specific vlan id and i did try using that when i created the interface. but it did not work. how do i find out if the network ports have a specific vlan and how do i know what are the network port addresses. is it the MAC address on the NIC cards?