Patch-ID# 107369-17 Keywords: SUNWcms audlinks devlinks add_drv disks tapes Synopsis: Netra ft1800 6.7: Misc. fix Patch Date: Jun/10/99 Solaris Release: 2.6 SunOS release: 5.6 Unbundled Product: Netra ft1800 Unbundled Release: 6.7 Topic: Netra ft1800 patch BugId's fixed with this patch: 4139353 4147690 4173741 4184310 4184612 4193152 BugId's fixed with this patch: 4198893 4199551 4203028 4203456 4203719 4204340 BugId's fixed with this patch: 4204421 4204646 4204669 4204933 4205053 4205091 BugId's fixed with this patch: 4205478 4205589 4206246 4206374 4207109 4207145 BugId's fixed with this patch: 4207491 4207504 4207511 4207587 4207862 4207870 BugId's fixed with this patch: 4207873 4207907 4207908 4208359 4208662 4208663 BugId's fixed with this patch: 4208749 4208751 4209090 4209131 4209135 4209163 BugId's fixed with this patch: 4209168 4209213 4209532 4209563 4209586 4209945 BugId's fixed with this patch: 4209959 4210001 4210021 4210425 4210440 4210740 BugId's fixed with this patch: 4210763 4211193 4211239 4211254 4211269 4211582 BugId's fixed with this patch: 4211583 4211680 4211681 4211759 4211772 4212183 BugId's fixed with this patch: 4213533 4213970 4215363 4215827 4216754 4216807 BugId's fixed with this patch: 4217181 4217188 4217229 4217678 4218110 4218454 BugId's fixed with this patch: 4218463 4218897 4220270 4220625 4220628 4221070 BugId's fixed with this patch: 4221944 4221992 4223003 4223975 4224330 4224335 BugId's fixed with this patch: 4224768 4225131 4225143 4225167 4225169 4225187 BugId's fixed with this patch: 4225948 4228193 4229033 4230278 4230735 4231072 BugId's fixed with this patch: 4234449 4235450 4243550 Changes incorporated in this version: Relevant Architectures: sparc NOTE: sparc.sun4u Patches accumulated and obsoleted by this patch: 106616-01 Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: SUNWftm/man/man1m/cmsrepairfru.1m SUNWftm/man/man1m/u4ftlogfmt.1m SUNWftm/man/man7d/u4ftalarm.7d etc/init.d/cms_sync etc/init.d/dumpvp_setup etc/init.d/init.pnet etc/init.d/u4ftsplit etc/init.d/u4ftsplitl1 platform/SUNW,Ultra-4FT/kernel/drv/dump platform/SUNW,Ultra-4FT/kernel/drv/dump.conf platform/SUNW,Ultra-4FT/kernel/drv/fzcpuset platform/SUNW,Ultra-4FT/kernel/drv/hme platform/SUNW,Ultra-4FT/kernel/drv/pci platform/SUNW,Ultra-4FT/kernel/drv/pnet platform/SUNW,Ultra-4FT/kernel/drv/qfe platform/SUNW,Ultra-4FT/kernel/drv/sd platform/SUNW,Ultra-4FT/kernel/drv/se platform/SUNW,Ultra-4FT/kernel/drv/u4ftbus platform/SUNW,Ultra-4FT/kernel/drv/u4ftdog platform/SUNW,Ultra-4FT/kernel/drv/u4fteintr platform/SUNW,Ultra-4FT/kernel/drv/u4ftfctlr platform/SUNW,Ultra-4FT/kernel/drv/u4fti2c platform/SUNW,Ultra-4FT/kernel/drv/u4ftiodr platform/SUNW,Ultra-4FT/kernel/drv/u4ftlog platform/SUNW,Ultra-4FT/kernel/drv/u4ftvm platform/SUNW,Ultra-4FT/kernel/drv/u4ioslot platform/SUNW,Ultra-4FT/kernel/misc/platmod platform/SUNW,Ultra-4FT/kernel/unix sbin/cip usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/A-MBD/A-MBD.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/A-MBD/A-MBD.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/B-MBD/B-MBD.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/B-MBD/B-MBD.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/CAF/CAF.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/CAF/CAF.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/CPU/CPU.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/CPU/CPU.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/DSK/DSK.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/DSK/DSK.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/HDD/HDD.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/HDD/HDD.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/PCI/PCI.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/PCI/PCI.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/PSU/PSU.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/PSU/PSU.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/cdrom/cdrom.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/cdrom/cdrom.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/cmsd.conf usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/cpuset/cpuset.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/cpuset/cpuset.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/disk/disk.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/disk/disk.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/disk/disk.start usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/ft_core/ft_core.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/ft_core/ft_core.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/ft_network/ft_network.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/ft_network/ft_network.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/glm/glm.online usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/registry/registry.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/registry/registry.so usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftdog/u4ftdog.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftdog/u4ftdog.so usr/platform/SUNW,Ultra-4FT/SUNWcms/include/split_api.h usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cip usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsconfig usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsd usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsenvd usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmspohd usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmspwrctl usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsrepairfru usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/icn.init usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/icn.keepalive usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/icn.terminate usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/libcms.so usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/libfru.so usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/libu4ftsplit.so.1 usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/libu4ftsplitmt.so.1 usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/scsilt usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/split_pre.1 usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/split_pre.2 usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/split_pre.3 usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/split_tempru usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ftmbox.init usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ftmbox.terminate usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ftsplitd usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/vxbootcheck usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/cms_start usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/splitadm usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/splitconf usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/splitinfo usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/splitnet usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/u4ft_change_hostid usr/platform/SUNW,Ultra-4FT/lib/fwupdate.fpga.258-7134-07 usr/platform/SUNW,Ultra-4FT/lib/netra_ft_1800.flash.update-07 usr/platform/sun4u/include/sys/u4ftalarm_io.h usr/sbin/add_drv usr/sbin/audlinks usr/sbin/devlinks usr/sbin/disks usr/sbin/ports usr/sbin/tapes Problem Description: 4139353 add_drv returns error if no instances of a driver can be attached 4147690 devlinks should not be deleted (cf entries in path_to_inst) 4173741 pn_do_back_enb panic: bad mutex 4184310 systems hangs during os startup, but only after a reboot 4184612 dropping into OBP whilst insync can cause latent OOS 4193152 need ddi framework change to stop panics caused by Veritas dev-tree walking 4198893 Typo - 'Returned from final of cpuset' in pri 4199551 bridge nex and slot nex should combine to set client pci latency values 4203028 fru library should retry when soft failures occur 4203456 CMS does not enforce FRU repair policy 4203719 master_sync is never ready if a DSK or MBD is not enabled 4204340 sh_nvram.h (cpuset_nvram_config_t in sh_nvram.h does not have osdog field 4204421 reboot can cause external disks to appear failed with veritas 4204646 se driver times out a command prematurely 4204669 cmsd socket provides indiscriminate access 4204933 cmspohd, cmspwrctl and scsilt sockets provide indiscriminate access 4205053 All non-infant mortality pri failures cause cpu to be failed 4205091 RED State Exception following an RCP reset. 4205478 log flood: Warning: nonempty ioerr reg 4205589 Repair of PWB test pattern after E_State could patch up wrong bit 4206246 integration receive keypress timeout leaves an item on the stack 4206374 install-cqueues attempts to install wrong device 4207109 writing of configfile deferred until lengthy scripts in ft_core complete 4207145 Infant mortality OOS not handled correctly by CMS 4207491 info field set to "fan0 speed is too low" when CPU powered off 4207504 Panic "streaming buffer flush timeout!" 4207511 cmsenvd core dumped. 4207587 Unable to boot Ultra-1 and it breaks server/client model. 4207862 cmsconfig should not allow string attributes to be set to a blank value 4207870 read error from fat controller 4207873 .lock directories not deleted following a reboot. 4207907 pci based ft_networks boot up with WARNING: unable to set address 4207908 psycho appears to be broken if we power off a side while in-sync 4208359 osdog enabled by cmsdef when configured off 4208662 spurious bridge interrupt, takes bridge degraded 4208663 kastat_q_exit panic when adding 4th disk to rootdg 4208749 Both CPU FRUs enabled after split 4208751 Error 62 on merge 4209090 mbd disable_failed -> disabled transition doesn;t offline bridges 4209131 Workaround for 4209129 - allow single PSU configuration 4209135 a motherboard is not hot swapable if rebooted since a bridge failure 4209163 u4ftctl disable needs to detach nodes that are in "offline/attached" state 4209168 need user utility to repair "failed" frus 4209213 u4ftsplitd: SPLIT_INIT_NET not expected when not in SPLIT mode seen in debug log 4209532 PSUs marked as faulty when one side is powered down 4209563 RFE: Should reduce the timing window in which PRIing CPUset drops primacy 4209586 frucfg unable to set date field in fru eeprom 4209945 Soft pri failures should be repeated indefinitely 4209959 vp->v_type == VCHR panic 4210001 Cannot initialise eeprom whose version number is incorrect 4210021 reversed pathnames for PCI slots 4210425 Workaround for 4209548 - CPUset fault light not lit although previous fault 4210440 u4ftalarm_io.h needs to be installed or in a developer package 4210740 cpuset pri and/or heavy io load causes disk checksum validation failure 4210763 bridge fails on split if force option is used 4211193 split mode operation can lead to split identity 4211239 qfe based ft_network does not successfully latent fault check 4211254 Write into unowned slot failed bridge 4211269 logging fails on sheffield 4211582 cmsrepairfru always gives spurious error messages 4211583 configfile invalid after patch/upgrade 4211680 Bug fix 4193716 introduced a bug in which vm_fixup could produce 2 'winners' 4211681 Will force primacy if real Solaris winner unable to contact other Motherboard 4211759 patch T107369-01 does not include u4ft_change_hostid 4211772 init.pnet fix (for client install) not in patch 4212183 u4ftsplitd may set srr bits incorrectly on split 4213533 POST stops if motherboard lock cable is not present. 4213970 cmsrepairfru has incorrect path to lib directory and so does not work 4215363 prom utility should report it can not upgrade whilst system is running in-sync 4215827 ftp across PCI based 100Mb/s network is slow/intermittent 4216754 fwupdate.fpga utility instructions does not accurately follow actual behaviour 4216807 sheffield OBP needs a more recent built-in download set. 4217181 gethrtime() program demonstrates non-monotonic timing 4217188 first attempt to enable modules after merge fails 4217229 pnet will not configure if controller fails to initialize 4217678 The ft_networks don't show a reason for switching controllers 4218110 Support for new memory timings required in prom. 4218454 The cheerio initialization code is too general 4218463 ft_network cmsdef calls ifconfig from multiple threads simultaneously 4218897 pnet/qfe panic whilst booting 4220270 PROM unix update utilities not executable on patch T107369-06 4220625 cpusets with 256M memory configuration caused fatal reset immediately after sync 4220628 The FPGA upgrade notes supplied with patch T107369-07 are incorrect 4221070 s/w TLB replacemnt scheme needed to workaround UltraSPARC-II non-determinism 4221944 u4ftalarm.7 required to be installed for Alrams ioctl API info 4221992 man page required for u4ftlogfmt to be installed on ft 1800. 4223003 /kernel/drv/qfe prevents sheffield qfe driver being loaded without a reboot 4223975 Powering on defective motherboard disrupted pil_14 intr_req queue causing PANIC 4224330 pri stop dead time enhancements 4224335 wait for pri code needs to run from memory/caches 4224768 should prevent cms_sync rc script from being interrupted by ^C 4225131 Need RAS-8 (PSARC/1999/135) interfaces for patch C 4225143 reset log can cause RED state exception. 4225167 panic: vp->v_type == VCHR, when dump device changed from stale disk 4225169 savecore can't always find coredump files - dumpvp correctly set up too late. 4225187 All of active IO-dirty RAM should be considered in pre-PRI synchronisation. 4225948 problem in do_copy_pages_ioctl causes instance offline to hang 4228193 vxbootcheck contains extra single quotes - can lose system dumps with veritas 4229033 _redundancy wrongly set in ft_network - causes misassessment of state 4230278 problem with cms not resetting pci bridge correctly 4230735 merging a split system causes the new sides motherboard to go failed 4231072 The lock file for splitd is in /tmp (wrong location) 4234449 Unable to integrate under load with 2p system 4235450 backoutpatch script for patch 107369-12 does not work correctly 4243550 patch-16 README file has been stripped of unix commands beginning with # Patch Installation Instructions: -------------------------------- Refer to the Install.info file within the patch for instructions on using the generic 'installpatch' and 'backoutpatch' scripts provided with each patch. Any other special or non-generic installation instructions should be described below. Special Install Instructions: ----------------------------- Workaround for 4236677 - Potential for eeprom CRC corruption 4236677 causes EEPROM checksum errors on the disk chassis which cause the disk chassis CMS object (i.e. DSK 0 or DSK 1) to go enable_failed if the problem occurs. Subsequent management of the disk objects (i.e. HDD 0-5 or HDD 6-11) cannot be performed using the CMS. The use of cmsrepairfru to repair a disk (e.g. A-DSK0) in the affected disk chassis will fix the CRC error on the disk chassis. Non-generic install instructions -------------------------------- Introduction ------------ Please note that installation and backing out of this patch causes the CMS configuration to be restored to its default (i.e. equivalent to the configuration adopted immediately following initial installation). Installation of this patch changes the behaviour of the CMS as regards FRUs which have a pre-existing fault. In some circumstances, these faults were 'spurious', i.e. they were an artifact of some other problem. A utility - cmsrepairfru - is included in the patch to mark FRUs 'repaired' where the previous fault indication is known to be 'spurious'. Prior to installation of this patch, previously-faulty FRUs can be successfully enabled and used, but once the system has been rebooted following the patch installation, these FRUs will go to the enable_failed state. This can result in little of the system being available. It is therfore necessary to identify spuriously-faulty FRUs and run the utility 'cmsrepairfru' on each FRU marked as faulty before the system is rebooted. The CMS will be disabled during patch installation until the reboot, so the spuriously-faulty FRUs must be identified *before* the patch is installed. Part of this procedure is designed to upgrade CPUsets on systems that are already installed with firmware up to the necessary level to run release 6.7 - that is CPUsets with version 17 or later PROMs. If a CPUset does not have version 17 or later PROMs then it may be necessary to bring it up to this level first: consult a field service engineer to arrange this. NB: the upgrade utilities cannot be run if the system was booted from a read-only device, such as a CD-ROM or a network: the system must be running from a writeable device such as a disk before this procedure can be performed. In particular, if the system has just been fully installed from CD-ROM, then it should be rebooted from disk before performing this procedure. The remainder of this section describes the following: . Special procedure for performing the patch install including: - use of the cmsrepairfru utility. - instructions for the OBP/Prom & FPGA upgrade utilities. . CPUset integration instructions . Instructions to enable a failed CAF following a merge (workround for bug # 4230739) Patch Installation Procedure ---------------------------- This procedure assumes you have access to the RCP port and/or the ft1800's Console Alarms and Fans (CAF) module/FRU. This procedure assumes that the CPUsets are already in sync. To determine if the CPUsets are in sync, use the procedure described in Note 5, Determining If In Sync. 1. Use cmsconfig to disable the CPUset in A-CPU (i.e. CPU 0). 2. Identify the spuriously faulty FRUs, then fix them using the procedure described below in note 1, Using cmsrepairfru. 3. Install the patch using the procedure described below in note 2, Installing The Patch. 4a. Upgrade the FPGAs on motherboard A using the procedure described below in note 3, Upgrading FPGAs. NOTE: This is a MANDATORY patch, therefore when asked for confirmation, enter 'yes'. failure to upgrade will leave the system with an unsupported configuration. 4b. Upgrade the FPGAs on motherboard B using the procedure described below in note 3, Upgrading FPGAs. NOTE: This is a MANDATORY patch, therfore when asked for confirmation, enter 'yes'. Failure to upgrade will leave the system with an unsupported configuration. 5. Upgrade the PROM of the CPUset in B-CPU using the procedure described below in note 4, Upgrading PROM. NOTE: This is a MANDATORY patch, therfore when asked for confirmation, enter 'yes'. Failure to upgrade will leave the system with an unsupported configuration. 6. Shutdown system to run level 0 (i.e. shutdown -g0 -i0 -y). 7. When the system has reached run level 0 disable auto boot (i.e. {0} ok setenv auto-boot? false). 8. Reset Motherboard/side B using one of the following methods. Via the Remote Control Processor (RCP), enter the command; BBres or use the the standby power switches on the "Console, Alarms and Fans" (CAF) module of side B (bottom CAF module). Press the Black button to power off, after 10 seconds press the Green button to power on. 9. Reset Motherboard/side A using one of the following methods. Via the Remote Control Processor (RCP), enter the command; AAres or use the the standby power switches on the "Console, Alarms and Fans" (CAF) module of side A (upper CAF module). Press the Black button to power off, after 10 seconds press the Green button to power on. 10. Allow the system to return to the PROM prompt. Re-enable auto boot (i.e. {0} ok setenv auto-boot? true). 11. Boot the system (i.e. boot). 12. Use 'prtconf -V' to verify the system is running the latest PROM (prtconf -V should result in the following text being displayed: OBP 3.7.21.0 1999/04/01 16:36) 13. The patch installation has reset the cms configuration files to default values, thus when the system comes up both CPUSETS will be enabled by the CMS and will automatically come into sync. Wait for the system to go into sync using the procedure described below in Note 5, Determining If In Sync. 14. After the CPUsets have gone into sync, use cmsconfig to disable the CPUset in B-CPU (i.e. CPU 1). 15. Upgrade the PROM of the CPUset in A-CPU using the procedure described below in note 4, Upgrading PROM. NOTE: This is a MANDATORY patch, therfore when asked for confirmation, enter 'yes'. Failure to upgrade will leave the system with an unsupported configuration. At this stage the utility will report the version of the PROM currently running, which will be the SAME as the new version delivered in the patch. This is due to the system booting off the previously upgraded CPUset. Ignore the version numbers reported, and proceed as normal, upgrade the CPUset firmware for A-CPU. 16. Use cmsconfig to enable the CPUset in B-CPU (i.e. CPU 1). Wait for the system to go into sync using the procedure described below in Note 5, Determining If In Sync. Note 1 - Using cmsrepairfru --------------------------- Spuriously faulty FRUs should be identified using cmsfix, xcmsfix, or cmsconfig, and examining the 'fault' column). It is necessary to set the environment variable CMSHOME to "/usr/platform/SUNW,Ultra-4FT/SUNWcms" before using cmsrepairfru. For csh users: # setenv CMSHOME /usr/platform/SUNW,Ultra-4FT/SUNWcms For ksh and sh users: # CMSHOME=/usr/platform/SUNW,Ultra-4FT/SUNWcms # export CMSHOME Run the utility 'cmsrepairfru' on each FRU marked as faulty before the system is rebooted. For example: # cmsrepairfru A-PCI3 # cmsrepairfru A-MBD Note 2 - Installing The Patch ----------------------------- 1. Copy the compressed patch file onto the target system, in the following directory. /var/tmp/ 2. Uncompress, extract and install the patch files using one of the following two methods. (a) If the patch delivered is a compressed cpio file, i.e file name of ".cpio.Z" format, use the following commands: # cd /var/tmp/ # zcat .cpio.Z | cpio -iBVdmcu # cd # ./installpatch . (b) If the patch delivered is a compressed tar file, i.e file name of ".tar.Z" format, use the following commands: # cd /var/tmp/ # zcat .tar.Z | tar -xvf - # cd # ./installpatch . Where is the identifier of the patch (e.g. 107369-17) Note 3 - Upgrading FPGA ----------------------- 1. The flash update utility shipped with this patch is called: fwupdate.fpga.258-7134-07 and can be found in the directory: /usr/platform/SUNW,Ultra-4FT/lib 2. At the command line execute the upgrade-utility, # cd /usr/platform/SUNW,Ultra-4FT/lib # ./fwupdate.fpga.258-7134-07 3. The update utility will verify the integrity of the binary delivered and will then ask the user to specify the side of the system which is to be updated. Enter this information as either 'A' or 'B' 4. The current versions of the motherboard firmware will be reported along with the versions that will be installed by the update. Confirm that these are suitable to your requirements. If they are then reply 'yes' to perform the upgrade, otherwise reply 'no' and the update program will abort. 5. The update now takes place (progress messages will be printed). 6. When the update succeeds you will be asked if you wish to halt the system (Solaris) to allow a power cycle to be performed. Reply 'no'. 7. If the update fails note any error messages and contact your Sun Microsystems representative. Note 4 - Upgrading PROM ----------------------- 1. The flash update utility shipped with this patch is called: netra_ft_1800.flash.update-07 and can be found in the directory: /usr/platform/SUNW,Ultra-4FT/lib The utility CANNOT be executed whilst running in sync. 2. At the command line execute the upgrade-utility, # cd /usr/platform/SUNW,Ultra-4FT/lib # ./netra_ft_1800.flash.update-07 The update utility will verify the integrity of the binary delivered and will return reporting the current version of the PROM running and the version available to upgraded to. 3. You will be asked if you wish to continue. Answer 'yes' to upgrade, 'no' to abort. Answering yes, will display a list of NVRAM variables for the user to note, and reset later if different from the default values. Note these for safety, though it should not be necessary to use them. 4. You will be asked if you wish to continue. Answer 'yes' to upgrade, 'no' to abort. Answering 'yes' will perform the upgrade, and indicate the success or failure of the upgrade, 5. If the update fails note any error messages and contact your Sun Microsystems representative. 6. You will be asked "Do you wish to halt the system now". Answer "no". Note 5 - Determining If In Sync ------------------------------- To determine if the CPUsets are in sync, the leds on the front panels of the CPUsets should be examined. If the CPUsets are in sync the small amber LEDs marked 'diag' will flash in sync. Alternatively use the following command to determine if running in-sync; /usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ftvmctl -c will report " CPUsets running combined " if running in-sync. CPUset Integration ------------------ In order to reduce the time during final CPUset integration, in which the system is not performing system services (i.e. "stop-dead time"), it is necessary to alter the default setting using cmsconfig. In cmsconfig: Select the 'ft_core' sub-system, select pri_stop_time_msecs (menu item 4), select 200 (menu item 1), Quit from cmsconfig. From now on the system will use the lower value to achieve the lowest possible 'stop-dead' time during final CPUset integration. Please note, although 200 ms is selected it is still not possible to achieve that time. However, it does play a significant role in deciding at what point to start final integration. Enabling a failed CAF following a merge --------------------------------------- If the CAF fails to enable after a merge operation, do the following: 1. disable the failed CAF 2. if the error has been propagated to the corresponding MBD, run cmsrepairfru to repair the MBD, re-enable MBD. 3. enable the CAF