Unsolved

This post is more than 5 years old

3404

October 30th, 2012 06:00

Incoming Ping EMC with Servers

EMC storage I have not get it to work.

I tell you how everything is set a bit to see if I can help.

I have several network and configured with VLAN switch.

The Celerra IP is 192.168.15.2.

At the interfaces I have

128.221.252.2.Network tcp-Block-It 128.221.252.100.58709 ESTABLISHED
128.221.252.2.Network tcp-Block-It 128.221.252.100.58710 ESTABLISHED
ESTABLISHED tcp 128.221.252.2.7777 128.221.252.100.38599
ESTABLISHED tcp 128,221,252,100,739 128.221.252.2.mac
128.221.253.2.Network tcp-Block-It 128.221.253.100.54910 ESTABLISHED

and then two more that are:

server_2 192.168.14.201
server_2 192.168.14.202

When pinging from a machine on the same network such as 192.168.14.205 not reach these ips them up.

I'm not sure that can happen I'm new at this.

Thanks for your help

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

October 30th, 2012 06:00

post output from "sever_ifconfig server_2 -all" and "server_route server_2 -l"

6 Operator

 • 

8.6K Posts

October 30th, 2012 06:00

Typical causes for this:

- VLAN or subnet config incorrect on the VNX or the switch or the client

- Mixed up cables

- Routing wrong or missing default route on the VNX

The Celerra/VNX doesn’t use the routing table when responding to a ping – it uses reflect mode (by default) which sends the packet back through the same interface and MAC that it came from.

That’s why often even with a misconfigured network the VNX/Celerra will respond to a ping but the other way doesn’t work.

Also remember that control station and data movers are separate objects each with its own interface config and routing table.

If you need to troubleshoot the data mover networking you need to use the server_ping, server_route, … command.

Rainer

October 30th, 2012 07:00

With server_route server_2 -l output next:

default 192.168.114.254 0.0.0.0 nfs_svc_interface

net 192.168.114.0 192.168.114.201 255.255.255.0 nfs_svc_interface

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

host 127.0.0.1 127.0.0.1 255.255.255.255 loop

October 30th, 2012 07:00

The name of my data is server_2 organizers

In making the server_route server_2-l returns me this:

server_route server_2 -l

server_2 :

default 192.168.114.254 0.0.0.0 nfs_svc_interface

net 192.168.114.0 192.168.114.201 255.255.255.0 nfs_svc_interface

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

host 127.0.0.1 127.0.0.1 255.255.255.255 loop

interfacesweb.jpg

October 30th, 2012 07:00

Sorry don´t answer:

server_ping server_2 192.168.114.205

server_2 :

Error 6: server_2 : No such device or address

no answer from 192.168.114.205

October 30th, 2012 07:00

But if I run it on command:

  server_2 server_ping 192.168.14.201 192.168.14.205
server_2: 192,168,114,201 is alive, time = 0 ms

I said to respond correctly

6 Operator

 • 

8.6K Posts

October 30th, 2012 07:00

Thats a strange error – did you rename your data movers ?

What does nas_server –l say ?

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

October 30th, 2012 08:00

can you ping the default gateway ?

server_ping server_2 -interface nfs_svc_interface 192.168.114.254

October 30th, 2012 08:00

And the configuration with command server_ifconfig server_2 -all is:

server_2 :

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:1e:3b:93 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:1e:3b:92 netname=localhost

loop6 protocol=IP6 device=loop

         inet=::1 prefix=128

        UP, Loopback, mtu=32768, vlan=0, macaddr=0:0:0:0:0:0 netname=localhost

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

isci_svc_interface protocol=IP device=trk1

         inet=192.168.114.202 netmask=255.255.255.0 broadcast=192.168.114.255

        UP, Ethernet, mtu=1500, vlan=5, macaddr=0:60:16:1f:6b:e

nfs_svc_interface protocol=IP device=trk0

         inet=192.168.114.201 netmask=255.255.255.0 broadcast=192.168.114.255

        UP, Ethernet, mtu=1500, vlan=5, macaddr=0:60:16:1f:6b:10

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

October 30th, 2012 08:00

is VLAN 5 correct, is the switch port tagged for VLAN 5 as well ?  Is 192.168.114.254 correct default gateway ?

October 30th, 2012 08:00

This is the result:

server_ping server_2 -interface nfs_svc_interface 192.168.114.254

server_2 :

Error 6: server_2 : No such device or address

no answer from 192.168.114.254

No ping the default gateway !!!!

October 30th, 2012 08:00

Yes, Ports are configurated correctly in switch.

And 192.168.114.254 is the default gateway yes too !!!!

October 30th, 2012 09:00

Hi Rainer,

The interface name is correct and the DM name is server_2.

I don´t Know it´s possible this failed !!!!

Thanks

6 Operator

 • 

8.6K Posts

October 30th, 2012 09:00

Dynamox your’re right – I just never noticed that error 6 before

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

October 30th, 2012 09:00

post output form this command:

server_sysconfig server_2 -virtual -info trk0

0 events found

No Events found!

Top