<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">Patch-ID# 115786-03
Keywords: storedge psx1000 storage firmware
Synopsis: PSX1000 R02.00.01.147: StorEdge PSX1000 firmware upgrade
Date: Jun/29/2004


Install Requirements: None                      
                      
Solaris Release: 8 9

SunOS Release: 5.8 5.9

Unbundled Product: StorEdge PSX1000 Firmware

Unbundled Release: R02.00.01.147

Xref: 

Topic: 

Relevant Architectures: sparc

BugId's fixed with this patch: 4761229 4807833 4820632 4821697 4850250 4852623 4853760 4860448 4952395 5043817

Changes incorporated in this version: 5043817

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

	3.0.1_README.txt # Readme for installing the file 3.0.1_Update.exe
	3.0.1_Update.exe # Update for Sun StorEdge Traffic Manager 3.0
        README.115786-03 # This file
        patchinfo
        rn2.0.01.145.pdf # Release notes
dist.par         # PSX1000 Firmware rev R02.00.01.147

Problem Description:

PSX1000 firmware version R02.00.01.147 addresses the following issues:
 
4952395 T3 F/W 3.1 causes problems with PSX-1000
4860448 Rebooting a chassis that is passing heavy I/O causes the Management
        Interface Card (MIC) to halt processor 3/1 or 4/1.
4807833 T3 LUNs do not fail back to their storage processors (SPs) when a failed
        Storage Resource Card (SRC) path is restored.
4850250 During Switch Fabric Card (SFC) or Storage Resource Card (SRC) failovers,
        the PSX-1000 experiences LUN degradation or loss due to bus-level
        transaction (ABTS) timeouts.
4852623 When rebooting the PSX-1000 during a software upgrade, the chassis halts
        due to a Fibre Channel (FC) Extended Link Services (ELS) issue, thereby
        delaying the reboot.
4853760 T3 LUNs do not failover or pause for up to three (3) minutes.
        This issue was resolved by modifying PSX-1000 internal retries to speed LUN
        failover times.
4761229 The PSX-1000 does not use the LUN primary controller when accessing
        T3/6320/6120/6020 LUNs.
4820632/4821697 When creating a volume and specifying the maximum available disk space
        (-force option used), only the maximum contiguous available disk space is
        reserved for the volume, not the entire available disk space on the T3.
5043817 Unable to set the clock at the time and date we want.

Patch Installation Instructions:
--------------------------------
 
This patch contains firmware which is installed on the StorEdge PSX1000,
rather than using installpatch or patchadd. This patch also contains an
update to the Sun StorEdge Traffic Manager 3.0 for Microsoft Windows NT.
For instructions on installing that update please refer to the file 
3.0.1_README.txt included in this patch.
 
Prerequisites for installing the new firmware include:
 
 
 * An RS232 Serial and an Ethernet connection from a Solaris host to the
   PSX1000.  To use the Ethernet connection, the PSX1000 must
   have an IP address assigned and the user must know the password
   assigned to the PSX1000. The ethernet connection is required to
   download the firmware image via ftp.
 
Unpack the patch into any convenient directory such as /var/tmp, and refer
to the Special Install Instructions below.

Special Install Instructions:
----------------------------- 
 
*** Warning *** Warning *** Warning *** Warning *** Warning ***
 
The PSX1000 supports two options to upgrade its firmware. When the
upgrade is initiated with the command "upgrade -a", the new firmware 
will be installed and the entire chassis will be rebooted with the 
new firmware. When the upgrade is initiated with the command
"upgrade -u", a rolling firmware upgrade will be initiated.
 
Using the firmware upgrade procedure that invokes the upgrade
command with the -a option will prevent the PSX1000 from servicing
normal I/O requests for several minutes.To avoid any possibility of 
application failures or filesystem corruption, it is necessary to
ensure that no host I/O is permitted while the upgrade is taking 
place.  For this reason, all PSX1000 logical disks should be unmounted,
from any Solaris hosts connected to the PSX1000, for the duration of the
install procedure.  For example, filesystems mounted on the PSX1000
should be unmounted, and databases accessing raw devices on the PSX1000
should be shut down.
 
 
PSX1000 Firmware Upgrade Option 1, "upgrade -a":
------------------------------------------------
 
 1. Change your working directory to the directory in which the patch
    was unpacked and confirm that the dist.par file is present
    using the "ls" command.
 
 2. Connect to the PSX1000 with the "ftp" command and transfer the
    image (the file dist.par) to the PSX1000. You must use binary mode to
    transfer the dist.par file.
 
       # ftp 10.1.1.1
       Connected to 10.1.1.1
       220 Pirus (1.0) FTP server ready
       Name (10.1.1.1:root): root
       331 Password required
       Password:
       230 User logged in
       ftp&gt; bin
       200 Type set to I, binary mode
       ftp&gt; put dist.par
       200 Port set okay
       150 Opening BINARY mode data connection
       226 Transfer complete
       local: dist.par remote: dist.par
       7274730 bytes sent in 6.3e+02 seconds (11.31 Kbytes/s)
       ftp&gt; bye
       221 Bye...see you later
       #
 
 3. Open a telnet or serial connection to the PSX1000 and issue the command
    "upgrade -a".
 
       PSX-1000# upgrade -a
       OK to overwrite configuration file[Y]? y
       Building configuration...................File A:\startup.cfg Created.
       ** WARNING: ABOUT TO UPGRADE SW on ENTIRE CHASSIS
       Are you sure(y/n)?y
       ** starting upgrade process - auto reboot mode
 
 4. Open a telnet connection to the PSX1000 and issue the command "show version"
    to verify that the firmware upgrade was successful.
 
	PSX-1000# show version
 
	VINFO: version info of all images in RAM on line cards:
 
           Image     Revision        Date        Time      Build     Build
Card Proc  Name      PC: PSX1000                           User      Host
==== ====  ========  ==============  ==========  ========  ========  ==========
MIC  SLV   micoper   R02.00.01.0147  06/24/2004  15:38:08  clearcas  PANDORA  
 6    0    nineoper  R02.00.01.0147  06/24/2004  15:41:44  clearcas  PANDORA  
 5    0    nineoper  R02.00.01.0147  06/24/2004  15:41:44  clearcas  PANDORA  
 3    0    nineoper  R02.00.01.0147  06/24/2004  15:41:44  clearcas  PANDORA  
 4    0    nineoper  R02.00.01.0147  06/24/2004  15:41:44  clearcas  PANDORA  
 3    1    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 3    3    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 4    1    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 4    2    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 4    4    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 3    2    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 3    4    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 4    3    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
MIC  MAS   micoper   R02.00.01.0147  06/24/2004  15:38:08  clearcas  PANDORA   
 
 
PSX1000 Firmware Upgrade Option 2, rolling upgrade, "upgrade -u":
------------------------------------------------
 
 1. Change your working directory to the directory in which the patch
    was unpacked and confirm that the dist.par file is present
    using the "ls" command.
 
 2. Connect to the PSX1000 with the "ftp" command and transfer the
    image (the file dist.par) to the PSX1000. You must use binary mode to
    transfer the dist.par file.
 
       # ftp 10.1.1.1
       Connected to 10.1.1.1
       220 Pirus (1.0) FTP server ready
       Name (10.1.1.1:root): root
       331 Password required
       Password:
       230 User logged in
       ftp&gt; bin
       200 Type set to I, binary mode
       ftp&gt; put dist.par
       200 Port set okay
       150 Opening BINARY mode data connection
       226 Transfer complete
       local: dist.par remote: dist.par
       7274730 bytes sent in 6.3e+02 seconds (11.31 Kbytes/s)
       ftp&gt; bye
       221 Bye...see you later
       #
 
3. Open a serial connection to the PSX1000. Type the commands "config" and
   "logging console" to route event messages to the console. Type the
   command "upgrade -u".
 
	PSX-1000# config
	PSX-1000(config)# logging console
 
	  Console logging is enabled
 
	PSX-1000# upgrade -u
** WARNING: ABOUT TO UPGRADE SW on ENTIRE CHASSIS
Are you sure(y/n)?
** starting upgrade process - manual reboot mode
PIRUS upgrade process -  START.
  disk space check ... OK
 phase 1:
  verifying PAR file - dist.par
 phase 2:
  un-PARing PAR file - dist.par
 
total files: 38
 
  checksum NEW PBZ files in newsw/
  checksum newsw/F_DMA.PBZ      ... OK
  checksum newsw/F_DMA_2.PBZ    ... OK
  checksum newsw/F_DMA_3.PBZ    ... OK
  checksum newsw/F_MEM.PBZ      ... OK
  checksum newsw/F_MEM_2.PBZ    ... OK
  checksum newsw/F_MEM_3.PBZ    ... OK
  checksum newsw/F_QM.PBZ       ... OK
  checksum newsw/F_QM_2.PBZ     ... OK
  checksum newsw/F_QM_3.PBZ     ... OK
  checksum newsw/F_QM_4.PBZ     ... OK
  checksum newsw/F_SCH.PBZ      ... OK
  checksum newsw/F_SCH_2.PBZ    ... OK
  checksum newsw/F_SI.PBZ       ... OK
  checksum newsw/F_SI_2.PBZ     ... OK
  checksum newsw/F_SI_3.PBZ     ... OK
  checksum newsw/F_SI_I.PBZ     ... OK
  checksum newsw/F_XBAR.PBZ     ... OK
  checksum newsw/F_XBAR_A.PBZ   ... OK
  checksum newsw/MICOPER.PBZ    ... OK
  checksum newsw/NINEOPER.PBZ   ... OK
  checksum newsw/SRCMED.PBZ     ... OK
  renaming mgmt to origmgmt
  renaming newmgmt to mgmt
  deleting ORIG PBZ files from /
  deleting F_DMA.PBZ    from /
  deleting F_DMA_2.PBZ  from /
  deleting F_DMA_3.PBZ  from /
  deleting F_MEM.PBZ    from /
  deleting F_MEM_2.PBZ  from /
  deleting F_MEM_3.PBZ  from /
  deleting F_QM.PBZ     from /
  deleting F_QM_2.PBZ   from /
  deleting F_QM_3.PBZ   from /
  deleting F_QM_4.PBZ   from /
  deleting F_SCH.PBZ    from /
  deleting F_SCH_2.PBZ  from /
  deleting F_SI.PBZ     from /
  deleting F_SI_2.PBZ   from /
  deleting F_SI_3.PBZ   from /
  deleting F_SI_I.PBZ   from /
  deleting F_XBAR.PBZ   from /
  deleting F_XBAR_A.PBZ from /
  deleting NINEOPER.PBZ from /
  deleting SRCMED.PBZ   from /
  copying  NEW PBZ files to /
  copying  newsw/F_DMA.PBZ    to /  OK
  copying  newsw/F_DMA_2.PBZ  to /  OK
  copying  newsw/F_DMA_3.PBZ  to /  OK
  copying  newsw/F_MEM.PBZ    to /  OK
  copying  newsw/F_MEM_2.PBZ  to /  OK
  copying  newsw/F_MEM_3.PBZ  to /  OK
  copying  newsw/F_QM.PBZ     to /  OK
  copying  newsw/F_QM_2.PBZ   to /  OK
  copying  newsw/F_QM_3.PBZ   to /  OK
  copying  newsw/F_QM_4.PBZ   to /  OK
  copying  newsw/F_SCH.PBZ    to /  OK
  copying  newsw/F_SCH_2.PBZ  to /  OK
  copying  newsw/F_SI.PBZ     to /  OK
  copying  newsw/F_SI_2.PBZ   to /  OK
  copying  newsw/F_SI_3.PBZ   to /  OK
  copying  newsw/F_SI_I.PBZ   to /  OK
  copying  newsw/F_XBAR.PBZ   to /  OK
  copying  newsw/F_XBAR_A.PBZ to /  OK
  copying  newsw/NINEOPER.PBZ to /  OK
  copying  newsw/SRCMED.PBZ   to /  OK
  copying  newsw/MICOPER.PBZ file to /MICOPER.NEW
  deleting /MICOPER.PBZ
  renaming /MICOPER.NEW to /MICOPER.PBZ
 
*****************************
*****************************
  UPGRADE phase 1 + 2 complete
  MUST reboot system!!!
 
4. After the upgrade command completes issue the command "reboot warm".
 
	PSX-1000# reboot warm
	Are you sure you want to reboot the MIC[N]? y
	OK to overwrite configuration file[Y]? 
	Building configuration...
 
5. After the management card reboots, login and issue the command "shutdown card 5".
 
	PSX-1000# shutdown card 5
	Shutting down card 5
	CPCM: SFC secondary card:5 halted!!
 
6. Wait for the message "Shutdown complete for card (5)" then type the command
   "reload card 5".  
 
        PSX-1000# reload card 5
	Restarting card 5
 
7. Wait for the message "(HOT_SWAP: 0-0)  Restart complete for card (5)" then
   repeat steps 5 and 6 above for card 6 and for the two SRC cards. The SRC cards
   may be installed in slots 1 and 2 or 3 and 4. To verify in which slots the SRC
   cards are installed you can issue the command "show chassis".
 
	PSX-1000# show chassis
 
--------------------------------------------------------------------------
Licensed Chassis Identifier:  100040
--------------------------------------------------------------------------
 
Power Supply   State                    Fan Tray State
-------------+-----------------------+------------------
     A         On                       On
     B         On
 
Slot Card Description                              CPUs Ports State
----+---------------------------------------------+----+-----+------------
   1   -- Empty --
       -- Empty --
   2   -- Empty --
       -- Empty --
   3 Storage Resource Card                            1     0 Normal
     Storage IO / 4 Port Two Gig Fibre Channel        5     4 Normal
   4 Storage Resource Card                            1     0 Normal
     Storage IO / 4 Port Two Gig Fibre Channel        5     4 Normal
   5 Switch Fabric Card                               1     0 Normal
     Management Interface Card                        1     1 Normal
   6 Switch Fabric Card                               1     0 Standing By
     Management Interface Card                        1     1 Standing By
 
8. Open a telnet connection to the PSX1000 and issue the command "show version" to
   verify that the firmware upgrade was successful.
 
	PSX-1000# show version
 
	VINFO: version info of all images in RAM on line cards:
 
           Image     Revision        Date        Time      Build     Build
Card Proc  Name      PC: PSX1000                           User      Host
==== ====  ========  ==============  ==========  ========  ========  ==========
MIC  SLV   micoper   R02.00.01.0147  06/24/2004  15:38:08  clearcas  PANDORA  
 6    0    nineoper  R02.00.01.0147  06/24/2004  15:41:44  clearcas  PANDORA  
 5    0    nineoper  R02.00.01.0147  06/24/2004  15:41:44  clearcas  PANDORA  
 3    0    nineoper  R02.00.01.0147  06/24/2004  15:41:44  clearcas  PANDORA  
 4    0    nineoper  R02.00.01.0147  06/24/2004  15:41:44  clearcas  PANDORA  
 3    1    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 3    3    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 4    1    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 4    2    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 4    4    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 3    2    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 3    4    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
 4    3    srcmed    R02.00.01.0147  06/24/2004  15:52:29  clearcas  PANDORA  
MIC  MAS   micoper   R02.00.01.0147  06/24/2004  15:38:08  clearcas  PANDORA

README -- Last modified date:  Monday, July 5, 2004

</pre></body></html>