Aaron,  Firstly, eth2 is reference to a Control Station interface which you have also configured as the mgmt interface used to remotely bring up Unisphere on the simulator.  It would not be the appropriate interface to run naviseccli commands against. naviseccli (block) commands are run against Storage Processor's and not Control Station mgmt interfaces.  However, the VNX/Celerra simulator doesn't have working/accessible captive SP's, which is part of a real unified array; and is therefore, made available to test file-only features (VNX OE for File/DART).  In anticipation of a follow-up question, the reason as I understand it preventing us from providing a block simulator (VNX OE for Block/FLARE) is due to Windows licensing.  On a real array, you'd have reference to public IP's assigned to each of the SP's (accessible via the Control Station mgmt port(s) via proxy ARP) which in turn each have the navisphere agent running, listening and responding to naviseccli commands (via port TCP/6389).   Even if you were to dig up reference to any private IP's used as part of the internal routing, you'd continue to find that nothing is running that can respond to external naviseccli commands.  Finally, I simply wanted to mention that I noticed in one of your screenshots the simulator you are currently running is v7.0.35.  There is a newer simulator running v7.1.47-5 which is available from support.emc.com.  However, it is still "file-only".
hello:  we have been using a CLARiiON so far, with Unisphere for use via a GUI and using Navisphere CLI (naviseccli) when a CLI has to be used. we would now like to check if our software is compatible with the new VNX.  we got a brilliant idea of using the VNX/Celerra Simulator with naviseccli Block commands to see if our existing software works. unfortunately, it seems that thee Simulator does not support naviseccli. there is no problem with Unisphere.  Simulator: login: root/nasadmin > ifconfig eth2 192.168.65.128  Local Host > ping 192.168.65.128 64 bytes from 192.168.65.128: icmp_seq=0 ttl=64 time=4 ms  > naviseccli -Address 192.168.65.128 -User nasadmin -Password nasadmin -Scope global getrg Error occurred while trying to connect: '192.168.65.128'. Message : Invalid server certificate: certificate not trusted.  > naviseccli -Address 192.168.65.128 -User nasadmin -Password nasadmin -Scope global -port 2162 getrg A network error occurred while trying to connect: '192.168.65.128'. Message : Error occurred because connection refused. Management Server is not running.  well, it says that the Simulator has one Control Station and one or two Data Movers. afaik, naviseccli Clariion commands would only be processed by a Service Processor (SP), which is not in the simulated Celerra. so, will the naviseccli commands work?  how can we get naviseccli commands to work with the Celerra Simulator?  thank you in advance.  Happy New Year 2013!  Aaron
does the VNX/Celerra Simulator support naviseccli?