Sun StorEdge T3 Array Release Notes, Version 1.18 Controller
Contents
1. TABLE 6 Embedded Operating System and Driver Errors Error Type Numerical Value pSOS 00000001 0000 0FFF reserved 00001000 0000 1FFF embedded file system pREPC reserved pNA pRPC pX11 reserved Networking libraries MMUIib reserved serial driver tick timer driver reserved RAM disk driver reserved TFTP driver SLIP driver 0000 2000 0000 2FFF 00003000 0000 3FFF 0000 4000 0000 4FFF 0000 5000 0000 5FFF 0000 6000 0000 FFFF 0110 0000 01FF FFFF 0120 0000 0120 00FF 0120 0100 1000 FFFF 1001 0000 1001 FFFF 1002 0000 1002 FFFF 1003 0000 1003 FFFF 1004 0000 1004 FFFF 1005 0000 1005 FFFF 1006 0000 1006 FFFF 1007 0000 1007 FFFF reserved 1008 0000 1004 FFFF SCSI driver 1050 0000 105F FFFF reserved 1060 0000 FFFF FFFF Sun StorEdge T3 Array Release Notes December 20012. the first date is the level 2 firmware version and the second date is the level 3 version fru list ID TYPE VENDOR MODEL REVISION SERIAL ulctr controller card 0301 501 5710 02 0200 020001 101291 uZctr controller card 0301 501 5710 02 0200 020001 101786 uldl disk drive SEAGATE ST318203FSUN D94A LR465826 uld2 disk drive SEAGATE ST318203FSUN D94A LR465384 uld3 disk drive SEAGATE ST318203FSUN D94A LR539076 uld4 disk drive SEAGATE ST318203FSUN D94A LR450095 A Diagnostics Issue Caution The Sun StorEdge T3 array ofdg utility is for service use only Use of this feature will make data unavailable The Sun StorEdge T3 array firmware provides a command line and graphical user interface to a diagnostics tab provided by Sun StorEdge Component Manager 2 2 The ofdg utility is used to perform offline diagnostic testing This tool should be used only by qualified Sun service providers at this time The ofdg utility is limited in its test capabilities and must be run while the system is offline to avoid problems 6 Sun StorEdge T3 Array Release Notes December 2001 Sun Cluster Issues 4348012 DMP must be disabled in Sun Cluster 2 2 configurations If the Sun StorEdge T3 array is part of a Sun Cluster 2 2 configuration and you are using VERITAS Dynamic Multipathing DMP software installed on a cluster host there can be conflicts with SCSI reservations To avoid th
3. 0x200007 Unable to read attributes VN_MOUNTED 0x200008 Volume already mounted VN UNMOUNTED 0x200009 Volume not mounted VN MNTINUSE 0x20000A Mount point in use VN NOMEMORY 0x20000B Could not allocate memory for operation VN_ALREADYDSBL 0x20000C There s already a disabled drive VN_NODSBL 0x20000D No drives are disabled VN_ABORTED 0x20000E Operation aborted VN_NOTSUP 0x20000F Operation not supported VN_UNKVOL 0x200010 Unknown volume VN_RAIDERR 0x200015 RAID error VN_NOPART 0x200016 Partition has size 0 VN_PARTSMALL 0x200017 Partition too small VN_UNKVIF 0x200019 Unknown interface VN_UNKVIFTYP 0x20001A Unknown interface type VN_BADVOLNAME 0x20001B Bad volume name VN_BADVOLNAMELEN 0x20001C Bad volume name too long Sun StorEdge T3 Array Release Notes December 2001 TABLE 3 Volume Related VN Errors Continued Message Unsupported volume configuration Standby unit number is wrong Invalid drive specified Local volume bad Volume still mapped to a port Volume is uninitialized Operation is pending Cache mode must be set to auto for mirroring Cannot change cache mode when mirroring is on Cannot mount volume because multiple disabled drives Slice start parameter invalid or in use Bad slice name No more slice can be created Slice not found Incorrect slice size parameter encountered Slice name exceeded 12 charcters allowed Slice n
4. 0x500032 Disk 2 Not Present DK3 NOTEXIST 0x500033 Disk 3 Not Present DK4 NOTEXIST 0x500034 Disk 4 Not Present DK5 NOTEXIST 0x500035 Disk 5 Not Present DK6 NOTEXIST 0x500036 Disk 6 Not Present DK7 NOTEXIST 0x500037 Disk 7 Not Present DK8 NOTEXIST 0x500038 Disk 8 Not Present DK9 NOTEXIST 0x500039 Disk 9 Not Present DK NONE 0x50003A No Disk Present DK1 BYPASSED 0x500041 Disk 1 Bypassed DK2_BYPASSED 0x500042 Disk 2 Bypassed DK3_BYPASSED 0x500043 Disk 3 Bypassed DK4_BYPASSED 0x500044 Disk 4 Bypassed DK5 BYPASSED 0x500045 Disk 5 Bypassed DK6 BYPASSED 0x500046 Disk 6 Bypassed DK7_BYPASSED 0x500047 Disk 7 Bypassed DK8_BYPASSED 0x500048 Disk 8 Bypassed DK9_BYPASSED 0x500049 Disk 9 Bypassed DK1_NOTREADY 0x500051 Disk 1 Not Ready DK2_NOTREADY 0x500052 Disk 2 Not Ready DK3_NOTREADY 0x500053 Disk 3 Not Ready DK4_NOTREADY 0x500054 Disk 4 Not Ready DK5 NOTREADY 0x500055 Disk 5 Not Ready DK6 NOTREADY 0x500056 Disk 6 Not Ready 24 Sun StorEdge T3 Array Release Notes December 2001 TABLE 5 Unit Related Errors Interconnect Card and Other FRUs Continued Error Name Numerical Value Message DK7_NOTREADY DK8_NOTREADY DK9_NOTREADY CT_NOTEXIST CT_QLOGNRDY CT_SEL_ID LP_VSC_ERR LC1_OFFLINE LC2_OFFLINE LP_CABLE1 LP_CABLE2 LC1_NSTART LC2_NSTART CT_NOALTLP LP SWITCH1 LP SWITCH2 LP MUX ISO LP MUX TOP LP MUX MID LP MUX BOT 0x500057 0x500058 0x500059 0x500061 0x500062 0x50
5. FRUs Error Name Numerical Value Message PS1_NOTEXIST 0x500001 Power Supply 1 Not Present PS2_NOTEXIST 0x500002 Power Supply 2 Not Present PS1_NOBATT 0x500003 Power Supply 1 Battery Not Present PS2 NOBATT 0x500004 Power Supply 2 Battery Not Present PS1 DISABLED 0x500005 Power Supply 1 Disabled PS2 DISABLED 0x500006 Power Supply 2 Disabled PS1 DISABLE 0x500007 Power Supply 1 Shutting off PS2 DISABLE 0x500008 Power Supply 2 Shutting off PS1 FAN1FAIL 0x500011 Power Supply 1 Fan 1 Failed PS2 FAN1FAIL 0x500012 Power Supply 2 Fan 1 Failed PS1 FAN2FAIL 0x500013 Power Supply 1 Fan 2 Failed PS2_FAN2FAIL 0x500014 Power Supply 2 Fan 2 Failed PS1 OVERTEMP 0x500015 Power Supply 1 Over Temperature PS2 OVERTEMP 0x500016 Power Supply 2 Over Temperature PS1 SWOFF 0x500017 Power Supply 1 Switch Off PS2 SWOFF 0x500018 Power Supply 2 Switch Off PS1 DCNOK 0x500019 Power Supply 1 DC Not OK PS2 DCNOK 0x50001A Power Supply 2 DC Not OK PS1_ONBATT 0x500021 Power Supply 1 On Battery Sun StorEdge T3 Array Release Notes 23 TABLE 5 Unit Related Errors Interconnect Card and Other FRUs Continued Error Name Numerical Value Message PS2_ONBATT 0x500022 Power Supply 2 On Battery PS1_FANHIGH 0x500023 Power Supply 1 Fan High PS2_FANHIGH 0x500024 Power Supply 2 Fan High PS1 REFBATT 0x500025 Power Supply 1 Refresh Battery PS2 REFBATT 0x500026 Power Supply 2 Refresh Battery DK1 NOTEXIST 0x500031 Disk 1 Not Present DK2 NOTEXIST
6. before the host server If this scenario still occurs contact an authorized Sun Service provider or Sun Service at 1 800 USA 4SUN for an evaluation and suggested workaround Note Any modification to the system non volatile random access memory NVRAM configuration should be avoided as errors can result in extensive system down time Before making modifications to NVRAM contact Sun Service 4497814 Must telnet from the Same Subnet The telnet command must be run from a host on the same subnet as the Sun StorEdge T3 array Sun StorEdge T3 Array Release Notes 13 4415132 Auto Cache Mode for a Sun StorEdge T3 Array Workgroup Configuration Runs in Write Behind Mode A Sun StorEdge T3 Array workgroup configuration with the Auto caching mode set uses the write behind cache mode This configuration does not offer the redundancy to provide cache mirroring and operating without a host based mirroring solution could lead to data loss in the event of a controller failure With workgroup configurations use a host based mirroring solution to protect data 4427874 Running boot i command during firmware upgrades can cause command to hang On Sun StorEdge T3 arrays running pre 1 17 firmware versions using the boot i command to upgrade the controller firmware to version 1 18 can in rare cases cause the boot i command to hang If this happens reset the Sun StorEdge T3 array and run the boot i command again 4427400 boot dela
7. remove the Alternate Pathing AP file to make sure that both types of storage devices co exist properly To perform the following procedure you must be logged in as root 1 On the data host type ls 1 kernel drv ap 2 If the kernel drv ap file is of 0 length remove kernel drv ap by typing rm kernel drv ap Sun StorEdge T3 Array Release Notes 9 3 Reboot the system reboot If the kernel drv ap file is not of 0 length AP is installed and you cannot enable DMP because AP and DMP cannot co exist Sun Microsystems Inc recommends that you remove the AP product entirely using pkgrm 1m Refer to the AP product documentation for further details 4253044 Volume usage does not refresh Within the Volume Manager Storage Administrator VMSA product volume usage information might not be refreshed correctly If this problem is encountered restart the VMSA application to update the volume usage statistics Service Issues FRU removal for longer than 30 minutes will initiate a partner group shutdown If any field replaceable unit FRU is removed for an extended period of time thermal complications might result To prevent this the Sun StorEdge T3 array is designed so that an orderly shutdown occurs when a component is removed for longer than 30 minutes Therefore a replacement part must be immediately available before starting a FRU replacement procedure You must replace a FRU that has been removed withi
8. the Controller swap to ensure the same IP address is retrieved from the RARP server when the new Sun StorEdge T3 array boots up Once the system comes up the root password should be null so this will have to be set up Sun StorEdge T3 Array Release Notes 11 4348664 fru list command should display new drive firmware versions automatically After upgrading the Sun StorEdge T3 array internal drive firmware perform a disk version umndl1 9 operation on the upgraded drives This Sun StorEdge T3 array command ensures that correct drive firmware version information gets updated correctly in internal databases If you do not do this after a drive firmware upgrade it is possible that stale drive firmware version information can be displayed when using the fru list command For more information on using the disk version and fru list commands refer to the Sun StorEdge T3 Array Administrator s Guide System Level Issues Dissimilar Disk Drives All Sun StorEdge T3 array disk drives either in a workgroup or an enterprise configuration must have the same storage capacity and drive speed Bootability The Sun StorEdge T3 array supports warm bootability for hosts running the Solaris operating environment that are connected by a Sun StorEdge SBus Dual Fibre Channel Host Bus Adapter p n X6730A Warm bootability means that the Sun StorEdge T3 array must be completely booted before attempting to boot the host from the Sun StorEdge T3 array volume
9. 0063 0x500064 0x500065 0x500066 0x500067 0x500068 0x500069 0x50006A 0x50006B 0x500071 0x500072 0x500073 0x500074 0x500075 0x500076 Disk 7 Not Ready Disk 8 Not Ready Disk 9 Not Ready Controller Not Present Qlogic Chip Not Ready Select ID Changed VSC7120 Loop Failed Loop Card 1 Offline Loop Card 2 Offline Cable 1 Not Present Cable 2 Not Present Loop Card 1 Failed to Start Loop Card 2 Failed to Start No Alternate Loop Switch to Loop 1 Switch to Loop 2 Loop Mux Changed to Isolated Loop Mux Changed to Top Loop Mux Changed to Middle Loop Mux Changed to Bottom Other Errors You will rarely see other types of errors such as logical volume manager LVM errors range 0x10001 0x1000A and operating system errors range 00000001 COOOFFFF The tftp error numerical values 10060001 10060005 is an exception that you can see when you try to download a new binary The tftp errors are usually generated by one of the following m The permissions for the file to be downloaded are too restrictive In general binaries should be world readable and executable m The checksum for the binary file to be downloaded is erroneous Sun StorEdge T3 Array Release Notes 25 a The Sun StorEdge T3 arrays have not been recognized by the network In this case a system administrator should make sure that the IP addresses of the Sun StorEdge T3 arrays are entered in the network database 26 The following table lists pSOS errors
10. MENTATION EST FOURNIE EN L ETAT ET TOUTES AUTRES CONDITIONS DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE A L APTITUDE A UNE UTILISATION PARTICULIERE OU A L ABSENCE DE CONTREFA ON ED me Ca Adobe PostScript Sun StorEdge T3 Array Release Notes Introduction This document contains important information about the Sun StorEdge T3 array that was not available at the time the product documentation was published Review this document so that you are aware of issues or requirements that can impact the installation and operation of the Sun StorEdge T3 array The information in this document supplements the information contained in the Sun StorEdge T3 Array Installation Operation and Service Manual and the Sun StorEdge T3 Array Administrator s Guide Use this release note in conjunction with other release notes and README files that you may have received with other software products related to the Sun StorEdge T3 array such as Sun StorEdge Component Manager software and VERITAS Volume Manager These release notes are organized as follows Required Patches on page 2 Required Firmware on page 4 General Issue on page 4 Firmware Updates and Modifications on page 5 Diagnostics Issue on page 6 Sun Cluster Issues on page 7 VERI
11. Sun Microsystems Inc 901 San Antonio Road Palo Alto CA 94303 U S A 650 960 1300 Part No 816 4107 10 December 2001 Revision 01 Send comments about this document to doc feedback sun com sS amp SUN microsystems Sun StorEdge T3 Array Release Notes Version 1 18 Controller Firmware Copyright 2001 Sun Microsystems Inc 901 San Antonio Road Palo Alto CA 94303 4900 U S A All rights reserved This product or document is distributed under licenses restricting its use copying distribution and decompilation No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors if any Third party software including font technology is copyrighted and licensed from Sun suppliers Parts of the product may be derived from Berkeley BSD systems licensed from the University of California UNIX is a registered trademark in the U S and other countries exclusively licensed through X Open Company Ltd Sun Sun Microsystems the Sun logo AnswerBook2 docs sun com SunSolve Sun StorEdge and Solaris are trademarks registered trademarks or service marks of Sun Microsystems Inc in the U S and other countries All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International Inc in the U S and other countries Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems Inc
12. TAS Issues on page 8 Service Issues on page 10 System Level Issues on page 12 Command Line Error Messages on page 17 Required Patches Install all the required patches listed below before installing the Sun StorEdge T3 array These patches are available on the SunSolve web site http sunsolve sun com To retrieve patches In the SunSolve Online column click on Patches In the Patches column click on PatchPro Click on Storage Products Wait the system might be slow Under Disk Arrays check the box next to StorEdge T3 Scroll to the bottom of the page and click Generate Patch List Refer to the patch README file for download instructions and patch information If you do not find a patch listed in TABLE 1 or a particular patch a Backup to the SUNSOLVE ONLINE Patches page that was obtained from step 1 b Enter a patch ID in the Patch Finder box and click Find Patch Note You may need other patches not listed below for related software products such as Sun StorEdge Component Manager or VERITAS Volume Manager Refer to the SunSolve web site and to the release notes of these products for their required patches TABLE1 Required Patches Solaris 2 6 Solaris 7 Solaris 8 System Type Operating Environment Operating Environment Operating Environment All 105356 18 or later 107458 13 or later 109524 09 or later ssd driver ssd driver ssd driver 106226 02 or
13. The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems Inc for its users and licensees Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry Sun holds a non exclusive license from Xerox to the Xerox Graphical User Interface which license also covers Sun s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun s written license agreements Federal Acquisitions Commercial Software Government Users Subject to Standard License Terms and Conditions DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS REPRESENTATIONS AND WARRANTIES INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON INFRINGEMENT ARE DISCLAIMED EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID Copyright 2001 Sun Microsystems Inc 901 San Antonio Road Palo Alto CA 94303 4900 Etats Unis Tous droits r serv s Ce produit ou document est distribu avec des licences qui en restreignent l utilisation la copie la distribution et la d compilation Aucune partie de ce produit ou document ne peut tre reproduite sous aucune forme par quelque moyen que ce soit sans l autorisation pr alable et crite de Sun et de ses bailleurs de licence s il y en a Le logiciel d tenu par des tiers et qui comprend la technologie relative aux polices de car
14. Warm bootability is supported by Solaris 7 Release 11 99 and later Bootability for the Solaris 2 6 operating environment is not currently supported Note Warm bootability is not supported with the ifp Qlogic 2100 HBA Cold bootability that is booting the Sun StorEdge T3 array and the host at the same time is not supported at this time 12 Sun StorEdge T3 Array Release Notes December 2001 Note In the next firmware upgrade the Sun StorEdge SBus Dual Fibre Channel Host Bus Adapter p n X6730A will not be supported as a bootable host bus adapter Note See issue 4253419 that follows The delayed time required for a Sun StorEdge T3 array to become fully available to host I O operations may cause issues especially if the array is used as a boot device If you have encountered this situation contact an authorized Sun Service provider or Sun Service at 1 800 USA 4SUN for an evaluation 4253419 Sun StorEdge T3 array controller extended boot times In some cases host systems running the Solaris operating environment can boot faster than Sun StorEdge T3 arrays This results in a host configuration that might not be able to detect all available Sun StorEdge T3 array storage during a full AC power loss boot cycle This can occur when the host system has minimal amounts of memory or memory power on self test operations have been disabled When powering up a configuration always power on the Sun StorEdge T3 arrays
15. act res est prot g par un copyright et licenci par des fournisseurs de Sun Des parties de ce produit pourront tre d riv es des syst mes Berkeley BSD licenci s par l Universit de Californie UNIX est une marque d pos e aux Etats Unis et dans d autres pays et licenci e exclusivement par X Open Company Ltd Sun Sun Microsystems le logo Sun AnswerBook2 docs sun com SunSolve Sun StorEdge et Solaris sont des marques de fabrique ou des marques d pos es ou marques de service de Sun Microsystems Inc aux Etats Unis et dans d autres pays Toutes les marques SPARC sont utilis es sous licence et sont des marques de fabrique ou des marques d pos es de SPARC International Inc aux Etats Unis et dans d autres pays Les produits portant les marques SPARC sont bas s sur une architecture d velopp e par Sun Microsystems Inc L interface d utilisation graphique OPEN LOOK et Sun a t d velopp e par Sun Microsystems Inc pour ses utilisateurs et licenci s Sun reconna t les efforts de pionniers de Xerox pour la recherche et le d veloppement du concept des interfaces d utilisation visuelle ou graphique pour l industrie de l informatique Sun d tient une licence non exclusive de Xerox sur l interface d utilisation graphique Xerox cette licence couvrant galement les licenci s de Sun qui mettent en place l interface d utilisation graphique OPEN LOOK et qui en outre se conforment aux licences crites de Sun LA DOCU
16. ame already exists Volume does not have slice s to be removed RAID error in Volume slicing Some of these errors are generated more often than others such as VN_MOUNTED Numerical Error Name Value VN CFGNOTSUPPORTED 0x20001D VN BADSTANDBYUNIT 0x20001E VN_DEVINVALID 0x20001F VN_LOCVOLBAD 0x200020 VN_PORTMAPR 0x200021 VN UNINITIALIZED 0x200022 VN PENDING 0x200023 VN BADMODE 0x200024 VN MIRRORON 0x200025 VN CANTMOUNT 0x200026 VN STARTPARA 0x200027 VN VSLBADNAME 0x200028 VN MAXSLICEERR 0x200029 VN VSLNOTFOUND 0x20002A VN SIZEPARA 0x20002B VN VSLBADNAMELEN 0x20002C VN VSLEXISTS 0x20002D VN NOSLICEINVOL 0x20002E VN VSLRAIDERR 0x20002F N UNMOUNTED VN MNTINUSE VN_C FGNOTSUPPORTED VN DEVINVALID V VN_LOCVOLBAD VN_UNITIALIZED VN_BADMODE and VN_MIRRORON In particular VN_RAIDERR code 0x200015 can result from a variety of scenarios and these warrant attention The Sun StorEdge T3 array uses a specific protocol for carrying out commands and this protocol uses be sent to the user As such the RAID the RAID error as a general error message to ERR may result from any of a number of software or hardware conditions Some cases involve problems related to the user configuration which can be remedied easily Other cases are more subtle and are Sun StorEdge T3 Array Release Notes 19 20 related to the function of the Sun StorEdge T3 array s internal software D
17. etailed information for specific instances of the RAID error can be found in the syslog an overview of the scenarios are provided here The following is a list of the categories that the Sun StorEdge T3 array s embedded protocol uses for RAID errors and a few of the cases within each category Each category code which can be useful in reference to the syslog is included Though not exhaustive this list provides a general breakdown of common RAID error generators 1 Command Incomplete 0x1A The command was not executed correctly internally The software responded to the command with too much or too little information In certain cases the command may simply be paused and will resume 2 Partial conditional Success 0x19 This category includes the following cases a Aborting a non existent command A user has issued a command then tried to abort it after the command is executed b Retry error The command was retried one or more times c Target error A volume is offline or disabled 3 Invalid Response part of the category above 0x19 The software did not provide a valid response to the user command These cases are more specific than the Command Incomplete category a Invalid information type parameter The software responded with the wrong type of information b Error in information returned The information returned in response to the command is erroneous This case implies an embedded software error c Funct
18. etters a numerical code in hexadecimal digits and a text message The following tables list the errors that Sun StorEdge T3 array displays TABLE 2 lists the types of errors and the numerical range associated with each TABLE 2 Error Message Types Numerical Range Description Type of Error Logical volume manager 0x10001 0x1000A Disk drive related errors LVM driver error codes Virtual Node VN error 0x200000 0x200025 Errors related to vol and other command line codes operations Port error codes 0x300000 0x300006 Errors related to the port command Sys error codes 0x400000 Only one error indicating a bad value FRU error codes 0x500001 0x500076 Errors related to field replaceable units FRUs pSOS operating system 00000001 CO00FFFF pSOS errors embedded operating system errors Sun StorEdge T3 Array Release Notes 17 18 RAID Errors and Other Common Errors VN_ERRORs are the most common error messages displayed The following table lists names and values of these errors TABLE 3 Volume Related VN Errors Numerical Error Name Value Message VN_BADUNIT 0x200000 Bad unit number VN_BADDRIVE 0x200001 Bad drive number VN_BADPART 0x200002 Bad partition id VN_VOLEXISTS 0x200003 Volume already in use VN_VOLNOTFOUND 0x200004 Volume name not found VN_PARTHASFS 0x200005 Partition already has file system VN_FACLOCKED 0x200006 Facility locked by other command VN_BADATTR
19. ger to activate the interface than the Sun StorEdge T3 array and the Sun StorEdge T3 array will time out waiting for the RARP server response To avoid this problem change the spanning tree setting of the Cisco Catalyst port to portfast which allows the switch to first enable the port and then check for integrity using the spanning tree algorithm By default the switch checks the integrity of the spanning tree first and then enables the port To change the port settings refer to the switch documentation for instructions 4395542 SUNWIux package installation required for hosts running Solaris 2 6 environment The SOC patch 105375 for the Solaris 2 6 software environment will install and not fail even when SUNWIux packages are not installed on the host This results in a configuration where the host can see only one LUN on a Sun StorEdge T3 array If this occurs and there is no indication of other problems check that SUNWIux packages are installed correctly on the host Sun StorEdge T3 Array Release Notes 15 4362567 Use default port addressing on the Sun StorEdge T3 array The default setting for Sun StorEdge T3 array port addressing is hard Although it is possible to change this setting use the default setting to avoid unexpected system behavior 4426672 Power management on host is not supported If a Sun StorEdge T3 array is connected to a host bus adapter HBA with power management enabled it can cause failover iss
20. ion failed The command failed to retrieve the appropriate information d Zero size The command accessed a volume with zero size 4 Command Aborted 0x18 The command is aborted often because of a time out A command aborts when a component in the system freezes or if a connection is defective 5 Command Exception 0x17 This category includes cases where the command cannot be executed This error type is generated when a disabled unavailable or invalid drive or volume is specified For example after using a hot spare standby to reconstruct the data on a drive you cannot refer to it again as a hot spare a Invalid name address Either the user or the internal software used a volume or disk drive name that is invalid or does not match the current configuration Sun StorEdge T3 Array Release Notes December 2001 Invalid command fields The command is no longer supported or the internal software used a command opcode that is unsupported Missing fields The user or the internal software issued a command with missing information Drive module errors The disk drive referenced may be unattached disabled substituted or in the process of being reconstructed 6 Machine Exception 0x16 This category includes cases where there is a hardware error or where other commands are being executed thereby giving a busy response a b Drive fatal error There is an error internal to a referenced drive Autorecons
21. is situation disable the DMP software on the host in the cluster 4406863 Sun Cluster 2 2 cannot use recon rate high Sun StorEdge T3 array setting If the Sun StorEdge T3 array is configured in a Sun Cluster 2 2 environment use either the low or med setting for the recon rate You can change this setting using the Sun StorEdge T3 array sys recon rate command The recon rate high setting on an Sun StorEdge T3 array running in a Sun Cluster 2 2 configuration breaks the clustering software Sun StorEdge T3 Array Release Notes 7 VERITAS Issues 4527907 VERITAS Volume Manager 3 2 Encapsulation of Alternate Master Volume can Fail If you use an alternate master controller unit disk as the boot disk VERITAS Volume Manager 3 2 will not select the path to that disk but will attempt to encapsulate the primary path boot disk Upon rebooting the system hangs up and the following message is displayed etc rcS d S86vxvm reconfig etc vx reconfig d disks cap cannot create If building an OS on a multipathed Sun StorEdge T3 and you plan to encapsulate the system boot disk build the OS on the first device in the device tree For example if the two paths to a T3 LUN are c1 and c3 build the OS on c1 even if it is the alternate path to the T3 LUN 4264118 DMP failback is not automatically enabled VERITAS Volume Manager 3 0 4 only After installing the VERITAS software to ensure correct operation of VERITAS Dynamic Mu
22. later 107473 07 or later format patch luxadm patch 105181 29 or later 107834 03 or later kernel update patch DKIO Extensions Patch 2 Sun StorEdge T3 Array Release Notes December 2001 System Type Sun StorEdge T3 array VERITAS VM 3 1 VERITAS VM 3 1 1 VERITAS VM 3 2 Volume Manager Storage Administrator PCI ifp Only SBus sf socal Only Sun StorEdge Network Foundation software TABLE 1 Solaris 2 6 Operating Environment 109115 10 firmware patch 110253 04 110451 05 111907 04 111904 04 107280 08 or later ifp PCI driver PCI Systems only 109399 03 or later PCI Host Adapter Firmware Fcode 105375 26 or later sf socal driver SBus systems only 109400 03 or later SBus Host Adapter Firmware Fcode Required Patches Continued Solaris 7 Operating Environment 106541 18 or later Kernel Update Patch 109115 10 firmware patch 110254 04 110452 05 111908 04 111904 04 107292 07 or later ifp PCI driver PCI Systems only 109399 03 or later PCI Host Adapter Firmware Fcode 107469 08 or later sf socal driver SBus systems only 109400 03 or later SBus Host Adapter Firmware Fcode Solaris 8 Operating Environment 109115 10 firmware patch 110255 04 111118 05 111909 04 111904 04 109189 02 or later ifp PCI driver PCI Systems only 109399 03 or later PCI Host Adapter Firmware Fcode 109460 05 or later sf socal driver SBus systems only 109400 03 o
23. ltipathing DMP auto failback operations type the following command as root on host systems connected to Sun StorEdge T3 arrays f vxdmpadm start restore interval 60 policy check all Note You must run this command after every system reboot 8 Sun StorEdge T3 Array Release Notes December 2001 4282806 vxinstall only displays the first Sun StorEdge T3 array controller for the configuration During the vxinstall procedure only the first connected host bus adapter in a Sun StorEdge T3 array partner group is displayed This occurs because vxinstall displays only the first path to an Sun StorEdge T3 array partner group even though other paths to the partner group have also been detected This can be misleading since in Sun StorEdge T3 array configurations volumes can also exist through second controller data paths You do not need to take any special action to correct this Allow vxinstall to proceed to completion Once the host system has rebooted from the VERITAS installation all paths to the Sun StorEdge T3 array are properly recognized by the Volume Manager software 4313336 Enable DMP support for a Sun StorEdge T3 array and StorEdge A3500 configuration DMP support is necessary to obtain full redundancy between interconnected Sun StorEdge T3 array controller units If you are connecting redundant Sun StorEdge T3 arrays to a host running DMP that also has StorEdge A3500 storage devices connected to it you must
24. n 30 minutes or the Sun StorEdge T3 array and all attached Sun StorEdge T3 arrays in that partner group will shut down and power off 10 Sun StorEdge T3 Array Release Notes December 2001 Interconnect Card syslog Notices The following feature is no longer valid for the 1 18 firmware In version 1 17b firmware the Sun StorEdge T3 array logs a notice message about the interconnect card in the syslog file once every six hours The following is an example of this notice SCHD 1 N ulctr ulll temperature 26 0 Celsius Because this notice is displayed for each interconnect card in a partner group up to four notices are displayed for a partner group every six hours This is just a status message and does not affect functionality Note In version 1 18 firmware the Sun StorEdge T3 array no longer logs this notice message about the interconnect card in the syslog file 4521218 T3 Workgroup Password and Set Command Configuration Lost when the Controller is Swapped An existing IP address and the root password set on a Sun StorEdge T3 configuration will be lost when m A Sun StorEdge T3 controller is upgraded to a T3 controller in a workgroup configuration m If performing maintenance on a T3 workgroup it is powered down and the T3 controller is replaced with a new T3 controller This is not a problem with a live controller swap in an enterprise configuration Have the jumpstart server available before performing
25. r later SBus Host Adapter Firmware Fcode 108984 08 108982 09 108983 08 Sun StorEdge T3 Array Release Notes 3 Required Firmware The latest controller firmware level is available on the SunSolve web site You can check the controller firmware level on the Sun StorEdge T3 array using the ver command as described in the Sun StorEdge T3 Array Administrator s Guide If the Sun StorEdge T3 array is configured with prerelease controller firmware in addition to upgrading controller firmware you must upgrade the htm files located in the Sun StorEdge T3 array web directory along with other Sun StorEdge T3 array firmware as described in the Sun StorEdge T3 Array Installation Operation and Service Manual Note Refer to the README file associated with the firmware upgrade patch for details on verifying the currently installed firmware level The latest htm files and all other Sun StorEdge T3 array firmware can be copied from the SunSolve web site http sunsolve sun com Or contact your Sun representative to obtain the latest firmware releases General Issue Caution Sun StorEdge T3 and T3 arrays should never be connected to a public network only to a secure network 4 Sun StorEdge T3 Array Release Notes December 2001 Firmware Updates and Modifications The following sections describe changes that have been included in the version 1 18 firmware release Sun Cluster S
26. r the error while reconfiguring the Sun StorEdge T3 array with volumes that have been added but not mounted or the problem may be related to the hardware or an embedded component Sun StorEdge T3 Array Release Notes 21 In general RAID errors can be diagnosed by checking the status of the volumes mounted on the Sun StorEdge T3 array Often an existing but unmounted volume can trigger the error Other times a conflict occurs when a new version of the binary is downloaded while previous volumes are still being used Here are some guidelines for investigating RAID errors 1 Check the state of the current volumes with the vol stat command m If the volumes are unmounted try re mounting them and then resetting the system using the Sun StorEdge T3 reset command a If you are unable to re mount the volumes try removing all the volumes resetting the system then adding them back before re mounting them 2 Check the host connection to the Sun StorEdge T3 array On hosts running the Solaris software environment the format command should match the number of volumes present on the Sun StorEdge T3 array If the number of volumes listed do not match refer to chapter 5 of the Sun StorEdge T3 Array Administrator s Guide for troubleshooting instructions Specifically the T300 entries listed by the format command should be recognized and labeled and the number of these entries should equal the number of volumes mounted on the Sun StorEdge T3 a
27. rray 3 If you suspect that a hardware problem may be causing the RAID error use the fru list and fru stat commands to check the status of the components It may also be worthwhile to check the cables and connections between partner group units and between the host and the Sun StorEdge T3 arrays More detail regarding the error may be available in the syslog in which case note the date and time of the error for lookup However most common cases can be handled as described above Port Errors The following table lists the port error messages that can be displayed TABLE 4 Port Errors Error Name Numerical Value Message PRT UNKNOWPORT 0x300000 Bad port number PRT ALREADYMAPPED 0x300001 Port is already mapped unmap first PRT INVALIDNAME 0x300002 Volume name is not correct PRT VOLNOTFOUND 0x300003 Volume name not found 22 Sun StorEdge T3 Array Release Notes December 2001 TABLE 4 Port Errors Continued Error Name Numerical Value Message PRT_INVALID 0x300004 Port number is incorrect PRT_LUNNOTMAPPED 0x300005 This lun is not mapped PRT ACCESSINVALID 0x300006 Need to specify the access mode Interconnect Card and Other FRU Errors The following table lists the various FRU related errors that you can encounter These include various power and cooling unit fault conditions missing disks and interconnect card errors TABLE 5 Unit Related Errors Interconnect Card and Other
28. truct or disable attempted A drive that is being reconstructed or disabled is specified Queue full or busy response The command cannot be executed because the system is busy processing other commands Unknown host The specified host address is invalid or unreachable Single Drive errors A drive referenced by the command was not detected the connection could not be opened or the sysarea on the drive could not be created This case implies that the drive or the connection to it is faulty Alternatively a retry of a command accessing a disk could fail to execute Multiple disk failure An error occurred involving more than one drive Standby already in use This error resembles the one in the Command Exception category In this case the drive is busy processing a previous command This case applies when the command is complete and if the drive configuration has changed as a result Volume LUN errors A volume may be inaccessible or its configuration may be corrupted and represented as nonvalid 7 Intervention Required 0x14 Here an error results when a volume is mounted or unmounted in contrast to what is expected Alternatively a physical connection may be broken and should be reinstated by replacing the appropriate FRUs RAIDERRs can result from invalid command arguments or from a system problem The error may refer to the configuration of a volume or an individual drive For example you can encounte
29. ues To avoid this disable power management on HBAs 4292162 Permanent serial cable connections to the Sun StorEdge T3 array are not recommended array to meet regulatory emissions requirements Do not leave it connected after 1 Caution The serial port cable must be disconnected from the Sun StorEdge T3 performing a procedure Note The serial cable is used for special service procedures only and should not be used by anyone except authorized qualified service personnel The serial cable must be removed when the service procedure has been completed Because the Sun StorEdge T3 array serial port provides diagnostic and EPROM access to the system during the boot cycle there is a risk of a security breach if the serial cable is left connected to the Sun StorEdge T3 array To avoid this risk remove the serial cable connection from the Sun StorEdge T3 array to external host systems after use 16 Sun StorEdge T3 Array Release Notes December 2001 Command Line Error Messages Types of Error Messages The Sun StorEdge T3 array issues a variety of error messages to the command line indicating an incorrectly entered command or invalid operation When you enter a command by itself or the error is purely syntactic for example missing an argument or using the wrong format the Sun StorEdge T3 array displays the command synopsis Otherwise the Sun StorEdge T3 array displays an error message consisting of a name in capital l
30. upport The 1 18 firmware release supports a Sun Cluster 2 2 and Sun Cluster 3 0 single Sun StorEdge T3 array workgroup configurations m Sun Cluster 3 0 Update 1 single Sun StorEdge T3 array and partner group enterprise configurations See the next section Explicit LUN Failover on page 5 for other related information For more details on supported Sun StorEdge T3 array Sun Cluster configurations refer to the Sun Cluster documentation Explicit LUN Failover Explicit LUN failover ELF is a feature that allows future host applications to eliminate unintentional Sun StorEdge T3 array LUN failovers To enable this feature two new option settings have been added to the sys mp support command mpxio and std a The mpxio setting is used for Sun StorEdge T3 array partner groups in Sun Cluster 3 0 configurations m The std setting is included in 1 18 firmware to take advantage of future product functionality The following screen capture shows all possible sys mp support commands sys mp_support lt none rw mpxio std gt For more information on using the mpxio utility on Sun StorEdge T3 array partner groups in clustered configurations refer to the Sun Cluster 3 0 documentation Sun StorEdge T3 Array Release Notes 5 Determining Controller Firmware Versions When using the fru command with the 1ist option the output now identifies both level 2 and level 3 controller firmware In the example below under Revision
31. y parameter set to 60 seconds causes a Sun StorEdge T3 array partner group boot failure The default boot delay parameter for the Sun StorEdge T3 array is set to a value of 3 To avoid problems with booting the Sun StorEdge T3 array system do not reset the bootdelay parameter to a higher value than the default setting 14 Sun StorEdge T3 Array Release Notes December 2001 4435299 Third party security penetration test software causes a controller reset If you use third party security penetration test software be aware that this can cause a Sun StorEdge T3 array controller reset causing the system to crash Caution Due to the fact that most security checking software can attempt to test target devices by massive attempts to break into a given device running these types of applications against a Sun StorEdge T3 array is risky and is not recommended To ensure adequate network security with a data center of Sun StorEdge T3 arrays it recommended that the Sun StorEdge T3 arrays only be connected to a private tightly controlled network 4309324 Extend RARP time out to better support Ethernet switches In a first time installation the Sun StorEdge T3 array is assigned its IP address from a RARP server that has been configured with the address When first powered on the Sun StorEdge T3 array waits for the RARP server response If the Sun StorEdge T3 array and RARP server are connected to a Cisco Catalyst switch the switch takes lon
Download Pdf Manuals
Related Search