On a systems that has an A1000 attached,  there are only SPARCstorage
Array Drivers(SUNWssad) and SPARCstorage Array
Drivers(64-bit)(SUNWssadx) shows on the system.  No  Open Storage
Array(such as SUNWosau) shows at all. there is no "rdaemon" running.
Just wonder if  there is anything wrong here?  But it seems that the
A1000 functions.

Thanks for advice!

bridge_xue@yahoo.com wrote:
> On a systems that has an A1000 attached,  there are only SPARCstorage
> Array Drivers(SUNWssad) and SPARCstorage Array
> Drivers(64-bit)(SUNWssadx) shows on the system.  No  Open Storage
> Array(such as SUNWosau) shows at all. there is no "rdaemon" running.
> Just wonder if  there is anything wrong here?  But it seems that the
> A1000 functions.

An A1000 will work just as a SCSI device, so you don't really need any
of the OSA stuff.  *But* you won't be able to do any management on it
at all: so you won't be able to create new LUNs, detect failed disks,
etc etc.

--tim

bridge_xue@yahoo.com wrote:
> On a systems that has an A1000 attached,  there are only SPARCstorage
> Array Drivers(SUNWssad) and SPARCstorage Array
> Drivers(64-bit)(SUNWssadx) shows on the system.  No  Open Storage
> Array(such as SUNWosau) shows at all. there is no "rdaemon" running.
> Just wonder if  there is anything wrong here?  But it seems that the
> A1000 functions.

You don't need the drivers to access the device as a disk, only to
access the managment capabilities.  

Assuming you're running Solaris SPARC earlier than 10, then you can
download Sun Raid Manager 6.22.1 for the drivers and utilities.
Actually, you can download them even if you're running something else,
but they won't be useful to install...

-- 
Darren Dunham                                           ddunham@taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

Darren Dunham wrote:
> bridge_xue@yahoo.com wrote:
> 
>>On a systems that has an A1000 attached,  there are only SPARCstorage
>>Array Drivers(SUNWssad) and SPARCstorage Array
>>Drivers(64-bit)(SUNWssadx) shows on the system.  No  Open Storage
>>Array(such as SUNWosau) shows at all. there is no "rdaemon" running.
>>Just wonder if  there is anything wrong here?  But it seems that the
>>A1000 functions.
> 
> You don't need the drivers to access the device as a disk, only to
> access the managment capabilities.  
> 
> Assuming you're running Solaris SPARC earlier than 10, then you can
> download Sun Raid Manager 6.22.1 for the drivers and utilities.
> Actually, you can download them even if you're running something else,
> but they won't be useful to install...

Hm ... i read that a lot here and believed it. Then out
of curiosity i actually tried using the RM with Solaris
10. It installed without a hitch, and i was able to use
rm6 like on all other Solaris releases.
Although this was done on a test system and because of
the unsupported nature of RM with Solaris 10 probably
not a good thing for a production environment ;-)

Regards,

	Frank

Frank Fegert <fra.nospam.nk@gmx.de> wrote:

> Hm ... i read that a lot here and believed it. Then out
> of curiosity i actually tried using the RM with Solaris
> 10. It installed without a hitch, and i was able to use
> rm6 like on all other Solaris releases.
> Although this was done on a test system and because of
> the unsupported nature of RM with Solaris 10 probably
> not a good thing for a production environment ;-)

Cool.  I've not tried it.  (Don't have an A1000 to test).  Many others
have reported that they could not get it to work.

I did note one post from a user that said that 'rm6' (the gui) didn't
work at all, but that the command line utilities like 'lad' worked
okay.  However he was the only one to mention that.

Do you actually load an RDAC driver?  That should the interface between
rm6 and the unit, and as far as I'm aware the driver will not load on a
Solaris 10 kernel.

-- 
Darren Dunham                                           ddunham@taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

In article <P%0Pf.19595$rL5.16031@newssvr27.news.prodigy.net>,
Darren Dunham  <ddunham@redwood.taos.com> wrote:
>Frank Fegert <fra.nospam.nk@gmx.de> wrote:
>
>> Hm ... i read that a lot here and believed it. Then out
>> of curiosity i actually tried using the RM with Solaris
>> 10. It installed without a hitch, and i was able to use
>> rm6 like on all other Solaris releases.

>Cool.  I've not tried it.  (Don't have an A1000 to test).  Many others
>have reported that they could not get it to work.

>Do you actually load an RDAC driver?  That should the interface between
>rm6 and the unit, and as far as I'm aware the driver will not load on a
>Solaris 10 kernel.

RDAC stands for Redundant Disk Array Controller Support, and is only needed for
path failover on RSM2000/A3000/A3500/A3500FC. Since A1000 only has a single 
controller it is not needed. rm6 talks to the A1000 through Lun 0.

Regards
Fredrik

-- 
Fredrik Lundholm   
dol @ ce.chalmers.se
				 

Fredrik Lundholm <dol@ce.chalmers.se> wrote:
> RDAC stands for Redundant Disk Array Controller Support, and is only
> needed for path failover on RSM2000/A3000/A3500/A3500FC. Since A1000
> only has a single controller it is not needed. rm6 talks to the A1000
> through Lun 0.

That was what I'd hoped but I'd seen some reports of issues with rm6 and
A1000 on Solaris 10 and until now hadn't seen a success report.

Perhaps in some cases RM6 is looking for the RDAC paths in order to
determine where the modules are?  So while the driver isn't technically
required it can still cause issues by its absence?

Here's someone that was moving it between 9 and 10 because it didn't
appear to work in 10....

http://groups.google.com/group/comp.unix.solaris/browse_thread/thread/3080358550587493/a9655ab1f9726301

-- 
Darren Dunham                                           ddunham@taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

Darren Dunham <ddunham@redwood.taos.com> writes:

> Fredrik Lundholm <dol@ce.chalmers.se> wrote:
> > RDAC stands for Redundant Disk Array Controller Support, and is only
> > needed for path failover on RSM2000/A3000/A3500/A3500FC. Since A1000
> > only has a single controller it is not needed. rm6 talks to the A1000
> > through Lun 0.
> 
> That was what I'd hoped but I'd seen some reports of issues with rm6 and
> A1000 on Solaris 10 and until now hadn't seen a success report.

I had complained loudly during Solaris 10 Platinum Beta when I first
learned about removal of RM6/A1000 support in S10 FCS *without any
appropriate prior notice (i.e.: EOL notices) in S9 Release Notes*.
Unfortunately, this didn't help to bring the support back, but my support
engineer quickly determined that RM6 runs just fine with an A1000.  I later
learned that the claimed reason for support removal was that the A1000
itself had been EOLed before S10 went FCS.

> Perhaps in some cases RM6 is looking for the RDAC paths in order to
> determine where the modules are?  So while the driver isn't technically
> required it can still cause issues by its absence?

The rdriver won't load in S10:

Nov 21 23:24:47 sequoia krtld: [ID 819705 kern.notice] /kernel/drv/sparcv9/rdriver: undefined symbol
Nov 21 23:24:47 sequoia krtld: [ID 826211 kern.notice]  'dev_get_dev_info'
Nov 21 23:24:47 sequoia krtld: [ID 472681 kern.notice] WARNING: mod_load: cannot load module 'rdriver'
Nov 21 23:24:47 sequoia genunix: [ID 370176 kern.warning] WARNING: forceload of drv/rdriver failed
Nov 21 23:24:47 sequoia krtld: [ID 819705 kern.notice] /kernel/drv/sparcv9/rdriver: undefined symbol
Nov 21 23:24:47 sequoia krtld: [ID 826211 kern.notice]  'dev_get_dev_info'
Nov 21 23:24:47 sequoia krtld: [ID 472681 kern.notice] WARNING: mod_load: cannot load module 'rdriver'

But since rdriver and rdnexus are only needed for RDAC (which doesn't do
anything useful with the single-controller A1000), I just rem_drv'ed both
and disabled RDAC support in /etc/osa/rmparams, as I had already done in S8:

--- rmparams.rm6221     Mon Nov 21 13:29:22 2005
+++ rmparams    Tue Nov 22 00:23:58 2005
@@ -80,8 +80,9 @@
 
 # RDAC driver/Resolution Daemon Failover parameters
 
-Rdac_SupportDisabled=FALSE
-Rdac_SinglePathSupportDisabled=FALSE
+# Disabled, useless on A1000 without redundant controllers
+Rdac_SupportDisabled=TRUE
+Rdac_SinglePathSupportDisabled=TRUE
 Rdac_HotAddDisabled=PARTIAL
 Rdac_HotAddIDs:4:5:
 Rdac_NativeScsiDrivers:sd:

This way, an A1000 works just fine when connected to an E3000 with 4 x 167
MHz UltraSPARC I CPUs running Solaris Express Build 33, including arraymon
and the RM6 GUI and CLI interfaces :-)

I'm actually using it for some ZFS testing, which works amazingly well,
considering the old and slow hardware.

Hope this helps.

	Rainer

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

Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> writes:

>I had complained loudly during Solaris 10 Platinum Beta when I first
>learned about removal of RM6/A1000 support in S10 FCS *without any
>appropriate prior notice (i.e.: EOL notices) in S9 Release Notes*.
>Unfortunately, this didn't help to bring the support back, but my support
>engineer quickly determined that RM6 runs just fine with an A1000.  I later
>learned that the claimed reason for support removal was that the A1000
>itself had been EOLed before S10 went FCS.

The Solaris 9 8/03 and 12/03 release notes mention the end of support;
originally the plan was to kill RM6 even in Solaris 9 and not support
it past Solaris 8.

>This way, an A1000 works just fine when connected to an E3000 with 4 x 167
>MHz UltraSPARC I CPUs running Solaris Express Build 33, including arraymon
>and the RM6 GUI and CLI interfaces :-)

Interesting ....

>I'm actually using it for some ZFS testing, which works amazingly well,
>considering the old and slow hardware.

I'm using D1000s for same.

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:

> Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> writes:
> 
> >I had complained loudly during Solaris 10 Platinum Beta when I first
> >learned about removal of RM6/A1000 support in S10 FCS *without any
> >appropriate prior notice (i.e.: EOL notices) in S9 Release Notes*.
> >Unfortunately, this didn't help to bring the support back, but my support
> >engineer quickly determined that RM6 runs just fine with an A1000.  I later
> >learned that the claimed reason for support removal was that the A1000
> >itself had been EOLed before S10 went FCS.
> 
> The Solaris 9 8/03 and 12/03 release notes mention the end of support;

At least the current online versions don't, and neither do those for
Solaris 9 9/05; they only mention A3000/A3500/A3500FC (probably due to the
removal of the pln ans soc drivers), but nothing about A1000 (or RM6):

	http://docs.sun.com/app/docs/doc/819-3807/6n60jqofd?a=view

> originally the plan was to kill RM6 even in Solaris 9 and not support
> it past Solaris 8.

I know; colleagues with a large deployment of (partially refurbished)
A3500FC and we complained so much (though we probably weren't alone) that
the support was revived in a RM 6.22.1 patch.

I still consider the removal in S10 not properly following established Sun
procedures for EOL notices, but given that the boxes work for me now (and
we may even get rid of them in the not too distant future), I won't try to
push this issue.

	Rainer

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

What is SUNspark2 unfixable error.

Raju KV

Will all the devices appear in /dev/dsk?

We have a few A1000 and all the devices do not currently display in
/dev/dsk. 

Will the Solaris 10 devfsadm take care of that?

..

greek_philosophizer@hotmail.com wrote:
> Will all the devices appear in /dev/dsk?

> We have a few A1000 and all the devices do not currently display in
> /dev/dsk. 

> Will the Solaris 10 devfsadm take care of that?

Stock Solaris 10 will only poll for LUN=0 devices.  Edit
/kernel/drv/sd.conf to create new entries for any extra luns you have.

Once done you need to reboot or reload the sd driver, then 'devfsadm'
should pick up the devices.

Even no changes, a Solaris 10 box should see the LUN 0 on the A1000.

-- 
Darren Dunham                                           ddunham@taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

Thanks!

..