Hi Guys I have a customer that has

[Koolcom]

Hi Guys
I have a customer that has 5 X V7.R0 Hipath-4000 sites and they want them upgraded to the latest V7 release. The info I found is that you must first migrate from V7.R0 to V7.R1.8 and then upgrade to V7.R2 and then to V7.R2.24.33 I tried this offsite but get issue with the Licence/Mac address so I would have to do this on site. I was wondering could you not do a new install of V7.R2 offsite then upgrade to V7.R2.24.33

TIA

The Kool Guy

 

[thepfy]

Think it should be possible to do an offsite upgrade.
Our maintainers upgrade our 2x 4K from V7 to V10 off site.
On the upgrade day they just shut the existing system down and replaced the hard drives.

 

[sbcsu]

The licensing of V7 is not MAC address dependent.
It looks at the network setup and the system number.
In software management/appliance management you can make an iso backup out to a usb.
Use that USB to start up another (off site) EcoServer and go from there.
When updated bring the new hard disks to site as thephy said to change out.
Yes, the MAC addresses need to be changed on the XML file to get the new system going.

 

[Moriendi]

The V7 licence is MAC dependent. It's V8 which uses ALI format.

A RISO backup is not possible on V7 R0, that feature came with V7 R2.

If you create a disc off site you would get 30 days grace licence to do whatever you wanted to do.

It's possible to upgrade directly from V7 R0 to V7 R2, just make sure the R0 has the current hotfixes before you start. Take a RAID backup via the Portal before you start and take the disc out in case you need to go back, and expect about an hours downtime.

Disk swap is fine too but you'll still get a delay where it loads new loadware onto the cards, so consider preloading the cards like SLMA STMI etc with the newer loadware before you start. You can take the newer loadware from V7 R2 and use it on R0, the 4K will not catch fire.

If you make a disk swap any APEs you have will not automatically upgrade themselves, they will have to be done manually. HF33 will take some time to apply so if you make a disk swap, you would definitely save some time having done that first. But going from HF0 to HF33 is not a problem, it's just time.

 

[sbcsu]

Thanks Moriendi - I somehow knew that my incorrect answer would bring out the correct answer
Apologies for my incorrect information - too many versions now.
You do however (as you say) get 30 days grace in which you can re-host the licences that you had for your original V7

 

[Koolcom]

Thanks guys for the feedback much appreciated will be starting this task next week

The Kool Guy

 

[Moriendi]

You shouldn’t need to rehost your licence, it’s the same file for V7 R0 as V7 R2 and I guess you are sticking with the same processors so MAC doesn’t change. Where you might have some difficulty is if the SLES licences have expired, it will stop you upgrading the platform. If that’s the case you’ll have to get new licences or use the 30 day grace on lab processors.

 

[Koolcom]

Hi Guys
I managed to install V7.R2.24.33 on my system with the regen run in as well went to customer to swop HDD but system won't load Linux seems to go in a loop see attachment. Is it not a hardware issue my DSCXL is the old version and the customer has the later version, the one with one HD on DSCXL board and the other HD on a seperate tray with a external cable connecting to the DSCXL.

I hope this makes sense

The Kool Guy

 

[Moriendi]

It sure looks like a hardware error. What model of HD is it? The release note for V7 will tell you the allowed types. Did you drop it getting out of the car ?!

 

[Koolcom]

It was old recovery HD's that I used but it's strange it boots fine on my test unit DSCXL2 but not on the DSCXLV2

The Kool Guy

 

[Moriendi]

You didn’t actually answer the question.

 

[Koolcom]

TOSHIBA MK2561GSYB HDD2F02 A SLO1 T and I did not drop the HDD's

The Kool Guy

 

[Moriendi]

OK so MK2561GSYB is absolutely supported, it's the correct HD.

But this looks like hardware error.

Strange if it boots on your lab 4K because it looks like HD problems. Maybe SMART info from when it's running in the lab might show something.

If this was me I'd swapping parts, cable, DSXCL etc, find out where the error comes from.

Did you get the HD from Unify? Even with the same model number, you might have one with different firmware/chip combinations etc, unless you bought from Unify.

 

[Koolcom]

Hi
As to your question about HD they were old recovery HD's but all is working now it was the SATA cable that was not seated properly thanks for the advice


The Kool Guy