CS cant ping its gateway

if the CS aka Controlstation can not ping anything of its network, then you need to check the network of the CS.

server_route is configuring the network of the datamovers, not the Controlstation.

Thanks for the clarification @Peter_EMC so if I cant ping anything off server_ping its the xblade correct?  and if i can SSH into control station odds are networking there is fine.

control station and datamovers have separate network interfaces, separate routing tables etc. Typically on a brand new VNX i configure a default gateway (as you just tried) but is that a valid default gateway ?

Do you already have a default route?

What does server_route server_2 -list  and server_ifconfig server_2 -a   look like?

yes, server_ping is the network of the datamovers aka xblades.

What is the output of the 2 commands Mark was asking?

Are you sure, there are network cables connected between the xblade and your network switch?

The "invalid argument" in this situation is actually "10.200.17.1" as your syntax looks good otherwise.  You will find that you don't have an interface supporting the subnet that 10.200.17.1 resides on; if it did, then the command would complete successfully.  While the error message could be a bit more intuitive, there is error checking to verify this as it needs to assign the interface that would be used to the access the default gateway (as seen in the fifth column of server_route -list), but that is where this command's error checking ends.  It doesn't actually verify the gateway is accessible so whether or not you actually have it cabled doesn't matter (at this point of course).

Furthermore, if a default gateway was already assigned, running the command again would overwrite it and not error so I would recommend that you don't already have one defined and verify that this wouldn't have possible consequences assuming you were in production (but I doubt you are).

Therefore, as already requested above, perform the following:

1) server_route server_2 -list

Again, if a default gateway already exists it would simply overwrite it; however, this does not explain the reason for the "invalid argument" above.

2) server_ifconfig server_2 -a

Again, as noted above, you will find that you don't yet have an interface supporting the subnet that 10.200.17.1 resides on and will need to create it if you want this to be your default gateway.

I love the Celerra - but it's cryptic error messages like this should really be more robust.... Actually giving the real reason for the failure...