This post is more than 5 years old
261 Posts
0
7251
Master server not able to ping datamover
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:88
usdadcgfspuw00 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:88
loop 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=localhost
el31 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=localhost
el30 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
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 5th, 2011 12:00
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@ns20 ~]$ 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).
gbarretoxx1
366 Posts
1
December 30th, 2010 17:00
Hi,
Can you ping your default gateway @ 206.245.41.1 ( server_ping server_2 206.245.41.1 ) ?
Please, also post the output of :
$ server_route server_2 -l
Gustavo Barreto.
deeppat
261 Posts
0
December 31st, 2010 01:00
Thanks for giving it a look , Gustavo.
Here's route output:
server_route server_2 -l
server_2 :
default 206.245.41.1 0.0.0.0 usdadcgfspuw00
net 206.245.41.0 206.245.41.14 255.255.255.224 usdadcgfspuw00
net 198.199.241.32 198.199.241.50 255.255.255.224 astellas
net 128.221.253.0 128.221.253.2 255.255.255.0 el31
net 128.221.252.0 128.221.252.2 255.255.255.0 el30
net 10.202.1.0 198.199.241.35 255.255.255.224 astellas
net 10.0.0.0 198.199.241.35 255.0.0.0 astellas
host 127.0.0.1 127.0.0.1 255.255.255.255 loop
and the Ping response:
[nasadmin@usdad~]$ server_ping server_2 206.245.41.1
server_2 : 206.245.41.1 is alive, time= 0 ms
Peter_EMC
674 Posts
1
December 31st, 2010 02:00
You are using different Vlans (1514 and 1526) and you have set this vlan ids on the interfaces, so you have disabled vlan tagging on the switch.
Are your backup servers also sending this vlan id?
Because if there will be network packets to the usdadcgfspuw00 interface, which is 206.245.41.14, these must be vlan taged with 1526 or the Datamover will ignore it.
deeppat
261 Posts
0
December 31st, 2010 03:00
Peter Thanks for the response,
usdadcgfspuw00 is the only VDM created. What changes you suggest to make in order to enable VLAN taggin on the switch?
How can i check the backup server in havin' the same VLAN ID . Is there a comand to run on the Master server ( Unix Box) / Media server( windows boxes) to check this? i can ask the Backup guy to have a check on it.
thanks for the help
Rainer_EMC
8.6K Posts
1
December 31st, 2010 07:00
VLAN tagging needs to be configured BOTH on the Celerra AND the switch
I would suggest to work with your network administrator who knows how the network looks like and how the switch should be configured
deeppat
261 Posts
0
December 31st, 2010 10:00
Rainer thanks for the suggestion! i 'll get this verified by the network admin .Meanwhile-
One thing 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 step help provide access to the gateway?
Wishing Happy new year to all the members here!!
cxCpyIzSVS12414
43 Posts
0
December 31st, 2010 11:00
As long as VLAN tagging is not sorted on the switch. Adding route entry on the server 198.199.241.50 for 206.245.36.0/24 will not help.
deeppat
261 Posts
0
January 2nd, 2011 20:00
thank you Gustavo, Peter ,Rainer and NaveenKumar for the suggestion.
The network Admin suspects it's because of the firewall, he will add rule to it and then asked me to add the specified route to routing table.
He doesn't suspect it to be a VLAN tagging issue.
One thing i would like to know is why the Virtual data mover assigned IP address :from server_ifconfig
usdadcgfspuw00 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:88
this is the setup done : server_sysconfig server_2 -v -i fsn0
server_2 :
*** FSN fsn0: Link is Up ***
active=cge0 primary=cge0 standby=cge1
How can i figure out how the DM is configured creating a trunked interface (LACP or EtherChannel)?Can someone please help me interpret this output.
Very much appreciate your help and time
deeppat
261 Posts
0
January 4th, 2011 09:00
Hello All,
Just to update - the back up interface is able to ping the DM now , the only change was done on the firewall setting b/w the DM and backup interface.
But another problem cropped up - now, with the telnet.
I can telnet my Datamover , but, the backup server is not able to. onething, why is it showing 128.221.252.2 as the Ip?
telnet server_2 10000
Trying 128.221.252.2...
Connected to server_2 (128.221.252.2).
Escape character is '^]'.
$M#R
PuTTYhelp
================================
when i can listen to the port 10000 and telnet to it. The backup server is able listen to it but not telnet ,don't think there could a firewall or something obstructing it...
please suggest
gbarretoxx1
366 Posts
0
January 4th, 2011 11:00
Hi,
Your DM ip address is 206.245.41.14 as per your outputs above.
What is 206.245.36.10 ? Maybe the Control Station ? If yes, the CS does not have port 10000 open.
Gustavo Barreto.
deeppat
261 Posts
0
January 4th, 2011 11:00
thanks Gustavo,
The port is open and i have this verified. But for some reason backup server is not able to telnet to the port:
Trying...
telnet: Unable to connect to remote host: Connection refused
Trying 128.221.252.2...
Connected to server_2 (128.221.252.2).
Escape character is '^]'.
$M#{rPuTTY
gbarretoxx1
366 Posts
0
January 4th, 2011 11:00
Hi,
this is the internal IP address of server_2.
If from the Control Station you can connect to DM's port 10000, this means the DM is listening this port correctly.
If you can ping the DM from the server, but cannot open port 10000, I can only imagine some firewall is blocking this port.
Gustavo Barreto.
deeppat
261 Posts
0
January 4th, 2011 12:00
Thanks again..
per the EMC ( case closed now)
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:88
usdadcgfspuw00 protocol=IP device=fsn0
206.245.41.14
198.199.241.50 was considered to be the interface IP for the DM. usdadcgfspuw00 ( 206.245.41.14) is the VDM.
206.245.36.10 is the master server IP (Backup server , its HP -unix box) .And telnet is not happening from that end. I can do it from 198.199.241.50 (the one i posted above) ..
My question is when i can listen to the port and do telnet why can't the backup server? Appreciate any insight on this...thanks for your time
Rainer_EMC
8.6K Posts
0
January 4th, 2011 13:00
When you use a telnet server_2 you are using the INTERNAL network between control station and data mover
To check your external network you need to use its external name or IP ……