Very Computer

by **Dan Gahlinge** » Fri, 14 Jun 2002 04:09:25

We have an ultra-2 running solaris-8 connected to a storedge A1000
drive array, and we're replacing the ultra-2 with an E450 running
Solaris-9.

I understand Solaris-9 has a lot of the volume manager built-in
(disksuite no longer needed), etc, but the ultra-2 currently has raid
manager installed (not sure which version).

when we move the drives over (we don't want to lose the contents),
what do I need to do to get it functional (ie: be able to mount the
drives on the E450) ??

I've looked everywhere for documentation, but solaris-9 is a bit too
new it seems for anything useful, especially given what I'm trying to
do.

appreciate any help, thanks

by **Akop Pogosia** » Fri, 14 Jun 2002 04:27:38

> We have an ultra-2 running solaris-8 connected to a storedge A1000
> drive array, and we're replacing the ultra-2 with an E450 running
> Solaris-9.
> I understand Solaris-9 has a lot of the volume manager built-in
> (disksuite no longer needed), etc, but the ultra-2 currently has raid
> manager installed (not sure which version).
> when we move the drives over (we don't want to lose the contents),
> what do I need to do to get it functional (ie: be able to mount the
> drives on the E450) ??

The Solaris volume manager is a software RAID implementation while the
A1000 has a built-in RAID controller. Raid Manager software is
required for configuring and monitoring Sun A1000 disk arrays, so you
will need RAID Manager installed on that E450. Since Solaris 9 is so
new, I don't even know if Raid Manager is supported on it yet. Be
-very- careful with A1000/RM as the management software is very
fragile and requires different combinations of Solaris and Raid
Manager patches and A1000 and server firmware revisions depending on
what version of Raid Manager you run and the OS that you use and how
you connect to the disk array. Even doing innocent things like
installing patches or firmware updates in a wrong order might render
your A1000 useless. Read all of A1000/RM documentation on sunsolve
before making any changes.

--
Akop Pogosian

This space has been accidentally left blank.

by **Darren Dunha** » Fri, 14 Jun 2002 04:39:52

> We have an ultra-2 running solaris-8 connected to a storedge A1000
> drive array, and we're replacing the ultra-2 with an E450 running
> Solaris-9.
> I understand Solaris-9 has a lot of the volume manager built-in
> (disksuite no longer needed)

I think you could reprhase that as "disksuite renamed".

, etc, but the ultra-2 currently has raid

Quote:> manager installed (not sure which version).
> when we move the drives over (we don't want to lose the contents),
> what do I need to do to get it functional (ie: be able to mount the
> drives on the E450) ??

You can probably mount the luns on the 450 without any software, but
you'll want to put RM on the box so you can manage it. At least so you
can be notified of any problems.

Quote:> I've looked everywhere for documentation, but solaris-9 is a bit too
> new it seems for anything useful, especially given what I'm trying to
> do.

Just go to sun.com and look under storage for software. You should be
able to download the latest copy of raid manager and install it.

It's always a good idea to go to sunsolve.sun.com and run the storage
PatchPro to find what patches are necessary.

--

Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

by **Dan Gahlinge** » Fri, 14 Jun 2002 06:39:10

On Wed, 12 Jun 2002 19:27:38 +0000 (UTC), Akop Pogosian

>The Solaris volume manager is a software RAID implementation while the
>A1000 has a built-in RAID controller. Raid Manager software is
>required for configuring and monitoring Sun A1000 disk arrays, so you
>will need RAID Manager installed on that E450. Since Solaris 9 is so
>new, I don't even know if Raid Manager is supported on it yet. Be
>-very- careful with A1000/RM as the management software is very
>fragile and requires different combinations of Solaris and Raid
>Manager patches and A1000 and server firmware revisions depending on
>what version of Raid Manager you run and the OS that you use and how
>you connect to the disk array. Even doing innocent things like
>installing patches or firmware updates in a wrong order might render
>your A1000 useless. Read all of A1000/RM documentation on sunsolve
>before making any changes.

Don't want firmware or software updates as such, and we need to save
the contents exactly as it is. Simply unplug from the ultra-2 and plug
into the 450.

I thought (perhaps mistakenly) that Solaris-9 had all the raid
management, etc built-in ? I know disksuite and volume manager
are built-in.

In either case, I have reviewed what little documentation Sun has on
their website and found only one useful link labelled "RAID Manager
6.22.1" which I'm not even sure is the latest version.

There is a Storedge RAID manager upgrade procedure included in this
document which I will definitely review.

Dan.

by **Dan Gahlinge** » Fri, 14 Jun 2002 06:41:22

On Wed, 12 Jun 2002 19:39:52 GMT, Darren Dunham

>I think you could reprhase that as "disksuite renamed".

yes, that mess does get very confusing, especially to me.

Quote:>You can probably mount the luns on the 450 without any software, but
>you'll want to put RM on the box so you can manage it. At least so you
>can be notified of any problems.

We tried connecting it to the 450 running solaris 8, and even running
the EXACT same copy of RM, installed with the EXACT same configs, etc
but we could not mount any drives off the storedge at all...

this is not good

Quote:>Just go to sun.com and look under storage for software. You should be
>able to download the latest copy of raid manager and install it.

>It's always a good idea to go to sunsolve.sun.com and run the storage
>PatchPro to find what patches are necessary.

I'll have to lookup both of these, thanks

Dan.

by **Darren Dunha** » Fri, 14 Jun 2002 07:08:11

>>You can probably mount the luns on the 450 without any software, but
>>you'll want to put RM on the box so you can manage it. At least so you
>>can be notified of any problems.
> We tried connecting it to the 450 running solaris 8, and even running
> the EXACT same copy of RM, installed with the EXACT same configs, etc
> but we could not mount any drives off the storedge at all...
> this is not good

Heck, you should be able to see the LUNs from the OK prompt with a
probe-scsi-all. If you can't see that, then something's wrong.

Oh.. unless you've done the RM install, your sd.conf file will generally
only have entries where lun=0. With RM, it'll populate that out with
entries with higher lun numbers. Until that is done and the machine
rebooted, you'll never see luns above 0.
--

Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

by **Dennis Clark** » Fri, 14 Jun 2002 08:34:39

> On Wed, 12 Jun 2002 19:39:52 GMT, Darren Dunham

> >I think you could reprhase that as "disksuite renamed".

> yes, that mess does get very confusing, especially to me.

> >You can probably mount the luns on the 450 without any software, but
> >you'll want to put RM on the box so you can manage it. At least so you
> >can be notified of any problems.

> We tried connecting it to the 450 running solaris 8, and even running
> the EXACT same copy of RM, installed with the EXACT same configs, etc
> but we could not mount any drives off the storedge at all...

> this is not good

> >Just go to sun.com and look under storage for software. You should be
> >able to download the latest copy of raid manager and install it.

> >It's always a good idea to go to sunsolve.sun.com and run the storage
> >PatchPro to find what patches are necessary.

> I'll have to lookup both of these, thanks

> Dan.

Dan, we have already spoken about this at length. You NEED Raid Manager version 6.22 at
least and probably 6.22.1 for Solaris 9. As I have already explained, the Solaris 9
release is very new and you are out there on the edge a bit with this. You should stay
with Solaris 8 fully patched and use Solstice Disksuite with Raid Manager 6.22 on the
A1000.

Dennis Clarke

by **Dan Gahlinge** » Fri, 14 Jun 2002 09:07:30

On Wed, 12 Jun 2002 22:08:11 GMT, Darren Dunham

>Heck, you should be able to see the LUNs from the OK prompt with a
>probe-scsi-all. If you can't see that, then something's wrong.

yes the LUNs show up at the ok prompt running the probe.

Quote:>Oh.. unless you've done the RM install, your sd.conf file will generally
>only have entries where lun=0. With RM, it'll populate that out with
>entries with higher lun numbers. Until that is done and the machine
>rebooted, you'll never see luns above 0.

yes, but we moved the config over from the other machine,
and rebooted. couldn't see them.

I think the problem is more likely the fact that on the E450
it's a different controller, channel, etc etc etc

So /dev/dsk/c1t4d2s0 or whatever will be completely different
on the E450.

And that may be a bigger hassle than anything, I have no idea
how to figure out what the units will be.

On the brighter side, I got RM 6.22.1 installed on Solaris9 (test
system) without a hitch, flawless install.

Simply amazing that something worked first try.

That may make things easier, I have no idea.

Dan.

by **Dan Gahlinge** » Fri, 14 Jun 2002 09:14:14

On Wed, 12 Jun 2002 19:34:39 -0400, Dennis Clarke

>Dan, we have already spoken about this at length. You NEED Raid Manager version 6.22 at
>least and probably 6.22.1 for Solaris 9. As I have already explained, the Solaris 9
>release is very new and you are out there on the edge a bit with this. You should stay
>with Solaris 8 fully patched and use Solstice Disksuite with Raid Manager 6.22 on the
>A1000.

Yes. Well, I have RM 6.22.1 installed on Solaris9 (test system) now.
perfect flawless install. Simply amazing.

As for sticking with Solaris8, it's not really an option. And given RM
seems to be working with Solaris9 so well (as well as I can test
anyhow), well, why not ?

Solaris9 is a full release and not a beta, so it's not really an edge
product. at least, not in my opinion. Sure, the packages on
sunfreeware aren't there yet, but the solaris8 ones work just fine,
and the v9 ones will be out in a timely fashion.

There are actually various important reasons for the upgrade, none of
which are appropriate to this channel.

And anyhow, it makes little difference. I tried the solaris8 route
with RM installed, could see the LUNs, but could not mount the drives.
the /dev (dsk and rdsk) entries didn't even exist for the LUNs, so I
couldn't mount them if I wanted to.

That was the major problem we had last month when we attempted
migration. probe-scsi-all showed the LUNs, but they were unmountable.

As I said in the previous message, it seems to have more to do with
the controller and channel identification than anything else.

I'm hoping that a fresh install (from scratch) of solaris9 with the
A1000 connected will allieviate the issues. And hopefully wont blow
away the data. (thank god for backups!)

So if you have any bright ideas, let me know, I'll keep plugging away
here.

Dan.

by **Dennis Clark** » Fri, 14 Jun 2002 10:05:12

Quote:> Yes. Well, I have RM 6.22.1 installed on Solaris9 (test system) now.
> perfect flawless install. Simply amazing.

OK. We can put that in the books then as a tested product.

Quote:
> As for sticking with Solaris8, it's not really an option. And given RM
> seems to be working with Solaris9 so well (as well as I can test
> anyhow), well, why not ?

> Solaris9 is a full release and not a beta, so it's not really an edge
> product. at least, not in my opinion. Sure, the packages on
> sunfreeware aren't there yet, but the solaris8 ones work just fine,
> and the v9 ones will be out in a timely fashion.

> There are actually various important reasons for the upgrade, none of
> which are appropriate to this channel.

OK. You have an agenda then and Sol8 is out. Fine.

Quote:
> And anyhow, it makes little difference. I tried the solaris8 route
> with RM installed, could see the LUNs, but could not mount the drives.
> the /dev (dsk and rdsk) entries didn't even exist for the LUNs, so I
> couldn't mount them if I wanted to.

That seems strange. I have had reasonably consistent success with RM6.22[.1] on Sol8 with the A1000 but if Sol9 is working well for
you then may the force be with you!

Quote:
> That was the major problem we had last month when we attempted
> migration. probe-scsi-all showed the LUNs, but they were unmountable.

> As I said in the previous message, it seems to have more to do with
> the controller and channel identification than anything else.

What does drivutil [ -i | -I | -l ] array_id report for you?

Quote:> I'm hoping that a fresh install (from scratch) of solaris9 with the
> A1000 connected will allieviate the issues. And hopefully wont blow
> away the data. (thank god for backups!)

Not a bad idea to disconnect the A1000 during the install. After the initial reboot you can always attach it and then do a devfsadm
-C -c disk -v to create/update the device path.

Quote:
> So if you have any bright ideas, let me know, I'll keep plugging away
> here.

I haven't had a bright idea in years. I'm still waiting for one however. :)

Dennis

by **Dennis Clark** » Fri, 14 Jun 2002 10:06:11

Sorry about the wide post there. I'm back to 78 chars now.

by **Dan Gahlinge** » Sat, 15 Jun 2002 00:31:12

On Wed, 12 Jun 2002 21:05:12 -0400, Dennis Clarke

>OK. We can put that in the books then as a tested product.

installed yes, fully functional - hmmmm ? :)

Quote:>That seems strange. I have had reasonably consistent success with RM6.22[.1] on Sol8 with the A1000 but if Sol9 is working well for
>you then may the force be with you!

the fork- luke, use the fork!

(sorry! - couldn't resist)

Quote:>What does drivutil [ -i | -I | -l ] array_id report for you?

well as the A1000 is in production I can't go moving it around.
Our maint window isn't until June 30th. BTW - we get ONE shot that
this, this month, June 30, otherwise I'll be looking for a new job.
ugh

Quote:>Not a bad idea to disconnect the A1000 during the install. After the initial reboot you can always attach it and then do a devfsadm
>-C -c disk -v to create/update the device path.

that was the command I was missing. devfsadm... damn. I used disk -v,
but it didn't do anything. Literally. There were a few other commands
I tried as well, related to disk, but I forgot about devfsadm...

Quote:>I haven't had a bright idea in years. I'm still waiting for one however. :)

well this is as good a time as any...

btw not sure I mentioned how much I appreciated your help so far...

Dan.

by **Dan Gahlinge** » Sat, 15 Jun 2002 00:49:18

>What does drivutil [ -i | -I | -l ] array_id report for you?

Here ya go (from the existing system) -
should I be concerned about the healthcheck info ?

./healthck -a

Health Check Summary Information

ea025_003: Failed Battery

healthck succeeded!

./drivutil -i ea025_003

Drive Information for ea025_003

Location Capacity Status Vendor Product Firmware Serial
(MB) ID Version Number
[1,0] 17274 Spare-Stdby SEAGATE ST318203LSUN18G 034A LRF3431100
[2,0] 17274 Optimal SEAGATE ST318203LSUN18G 034A LRF0346300
[1,1] 17274 Optimal SEAGATE ST318203LSUN18G 034A LRF3100200
[2,1] 17274 Optimal SEAGATE ST318203LSUN18G 034A LRF3557700
[1,2] 17274 Optimal SEAGATE ST318203LSUN18G 034A LRF3334700
[2,2] 17274 Optimal SEAGATE ST318203LSUN18G 034A LRF3713600
[1,3] 17274 Optimal SEAGATE ST318203LSUN18G 034A LRF3728400
[2,3] 17274 Optimal SEAGATE ST318203LSUN18G 034A LRF2139600
[1,4] 17274 Optimal SEAGATE ST318203LSUN18G 034A LRF3411600
[2,4] 17274 Optimal SEAGATE ST318203LSUN18G 034A LRF0077400
[1,5] 17274 Optimal SEAGATE ST318203LSUN18G 034A LRF3798800
[2,5] 17274 Optimal SEAGATE ST318203LSUN18G 034A LRF3826500

drivutil succeeded!

./drivutil -I ea025_003

Group Information for ea025_003

Group No. of RAID No. of Total Remaining
LUNs Level Drives Space(MB) Space(MB)

Hot Spare - - 1 - -
1 5 5 11 172346 42146

drivutil succeeded!

by **Darren Dunha** » Sat, 15 Jun 2002 01:06:53

> yes, but we moved the config over from the other machine,
> and rebooted. couldn't see them.

I'm assuming that's a 'boot -r'...

Quote:> I think the problem is more likely the fact that on the E450
> it's a different controller, channel, etc etc etc
> So /dev/dsk/c1t4d2s0 or whatever will be completely different
> on the E450.

Shouldn't matter at all. The boot -r will ask the sd driver to find the
target/lun combos on any channel and create the devices.

Quote:> And that may be a bigger hassle than anything, I have no idea
> how to figure out what the units will be.

They'll show up in format once the devices get built. None of this
(yet) should depend on RM6 being installed.

Quote:> On the brighter side, I got RM 6.22.1 installed on Solaris9 (test
> system) without a hitch, flawless install.
> Simply amazing that something worked first try.
> That may make things easier, I have no idea.

Shouldn't matter.

--

Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

by **Dan Gahlinge** » Sat, 15 Jun 2002 01:22:17

>I'm assuming that's a 'boot -r'...

you betcha...

Quote:>Shouldn't matter at all. The boot -r will ask the sd driver to find the
>target/lun combos on any channel and create the devices.

I wondered about that. thanks

Quote:>They'll show up in format once the devices get built. None of this
>(yet) should depend on RM6 being installed.

well disks did nothing, although I didn't run devfsadm.
if you check my other post (reply to Dennis Clark) you'll
see the output of the devutil command.

Quote:>Shouldn't matter.

I thought RM had to be installed to access them? Again, I'm out of my element.
probe-scsi-all showed them I believe (with boot -r) but the devices weren't built.

All I am missing I guess is building the devices.

Would you say it's fairly safe to have the A1000 connected during the initial
solaris9 install ? I don't see why it wouldn't be. And in this case, the devices might
actually be built automatically (at least that's what I'm hoping).

Dan.

Very Computer

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)

server/raid/solaris upgrading - need help (raid manager)