Pki Sistemas | 14 Sep 2011 12:41

Publicada openindiana 151a


Como principal novedad (muy interesante por cierto): incluye KVM para virtualizacion (por el momento solo soporte para Intel VT...)

Enlace a las notas del lanzamiento:


http://wiki.openindiana.org/oi/oi_151a+Release+Notes



Fco. Javier Garcia Rodriguez
Responsable Sistemas
Pki Sistemas


C/ Diputacion 12
31513 Arguedas
Navarra

C/ Donamaria 8
31013 Berriozar Navarra

Tfno: 948-830051 // 622-240404
www.pkisistemas.com

<div>
<br>Como principal novedad (muy interesante por cierto): incluye KVM para virtualizacion (por el momento solo soporte para Intel VT...)<br><br>Enlace a las notas del lanzamiento:<br><br><br><a href="http://wiki.openindiana.org/oi/oi_151a+Release+Notes"> http://wiki.openindiana.org/oi/oi_151a+Release+Notes</a><br><br><br><br clear="all"><p>Fco.
Javier Garcia Rodriguez<br><span>Responsable
Sistemas<br>Pki Sistemas</span></p>
<p><span><br></span></p>
<p>
</p>
<table width="183" border="0" cellpadding="0" cellspacing="0" height="61"><tr>
<td width="161" height="61">
			<p align="CENTER">C/ Diputacion 12<br>31513 Arguedas <br>Navarra</p>
		</td>
		<td width="160">
			<p align="CENTER">C/ Donamaria 8 <br>31013 Berriozar Navarra</p>
		</td>
	</tr></table>Tfno: 948-830051 // 622-240404<br><a href="http://www.pkisistemas.com/" target="_blank">www.pkisistemas.com</a> <br><br>
</div>
Francisco Javier Garcia | 14 Feb 2011 23:55

AMD fusion y almacenamiento... parcial off-topic

Si alguien esta pensando en montar un sistema de almacenamiento de bajo consumo... quizas le interese el ultimo post de nuestro blog:

http://www.pkisistemas.com/blog/

Un saludo

<div><p>Si alguien esta pensando en montar un sistema de almacenamiento de bajo consumo... quizas le interese el ultimo post de nuestro blog:<br><br><a href="http://www.pkisistemas.com/blog/">http://www.pkisistemas.com/blog/</a><br><br>Un saludo<br></p></div>
Juan Jose Amor | 18 Nov 2010 11:35
Picon

Baja en las listas


Hola,

Igual que ha hecho algún compañero, me doy de baja de estas listas.

Aunque me considero técnicamente bastante competente en Oracle Solaris,
en este momento no lo uso profesionalmente (y personalmente tampoco
tengo tiempo), con lo que no me aporta mucho estar en una lista técnica
sobre tecnologías Solaris.

Y a lo que sí dedico mucho tiempo libre es a la divulgación del software
libre, razón por la que estaba vinculado a Opensolaris. Sin embargo,
esta comunidad ya no existe y sus antiguos miembros estamos cada vez más
refugiados en torno a Illumos o a Openindiana.

Por esta razón no voy a continuar en estas listas, en la que el 99% de
los mensajes son sobre Solaris (software privativo), y el 1% restante
son quejas por no respetar el topic original (Opensolaris, software libre).

En fin, que ha sido un placer. Seguiré muy de cerca la evolución de
Openindiana e Illumos, y trataré de colaborar con sus comunidades
hispanas, pero esto ha sido todo por ahora. ¡Hasta pronto!

Saludos,

--

-- 

  Juan Jose Amor Iglesias  //  -+- ¡Vorágine! -+-
  jjamor -at- gmail.com // juanjo -at- dramor.net

--------------------       Visit my Blog! ---------------------
 The Boring Stories Written By DrAmor: http://dramor.net/blog/
---------------------------------------------------------------
Francisco Javier Garcia | 18 Nov 2010 11:22

Novedades en zfs de solaris express 11

Algunas no son novedades como tal (fueron introducidas en las ultimas versiones dev de opensolaris):

- Encriptacion (AES 128 por defecto.. penalizacion de entre un 3% y un 7% en el rendimiento del sistema).
- Creacion de mirros en el root pool ... no permite la instalacion en un mirror, pero una vez instalado el sistema podemos añadir un disco al rpool, el cual automaticamente instala los boot bloks (en definitiva, que nos hace el mirror y nos instala y configura grub), lo mismo si añadimos discos spare al sistema.
- Mejor gestion de zfs send and receive en los rpool (era un problema curioso, al enviar un rpool a otro equipo, nos encontrabamos con que el nombre del pool estaba duplicado, y ademas en muchos casos no era modificable...).
- Deduplicacion... bueno esto ya es un poco viejo
- Raidz mirror allocator... una mejora en el rendimiento, basicamente crea mirrors de determinados metadatos en  pools de raidz... de ese modo, p.ejm, la navegacion y lectura del arbol de ficheros es considerablemente mas rapida (en lugar de estar en algunos discos los datos... esos datos estan en todos los discos... mayor velocidad de acceso).
- Podemos importar pools con las unidades logs ausentes o dañadas...
- Añadido un "modo de emergencia"... en el supuesto de que el pool este dañado y no se pueda importar, nos permite la importacion en modo solo lectura para recuperar datos (los que esten disponibles).
- Mejores en las capacidades de zfs send: puedes enviar un stream de un pool no comprimido, y recibirlo en uno comprimido y viceversa... lo mismo con el resto de opciones.
- ZFS diff: compara 2 diferentes snapshots y nos indica que ficheros y carpetas han cambiado, que se ha renombrado... borrado o añadido.
- Eliminada la opcion zil_disable, se ha sustituido por la opcion sync, que puede ser standard (solo usar zil con operaciones sincronas), always (todas las operaciones) o disabled (no usar zil)


Desconozco si han solventado los problemas relacionados con la congelacion del sistema en entornos con deduplicacion activada.

Y eso es todo.

<div><p>Algunas no son novedades como tal (fueron introducidas en las ultimas versiones dev de opensolaris):<br><br>- Encriptacion (AES 128 por defecto.. penalizacion de entre un 3% y un 7% en el rendimiento del sistema).<br>-
 Creacion de mirros en el root pool ... no permite la instalacion en un 
mirror, pero una vez instalado el sistema podemos a&ntilde;adir un disco al 
rpool, el cual automaticamente instala los boot bloks (en definitiva, 
que nos hace el mirror y nos instala y configura grub), lo mismo si 
a&ntilde;adimos discos spare al sistema.<br>

- Mejor gestion de zfs send and receive en los rpool (era un problema 
curioso, al enviar un rpool a otro equipo, nos encontrabamos con que el 
nombre del pool estaba duplicado, y ademas en muchos casos no era 
modificable...).<br>

- Deduplicacion... bueno esto ya es un poco viejo<br>- Raidz mirror 
allocator... una mejora en el rendimiento, basicamente crea mirrors de 
determinados metadatos en&nbsp; pools de raidz... de ese modo, p.ejm, la 
navegacion y lectura del arbol de ficheros es considerablemente mas 
rapida (en lugar de estar en algunos discos los datos... esos datos 
estan en todos los discos... mayor velocidad de acceso).<br>

- Podemos importar pools con las unidades logs ausentes o da&ntilde;adas...<br>-
 A&ntilde;adido un "modo de emergencia"... en el supuesto de que el pool este 
da&ntilde;ado y no se pueda importar, nos permite la importacion en modo solo 
lectura para recuperar datos (los que esten disponibles).<br>

- Mejores en las capacidades de zfs send: puedes enviar un stream de un 
pool no comprimido, y recibirlo en uno comprimido y viceversa... lo 
mismo con el resto de opciones.<br>- ZFS diff: compara 2 diferentes 
snapshots y nos indica que ficheros y carpetas han cambiado, que se ha 
renombrado... borrado o a&ntilde;adido.<br>

- Eliminada la opcion zil_disable, se ha sustituido por la opcion sync, 
que puede ser standard (solo usar zil con operaciones sincronas), always
 (todas las operaciones) o disabled (no usar zil)<br><br><br>Desconozco si han solventado los problemas relacionados con la congelacion del sistema en entornos con deduplicacion activada.<br><br>Y eso es todo.<br><br></p></div>
Iban Nieto | 18 Nov 2010 09:39
Picon
Picon
Favicon
Gravatar

Bye bye

Hola chicos,

Pues nada, que yo me bajo del barco, abandono éstos temas para dedicarme a otras 
cosas que me molan más.
Ha sido un placer estar/hablar/trabajar con vosotros, cuidaros mucho y lo 
dicho... nos vemos en los bares ;-)

Un abrazo
 Iban Nieto - also in (facebook)
ibantxuyn at yahoo dot es (email)
http://inieto.wordpress.com (blog)

      
Francisco Javier Garcia | 16 Nov 2010 14:11

Publicado solaris Express 11

http://www.oracle.com/technetwork/server-storage/solaris11/downloads/index.html

cuidado con la version que descargais (la primera os dejará el sistema sin entorno grafico...), el live cd esta un poco mas abajo.
<div>
<a href="http://www.oracle.com/technetwork/server-storage/solaris11/downloads/index.html">http://www.oracle.com/technetwork/server-storage/solaris11/downloads/index.html</a><br><br>cuidado con la version que descargais (la primera os dejar&aacute; el sistema sin entorno grafico...), el live cd esta un poco mas abajo.<br>
</div>
Jose Castro | 13 Oct 2010 17:08
Favicon

Podcast sobre Illumos

Hola,

la comunidad JavaHispano ha publicado un podcast sobre illumos [1] con
una entrevista que nos hicieron a Miguel Vidal y a mí donde comentamos
los últimos acontecimientos que han producido que la comunidad tome
las riendas del proyecto, dando lugar a illumos y a la distribución
OpenIndiana.

Espero que sea útil y, si es así, que tenga difusión.

Saludos.

--

-- 
Jose Castro
  Madrid OpenSolaris User Group (madrid-osug)
  http://hub.opensolaris.org/bin/view/User+Group+madridosug/
Jesus Cea | 6 Oct 2010 05:56
Picon
Favicon

Fwd: [solarisx86] Great article on ZFS building and benchmarks


El artículo tiene algunos errores sutiles, como que el ZIL se utiliza en
todas las escrituras, pero es una lectura recomendable.

-- 
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea <at> jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea <at> jabber.org         _/_/    _/_/          _/_/_/_/_/
.                              _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
From: palowoda <palowoda <at> fiver.net>
Subject: [solarisx86] Great article on ZFS building and benchmarks
Date: 2010-10-05 22:46:20 GMT

http://www.anandtech.com/show/3963/zfs-building-testing-and-benchmarking

 Anandtech did a great job on this article.

---Bob

------------------------------------

Please check the Links page before posting:
    http://groups.yahoo.com/group/solarisx86/links
Post message: solarisx86 <at> yahoogroups.com
UNSUBSCRIBE:  solarisx86-unsubscribe <at> yahoogroups.com 

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/solarisx86/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/solarisx86/join
    (Yahoo! ID required)

<*> To change settings via email:
    solarisx86-digest <at> yahoogroups.com 
    solarisx86-fullfeatured <at> yahoogroups.com

<*> To unsubscribe from this group, send an email to:
    solarisx86-unsubscribe <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/


http://www.anandtech.com/show/3963/zfs-building-testing-and-benchmarking

 Anandtech did a great job on this article.

---Bob

------------------------------------

Please check the Links page before posting:
    http://groups.yahoo.com/group/solarisx86/links
Post message: solarisx86 <at> yahoogroups.com
UNSUBSCRIBE:  solarisx86-unsubscribe <at> yahoogroups.com 

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/solarisx86/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/solarisx86/join
    (Yahoo! ID required)

<*> To change settings via email:
    solarisx86-digest <at> yahoogroups.com 
    solarisx86-fullfeatured <at> yahoogroups.com

<*> To unsubscribe from this group, send an email to:
    solarisx86-unsubscribe <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Marcos Nadamas | 29 Sep 2010 22:51
Picon
Favicon

Password_Storedge_L20

Hola.
Tengo un Storedge_L20 al que actualice el firmware al 111972-05 cuando cargue el archivo  L20-SUN-1_05S-dnld_all, me reseteo la configuracion de la placa de red y tambien el password..!!! Lo upgrade via ftp, user: downlod y el pass: es el de administrador, hasta ese momento era: 11111111 (lo pusieron los anteriores dueños del equipo).
Ya porbe los pass por default que aparencen en internet y nada (12341234, no pass, 42311324), y con este modelo no se puede hacer nada sin el password de adminstrador.
Les agradeceria si alguien me puede ayudar de alguna manera.

PD: adjunto el README:
============================================================================
============================================================================
Status: RELEASEDPatch Id: 111972-05Summary: L20/L40/L60 robotics firmware upgradeDate:  Feb/10/2005Installation Requirements:Additional instructions may be listed belowSolaris Release: Sun OS Release: Unbundled Product: Hardware/TapeUnbundled Release: N/AXref: Topic: Relevant Architecture: BugId's fixed with this patch:Changes incorporated in this version:

Patches accumulated and obsoleted by this patch:Patches which conflict with this patch: Required Patches:Obsoleted by:  Files Included in this Patch: L20-SUN-1_05S-dnld_all (2,458,688 bytes) L20-SUN-1_25S-dnld_all (2,326,528 bytes) L20-SUN-1_33S-dnld_all (2,359,296 bytes) L20-SUN-1_55S-dnld_all (2,457,600 bytes) L20_SUN-1_71S-dnld_all (2,555,904 bytes) README.111972-05 sgen.conf.example ( 2,899 bytes) tload ( 57,472 bytes)Problem Description: 1) Internet Browser compatibility issue fixes new dependency of SUN Java 1.4.1_01 or later runtime plug-in now required for various browser support with this product's Remote Management Card (RMC). 2) Added a Front panel 'emergency' unload capability for HP LTO drives. 3) Added 25 sweeps once/day to the hourly maintenance routine. The default time is 12:00 PM (Noon). The 25-sweep maintenance hour is configurable. This sweeping prevents any oxidation of the transport track surface. 4) Various Front Panel and RMC messages enhanced. 5) Various SCSI, Logging, Error Reporting and Downloading issues addressed. 6) Various Motion enhancements. (from 111972-04) 4736628 Firmware 1.33 for L60 can prolong system boot up time. (from 111972-03) 4636180 robtest fails after upgrading firmware on L40 jukebox robotics 4635994 firmware is inconsistent, breaks netbackup functionality (from 111972-02) 4521629 1.25.S firmware for L20, L40, L60 in 111972-01 causes major inventory problems. NOTE: The firmware also needs to be updated in the L20/L40/L60 after any FRU is removed or replaced to assure that the library has the newest firmware possible.Revision History: 111972-03 111972-04 111972-01 111972-02
Patch Installation Instructions: -------------------------------- None.Special Install Instructions: ----------------------------- --------------------------------------------------------------------------- Instructions for Updating Firmware in the L20/L40/L60 Series -- RMC Method --------------------------------------------------------------------------- The following instructions explain how to, at a high level, upgrade the firmware in the L20/L40/L60 series of libraries. The firmware that gets updated is as follows: Picker/Translator Assembly Library Controller RMC (Remote Management Control) Card NOTE: The GUI interface may be a bit different depending on the firmware level present on the RMC card but most people should be able to follow the steps below and perform the upgrade. Before starting the upgrade procedure, assure that the RMC card is functioning properly and that an Administrator Password (done from front panel) is set up for the library. Also note the IP address for the library to be upgraded since the upgrade is done over the network by means of the host. If the RMC card is not available, see below: Instructions for Updating Firmware via SCSI Download Proceduret -- tload Method. To upgrade the firmware, do the following: 1) Move the firmware files onto the directory-of-choice on the host. 2) Open the Mozilla browser and type in the IP address for the library in the Mozilla Location field. When the connection is made, you should see the the IP address followed by: main_id.html 3) During some upgrade installations, the NVRAM settings have been corrupted, before downloading the firmware, document the following information: * SCSI I.D. for Library and all drives * Admin password * Network settings 4) From the left column of choice, click on: Configuration 5) A sub-menu will open, then click on: Firmware Download 6) The Firmware Download page opens (Source Firmware File). Enter the location of the file or else click on Browse to find the file. Then click on the appropriate firmware file until it is highlighted and then click: OK Due to firmware dependencies, multiple firmware loads may be required or the unit may show partial availability. By rule: If 1.05S is currently loaded, first load 1.25S, then load 1.33S, then load 1.55S, and finally load 1.71S. If 1.25S is loaded, first load 1.33S, then load 1.55S, and finally load 1.71S. If 1.33S is loaded, first load 1.55S, and finally load 1.71S. If 1.55S is loaded, you may load 1.71S. 7) Check the Source Firmware File box and assure the driver file is there, then click: Start Download 8) If the Java Security windows open, click Grant. This is your way of giving permission to do the download. 9) When you are prompted for the Administration Password, enter the password in the field. 10) If the password is accurate and accepted, a Reboot Warning Message appears to assure it will be safe for the library to reboot automatically. NOTE: Assure that no backups or other important functions are occuring on the library. 11) The Download Monitor window appears and some messages are displayed, such as Flash Erase/Rewrite. Please note the Progress Monitor doesn't always stay current. The activity is also displayed on the front panel of the library. 12) The library does a power-on reset and the Download Status Window shows Completed. Close the download status and Mozilla browser windows. 13) Open a new Mozilla browser and type in the IP address for the library in the Mozilla Location field. When the connection is made, you should see the the IP address followed by: main_id.html 14) Making sure a connection is still available to the library as shown above, click on: Identify 15) The library will identify and show the latest loaded version of firmware. 16) From the left column of choice, click on: Status 17) A sub-menu will open, then click on: Overview 18) If the Drive Status is OK for all attached drives go on to step 24. 19) If drive status is: "No drives were detected" From the front panel of the L20/L40/L60, verify the SCSI IDs of the Library and Drives are the same as documented in Step 3. If they have changed, reset the original SCSI IDs. 20) Press the Shift key on the keyboard and click on the Mozilla browser window Reload Icon at the same time. This will reload the library information to the Mozilla browser window without taking the information from cache. 21) From the left column of choice, click on: Status 22) A sub-menu will open, then click on: Overview 23) Verify the Drive Status is OK for all attached drives. 24) Repeat steps 4 through 23 for all remaining firmware files as required in Step 6. When you click on: Identify, and the firmware version shows 1.55S, you have fully completed the upgrade procedure. --------------------------------------------------------------------------- Instructions for Updating Firmware via SCSI -- tload Method --------------------------------------------------------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Contents -------- A.0 Solaris/Driver Requirements B.O Precautionary Statements C.O Patch Installation and Utility Usage Instructions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A.0 Solaris/Driver Requirements ----------------------------------------------- Solaris 8 and later bundled with a uscsi compliant driver such as the 'sgen' driver is required for this procedure. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ B.0 Precautionary Statements ----------------------------- **WARNING:****WARNING:****WARNING:****WARNING:****WARNING:****WARNING:** B.1 The system MUST BE IDLE during the firmware download process! No other programs should be running while this utility is being used. Failure to do so may cause the devices being upgraded to fail or the system to crash. Any other computers sharing the same I/O bus as the host system must be either disconnected or offline. B.2 If any upgrade failures occur, do not continue upgrading devices. For example, loss of power during download will result in damaged peripherals and require replacement. If any failures occur, please collect the following log file: "/var/adm/messages", and an explorer dump. Please forward these files to your service provider for analysis. B.3 This package will only function on StorEdge L20/40/60 Tape Libraries. B.4 Please READ instructions below completely BEFORE starting download procedure. Follow the procedures carefully. You may program multiple libraries at the same time, however, you may not exit the utility until all libraries have completed the download process. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ C.O Patch Installation and Utility Usage Intructions ----------------------------------------------------- C.1 General guidelines for upgrading: EJECT MEDIA FROM DEVICE TO BE UPGRADED. Download utility will eject media from the device if it is found to be loaded. Do NOT attempt to force media back into the drive. STOP ALL APPLICATIONS. The system must be idle during the firmware upgrade process. DISCONNECT or take OFFLINE any other computers sharing the same I/O bus as the host. C.2 Firmware Dependencies and Download Order: Due to firmware dependencies, multiple firmware loads may be required or the unit may show partial availability. By rule: If 1.05S is currently loaded, first load 1.25S, then load 1.33S, then load 1.55S, and finally load 1.71S. If 1.25S is loaded, first load 1.33S, then load 1.55S, and finally load 1.71S. If 1.33S is loaded, first load 1.55S, and finally load 1.71S. If 1.55S is loaded, you may load 1.71S. In case of any disruption or unforeseen events happening on the relevant bus during the firmware download process, it may be that the upgraded device becomes non-functional. In this event, it will be necessary to replace the device. This would happen as a result of an incomplete or corrupted firmware file being downloaded. Loss of power during the upgrade process would also damage the device. **NOTE** If you cannot upgrade devices due to software application interference, try booting off of the Solaris release CD. **NOTE** After the firmware download is completed, it may be necessary to power cycle the device to ensure fully resetting the device. In turn, this may also require a successive reboot of the host system to ensure all functionality is restored. C.3 Procedure for L20/40/60 Tape Library Firmware Download: The procedure to be used for upgrading the device's firmware is explained below. Total upgrade time will be approximately 10-15 minutes for each device. You must have root/super-user privileges in order to perform this operation. a). Ensure you are logged in as root on the machine attached to the L20/40/60 tape libraries you wish to upgrade. b). Unpack the patch (through tar) into any directory, e.g. /var/spool/patch (Note, if the patch ends in a ".Z" suffix, you will need to first uncompress it.) Example: # uncompress <filename.tar.Z> # tar xvf <filename.tar> c). Modify the /kernel/drv/sgen.conf file so that the sgen target driver will have a device link allowing access to the L20/40/60 tape libraries via a /dev/scsi/changer device link. SUGGESTED METHOD: ---------------- The sgen.conf.example file included with this patch may be utilized by first moving /kernel/drv/sgen.conf to /kernel/drv/sgen.conf.bak. Secondly, copy the included sgen.conf.example file to /kernel/drv/sgen.conf which supports tape library target (changer) devices operating on a parallel SCSI bus (SCSI target ID's 0-15 are supported). After completing this task, run: /usr/sbin/devfsadm -i sgen to create the /dev/scsi/changer/c#t#d# device link. MANUAL METHOD: ------------- Note: If you have used the SUGGESTED METHOD, skip to step C.2.d below in this section, else for manual sgen modifications: Refer to /kernel/drv/sgen.conf and/or the sgen man page for instructions on how to configure the sgen driver (included in Solaris 8 and later) to support tape library target (changer) devices operating on a parallel SCSI bus. First, copy /kernel/drv/sgen.conf to /kernel/drv/sgen.conf.bak to ensure preservation of the original sgen.conf file. Modify /kernel/drv/sgen.conf to enable sgen attach to tape library target (changer) devices operating on a parallel SCSI bus and enable the appropriate SCSI target ID(s) for your L20/40/60 tape library. The following lines must exist in /kernel/drv/sgen.conf after modification: device-type-config-list="changer"; name="sgen" class="scsi" target=0 lun=0; where target=<L20/40/60_SCSI_ID> (target is set to SCSI ID 0 above). Uncomment the appropriate "name=..." lines to support your L20/40/60 tape library SCSI target IDs. Do not modify the lun address as all L20/40/60 libraries use lun=0 in all cases. After completing this task, run: /usr/sbin/devfsadm -i sgen to create the /dev/scsi/changer/c#t#d# device link. d). In the patch directory, type the "tload" command to load the firmware: # ./tload L20_SUN-1_71S-dnld_all **NOTE** Do not rename the firmware filename or change it to lowercase characters. e). Select the device to be upgraded (see example below--the L20/40/60 tape library corresponds to a Vendor ID of HP and Product ID of C7200-8000). f). Answer the question: Do you want to download firmware to this tape device [N]? with a 'y' for yes or anything else for no. Default answer is no. **NOTE** While the SCSI Controller firmware is downloading, the LCD on the library will display various messages. It is good practice to monitor the LCD display while the download is occurring. g). If there is an additional device to be upgraded (same device type and desire to upgrade to the latest firmware), select that device as previously done in C.2.e). & C.2.f). above. Continue in this fashion until all desired devices have been upgraded. h). Quit the "tload" program by typing '0' (see example below). i). Repeat the above sequence of steps if you have had to make multiple firmware upgrades to bring the device to the latest firmware revision. j). After the device has been fully upgraded, the displayed tape device list will be refreshed. Device(s) upgraded should reflect having the new code level, "171S", in the "Rev" field (see example below). k). Upon completion of upgrading all L20/40/60 tape libraries, the user may move the /kernel/drv/sgen.conf.original file back to the original /kernel/drv/sgen.conf file thus restoring the original sgen configuration. ****************************************************************************** C.3 EXAMPLE # ######################################### # # Launch Tape Firmware Download Utility: # ######################################### # # ./tload L20_SUN-1_71S-dnld_all ATTACHED DEVICES: Device Supplier Product Rev Serial Number Device State -------------- -------- ---------------- ---- ------------- ------------- 1:0ln QUANTUM DLT8000 0258 PXB17P2902 Available 2:c5t5d0 HP C7200-8000 155S PRTN000054 Available Select Device(s) (ex: 1,3-4)0 to quit) [1]: 2 c5t5d0 HP C7200-8000 155S PRTN000054 Selected Do you want to download firmware to this device [N]? y ATTACHED DEVICES: Device Supplier Product Rev Serial Number Device State -------------- -------- ---------------- ---- ------------- ------------- 1:0ln QUANTUM DLT8000 0258 PXB17P2902 Available 2:c5t5d0 HP C7200-8000 155S PRTN000054 Downloading Downloading /dev/scsi/changer/c5t5d0... please wait. ATTACHED DEVICES: Device Supplier Product Rev Serial Number Device State -------------- -------- ---------------- ---- ------------- ------------- 1:0ln QUANTUM DLT8000 0258 PXB17P2902 Available 2:c5t5d0 HP C7200-8000 155S PRTN000054 Writing Flash Select Device(s) (ex: 1,3-4) or 0 to quit) [2]: 0 ATTACHED DEVICES: Device Supplier Product Rev Serial Number Device State -------------- -------- ---------------- ---- ------------- ------------- 1:0ln QUANTUM DLT8000 0258 PXB17P2902 Available 2:c5t5d0 HP C7200-8000 171S PRTN000054 F/W Upgraded # ######################################### # # The example above only upgrades one # device. You do not have to exit with # a "0" and initiate the 'tload' utility # again. You may continue instead and # directly upgrade the next tape device, # following the same steps as before # for each device until all devices # have been upgraded # ######################################### # # ######################################### # # After devices are upgraded, the Rev # will be 171S # ######################################### # # ######################################### # # To Quit, enter '0'. System prompt # will return. # ######################################### # ************************************************************************** ************************************************************************** C.4 tload (ABOUT THE UTILITY): tload - Firmware Download utility for tape drives. SYNOPSIS tload [ filename ] [ -v ] filename firmware/microcode filename DESCRIPTION tload is an firmware download utility for Sun supported tape devices. If the firmware_file is specified, then it will display the list of tape devices present on the host system and asks the user to select the tape device which is to be upgraded. If the firmware_file is not specified, then it will display the list of tape devices present on the host system along with their FIRMWARE revision levels. tload will exit upon completion; please do not attempt to halt or stop prior to utility's menu exit option being presented. The command can be run only as a super-user. DISCLAIMER This utility is ONLY supported for downloading, to Sun supported tape devices, the Sun supported firmware binary (firmware_file) which has officially been released via the official Sun Patch Process. This utility is only supported with the release of firmware (binary) bundled with said patch. Do not attempt to use any other version of 'tload' that may have been acquired previously else device damage may occur. Use only the version provided with this patch, version 4.1 (tload). Use of tload to load non-Sun supported tape devices is at the user's own risk, and is not supported. Use of tload to load Sun supported tape devices with firmware NOT bundled with the utility in an officially released Sun Patch is at the user's own risk, and is not supported. PROBLEMS Any problems regarding this utility by the user following proper procedures should be reported to the user's service provider along with the following items: 1) /var/adm/messages file 2) explorer dump 3) tload <firmware_file> -v README -- Last modified date: Thursday, February 10, 2005
================================================================================
================================================================================


 


Marcos


<div>
Hola.<br>Tengo un Storedge_L20 al que actualice el firmware al 111972-05 cuando cargue el archivo&nbsp; L20-SUN-1_05S-dnld_all, me reseteo la configuracion de la placa de red y tambien el password..!!! Lo upgrade via ftp, user: downlod y el pass: es el de administrador, hasta ese momento era: 11111111 (lo pusieron los anteriores due&ntilde;os del equipo).<br>Ya porbe los pass por default que aparencen en internet y nada (12341234, no pass, 42311324), y con este modelo no se puede hacer nada sin el password de adminstrador.<br>Les agradeceria si alguien me puede ayudar de alguna manera.<br><br>PD: adjunto el README:<br>============================================================================<br>============================================================================<br><div class="marked">Status:&nbsp;RELEASEDPatch Id:&nbsp;111972-05Summary:&nbsp;L20/L40/L60 robotics firmware upgradeDate:&nbsp; Feb/10/2005Installation Requirements:Additional instructions may be listed belowSolaris Release:&nbsp;Sun OS Release:&nbsp;Unbundled Product:&nbsp;Hardware/TapeUnbundled Release:&nbsp;N/AXref:&nbsp;Topic:&nbsp;Relevant Architecture:&nbsp;BugId's fixed with this patch:Changes incorporated in this version:<br><br>Patches accumulated and obsoleted by this patch:Patches which conflict with this patch:&nbsp;Required Patches:Obsoleted by:&nbsp;
    Files Included in this Patch:&nbsp;L20-SUN-1_05S-dnld_all (2,458,688 bytes)
L20-SUN-1_25S-dnld_all (2,326,528 bytes)
L20-SUN-1_33S-dnld_all (2,359,296 bytes)
L20-SUN-1_55S-dnld_all (2,457,600 bytes)
L20_SUN-1_71S-dnld_all (2,555,904 bytes)
README.111972-05
sgen.conf.example     (    2,899 bytes)
tload                 (   57,472 bytes)Problem Description:&nbsp;1) Internet Browser compatibility issue fixes new dependency of SUN
   Java 1.4.1_01 or later runtime plug-in now required for various browser
   support with this product's Remote Management Card (RMC).
2) Added a Front panel 'emergency' unload capability for HP LTO drives.
3) Added 25 sweeps once/day to the hourly maintenance routine. The default
   time is 12:00 PM (Noon). The 25-sweep maintenance hour is configurable.
   This sweeping prevents any oxidation of the transport track surface.
4) Various Front Panel and RMC messages enhanced.
5) Various SCSI, Logging, Error Reporting and Downloading issues addressed.
6) Various Motion enhancements.

(from <a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-21-111972-04-1">111972-04</a>)

<a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-1-4736628-1">4736628</a> Firmware 1.33 for L60 can prolong system boot up time.

(from <a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-21-111972-03-1">111972-03</a>)

<a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-1-4636180-1">4636180</a> robtest fails after upgrading firmware on L40 jukebox robotics

<a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-1-4635994-1">4635994</a> firmware is inconsistent, breaks netbackup functionality

(from <a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-21-111972-02-1">111972-02</a>)

<a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-1-4521629-1">4521629</a> 1.25.S firmware for L20, L40, L60 in <a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-21-111972-01-1">111972-01</a> causes major inventory 
problems.

 
NOTE: The firmware also needs to be updated in the L20/L40/L60 after any FRU 
       is removed or replaced to assure that the library has the newest 
       firmware possible.<a name="rev-history"></a>Revision History:&nbsp;<a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-21-111972-03-1">111972-03</a> <a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-21-111972-04-1">111972-04</a> <a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-21-111972-01-1">111972-01</a> <a href="http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-21-111972-02-1">111972-02</a> <br>Patch Installation Instructions:&nbsp;-------------------------------- 

None.Special Install Instructions:&nbsp;-----------------------------

---------------------------------------------------------------------------
Instructions for Updating Firmware in the L20/L40/L60 Series -- RMC Method
---------------------------------------------------------------------------

The following instructions explain how to, at a high level, upgrade the
firmware in the L20/L40/L60 series of libraries. The firmware that gets
updated is as follows:

 	Picker/Translator Assembly

 	Library Controller

 	RMC (Remote Management Control) Card 

NOTE: The GUI interface may be a bit different depending on the firmware 
      level present on the RMC card but most people should be able to follow 
      the steps below and perform the upgrade.

Before starting the upgrade procedure, assure that the RMC card is functioning 
properly and that an Administrator Password (done from front panel) is set 
up for the library. Also note the IP address for the library to be upgraded 
since the upgrade is done over the network by means of the host.  If the RMC
card is not available, see below: Instructions for Updating Firmware via SCSI
Download Proceduret -- tload Method.

To upgrade the firmware, do the following:

1)	Move the firmware files onto the directory-of-choice on the host.

2)	Open the Mozilla browser and type in the IP address for the library
	in the Mozilla Location field. When the connection is made, you 
	should see the the IP address followed by:  main_id.html

3)	During some upgrade installations, the NVRAM settings have been 
	corrupted, before downloading the firmware, document the following 
	information:
	*  SCSI I.D. for Library and all drives
	*  Admin password
	*  Network settings

4)	From the left column of choice, click on:  Configuration

5)	A sub-menu will open, then click on:  Firmware Download

6)	The Firmware Download page opens (Source Firmware File). Enter the 
	location of the file or else click on Browse to find the file. Then 
	click on the appropriate firmware file until it is highlighted and
	then click:  OK

	Due to firmware dependencies, multiple firmware loads may be required
	or the unit may show partial availability.  By rule:

	If 1.05S is currently loaded, first load 1.25S, then load
	1.33S, then load 1.55S, and finally load 1.71S.

	If 1.25S is loaded, first load 1.33S, then load 1.55S, and finally load
	1.71S.

	If 1.33S is loaded, first load 1.55S, and finally load 1.71S.

	If 1.55S is loaded, you may load 1.71S.

7)	Check the Source Firmware File box and assure the driver file is 
	there, then click:  Start Download

8)	If the Java Security windows open, click  Grant.  This is your way 
	of giving permission to do the download.

9)	When you are prompted for the Administration Password, enter the 
	password in the field.

10)	If the password is accurate and accepted, a Reboot Warning Message 
	appears to assure it will be safe for the library to reboot 
	automatically.

NOTE:	Assure that no backups or other important functions are occuring on 
	the library.

11)	The Download Monitor window appears and some messages are displayed, 
	such as Flash Erase/Rewrite. Please note the Progress Monitor doesn't 
	always stay current. The activity is also displayed on the front panel 
	of the library.

12) 	The library does a power-on reset and the Download Status Window shows 
	Completed. Close the download status and Mozilla browser windows.

13) 	Open a new Mozilla browser and type in the IP address for the library 
	in the Mozilla Location field. When the connection is made, you should 
	see the the IP address followed by:  main_id.html

14)	Making sure a connection is still available to the library as shown 
	above, click on: Identify

15)	The library will identify and show the latest loaded version of
	firmware.

16)	From the left column of choice, click on: Status

17)	A sub-menu will open, then click on: Overview    

18)	If the Drive Status is OK for all attached drives go on to step 24.

19)	If drive status is:  "No drives were detected" From the front panel
	of the L20/L40/L60, verify the SCSI IDs of the Library and Drives are 
	the same as documented in Step 3.  If they have changed, reset the
	original SCSI IDs. 

20)	Press the Shift key on the keyboard and click on the Mozilla browser
	window Reload Icon at the same time. This will reload the library 
	information to the Mozilla browser window without taking the 
	information from cache.

21)	From the left column of choice, click on: Status

22)	A sub-menu will open, then click on: Overview    

23)	Verify the Drive Status is OK for all attached drives.

24)	Repeat steps 4 through 23 for all remaining firmware files as required
	in Step 6.  When you click on: Identify, and the firmware version
	shows 1.55S, you have fully completed the upgrade procedure. 

---------------------------------------------------------------------------
Instructions for Updating Firmware via SCSI -- tload Method
---------------------------------------------------------------------------

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Contents
--------
A.0  Solaris/Driver Requirements
B.O  Precautionary Statements
C.O  Patch Installation and Utility Usage Instructions

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

A.0  Solaris/Driver Requirements
-----------------------------------------------
Solaris 8 and later bundled with a uscsi compliant driver such as the 'sgen'
driver is required for this procedure.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

B.0  Precautionary Statements
-----------------------------

**WARNING:****WARNING:****WARNING:****WARNING:****WARNING:****WARNING:**
 
B.1 The system MUST BE IDLE during the firmware download process!  No
    other programs should be running while this utility is being used.
    Failure to do so may cause the devices being upgraded to fail or
    the system to crash.

    Any other computers sharing the same I/O bus as the host system
    must be either disconnected or offline.

B.2 If any upgrade failures occur, do not continue upgrading devices.
    For example, loss of power during download will result in damaged
    peripherals and require replacement.

    If any failures occur, please collect the following log file:
    "/var/adm/messages", and an explorer dump.  Please forward these
    files to your service provider for analysis.

B.3 This package will only function on StorEdge L20/40/60 Tape Libraries.

B.4 Please READ instructions below completely BEFORE starting download
    procedure.  Follow the procedures carefully.  You may program
    multiple libraries at the same time, however, you may not exit the
    utility until all libraries have completed the download process.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

C.O  Patch Installation and Utility Usage Intructions
-----------------------------------------------------

C.1 General guidelines for upgrading:

        EJECT MEDIA FROM DEVICE TO BE UPGRADED.  Download utility will
        eject media from the device if it is found to be loaded.  Do
        NOT attempt to force media back into the drive.

        STOP ALL APPLICATIONS. The system must be idle during the
        firmware upgrade process.

        DISCONNECT or take OFFLINE any other computers sharing the same
        I/O bus as the host.

C.2 Firmware Dependencies and Download Order:

        Due to firmware dependencies, multiple firmware loads may be required
        or the unit may show partial availability.  By rule:

	If 1.05S is currently loaded, first load 1.25S, then load
	1.33S, then load 1.55S, and finally load 1.71S.

	If 1.25S is loaded, first load 1.33S, then load 1.55S, and finally load 
	1.71S.

        If 1.33S is loaded, first load 1.55S, and finally load 1.71S.

	If 1.55S is loaded, you may load 1.71S.

        In case of any disruption or unforeseen events happening on the
        relevant bus during the firmware download process, it may be
        that the upgraded device becomes non-functional.  In this event,
        it will be necessary to replace the device. This would happen
        as a result of an incomplete or corrupted firmware file being
        downloaded.  Loss of power during the upgrade process would also
        damage the device.

**NOTE**    If you cannot upgrade devices due to software application
            interference, try booting off of the Solaris release CD.

**NOTE**    After the firmware download is completed, it may be necessary
            to power cycle the device to ensure fully resetting the device.
            In turn, this may also require a successive reboot of the host
            system to ensure all functionality is restored.

 
C.3 Procedure for L20/40/60 Tape Library Firmware Download:

The procedure to be used for upgrading the device's firmware is explained
below.  Total upgrade time will be approximately 10-15 minutes for each device.
You must have root/super-user privileges in order to perform this operation.

a). Ensure you are logged in as root on the machine attached to the L20/40/60
    tape libraries you wish to upgrade.

b). Unpack the patch (through tar) into any directory, e.g. /var/spool/patch
    (Note, if the patch ends in a ".Z" suffix, you will need to first
    uncompress it.)  Example:
	# uncompress &lt;filename.tar.Z&gt;
        # tar xvf &lt;filename.tar&gt;

c). Modify the /kernel/drv/sgen.conf file so that the sgen target driver will
    have a device link allowing access to the L20/40/60 tape libraries via a
    /dev/scsi/changer device link.

    SUGGESTED METHOD:
    ----------------
    The sgen.conf.example file included with this patch may be utilized by
    first moving /kernel/drv/sgen.conf to /kernel/drv/sgen.conf.bak.  Secondly,
    copy the included sgen.conf.example file to /kernel/drv/sgen.conf which
    supports tape library target (changer) devices operating on a parallel
    SCSI bus (SCSI target ID's 0-15 are supported).

    After completing this task, run:
	  /usr/sbin/devfsadm -i sgen
    to create the /dev/scsi/changer/c#t#d# device link.

 
    MANUAL METHOD:
    -------------
    Note:  If you have used the SUGGESTED METHOD, skip to step C.2.d below in
	   this section, else for manual sgen modifications:

    Refer to /kernel/drv/sgen.conf and/or the sgen man page for instructions
    on how to configure the sgen driver (included in Solaris 8 and later) to
    support tape library target (changer) devices operating on a parallel SCSI
    bus.

    First, copy /kernel/drv/sgen.conf to /kernel/drv/sgen.conf.bak to ensure
    preservation of the original sgen.conf file.

    Modify /kernel/drv/sgen.conf to enable sgen attach to tape library target
    (changer) devices operating on a parallel SCSI bus and enable the
    appropriate SCSI target ID(s) for your L20/40/60 tape library.

    The following lines must exist in /kernel/drv/sgen.conf after modification:

		device-type-config-list="changer";
		name="sgen" class="scsi" target=0 lun=0;

    where target=&lt;L20/40/60_SCSI_ID&gt; (target is set to SCSI ID 0 above).
    Uncomment the appropriate "name=..." lines to support your L20/40/60 tape 
    library SCSI target IDs. Do not modify the lun address as all L20/40/60
    libraries use lun=0 in all cases.

    After completing this task, run:
	  /usr/sbin/devfsadm -i sgen
    to create the /dev/scsi/changer/c#t#d# device link.

d). In the patch directory, type the "tload" command to load the firmware:
        # ./tload L20_SUN-1_71S-dnld_all

**NOTE**    Do not rename the firmware filename or change it to lowercase
            characters.

e). Select the device to be upgraded (see example below--the L20/40/60 tape
    library corresponds to a Vendor ID of HP and Product ID of
    C7200-8000).

f). Answer the question:
       Do you want to download firmware to this tape device [N]?
    with a 'y' for yes or anything else for no.  Default answer is no.

**NOTE**  While the SCSI Controller firmware is downloading, the LCD on the
          library will display various messages.  It is good practice to
	  monitor the LCD display while the download is occurring.

g). If there is an additional device to be upgraded (same device type
    and desire to upgrade to the latest firmware), select that device
    as previously done in C.2.e). &amp; C.2.f). above.  Continue in this
    fashion until all desired devices have been upgraded.

h). Quit the "tload" program by typing '0' (see example below).

i). Repeat the above sequence of steps if you have had to make multiple
    firmware upgrades to bring the device to the latest firmware revision.

j). After the device has been fully upgraded, the displayed tape device
    list will be refreshed.  Device(s) upgraded should reflect having
    the new code level, "171S", in the "Rev" field (see example below).

k). Upon completion of upgrading all L20/40/60 tape libraries, the user may move
    the /kernel/drv/sgen.conf.original file back to the original
    /kernel/drv/sgen.conf file thus restoring the original sgen configuration.
******************************************************************************

C.3  EXAMPLE

#
#########################################
#
# Launch Tape Firmware Download Utility:
#
#########################################
#
# ./tload L20_SUN-1_71S-dnld_all 

 
ATTACHED DEVICES:

Device          Supplier  Product           Rev   Serial Number  Device State
--------------  --------  ----------------  ----  -------------  -------------
1:0ln           QUANTUM   DLT8000           0258  PXB17P2902     Available    
2:c5t5d0        HP        C7200-8000        155S  PRTN000054     Available    

Select Device(s) (ex: 1,3-4)0 to quit) [1]: 2

c5t5d0          HP        C7200-8000        155S  PRTN000054     Selected

Do you want to download firmware to this device [N]? y

ATTACHED DEVICES:

Device          Supplier  Product           Rev   Serial Number  Device State
--------------  --------  ----------------  ----  -------------  -------------
1:0ln           QUANTUM   DLT8000           0258  PXB17P2902     Available    
2:c5t5d0        HP        C7200-8000        155S  PRTN000054     Downloading  

Downloading /dev/scsi/changer/c5t5d0... please wait.

ATTACHED DEVICES:

Device          Supplier  Product           Rev   Serial Number  Device State
--------------  --------  ----------------  ----  -------------  -------------
1:0ln           QUANTUM   DLT8000           0258  PXB17P2902     Available    
2:c5t5d0        HP        C7200-8000        155S  PRTN000054     Writing Flash

Select Device(s) (ex: 1,3-4) or 0 to quit) [2]: 0

ATTACHED DEVICES:

Device          Supplier  Product           Rev   Serial Number  Device State
--------------  --------  ----------------  ----  -------------  -------------
1:0ln           QUANTUM   DLT8000           0258  PXB17P2902     Available    
2:c5t5d0        HP        C7200-8000        171S  PRTN000054     F/W Upgraded 

#
#########################################
#
# The example above only upgrades one
# device.  You do not have to exit with
# a "0" and initiate the 'tload' utility
# again.  You may continue instead and
# directly upgrade the next tape device,
# following the same steps as before
# for each device until all devices
# have been upgraded
#
#########################################
#

 
#
#########################################
#
# After devices are upgraded, the Rev
# will be 171S
#
#########################################
#

#
#########################################
#
# To Quit, enter '0'.  System prompt
# will return.
#
#########################################
#

**************************************************************************
**************************************************************************
 
C.4  tload (ABOUT THE UTILITY):

 
   tload - Firmware Download utility for tape drives.

SYNOPSIS

   tload [ filename ] [ -v ] 
        filename        firmware/microcode filename

DESCRIPTION

   tload is an firmware download utility for Sun supported tape 
   devices.

   If the firmware_file is specified, then it will display the list 
   of tape devices present on the host system and asks the user to 
   select the tape device which is to be upgraded.

   If the firmware_file is not specified, then it will display the 
   list of tape devices present on the host system along with their 
   FIRMWARE revision levels.

   tload will exit upon completion; please do not attempt to halt or 
   stop prior to utility's menu exit option being presented.

   The command can be run only as a super-user.

DISCLAIMER

   This utility is ONLY supported for downloading, to Sun supported
   tape devices, the Sun supported firmware binary (firmware_file)
   which has officially been released via the official Sun Patch 
   Process.  This utility is only supported with the release of
   firmware (binary) bundled with said patch.

   Do not attempt to use any other version of 'tload' that may have
   been acquired previously else device damage may occur.  Use only 
   the version provided with this patch, version 4.1 (tload).

   Use of tload to load non-Sun supported tape devices is at
   the user's own risk, and is not supported.

   Use of tload to load Sun supported tape devices with firmware
   NOT bundled with the utility in an officially released Sun Patch 
   is at the user's own risk, and is not supported.

PROBLEMS

   Any problems regarding this utility by the user following proper 
   procedures should be reported to the user's service provider along
   with the following items:
        1) /var/adm/messages file
        2) explorer dump
	3) tload &lt;firmware_file&gt; -v

README -- Last modified date:  Thursday, February 10, 2005<br>================================================================================<br>================================================================================<br>
</div>
<br><br>&nbsp;<br><div><div align="right">
<br><br>Marcos <br>
</div></div>
<br><br>
</div>
Jesus Cea | 30 Sep 2010 14:30
Picon
Favicon

Actualización de Solaris 10 con "Live Upgrade" (de Update 8 a Update 9)


Por si a alguien le resulta útil:

http://www.jcea.es/artic/sol10lu9.htm

El procedimiento se me complica mucho por detalles de como tengo (mal)
configurada esta máquina. En un caso más normal, el procedimiento
debería ser simple e indoloro.

--

-- 
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea <at> jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea <at> jabber.org         _/_/    _/_/          _/_/_/_/_/
.                              _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
Francisco Javier Garcia | 28 Sep 2010 17:30

Y el penultimo en abandonar el barco es.....


El creador de ZFS... Jeff Bonwicks...


http://blogs.sun.com/bonwick/entry/and_now_page_2


Me encantaría que fuera a Nexenta o Joyent....

<div>
<div class="gmail_quote">
<br>El creador de ZFS... Jeff Bonwicks...<br><br><br><a href="http://blogs.sun.com/bonwick/entry/and_now_page_2" target="_blank">http://blogs.sun.com/bonwick/entry/and_now_page_2</a><br><br><br>Me encantar&iacute;a que fuera a Nexenta o Joyent....<br>
</div>
<br>
</div>

Gmane