when EMC told you to use server_2 ..he/she is basically verifying that NDMP port is listening. If you look at /etc/hosts file on control station you will see that it's assigned an inernal to Celerra ip address, for example:  [nasadmin[NAME] ~]$ cat /etc/hosts |grep -i server_2 192.168.1.2  server_2   #DART_data_mover_2  so if you telnet to server_2 you are actually connecting to internal interface on datamover. If you are successful with that, that means NDMP is listening and it's something on the outside network that's preventing NDMP connection (firewall, ACL on the network switch).
Hello All,  I need some expert advice here. I am in the process of configuring NDMP to NB server on celerra NS40.The problem is the media server as well as the master server is not able to ping the DM IP.  I have this routing info from Server_2  server_netstat server_2 -r Destination     Gateway         Mask            Type       Proto      Interface ******************************************************************************* 0.0.0.0         206.245.41.1    0.0.0.0         DIRECT     LOCAL 10.0.0.0        198.199.241.35  255.0.0.0       DIRECT     LOCAL 10.202.1.0      198.199.241.35  255.255.255.224 DIRECT     LOCAL 128.221.252.0   128.221.252.2   255.255.255.0   DIRECT     LOCAL      mge0 128.221.253.0   128.221.253.2   255.255.255.0   DIRECT     LOCAL      mge1 198.199.241.32  198.199.241.50  255.255.255.224 DIRECT     LOCAL 206.245.41.0    206.245.41.14   255.255.255.224 DIRECT     LOCAL =========================================================== this is the output from server_ifconfig server_2 :client* protocol=IP device=fsn0         inet=198.199.241.50 netmask=255.255.255.224 broadcast=198.199.241.63        UP, ethernet, mtu=1500, vlan=1514, macaddr=0:60:16:3e:4e:88usdadcgfspuw00 protocol=IP device=fsn0         inet=206.245.41.14 netmask=255.255.255.224 broadcast=206.245.41.31        UP, ethernet, mtu=1500, vlan=1526, macaddr=0:60:16:3e:4e:88loop protocol=IP device=loop         inet=127.0.0.1 netmask=255.0.0.0 broadcast=127.255.255.255        UP, loopback, mtu=32768, vlan=0, macaddr=0:0:0:0:0:0 netname=localhostel31 protocol=IP device=mge1         inet=128.221.253.2 netmask=255.255.255.0 broadcast=128.221.253.255        UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:35:68:35 netname=localhostel30 protocol=IP device=mge0         inet=128.221.252.2 netmask=255.255.255.0 broadcast=128.221.252.255        UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:35:68:36 netname=localhost  What could be the possible reason for the backup server not able to communicate with the DM? i 'd also like to know if i can add  route entry on the server 198.199.241.50  for  206.245.36.0/24 subnet( these are the backup servers)  with the next-hop 198.199.241.33.  Destination     Gateway         Mask            206.245.36.0 198.199.241.33   255.255.255.0  would this help? Adding a new route should not impact the production?  somebody told me,  I  do not have an interface called DIRECT LOCAL so traffic can't get off the DM.DIRECT LOCAL doesn't exist but is used for route.    please shed some light on this ...Very much appreciate your help. Let me know if any other output will be required?  thanks for reading
Master server not able to ping datamover