NS120 installation

you would use it as any other Clariion array, use Navisphere to register hosts, create raid groups and LUNs. Did you have something specific in mind ?

Thanks Dynamox,

Ok , No problem with Clariion, just that I am not used to Celerra,

I am looking for steps to install the control station manually from the console (ascii).

Regards

Consty

the unit should've come with a CSA cd, it will walk you through getting everything setup.

do you mean install as in re-install the software of just configure like setting the IP adresses ?

what state is the system in? was is properly installed and configured with CSA ?

Hi,

It was just setting the IP but the guy who worked on it said he did not

see the Celerra when launching CSA, now have to go there and see what is wrong.

All the equipment connected PC, Celerra, ... are connected to the same switch.

Regards

Consty

If this is a new machine I would suggest to first do some troubleshooting and get CSA to work

often its a problem with the Windows box that you run CSA from like a firewall enabled or wrong network config

Info for that can be found on Powerlink
Home > Support > Product and Diagnostic Tools > Celerra Tools > Celerra Startup Assistant

and in the knowledgebase

If you are an authorized partner you can get the information about manual setup in the Phase 1/2/3 installation guides on Powerlink

I would strongly suggest to not give up on CSA that easily - it does a lot of config work that otherwise can be forgotten

Rainer

probably someone used CSA first and it didnt complete, then you ran CSA from a different computer

once it did some steps it removes the skript that answers the broadcast so you wont discover the Celerra again from a new CSA

it will however remember the config info on the first CSA computer and you can resume from there

I just configured a NS-120 with CSA today

first it discovered the NS-120 fine but failed cable check for the Blade

turned out the internal management cables were reversed

once I fixed the cables I started CSA agan and selected existing config

at that point the CS had an IP address and I could ssh in but NAS services werent running

so CSA failed again

reboot - CSA failed again

turned out the FC cables between blade and SP were wrong as well

once I fixed that and rebooted NAS services got started

I could run CSA again, continue installation, it did the cable checks again and continued setting up everything just fine

so CSA works fine it you let it work as intended

well - it sounds like CSA was run partially - otherwise you would get a warning when logging in

once CSA has done the first config steps it will remove the S96cablecheck rc skript that answers the CSA broadcast

since it looks like you are going for a new install you first have to do a backend cleanup

look for a Primus article that details the steps, then re-install DART and run CSA again

Thanks Rainer,

I agree with you, I am still looking for the reason why CSA is not working,

There is a very quick black screen displayed before the csa screen, then

the system searches for a Celerra and displays the message "ERROR:celerra not found"

I also connected to the Celerra via serial port and got a screen, I proceeded with fresh install

Option and modified only the Lan IP information of the name of the Celerra, everything was ok

except that at the end I got the message "Celerra has detected an existing storage group

(Celerra_emcnas-i0) with possible Control LUNs, please cleanup this existing Storage Group

and restart the installation". Now I can "ping" the Celerra.

Any idea ?

Thanks

Consty

Yes, someone used CSA first and it did not complete, he even re-installed the control station O.S.

Yes, I ran CSA from a different computer. The trouble is that the guy travelled and I cannot get the

computer he used.

If I have well understood what you say, I should re-install the DART (data mover) again and rerun

CSA. I'll appreciate more information  about DART installation.

Thanks

Consty

And that is right about the point where you can't continue any further on your own.

Normally, CSA failures can be recovered (we have several Knowledgebase solutions on how to recover from a failed CSA run).  You should try running through one of those procedures.  The one I prefer is emc166265.  It will require you connect to the Control Station either over SSH or using your serial connection.  Near the end of the procedure, you have to use your serial cable.

If you successfully run through this procedure, you will be able to re-run CSA from scratch.  If this fails, there will be nothing more you can do on your own; you will need to open a Service  Request and have someone come out to the site to do the re-install.  DART code is not yet customer-installable, so doing a full reinstall without using CSA is not something we can assist you with here in the forum.

Hi,

We are preparing NS-120 installation and review the doc "P/N 300-007-881 Rev A04"

The CSA worksheet  (page 32) listed public address  "Storage processor A" IP address, and "Storage processor B" IP address.  But the page 3 listed them as internal IP address.  Which is correct?

In addition, Page 31 listed "blade external network".  Do we  assign IP address to Blade server?

We are preparing NS-120 installation and review the doc "P/N 300-007-881 Rev A04" The CSA worksheet  (page 32) listed public address  "Storage processor A" IP address, and "Storage processor B" IP address.  But the page 3 listed them as internal IP address.  Which is correct?

The system ships with factory-installed internal IP addresses for the SP's.  These addresses are in place so that CSA can initially connect to the SPs and assign them public IP addresses.  But as you are probably noticing, the SPs are not connected to the public LAN; they are cabled internally only.  So why are there public addresses?

Don't forget the note on page 32:

Public IP addresses for your storage processors are required to use the Navisphere Service
Taskbar on both Fibre Channel (FC) and non-FC enabled models for routine array maintenance. The
IP addresses must be on the same subnet as the Control Station.

The SP's use proxy-ARP network routing through the public LAN connection on the Control Station.  The one physical cable serves three MAC addresses, and thus three IP addresses.

In addition, Page 31 listed "blade external network".  Do we  assign IP address to Blade server?

The CSA worksheet has items in shaded boxes and items in unshaded boxes.  The "Blade external network settings" on page 31 are in a shaded box (except for the NTP server).  This means that the information listed there (Blade DNS domain, blade primary DNS server, and blade secondary DNS server) are auto-populated by CSA.  Again, reference the note on that page:

Note: The CSA pre-populates values based on auto-discovery from your Windows client.
Shaded areas are values that will be auto-discovered based on your system and network
environment; if auto-discovery fails, you need to provide the information manually.

If, for some reason, CSA can't figure out the network information of the client running CSA, you will have to manually enter things like DNS servers and DNS domains.  The items in the unshaded boxes in the worksheet have to be provided to CSA, such as the IP address of the Control Station.  Fill in all of the unshaded areas in the worksheet so that you can use them when you run CSA.

To answer your specific question, you will be assigning IP addresses to the Data Movers (blades).  The blades contain the servers that will actually serve your data, so they will need IP addresses on your network.

-bill