Hi there,

I've seen this discussed on and off over the past year since Solaris 10
has been released.

I have a bunch of V880s in my org, and even more A1000's. Due to
budgetary concerns, we ain't replacing the A1000's for a while, so I'm
now at the stage where I *have* to get them working with my V880s
running Solaris 10.

Now - I carried out an installation about 6 months ago (before I
realised this could be an issue), and the SPARC 64 bit Solaris 10
installation flew through without an issue, including the addition of
RM 6.22.1.

Even now, I can log into my machine (which has 2x A1000s attached to
it), and bring up RM6 and view the details of the LUN, including which
disks are hot swaps etc.

It seems to function perfectly (although I do get the forceload rdnexus
and rdriver failed warnings when booting).

Now, here I am 6 months down the line with a recently installed Solaris
10 03/05 SPARC 64bit installation on a V880, with the October 05
recommended patches, and I can't get the bloomin' thing to run RM6.

I really can't recall how (or if) I tweaked the original v880, which is
working fine.

This is pretty frustrating - can anyone advise if they've encountered
the same issues and worked around them?

BTW - If and when I find a solution, I'll be sure to post it up
here.... I don't want to lose it again!

D.

"Dougiesic" <dougiesic@gmail.com> writes:

>I have a bunch of V880s in my org, and even more A1000's. Due to
>budgetary concerns, we ain't replacing the A1000's for a while, so I'm
>now at the stage where I *have* to get them working with my V880s
>running Solaris 10.

They work but you can't configure them, I believe.

>Now - I carried out an installation about 6 months ago (before I
>realised this could be an issue), and the SPARC 64 bit Solaris 10
>installation flew through without an issue, including the addition of
>RM 6.22.1.

>Even now, I can log into my machine (which has 2x A1000s attached to
>it), and bring up RM6 and view the details of the LUN, including which
>disks are hot swaps etc.

Ok, so you installed the drivers and they mostly work (no surprise
there)

>Now, here I am 6 months down the line with a recently installed Solaris
>10 03/05 SPARC 64bit installation on a V880, with the October 05
>recommended patches, and I can't get the bloomin' thing to run RM6.

Yep, RM6 is not supported on S10. So what happens on this one?

Check the /etc/*_* aliases files etc?

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Casper H.S. Dik <Casper.Dik@Sun.COM> writes:

> "Dougiesic" <dougiesic@gmail.com> writes:
>
> >I have a bunch of V880s in my org, and even more A1000's. Due to
> >budgetary concerns, we ain't replacing the A1000's for a while, so I'm
> >now at the stage where I *have* to get them working with my V880s
> >running Solaris 10.
>
> They work but you can't configure them, I believe.

You can: there's no loss of functionality at all for A1000 (unlike the
A3x00, where you loose controller failover which depends on rdriver/rdnexus
which don't load any longer in S10).

> >Now, here I am 6 months down the line with a recently installed Solaris
> >10 03/05 SPARC 64bit installation on a V880, with the October 05
> >recommended patches, and I can't get the bloomin' thing to run RM6.
>
> Yep, RM6 is not supported on S10. So what happens on this one?
>
> Check the /etc/*_* aliases files etc?

I have an A1000 working seamlessly on snv_33 (i.e. a not-too-old Solaris
Express), so I would be astonished to see it break in some S10
Update/patch.

Rainer

--
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University

Just to update on the situation - despite the RM6.22.1 installation
saying it had failed and that it could not install on Solaris 10, I
eventually decided to do a reconfigure reboot anyways....

As it turns out, I didn't have to do any OS tweaking at all... The
A1000 can be seen PERFECTLY from Solaris 10 running RM6.

As per thread above, I think this would only be a problem if I were
running a multi controller RAID module.

The question remains, I guess, as to whether I should remove the two
failing forceload lines from the /etc/system file.

As they fail to forceload, I don't think removing them will make any
difference to the functionality of RM6.22.1.

Thoughts?

"Dougiesic" <dougiesic@gmail.com> writes:

>The question remains, I guess, as to whether I should remove the two
>failing forceload lines from the /etc/system file.

Yes; it cuts down on the alarmist messages.

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.