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.

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

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.

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

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

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!!

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.

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

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