problem with eth0 and eth1

The eth0 and eth1 is used by Celerra control station. Please follow EMC document emc252713, this document will explain what to do when 'The Control Station eth0 interface is not configured."

this is a simulator

Sorry for possibly stating the obvious, but I would like to remind everyone that everything mentioned above are specific to the Celerra/VNX simulators.

ramasingh,

Please review the "Installation and Configuration Guide" on PowerLink.  It is available via the following breadcrumb trail:

Home > Support > Product and Diagnostic Tools > Celerra Tools > Celerra Simulator

In the paragraphs above, click on the hyperlink "installation instructions".   If you step through the short guide, I assure you that you will have a running simulator.  For instance, one of the first steps is to run the command:

netconfig -d eth0

For the simulator, it uses eth0 for the Control Station IP.  In regards to eth1, this will be used as one of the datamover ports and you will have to bind it via the following command:

./configure_nic server_ -a eth

The guide also mentions which VMnet adapter each bind to.

Again, please walk through the guide from the beginning.  An alternative is to use Nick Weaver's UBER edition which is a spin-off of the original simulators (there is a version 5.6 which you are trying to configure as well as a version 6.0) which simplifies assigning the interfaces and also are tweaked to perform much better than the originals.  You can use your favorite search engine to find copies of these.

Yes  i'm using simulator..

It's showing eth0 is down at the time of bootup process...

So Rama_singh, you followed the guide and as instructed run the commands (as a reminder, these steps are specific to the simulator):

netconfig -d eth0

ifup eth0

I'll assume you are then able to access the control station, then upon reboot it starts down (until you manually keep running ifup eth0 which you should not have to)?  How much of the guide have you followed and completed without error?

Another thing to review is to check the "Virtual Network Editor" in VMware Workstation/Player and check the configuration of VMnet0 which maps to eth0 (as described in the above mentioned guide).

i was used below command in simulator it's giving error "command not found"

netconfig -d eth0

ifup eth0

Rama_singh,

Please follow the installation document that was mentioned above. Location via breadcrumb trail supplied above.  It is only a handful of pages, and if followed properly, I assure you that you'll have a running simulator (Celerra or VNX).  On page 15, before it discusses how to configure the mgmt IP using netconfig, it states:

Log in as root using the default password nasadmin to configure

the virtual external network interface

I'll assume you are logging in as nasadmin and issuing su to gain root access.  netconfig is not in the path for nasadmin (and that is being carried over if you su to obtain root access).  Yes, you could also provide the full path to netconfig or issue "su -", but I'd just follow the document and not get creative at this point.  After you run netconfig, try accessing Unisphere.  Only if you can't, then issue the ifup command (as root).

Keep in mind, for the initial setup, the steps are unique to the simulator.  For instance, you wouldn't run netconfig to initialize/Re-IP an actual array, eth0 is not the mgmt IP, etc.  Therefore, for just the initialization of the simulator, I would stick to the installation guide.

Thanks crystopher, I have set 192.168.240.1 to access unisphere, but it asking about host name and password..

But i have one other problem as well.Please help me to solve this problem.

when our AD (Active Directory) is in Physical server, Users are able to connected to the EMC server (Storage Server) without any issue.

Now we are going into VMware virtualization, so we moved the AD server to virtual server.
After the moving the AD in Virtual server, User's are not able to connected the EMC server. It says "Access is Denied". But all servers are connecting fine. Only EMC server is not getting connected.

check time skew, also make sure virtualized VM AD controllers to do not use time from ESX server.

Take a look at the data mover logs with server_log

Most likely a time problem