SMA upgrade to Windows 2003 (Management Server)

[Fabian_Nowee]

I'm currently struggeling with two SMA's. CPU% are at 100, doesn't want to reboot, ISEE will not install etc.

The 2 SMA's are a mess. two options, use the restore CD or make a new management server based on Windows2003.

Is this possible, are there restrictions?

btw, the customer has 4 eva's & 2 msa1500's fully configured (48TB)

thanks in advance.

[Richard Perez]

Please use the restore CD

BTW, why an upgrade to 2003 could solve the problems you are having? Do you know if 2003 is supported in the SMA?

[Fabian_Nowee]

some of the advantages windows2003 management gives is that i can use other tools (MRTG etc) and have an heterogenic Management server. (in combination with ESE).


It's a 2.4Ghz xeon 2GB machine, should be capable of many nice things. CVE 4.0 is supported on a standalone Windows 2003 server.

[Uwe Zessin]

Richard,
my understanding is that he does a new installation of Windows Server 2003 (with an appropriate license). The important difference between an SMA and a standard ProLiant server is a different serial number range so that the restore CD does only install on the SMA hardware.

CV-EVA V3.3.* is supported on a standard server, too.

[Fabian_Nowee]

Yes, Uwe, a new installation and 3.3.* is also possible, yes.

I guess the additional license will not cost too much.

I "hear" that there are limitations about the number of eva's you can manage, 4 instead of 16, is this correct?

Is the Bios limited? or is this only applicable on the NAS Machines?

[Uwe Zessin]

Yes, I've read about 4 EVAs on a non-SMA management server, too - should be in one of the EOL documents available through the SMA/ OVSOM web pages, but I have heard that this limit is about to be lifted in the future. My guess is that they simply did not test more, because the CPU or memory in a standard ProLiant should not be a problem.

I don't think the SMA's BIOS is limited - it has just a different serial number range for the reason I've explained above. There's been some talk about replacing the OSM with a standard Windows OS in some document. I don't recall any details, because I have not bothered about this process - there is only so much time :-(

I've never seriously considered a NAS box for EVA management - it might have changed now, but when I checked it, not all required service tools were supported on the NAS box. Perhaps somebody who has gone that route can share his/her experience?

[Fabian_Nowee]

for the record, we are not considering a nas box to use for EVA management.

But, í'm thinking to keep one SMA working normaly and perhaps to upgrade the second SM

[Matt Tourney]

Gentlemen, I just received the attached advisory in my inbox that explains how to convert an SMA platform into a general purpose server AND be supported by HP.

I hope this helps!
Matt

[Fabian_Nowee]

thanks!

Is there also something about limit's
(number of eva's) documented?

[Uwe Zessin]

Yes. If you download the OVSOM specifications, it's at the bottom of page 4 of the .PDF file (version 10).

[Craig Howe_1]

Hi

Back to the first post, we had problems with 100% cpu because of installing YEAH on the SMA. (Yet Another Event Analyser) It mentioned in the new release that the 100% CPU bug would be fixed, but these versions were no better than previous.

Uninstalled it and went with the alternative and things were fine.

[Fabian_Nowee]

Are there already people who have done this?

W2k3 standard in combination with CVE 4.1

[Steven Clementi]

I am running 3 separate Storage Management Servers...

Windows Server 2003 SP1
Command View EVA 4.1.1.3
SANSurfer
RSM 1.2
Access to vdisks (for testing)


no problems, works great.

Steven

[Uwe Zessin]

Yes, with 3.3.?, 4.0, 4.0.1, 4.1 + 4.1.1
Works fine.

[Steven Clementi]

Win2k3 Standard... that is.

Started out with CV-EVA 4.0 as well... so I know what Uwe says is try... has 4.0, 4.0.1, 4.1 and 4.1.1 and everything else inbetween.


Steven

[Fabian_Nowee]

So based on SMA model III hardware?

(just to make sure, I just got an error from the restore CD, so there's probably no other solution :) )

[Steven Clementi]

Oh... not at all.. I am using DL380G4's.

I haven't converted an SMA.


Steven

[Steven Clementi]

You should not need to use the restore CD. In fact, you want to use the Smart Start CD and a Win2k3 Standard cd and set the box up like you would set up a normal Proliant.


Steven

[Fabian_Nowee]

I turned today a SMAIII in a general Purpose server. (W2k3 no SP1 because of 3025)

I installed CVE4, but no default page?
I Installed IIS, reinstalled CVE, but still no management page

I tried all user and installation guides, but no chapter about IIS settings....

[Uwe Zessin]

IIS??

CV-EVA lives in the ProLiant system management home page and its web server. You either install via SmartStart or put a PSP on the system.

[Fabian_Nowee]

Thanks, it works.

I was comparing it with Windows2000.. our primary sma is still running on sma v2.1 w2k cve 3.3.3

I see it now in our System Management HomePage... great!