01-26-2013
Yes, we upgraded the array to all 600GB drives. The current firmware doesn't support using all 12 drives in single array. Furthermore, the current firmware has known performance issues.
When we first got the array, we were able to download all the software freely from Sun, including the CAM and firmware we have on there now. The latest firmware was also freely available on Sun's site prior to their acquisition and Oracle hasn't made any updates to the firmware that I'm aware of.
chilinski, to your point, lots of people were able get for free what Oracle is charging for now. An argument could be made that anyone who downloaded the firmware prior to the acquisition would have the license to install that firmware on any array.
Either way, I've called Oracle trying to buy a support contract, but they won't let me. From what I understand, without having an original receipt from Sun or an authorized Sun vendor, Oracle we simple cannot get a support contract for this Sun hardware. If anyone can tell me otherwise, I'm all ears.
I do have an Oracle support *account* that was migrated from the free Sun account, but I cannot access the firmware URL. I can only assume that's due to not having a support contract.
If I'd had any idea that Oracle would be like this, I would have stayed on top of the firmware and downloaded the later version prior to the buyout.
I just want a properly-working array.
10 More Discussions You Might Find Interesting
1. Solaris
I have a Sun Sparc T2000 (Solaris 10 05-08) and have installed a PCI-X 4GB Single Port HBA card in it.
I have one StorageTek 2540 array that I would like to connect to the T2000.
For the moment it would be a single path connection, but I've ordered a 2nd HBA, so eventually it would be... (4 Replies)
Discussion started by: soliberus
4 Replies
2. Solaris
We're moving our production 3510FC to development, so we need to replace the production 3510FC. The 6140 is nice, but pricey.
Here's the question: Would two 2540's (RAID 10) be 'faster' than one 3510? (RAID 10) and faster than one 6140 (RAID 10)?
One StoregeTek 6140 (16x72GB 15k rpm fc-al... (12 Replies)
Discussion started by: buddhavelvet
12 Replies
3. Filesystems, Disks and Memory
Hi,
We have 12x1TB SATA disks in our array and I need to create 10TB volume. I defined new storage profile on array and when I tried to add volume, I faced with ~2TB limit for new volumes. I didn't find how to set another limit on my storage profile. Is there is a way to configure one large... (3 Replies)
Discussion started by: Sapfeer
3 Replies
4. Solaris
Hi,
I have a simple question on how to correctly disable the matrix?
Looking for the Common Array Manager and I do not see this option...
Thank for help (3 Replies)
Discussion started by: bieszczaders
3 Replies
5. Solaris
Hi peeps,
Was wondering if anyone can help me, got a couple of storagetek 2540's that I need to configure. Trouble is I think they were brought as second user as all that came with them was cables.
Does anyone know how to configure them (i.e. create raid sets and map to Luns and present... (1 Reply)
Discussion started by: callmebob
1 Replies
6. Hardware
Hello all !
I am a beginner about system and networking , and after some research on internet , i didn't find any relevant information , so i post here , if someone have an experience with this kind of material or if some documentation about how to connect my storage device on my server.
I... (2 Replies)
Discussion started by: acorradi
2 Replies
7. Filesystems, Disks and Memory
Hi,
I have a question about Sun StorageTek Common Array Manager (CAM): What is the concept of 'host'? Is it the hostname of the server that has access to the managed array? If so, can I use its IP instead of its hostname?
I've found a 'host' under CAM called XYZ (See below). In our... (7 Replies)
Discussion started by: aixlover
7 Replies
8. Hardware
Hi all,
My Sun StorageTek 2540 have redundant batteries, but a battery was failed.
# /opt/SUNWstkcam/bin/sscs list -d MyStorage1 fru
Name FRU Alarm State Status Revision Unique Id
-------------------------- ----------- --------... (2 Replies)
Discussion started by: buyantugs
2 Replies
9. Hardware
Hi Guys and Gals,
Wionder if you could help me, got a problem with a controller on a storagetek 2540, dead when fully powered up but if you reboot, it is ok for a couple of seconds (and you can ping it). Then once the array is fully up, it goes faulty and is un-pingable.
Had anyone... (4 Replies)
Discussion started by: callmebob
4 Replies
10. Solaris
Hi Guys,
I have situation here ...
server M4000 server lost connectivity to storagetek 2540
, storagetek 2540 unable to be ping.From DAS URL the storage is undetected.
Any idea why this is happening. Please share.
Thank you.
Raj (1 Reply)
Discussion started by: muralirajah
1 Replies
LEARN ABOUT OPENSOLARIS
mms
mms(5) Standards, Environments, and Macros mms(5)
NAME
mms - MMS service overview
DESCRIPTION
MMS is a distributed removable media management system. It is based on the standard, IEEE 1244, Media Management System (MMS).
The current implementation of MMS manages tapes and cartridges in a Sun StorageTek ACSLS tape library and emulated tapes on a file system.
MMS is capable of sharing drives among multiple hosts. An important feature of MMS is that it provides a uniform and consistent tape inter-
face to its client applications.
MMS consists of a media manager (MM) which manages the entire MMS system. Information about the system is maintained by MM in a database.
Every library managed by MMS has an active library manager (LM). An LM provides library access and mounting service to MMS.
A drive managed by MMS has a drive manager (DM) on each host that has access to the drive. A DM provides device specific operations. A DM
also provides label processing. The current implementation supports only ANSI labels.
MMS client applications request MM to mount and unmount cartridges and process them after they are mounted. Applications use the Media Man-
agement Protocol (MMP) to make requests. A library of client application functions is available.
The Solaris implementation of the MMS uses the mmsinit(1M) command to configure and start the MMS service and the mmsadm(1M) command to
list and set parameters required by the service.
The MMS service instances, as reported by svcs(1), are:
mms:wcr
watcher
mms:db
Media Manager PostgreSQL database
mms:mm
Media Manager
The MMS service RBAC (see rbac(5)) authorizations are:
o solaris.smf.manage.mms
o solaris.smf.value.mms
The following are the MMS service configuration data accessible through the service management facility (see smf(5)):
config/type
Host is media manager or watcher only. Valid values are server or client.
manager/host
Host name where the media manager is running.
manager/port
Port the media manager is using.
ssl/enabled
Media Manager is using SSL. Valid values are true or false. Note the Media Manager needs an SSL RSA certificate and Diffie-Hellman
parameters must be 'true'.
ssl/verify
Media Manager-only value, determines whether two-way authentication is enabled, which requires all Media Manager clients to have SSL
RSA certificate. Valid values are are true for two-way authentication and false for one-way authentication.
ssl/cert_file
Name of file that contains the SSL RSA certificate, private key, and RSA certificate chain.
ssl/pass_file
Name of file for the private key password phrase if the RSA certificate is encrypted.
ssl/dh_file
Media Manager-only value, name of file that stores the Diffie-Hellman parameters.
ssl/crl_file
Name of optional CRL file.
ssl/cipher
Optional cipher change from EDH-RSA-DES-CBC3-SHA.
ssl/peer_file
Optional client only, name of file that stores the media manager certificate. The certificate is checked against the certificate
returned by SSL_get_peer_certificate() function.
The following are the MMS Database fault management resource identifier (FMRI) configuration data:
postgresql/bin
Directory where the PostgreSQL binaries are located. The directory is specific to the version of PostgreSQL qualified for use by the
MMS software.
postgresql/data
Directory where the PostgreSQL database is located. The default location is a version-specific subdirectory of /var/mms/db.
The following are the MMS Media Manager FMRI configuration data:
db/host
For future use. Set to localhost.
db/port
Port number to use for PostgreSQL login. The default value is 7656.
db/user
PostgreSQL user name. The default user name is postgres.
db/name
Name of PostgreSQL database to which to connect. The default value is mms.
option/trace
Optional. The Media Manager trace level before connecting to the PostgreSQL database.
option/db_reconnect_max_retry
Number of times to wait for the database to accept a Media Manager connection.
option/db_reconnect_timeout
Number of seconds to wait between reconnect tries.
The following are the MMS Watcher FMRI configuration data:
option/ssi_path
Path to ACSLS SSI daemon.
option/libapi_path
Path to ACSLS API library.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), mmsadm(1M), mmsclient(1M), mmsexplorer(1M), mmsinit(1M), mmsclient_script(4), attributes(5), rbac(5), smf(5)
SunOS 5.11 11 Nov 2008 mms(5)