Patch-ID# 108145-10 Keywords: hardware netra ft1800 Synopsis: Netra ft1800 6.7: Multiple fixes patch Date: Oct/12/99 Solaris Release: 2.6 SunOS release: 5.6 Unbundled Product: Netra ft1800 Unbundled Release: 6.7 Topic: Netra ft1800 6.7: Multiple fixes patc NOTE: Refer to Special Install Instructions section for IMPORTANT specific information on this patch. This README is best viewed on an 80 character wide terminal. BugId's fixed with this patch: 4139353 4147332 4147690 4148160 4154801 4155801 4155823 4157406 4157416 4157443 4157789 4157801 4157817 4157821 4157831 4157887 4158260 4158266 4160733 4160741 4160746 4162741 4162744 4162788 4163707 4165747 4166424 4167070 4167079 4167470 4167780 4167781 4167784 4168160 4171153 4171836 4173477 4173741 4174046 4174067 4174112 4174727 4176384 4177626 4177923 4177937 4177958 4177961 4178284 4178294 4178314 4178334 4178336 4178633 4178688 4179203 4179369 4179370 4180164 4180176 4180186 4180199 4181612 4181629 4181637 4181642 4181666 4181824 4182337 4182338 4182344 4182679 4182689 4182692 4182732 4182739 4182746 4183200 4183224 4183235 4183508 4183509 4183511 4183553 4183591 4183595 4183600 4183622 4183664 4183870 4184310 4184612 4187074 4187111 4187398 4187400 BugId's fixed with this patch: 4187403 4187404 4187406 4187409 4187410 4187411 4187725 4187726 4187732 4187791 4187821 4187825 4187832 4187859 4187860 4188172 4188187 4188350 4188357 4189766 4190086 4191785 4191793 4193139 4193152 4193734 4197464 4197663 4197838 4197847 4198181 4198183 4198893 4199551 4200586 4200954 4201230 4201732 4201781 4201782 4201785 4201786 4201787 4201788 4201793 4201801 4203028 4203456 4203719 4203815 4204340 4204421 4204646 4204669 4204723 4204933 4205053 4205091 4205478 4205589 4206240 4206246 4206317 4206374 4206826 4207109 4207111 4207145 4207341 4207491 4207504 4207511 4207587 4207862 4207864 4207870 4207872 4207873 4207878 4207904 4207907 4207908 4207927 4208359 4208662 4208663 4208749 4208751 4209090 4209129 4209131 4209135 4209163 4209168 4209213 4209532 BugId's fixed with this patch: 4209548 4209563 4209586 4209739 4209945 4209959 4210001 4210021 4210425 4210440 4210739 4210740 4210761 4210763 4210792 4211193 4211239 4211254 4211269 4211582 4211583 4211673 4211676 4211680 4211681 4211759 4211772 4212126 4212183 4212784 4213525 4213533 4213970 4214340 4214417 4214916 4214918 4215346 4215363 4215824 4215827 4216288 4216754 4216780 4216787 4216795 4216807 4217181 4217188 4217229 4217258 4217265 4217279 4217678 4218110 4218454 4218463 4218897 4218916 4219764 4220270 4220625 4220628 4220735 4220740 4221070 4221113 4221618 4221944 4221992 4222456 4222929 4223003 4223869 4223975 4224330 4224335 4224768 4224818 4225131 4225143 4225167 4225169 4225187 4225899 4225918 4225948 4227405 4227426 4227448 4227455 4227831 4228179 4228183 4228193 4228281 BugId's fixed with this patch: 4228624 4228638 4229011 4229033 4229046 4229411 4230029 4230278 4230315 4230732 4230735 4231072 4231092 4231942 4232034 4232057 4232368 4233550 4233552 4233553 4234404 4234421 4234449 4235104 4235450 4235881 4235889 4236281 4236625 4236680 4236732 4236865 4236872 4237440 4237454 4237534 4237858 4237896 4237938 4238262 4238265 4238273 4238285 4238320 4239178 4239299 4239336 4239870 4240559 4243212 4243236 4243303 4243326 4243534 4243544 4243550 4243643 4243689 4243949 4243954 4244044 4244321 4244332 4244673 4244668 4244693 4244704 4245094 4245194 4245204 4245362 4245527 4245833 4245835 4245845 4246275 4246541 4247292 4247294 4247319 4247673 4247681 4248032 4248082 4248122 4248415 4248454 4248468 4249612 4249613 4249627 4250009 4250027 4250037 4250039 4250088 BugId's fixed with this patch: 4250382 4250411 4250436 4250448 4250808 4251103 4251117 4251119 4251439 4251729 4252082 4252085 4252100 4252131 4252139 4252147 4252157 4253255 4253267 4253579 4253608 4253668 4253685 4254304 4254314 4254340 4254464 4254773 4255552 4255562 4255810 4255820 4255821 4255868 4255915 4256378 4256957 4257396 4257719 4257742 4257744 4257761 4258161 4258489 4259079 4259086 4259110 4259482 4259537 4259543 4259943 4259985 4260297 4260309 4260843 4260845 4261246 4261263 4261287 4261961 4262297 4262617 4268608 4269213 4269227 4270084 4270177 4273105 4275799 Changes incorporated in this version: 4273105 4275799 Relevant Architectures: sparc Patches accumulated and obsoleted by this patch: 108065-03 107926-03 107369-16 Patches which conflict with this patch: Patches required with this patch: 105181-14 Obsoleted by: Files included with this patch: SUNWftm/man/man1m/cmsrepairfru.1m SUNWftm/man/man1m/u4ftlogfmt.1m SUNWftm/man/man7d/u4ftalarm.7d etc/806-3437-10.pdf etc/config.icn0 etc/config.icn1 etc/config.icn2 etc/config.icn3 etc/init.d/cms etc/init.d/cms_finish etc/init.d/cms_sync etc/init.d/dumpvp_setup etc/init.d/init.pnet etc/init.d/init.pnetd etc/init.d/ttymuxrc etc/init.d/u4ftlogging etc/init.d/u4ftsplit etc/init.d/u4ftsplitl1 etc/init.d/u4ftsplitl2 etc/init.d/u4ftsplitnet etc/splitd.conf kernel/drv/ttymux kernel/drv/ttymux.conf platform/SUNW,Ultra-4FT/kernel/cpu/SUNW,UltraSPARC platform/SUNW,Ultra-4FT/kernel/drv/dump platform/SUNW,Ultra-4FT/kernel/drv/dump.conf platform/SUNW,Ultra-4FT/kernel/drv/ebus platform/SUNW,Ultra-4FT/kernel/drv/fzcpuset platform/SUNW,Ultra-4FT/kernel/drv/fzcpuset.conf platform/SUNW,Ultra-4FT/kernel/drv/glm platform/SUNW,Ultra-4FT/kernel/drv/hme platform/SUNW,Ultra-4FT/kernel/drv/icn platform/SUNW,Ultra-4FT/kernel/drv/icn.conf platform/SUNW,Ultra-4FT/kernel/drv/pci platform/SUNW,Ultra-4FT/kernel/drv/pci_pci platform/SUNW,Ultra-4FT/kernel/drv/pnet platform/SUNW,Ultra-4FT/kernel/drv/pnet.conf platform/SUNW,Ultra-4FT/kernel/drv/qfe platform/SUNW,Ultra-4FT/kernel/drv/rootnex platform/SUNW,Ultra-4FT/kernel/drv/sad platform/SUNW,Ultra-4FT/kernel/drv/sad.conf platform/SUNW,Ultra-4FT/kernel/drv/sd platform/SUNW,Ultra-4FT/kernel/drv/sd.conf platform/SUNW,Ultra-4FT/kernel/drv/se platform/SUNW,Ultra-4FT/kernel/drv/se.conf platform/SUNW,Ultra-4FT/kernel/drv/st platform/SUNW,Ultra-4FT/kernel/drv/st.conf platform/SUNW,Ultra-4FT/kernel/drv/sysctrl platform/SUNW,Ultra-4FT/kernel/drv/u4ft-eeprom platform/SUNW,Ultra-4FT/kernel/drv/u4ftalarm platform/SUNW,Ultra-4FT/kernel/drv/u4ftalarm.conf platform/SUNW,Ultra-4FT/kernel/drv/u4ftbus platform/SUNW,Ultra-4FT/kernel/drv/u4ftbus.conf platform/SUNW,Ultra-4FT/kernel/drv/u4ftcmd platform/SUNW,Ultra-4FT/kernel/drv/u4ftcmd.conf platform/SUNW,Ultra-4FT/kernel/drv/u4ftdog platform/SUNW,Ultra-4FT/kernel/drv/u4ftdog.conf platform/SUNW,Ultra-4FT/kernel/drv/u4fteintr platform/SUNW,Ultra-4FT/kernel/drv/u4fteintr.conf platform/SUNW,Ultra-4FT/kernel/drv/u4ftfctlr platform/SUNW,Ultra-4FT/kernel/drv/u4ftfctlr.conf platform/SUNW,Ultra-4FT/kernel/drv/u4fti2c platform/SUNW,Ultra-4FT/kernel/drv/u4fti2c.conf platform/SUNW,Ultra-4FT/kernel/drv/u4fticc platform/SUNW,Ultra-4FT/kernel/drv/u4fticc.conf platform/SUNW,Ultra-4FT/kernel/drv/u4ftiodr platform/SUNW,Ultra-4FT/kernel/drv/u4ftiodr.conf platform/SUNW,Ultra-4FT/kernel/drv/u4ftlog platform/SUNW,Ultra-4FT/kernel/drv/u4ftlog.conf platform/SUNW,Ultra-4FT/kernel/drv/u4ftmbox platform/SUNW,Ultra-4FT/kernel/drv/u4ftmbox.conf platform/SUNW,Ultra-4FT/kernel/drv/u4ftpto platform/SUNW,Ultra-4FT/kernel/drv/u4ftpto.conf platform/SUNW,Ultra-4FT/kernel/drv/u4ftrcp platform/SUNW,Ultra-4FT/kernel/drv/u4ftrcp.conf platform/SUNW,Ultra-4FT/kernel/drv/u4ftvm platform/SUNW,Ultra-4FT/kernel/drv/u4ftvm.conf platform/SUNW,Ultra-4FT/kernel/drv/u4ioslot platform/SUNW,Ultra-4FT/kernel/drv/u4ioslot.conf platform/SUNW,Ultra-4FT/kernel/drv/vol platform/SUNW,Ultra-4FT/kernel/drv/vol.conf platform/SUNW,Ultra-4FT/kernel/fs/specfs platform/SUNW,Ultra-4FT/kernel/fs/ufs platform/SUNW,Ultra-4FT/kernel/genunix platform/SUNW,Ultra-4FT/kernel/misc/consconfig platform/SUNW,Ultra-4FT/kernel/misc/platmod platform/SUNW,Ultra-4FT/kernel/misc/scsi platform/SUNW,Ultra-4FT/kernel/misc/swapgeneric platform/SUNW,Ultra-4FT/kernel/tod/todu4ft platform/SUNW,Ultra-4FT/kernel/unix platform/SUNW,Ultra-4FT/lib/pnetctl platform/SUNW,Ultra-4FT/lib/pnetd platform/SUNW,Ultra-4FT/lib/u4ftctl platform/SUNW,Ultra-4FT/lib/u4ftmode sbin/crashplus sbin/ttymuxadm 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.init usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/A-MBD/A-MBD.start 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.init usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/B-MBD/B-MBD.start usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/CAF/CAF.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/CAF/CAF.init usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/CPU/CPU.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/CPU/CPU.init usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/DSK/DSK.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/DSK/DSK.init usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/HDD/HDD.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/PCI/PCI.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/PCI/PCI.init usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/PCI/findPCIDevices usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/PSU/PSU.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/PSU/PSU.init usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/RMM/RMM.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/RMM/RMM.init usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/RMM/findRMMDevices usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/bridge/bridge.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/cdrom/cdrom.cmsdef 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/cpusetio/cpusetio.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/disk/disk.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/disk/disk.start usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/ebus/ebus.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/eintr/eintr.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/ft_alarm/ft_alarm.cmsdef 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.start usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/ft_network/ft_network.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/ft_serial/ft_serial.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/glm/glm.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/glm/glm.offline usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/glm/glm.online usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/icn/icn.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/icn_system/icn_system.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/icnio/icnio.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/master_sync/master_sync.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/network/network.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/pci/pci.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/pci_pci/pci_pci.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/pcidef/pcidef.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/port/port.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/registry/registry.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/scsi/scsi.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/serial/serial.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/slot/slot.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/sync_HDD/sync_HDD.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/sync_PCI/sync_PCI.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/tape/tape.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftalarm/u4ftalarm.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftalarm/u4ftalarm.prop0 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftalarm/u4ftalarm.prop1 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftdog/u4ftdog.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftdog/u4ftdog.prop0 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftdog/u4ftdog.prop1 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftfctlr/u4ftfctlr.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftfctlr/u4ftfctlr.prop0 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftfctlr/u4ftfctlr.prop1 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4fti2c/u4fti2c.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4fti2c/u4fti2c.prop0 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4fti2c/u4fti2c.prop1 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4fti2c/u4fti2c.prop2 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4fti2c/u4fti2c.prop3 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftiodr/u4ftiodr.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftiodr/u4ftiodr.prop0 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftiodr/u4ftiodr.prop1 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftiodr/u4ftiodr.prop2 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftiodr/u4ftiodr.prop3 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftmbox/u4ftmbox.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftvm/u4ftvm.cmsdef usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftvm/u4ftvm.prop0 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftvm/u4ftvm.prop1 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftvm/u4ftvm.prop2 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/cmsdef.d/u4ftvm/u4ftvm.prop3 usr/platform/SUNW,Ultra-4FT/SUNWcms/etc/u4ftloc.data usr/platform/SUNW,Ultra-4FT/SUNWcms/include/cms_api.h 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/cmsCreateDevice usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsTagDevice usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmscheckfru usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsconfig usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsconfig.retry usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsd usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsdebug usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsenvadm usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsenvd usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsfailfru usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsfix usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsfruinfo usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsintroduce_mbd usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsledctl usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmslock usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmslog usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsmonitord usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsmreport 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/cmsreport usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/cmsrootdisks 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/pnetctl usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/pnetd usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/scsictl 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/u4ft_checkFRUBusyStatus usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ft_controlDevice usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ft_deleteCMSDeviceTag usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ft_findPath usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ft_offlineParent usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ft_onlineParent usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ft_setMBDLocation usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ft_unsetCMSDeviceTag usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ft_validateFRU usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ftdev_enq usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ftdev_match usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ftdev_select usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ftdev_setprops usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ftloc_get_parameter 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/u4ftvmctl usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/vxbootcheck usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/xcmsfix usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/cms_start usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/cmsenvadm usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/cmsinitialise usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/cmsleaky usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/cmsphonehome usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin/pmstat 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/SUNWlogu/lib/u4ftlog_salvage usr/platform/SUNW,Ultra-4FT/SUNWlogu/lib/u4ftlogctl usr/platform/SUNW,Ultra-4FT/SUNWlogu/lib/u4ftlogd usr/platform/SUNW,Ultra-4FT/SUNWlogu/lib/u4ftlogfmt usr/platform/SUNW,Ultra-4FT/lib/fwupdate.fpga.258-7134-08 usr/platform/SUNW,Ultra-4FT/lib/netra_ft_1800.flash.update-10 usr/platform/SUNW,Ultra-4FT/sbin/prtdiag usr/platform/SUNW,Ultra-4FT/sbin/u4ftalctl usr/platform/SUNW,Ultra-4FT/sbin/u4ftdogctl 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 4147332 setSerialPorts has malformed call to cmsconfig 4147690 devlinks should not be deleted (cf entries in path_to_inst) 4148160 cmsinitialise should only look at FRUs owned by the side it's running on 4154801 System panics immediately after logging in. 4155801 Need causefault for FCS 4155823 cmsfix core dumped during transition to run level 2 4157406 saip install output error msg 4157416 Semantics of dz_idle_other_cpus() differ between SP & MP 4157443 cmsledctl prints incorrect usage prompt when invalid input is received 4157789 Logging system broken. 4157801 smadm utility doesn't lock out concurrent accesses 4157817 hme cmsdef leads to shell 'syntax error' 4157821 cmspohd resets invalid EE_GEN_CUR_POSITION to arbitrary valid value 4157831 RFE: To allow a losing CPUset to reset itself. 4157887 CMS cannot handle non-predefined third party devices 4158260 System panics when trying to pri 4158266 Test Harness panicsShould on attempting to bind bound dma handle 4160733 HME driver 'interrupt failure' check does not work 4160741 glm controlled cards do not online early enough 4160746 unrecognized print option in network print interface causes error 4162741 Alias attribute should be renamed "user_label" 4162744 cmsconfig should provide direct link between FRUs and devices 4162788 cmspwrctl does not manage PSU power 4163707 System panics whilst configuring an ft_network using CMS 4165747 u4ftser info command 4166424 Writing to Psycho interrupt clr regs occasionally causes UPA lock up (in-sync) 4167070 u4ft_offlineParent should no longer check for failed non-cms managed siblings 4167079 u4ftser fails to handle transparent TIOCMGET M_IOACK message 4167470 CMS incorrectly displays a fault after hot plugging 4167780 CMS needs /opt to be root-writable 4167781 PRI breaks trap_trace (trap_trace may also cause early OOS event). 4167784 SUNWpnetc postinstall fails when specifying -R /a to pkgadd 4168160 cmscheckfru does not support reading alternative maintenance bus 4171153 upgrade "nuke" test interface to support bridge fault-injection 4171836 DTLB can have duplicate entries leading to unspecified errant behaviour 4173477 Inapplicable/inappropriate messages during boot-up 4173741 pn_do_back_enb panic: bad mutex 4174046 Additional fields in motherboard eeprom structure to configure osdog. 4174067 Splitting a system may lead to ethernet address clash 4174112 Extension/amendment to FRU thermal monitoring and recording 4174727 cmspreupgrade and cmspostupgrade don't have split library on LD_LIBRARY_PATH 4176384 Userland utilities build dependencies not correct 4177626 Pre & Post PRI events need to be run at EPL_CRITICAL 4177923 Allegedly idle processors moonlight more often than first thought 4177937 Lock files do not write pid correctly 4177958 Modify cmsd to make debugging cmsdefs easier 4177961 Disk FRU failures cause Disk Chassis FRU to be marked as failed 4178284 Need cms support in cpuset driver 4178294 se driver doesn;t detach - prevents ebus being offlined 4178314 framework not reporting online->online transitions - cms won't start up 4178334 INO test in hme fails 4178336 If a bridge is broken u4ftser splutters gibberish 4178633 Log rotation cron job fails (cannot extract u4ftlogctl pathname) 4178688 show-pci-config fails 4179203 pkgchk(1M) fails for installed SUNWcms/SUNWftcao package 4179369 frucfg expects times to be entered using "string" notation 4179370 EE_CPU_VERSION handled incorrectly by cmsfruinfo 4180164 EE_GEN_POSITION_HISTORY_n_LOCATION_SLOT_NO handled incorrectly by frucfg 4180176 Unable to attach fzcpuset driver underneath slot nexus using u4ft framework 4180186 new drvconfig script doesn't work 4180199 New disk FRUs can be marked as faulty when first configured 4181612 cmsmonitord sends multiple error messages to log when both alarms are offline 4181629 cms starts two scsilt processes erroneously 4181637 logging timestamp entries unclear 4181642 failing fan speeds not reprted to log when failures occur 4181666 libfru is now too tolerant of missing split library 4181824 Deliverables conflict with point patch deliverables. 4182337 cmsfix does not update display following a keyboard command 4182338 Returning from OBP to unix sometimes hangs console output for 8 seconds. 4182344 br_intr u4ft_critical_level assertion failure panic 4182679 no latent fault checker for fans 4182689 ddi_get_name returns null in alarms driver causing panic 4182692 sm cmsdef contains errors 4182732 pseudo console device driver needed (u4fticc) 4182739 machine requires a reboot if an out-of-sync occurs (slot 6 won't offline) 4182746 SUNWftcau packaging incorrect 4183200 ft_network does not honour preferred_controller when initialising 4183224 Sheffield VERSION problem might prevent upgrade to 2.8 to work successfully. 4183235 bus errors on attempts to pri 4183508 slot.cmsdefs does not contain all valid hme combinations 4183509 Class specific scripts not long enough 4183511 ft_network will not link plug-in network controllers 4183553 vm_fixup has Psycho flush flag pointing beyond assigned buffer 4183591 slot.cmsdef may contain unnecessary options for dev[0-3] 4183595 *-caf-test reports identical speeds for non-identical fans 4183600 hostid becomes corrupted after re-boot 4183622 RFE: u4ftvmctl should have -t (& hence -p) option enabled by default 4183664 fzcpuset does not report correct _cpuset_status prop to cms 4183870 The svrmgrl command of ORACLE8 dumps core under bad cpu module. 4184310 systems hangs during os startup, but only after a reboot 4184612 dropping into OBP whilst insync can cause latent OOS 4187074 u4ftmbox driver hangs when offlined 4187111 Cheerio arbiter bit turned off during CAF-TEST 4187398 Addition of OSDOG driver to sheffield tree 4187400 need script to call cmsrootdisks to update list of boot disks 4187403 Implement alarms utilities 4187404 Provide man pages for the u4ftalarm driver and associated utilities 4187406 ft_network.cmsdef does not have enough hme constituents 4187409 File no longer needed by cmsdefs 4187410 if two devices on same pci bugs disabled at same time, can't enable again 4187411 obp leaves motherboard mb port 4 in a state that might prevent power on. 4187725 CE signature not gathered on OOS 4187726 PROM test all-leds-on fails to illuminate system LEDs on both CAFs. 4187732 PROM command 'probe-mbus' does not report an lm78 device for cpusets 4187791 Tidy up debug logging 4187821 make install fails for package SUNWftutu.u 4187825 make install fails for package SUNWftmur.u 4187832 make install fails for package SUNWftcao 4187859 latent fault checker can sometimes lock up after offlining a disc 4187860 stop/start vold when removing/adding cdrom 4188172 PROM fails OBP_vtt test, OBPVTS_math 4188187 pnetd does not promote itself to an RT thread 4188350 SUNWsmadm violates the package guideline and should be fixed. 4188357 If CPUset with CE wins (say after recent PRI) then CMS not told of CE 4189766 Losing CPUset (OOS) should record last failure message in EEPROM 4190086 Infant mortality OOS in 1 out of 100+ PRI attempts 4191785 FRUs should display device info strings when problems occur 4191793 u4ftloc.data incorrect for osdog 4193139 sheffield system takes too long to boot up 4193152 need ddi framework change to stop panics caused by Veritas dev-tree walking 4193734 CAF sometimes cannot be offlined 4197464 rcp AAres/BBres command causes osdog monitoring takeover 4197663 Cannot install software on loxley 4197838 4p cpusets sometimes don't see all processors. 4197847 cmsconfig core dumps when the VIEW options is selected with no options. 4198181 Solaris bug 4106093 is not fixed in our tree & has caused a hang, need fix 4198183 Split mode config files are now in wrong location in file system 4198893 Typo - 'Returned from final of cpuset' in pri 4199551 bridge nex and slot nex should combine to set client pci latency values 4200586 nvram read from post menu fails when given count and increment 4200954 Exec POST from memory causes exception if run twice 4201230 Osdog in solaris always uses the 85 second timeout 4201732 ttymux driver drops into OBP when parity errors are detected. 4201781 wrong basedir value and attributes in SUNWcmscu.u 4201782 wrong basedir value and attributes in SUNWcmsdf.u 4201785 wrong attributes in SUNWcmsr 4201786 wrong basedir value and attributes in SUNWcmsu 4201787 wrong basedir value and attributes in SUNWcrash 4201788 wrong attributes in SUNWftcar.u 4201793 wrong basedir value and attributes in SUNWftutu.u 4201801 wrong attributes in SUNWttymx 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 4203815 inconsistent behaviour on 'init 5' 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 4204723 i2c_faulty set to yes results in faulty being set to no, clearing existing fault 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 4206240 OBP should update eeprom bridge/rcp partnumbers when restoring default images 4206246 integration receive keypress timeout leaves an item on the stack 4206317 Osdog barked after "shutdown -i0 -g0 -y" followed by "reset-all" 4206374 install-cqueues attempts to install wrong device 4206826 sheffield package copyright files are outdated 4207109 writing of configfile deferred until lengthy scripts in ft_core complete 4207111 u4ft_findPath reports complete path for targets with two character in 4207145 Infant mortality OOS not handled correctly by CMS 4207341 NVRAM on sheffield system is not consistent with other Sun platforms 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 4207864 cms does not handle blank string attributes in a the configfile 4207870 read error from fat controller 4207872 PCI eeprom attributes not refreshed on enable_failed -> enabled 4207873 .lock directories not deleted following a reboot. 4207878 'Stack Underflow' after rcp repair 4207904 i2c buses not used correctly with motherboard powered off 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 4207927 cmsfix help screen displays help on out-of-date commands, un/configure etc. 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 4209129 cms should consider "supported" configurations when diagnosing failures 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 4209548 CPUset power control via I2C doesn't set alternate power bit 4209563 RFE: Should reduce the timing window in which PRIing CPUset drops primacy 4209586 frucfg unable to set date field in fru eeprom 4209739 SUNWpnet upgrade fails due to bad postinstall script. 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 4210739 prom corruption in post area not detected 4210740 cpuset pri and/or heavy io load causes disk checksum validation failure 4210761 osdog-get-timeout does not work in combined mode 4210763 bridge fails on split if force option is used 4210792 Default NVRAM parameters are for a workstation. 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 4211673 osdog not disabled during driver offline 4211676 osdog reset not reported in ft system with power supplies 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 4212126 Obp does not provide functionality to clear boot-list eeprom property 4212183 u4ftsplitd may set srr bits incorrectly on split 4212784 system hangs with callb_delete blocked on mutex_enter 4213525 OBP stops if lock cable is not present. 4213533 POST stops if motherboard lock cable is not present. 4213970 cmsrepairfru has incorrect path to lib directory and so does not work 4214340 u4ftdog source code should be lint and cstyle clean 4214417 The function lm75_temp() should read two bytes not one from the I2C bus 4214916 cmsphonehome is not invoked following an environmental failure 4214918 osdog patting fails with 1 motherboard powered off 4215346 Went OOS - CPUset had started to PANIC 4215363 prom utility should report it can not upgrade whilst system is running in-sync 4215824 veritas fails to recognise external disk volume when booting 4215827 ftp across PCI based 100Mb/s network is slow/intermittent 4216288 Inconsistency in CAF output for a-probe-mbus and b-probe-mbus tests 4216754 fwupdate.fpga utility instructions does not accurately follow actual behaviour 4216780 _cpu_status not sent when in sync operation achieved 4216787 Over/undertemperature should not cause hard failure of module 4216795 [ab]-caf-test fails serial and network tests 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 4217258 banner and suppress-banner (in nvramrc) work incorrectly on Sheffield 4217265 console-list helper functions do not check for initialised consoles 4217279 failure to access pci device nodes results in stack underflow 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 4218916 pre-split operation on secondary FT networks should be done automatically 4219764 PCI class code for network device nodes is wrong 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 4220735 some pci slot maintenance bus words don't work. 4220740 PSU object reports "problem with input source" when input supply reintroduced 4221070 s/w TLB replacemnt scheme needed to workaround UltraSPARC-II non-determinism 4221113 [ab]-caf-test network test (net-selftest) jams 10Mb hub 4221618 status log needs to record reason for OOS events 4221944 u4ftalarm.7 required to be installed for Alrams ioctl API info 4221992 man page required for u4ftlogfmt to be installed on ft 1800. 4222456 CAF LM78 can get wedged in a half-configured state 4222929 circular dependency in split tree 4223003 /kernel/drv/qfe prevents sheffield qfe driver being loaded without a reboot 4223869 cms_tag field of cpu_t and related structures has wrong type 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 4224818 failure to 'probe-all' results in osdog not being patted 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. 4225899 offlining motherboard can fail to offline fctlr and bridge 4225918 alarms are not split aware 4225948 problem in do_copy_pages_ioctl causes instance offline to hang 4227405 FPGA update utility for T107369-10 gives incorrect data-path & data-path64 info 4227426 Not all of C prom is checksummed. 4227448 OBP gives away ownership of slot 6 slots at reset. 4227455 pnet can maintain spurious hold on qfe driver - cannot modunload without reboot 4227831 alarms are not mngd properly after split, related to bug 4225918 4228179 motherboard osdog tests fail when primary tests secondary's motherboard 4228183 Speed up u4ftsplitd startup performance 4228193 vxbootcheck contains extra single quotes - can lose system dumps with veritas 4228281 .onboard-versions word decodes UPA config register incorrectly 4228624 PANIC : send_mondo: timeout (target 0x1) 4228638 Disk was marked as faulty due to motherboard "failure" 4229011 cpuset failure during PRI requires system reboot to recover 4229033 _redundancy wrongly set in ft_network - causes misassessment of state 4229046 panic: mutex_exit: not owner 4229411 help for the 'netload' command has a typing error 4230029 WARNING: pnet#2: unable to set node type of device (qfe#1) 4230278 problem with cms not resetting pci bridge correctly 4230315 mbrd_flags field (in sh_nvram.h) is hardcoded to zero by OBP 4230732 Potential for stuck in busy when device tag not present 4230735 merging a split system causes the new sides motherboard to go failed 4231072 The lock file for splitd is in /tmp (wrong location) 4231092 fix for panic after bridge failures may allow latent faults 4231942 u4ftdogctl reports status to standard error 4232034 Cmsconfig shows incorrect environmental values for PSU's 4232057 cms fails to set funct_0 correctly when transitioned offline_failed - online 4232368 PSUs do not latch overcurrent fault status 4233550 simplify and speed up meta_action create code. 4233552 soft_fail confuses the real FRU with the management FRU 4233553 device failure diagnosed as report_to_eeprom=no still sets faulty 4234404 faulty rcp motherboard fpga images are not mended by cpuset B for mbrd B 4234421 obp does not recognised motherboard fpga download failures 4234449 Unable to integrate under load with 2p system 4235104 can not ftp files on UP system without drastically affecting system performance 4235450 backoutpatch script for patch 107369-12 does not work correctly 4235881 cmsTagDevice is too expensive 4235889 B-CPU started to panic during the pri after a system reboot 4236281 pnet causes ifconfig to hang 4236625 scsi_probe failures in sd and st drivers attach should be high severity faults 4236680 memory leak in pnet: pn_xping 4236732 ftSafe: Diagnostic output from fruoeminit could be improved 4236865 split failed because the wrong CPU went out-of-sync 4236872 enable/disable of osdog using u4ftdogctl should update /u4ft-options node 4237440 potential race condition in serial action_unlink 4237454 CMS should take charge of all ttymux driver links 4237534 if driver attach reports fault and returns DDI_FAILURE it is left attached 4237858 Volume Manager appears hung during checksum building 4237896 online sm objects need to be specifically included in cmsconfig 4237938 ttymuxadm produces warnings in a split system 4238262 remove state change messages (S) from status logs 4238265 ft_service action_link/unlink should be carried out while device node is locked 4238273 st.c fails to compile in 1U source stream - breaking build 4238285 splitconf does not fail on master side when FRU does not disable 4238320 OBP crashes when initialising with it's own motherboard broken 4239178 set-conf-osdog-a/b need replacing by set-conf-osdog 4239299 OSdog driver should comply with the osdog design document 4239336 tickint_clnt_add fix needs backporting to the netra ft1800 patch tree 4239870 RFE: u4ftlogfmt should use LC_* variables to localise output 4240559 Debug log reports " ksh: checks: not found" 4243212 OSdog barks when post memory tests are executed 4243236 POST memory test fails on system with two memory banks populated 4243303 Status log should record 'user initiated attribute changes' 4243326 Make deadman kernel work on MP Netra FT 1800 (Solaris 5.6) 4243534 pnet is not correctly installed by build 7.0 4243544 Cip needs to be enhanced for CMS to detect the other cpuset is waiting for pri 4243550 patch-16 README file has been stripped of unix commands beginning with # 4243643 POST occasionally fails (CPU Module 1 Error)processor 1 when diag-level=max 4243689 core dump lost after panic 4243949 level 12 interrupt lockup halt system 4243954 PCI stuck in busy 4244044 ft_network does not 'come up' following post-install reboot 4244321 pnet panic when removing a multicast broadcast with ShowMeTV 4244332 OBP calibrates clock interrupts incorrectly on 2P 512M systems 4244668 need to put tlb fix in build 7 4244673 asynchronous saip loopback test has intermittent high values 4244693 System hang on a 1P system due to try_enters in pnet 4244704 Patch C: MBD faults, Dbus master-abort observed (dma) DMA_RD/WR ft 36 / 39 4245094 i2c error message in log 4245194 The Osdog did not trigger when a priority 10 hang was generated using causefault 4245204 motherboard goes failed when slot6s fail 4245362 sun4u softint pool needs to be expanded 4245527 RFE: Provide hooks for vm_fixup processor self tests 4245833 Multiprocessor post sometimes fails with RED-state exception. 4245835 OSdog goes off in dtag init test if diag-level is max. 4245845 disk occasionally failing to disable if checksums were building 4246275 Unable to integrate CPUset with dual scsi and external disks on system 4246541 split fails saying erroneously that DSK didn't disable 4247292 _device_failed not relinked to _device_soft_fault in _cms_fru_action 4247294 Remove debugging messages from u4ftdog 4247319 Need fix for 4128397 (kernel crash dump causes another panic in bio.c::getblk() 4247673 Spurious error message from cmsd "unsolicited property event" 4247681 Tags for glm controlled external disks cause spurious log messages 4248032 Inconsistencies in handling pre-enable checks for FRUs 4248082 more controls before splitting 4248122 further pri stop dead time enhancements. 4248415 warning message on merge may be mildly misleading 4248454 wait for pri code needs to enable streaming cache 4248468 cmsd to support generic scripts up to 64kbytes in length 4249612 cms should not worry about discontinued "no restore" attributes in configfile 4249613 disable_failed message should be more useful 4249627 pnet should be swicthed if primary controller goes enable_failed 4250009 ft_network can lose configuration after system panic 4250027 PCI scsi FRU object gets stuck in busy 4250037 message string for EIO is inaccurate 4250039 Too many scsictl BUILDs started at boot time. 4250088 RFE: i2c tracing could be improved 4250382 RFE: u4ftlogfmt should buffer output less 4250411 man pages revised 4250436 DDR access should use Netra FT 1800 IO access coding rules. 4250448 ft_network hanges if both CAFs are enable_failed 4250808 cmsclass class action script does not maintain timestamp for deliverables 4251103 dump and dump.conf missing from packaging 4251117 cmsd waits for 20 secs unneccessarily when exiting 4251119 cmsd isn't successfully restarted by cmsmonitord when killed 4251439 usable_controllers etc don't get immediately updated if controller unconfigured 4251729 split loser has CMS attribute *hostname* incorrect in ft_network 0 4252082 Spurious fault message during disable of icn_system 4252085 icn fails to enable/disable correctly 4252100 if icnio or u4ftmbox device fails behaviour looks broken 4252131 Spurious error _CPU_####_event in log 4252139 i2c hung after disabling a cpuset 4252147 Hard PRI failure causes ft_core info to be set to "Running on side-CPU" 4252157 validate_eeprom and power_on failures set info even when still allowing enable 4253255 No abort handling until the cn driver is opened. 4253267 Disabled CPU: reports "unable to get cpuset _cpu_status property" 4253579 Bridge 0 patch (108065) has not been rolled up into Patch D 4253608 e_dovmfix has incorrect sprintf string 4253668 Race condition gives spurious error messages 4253685 RFE: Tolerance of infant mortality required 4254304 Need a way to time stop-dead period in software. 4254314 default 'stop-dead' parameter is too high in ft_core 4254340 disable CAF fails if device fruname is not x-CAF 4254464 pnet 1 causes thrashing problem 4254773 glm driver took 15 minutes to time out after a BBres 4255552 need fix for 4245362 applied to Sheffield 4255562 opening the se driver hangs 4255810 If a side is powered off i2c_faulty sets "faulty" of all FRUs to yes 4255820 PRI hang in pre-pri phase-2 due to suspected sbuf_flush_vaddr() mutex contention 4255821 ambient_temperature errors go into _info_1 4255868 replacing qfe card with atm card locks cms in busy 4255915 CAF serial devices listed incorrectly 4256378 SUWcmsdf.u package build fails 4256957 RMM 1 cms object stuck in busy 4257396 split mode: bridge not offlined when MBD is disabled 4257719 A system panic was seen using patch D 4257742 All disks are always re-checksummed even after clean shutdown 4257744 External disks under Veritas control always require a full re-mirror after boot 4257761 cms icn enable/disable inconsistency 4258161 Typo in info message associated with hard OOS 4258489 syncing file systems... [1] [1] [1] [1] [1] [1] [1] [1] [1] ....... 4259079 need work-around for 4257703 (sunvts:ftcpuset doesn't work) 4259086 scsictl BUILD commands should be killable (otherwise delays reboot) 4259110 _device_failed and _info_1 should not be cleared on action disable 4259482 Potential for incorrect osdog control on infant mortality 4259537 icn cms objects stuck in busy 4259543 Cannot remove the final controller from a ft_network with no hostname 4259943 CAF object 'unlinks' console and network on failure to initialise. 4259985 pci_pci_bridge causes invalid value message in debug log 4260297 /etc/link.hme* files not recreated if ft_network 0/1 config changed 4260309 u4ftrcp does not perform atomic firmware upgrade operations 4260843 Portions of configfile not written correctly by cmsd 4260845 Configuring an ft_network caused system panic 4261246 typo in auto-pri when recoverable pri occurs 4261263 Disabling CPUset should not leave vm_fixup management penalties set 4261287 CMS should not assume that the 'offlined' CPUset lost the OOS contest 4261961 splitd daemons fail to communicate the owner of a device correctly 4262297 RFE: Add check for processor bug 4183870 during vm_fixup evaluation 4262617 E_state forced in split mode 4268608 Searching for FINS is made more difficult because of the leading zero in the id. 4269213 108145-04: cmsd & cmsmonitord are not killed prior to installing patch 'D' 4269227 108145-04: cmsconfig.rule is not always correctly updated 4270084 Panic : mutex_exit: not owner ... 4270177 accidental ^C during startup, presence of split lock, leaves system unuseable 4273105 Cannot back out patch 'D' (107369-18) 4275799 Inclusion of updated PDF and a corresponding Postscript file in Patch 108145-10 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. In addition to this patch, (108145-10), you must download patch 108181-01 from Sunsolve. This patch will deliver the KU14 patch, (105181-14), which can then be installed. Special Install Instructions: ----------------------------- ************************************************************************* * This patch, (108145-10), requires that you have Patch C, * * (107369-16 or 107369-17), already installed on your system. * * DO NOT PROCEED UNLESS PATCH 107369-16 or 107369-17 HAS BEEN APPLIED * * TO YOUR SYSTEM. THIS RESTRICTION ALSO APPLIES TO THE KERNEL UPDATE * * PATCH KU14, (105181-14 delivered in patch 108181-01). * * * * Because the installation procedure supersedes instructions given in * * the related patches, the full prerequisites and installation * * procedure for Patch D, along with details of the enhanced/new * * functionality delivered in this patch, (108145-10), are provided in a * * seperate document, "Netra ft 1800 Interim Update Instructions", which * * is provided in the following files: /etc/806-3437-10.pdf * * (which will be available once the patch has been installed). * * * * You are strongly advised to follow the instructions given in the * * /etc/806-3437-10.pdf file. * * * * Note: Any deviation from the procedure will require a complete * * Solaris re-installation before service can be resumed. * ************************************************************************* Non-generic install instructions -------------------------------- Introduction ------------ This section describes the following: . Patch Install Strategy. . Patch Backout Strategy. . Patch Installation Procedure. - FPGA upgrade instructions. - PROM upgrade instructions. . Patch Backout Procedure. - PROM regression instructions. . Failing to establish ICN network on split action . Enabling a failed CAF following a merge . Behaviour of CMS CPU object Patch Install Strategy ---------------------- This patch, (108145-10), can only be installed once the KU14 (kernel update) patch has been installed. This patch has now been superceded and is thus unavailable, it has been made available via the patch 108181-01, which is available from Sunsolve. Install the KU14 patch directly or install patch 108181-01 and then install the delivered KU14 patch 105181-14 from it. Having installed the KU14 patch, *** DO NOT *** reboot the system, (as advised in the KU14 patch README file). Note: If the QFE patch (107778) has been applied prior to applying this patch, (108145-10), the QFE patch (107778) must be backed out (and re-applied following application of this patch, (108145-10)). The installation steps are as follows:- . Verify Pre-requisites . Install KU14 Delivery Patch, (108181-01) . Install KU14 Patch, (105181-14) . Backout QFE Patch, (107778-04), if installed . Install this Patch, (108145-10) . Reboot the system . Re-install QFE Patch, (107778-04) . Upgrade Motherboard Firmware, (FPGAs) . Upgrade CPUset Firmware, (PROMs) . Power Reset the system The instructions detailed herein contain additional 'tick' boxes to assist in recording the progress through the procedures. These appear as follows:- e.g. Patch Installed: [ ] Patch Backout Strategy ---------------------- Before the patch can be backed out, the cpuset prom firmware must first be regressed to the level appropriate to the previous patch: if not then the cpusets will no longer come into sync using the previous patch software. Note that the motherboard firmware must NOT be regressed. This patch, (108145), can then be backed out normally. However, due to a bug in the patch database, the KU14 patch (105181-14) must be backed out twice - the initial attempt will fail with a 'patch not installed' error, the second attempt will succeed - the system can then be rebooted to regress the system back to patch 'C' (107369) level. Note: If the OSdog patch (107926) has been applied prior to applying this patch, (108145-10), the OSdog patch (107926) must be backed out (and re-applied following the backout of this patch). The backout steps are as follows:- . Backout the CPUset Firmware, (PROMs) . Backout the QFE Patch, (107778-04), if installed . Backout the OSdog Patch, (107926-04), if installed . Backout this Patch, (108145-10) . Backout the KU14 Patch, (105181-14) . Re-install the OSdog Patch, (107926-04), if required . Re-install the QFE Patch, (107778-04), if required . Reboot the system Patch Installation Procedure ---------------------------- In order to upgrade the system successfully you must already have installed: The base system from the Netra ft 1800 Installation CD (part no. 704-6491-11). The mandatory patches from the Netra ft 1800 Patch CD (part no.704-6823-12). These patches are: 107369-16 or -17 (Netra ft 1800 software patch) 106929-01 (SunOs 5.6 /usr/uadmin patch) and are also available from SunSolve. Caution - The mandatory patches listed above must be installed before you proceed with the upgrade. In addition you may have also installed: 108065-03 (Netra ft 1800 Bridge patch) 107926-04 (Netra ft 1800 OSdog patch) If you installed the Sun QFE/P patch 107778 as part of the existing installation, it will be necessary to back out the patch and then re-install it following the instructions in this document. Instructions for installing the base system and mandatory patches are contained in the Netra ft 1800 Software Release Notes (part no. 805-4527-13). Caution - You must follow precisely the installation instructions in this document. The installation procedure for the patches involves special instructions. Installing the patches incorrectly can leave your system unusable, requiring a complete re-installation of all software which can take up to four hours. Caution - Read all the instructions before attempting the installation procedure to ensure that you understand them and have everything required to hand. All operations must be performed at the OBP ok prompt or as root. Verifying the Prerequisites Before You Start If any of the following verifications fails, consult your Sun Enterprise Services Representative. General: The system should be free from faults (that is, no red LEDs showing) and running in sync. 1. To Verify Mandatory Patches. Type: # showrev -p | grep 107369 The output should include: Patch: 107369-17 Obsoletes: 106616-01 Requires: Incompatibles: Packages: SUNWcsu, SUNWftcar, SUNWcmscu, SUNWcmsr, SUNWcmsu, SUNWcmsdf, SUNWftm, SUNWftmuu, SUNWftutr, SUNWftutu, SUNWpnet, SUNWspltr, SUNWspltu or: Patch: 107369-16 Obsoletes: 106616-01 Requires: Incompatibles: Packages: SUNWftcar, SUNWcmscu, SUNWcmsr, SUNWcmsu, SUNWcmsdf, SUNWftm, SUNWftmuu, SUNWftutr, SUNWftutu, SUNWpnet, SUNWspltr, SUNWspltu Patch 107369 Verified: [ ] # showrev -p | grep 106929 The output should include: Patch: 106929-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch 106929 Verified: [ ] 2. To Verify FPGA Firmware Levels. For each motherboard type: # cd /usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin # ./cmsfruinfo -l x-MBD -i -s EE_MBD_BRIDGE_FWARE_PARTNO \ EE_MBD_BRIDGE_FWARE_DASH where x is A for motherboard A or B for motherboard B. For both motherboards the output should be: 2587134 07 or 2587134 08 Both sides should be at the same revision level, that is, both -07 or both -08. FPGA Version Verified: [ ] 3. To Verify PROM Firmware Levels. For each CPUset type: # cd /usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin # ./cmsfruinfo -l x-CPU -i -s EE_CPU_PROM_PARTNO \ EE_CPU_PROM_DASH where x is A for A-CPU or B for B-CPU. For both CPUsets the output should be: 2587354 07 (PROM Version 21) or 2587354 09 (PROM Version 23) Both sides should be at the same revision level, that is, both -07 or both -09. Check the PROM version by typing: # prtconf -V Record the version in the box. In the following example: OBP 3.7.23.0 1999/06/24 14:24 OBP 3.7.23.0 indicates version 23. PROM Version: [ ] This installation procedure, including the two required reboots, will take approximately ninety minutes. Note - There are special instructions for backing out this patch. Refer to the Patch Backout Strategy above. Caution - Do not reboot at any stage of the installation process unless specifically requested to do so in this document. In particular, rebooting after step 9 and before step 10 has completed will render the system unusable. 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 3, "Determining If In Sync". 4. Verify that all prerequisites have been met. Verify Prerequisites: [ ] 5. If step 4 is not satisfied then contact Sun Enterprise services to assist you in achieving the correct level of installation, then repeat step 4. Base Software and Patches installed: [ ] 6. If you installed the Sun QFE/P patch 107778 as part of Step 2 or in a previous installation, you must backout the patch before proceeding. Type: # cd /var/sadm/patch # ./107778-04/backoutpatch 107778-04 QFE Patch Backed Out: [ ] 7. Download patches 108181-01 and 108145-10 (or the latest versions) from the web site at SunSolve (http://sunsolve.sun.com). Copy them into the subdirectory /var/tmp. Patches Downloaded: [ ] 8. Extract the files: # cd /var/tmp # zcat 108181-01.tar.Z | tar -xvf - # zcat 108145-10.tar.Z | tar -xvf - Patch Files Extracted: [ ] 9. Install the Kernel Update Patch: # cd 108181-01 # ./installpatch . # cd /usr/platform/SUNW,Ultra-4FT/lib/105181-14 # ./installpatch . When prompted, type yes to confirm the installation. When installation of the patch is complete do not reboot. Kernel Update Patch Installed: [ ] 10. Install the Netra ft 1800 upgrade patch: # cd /var/tmp/108145-10 # ./installpatch . When prompted, type yes to confirm the installation. Note - The patch delivers an updated version of the Configuration Management System (CMS). To do this, the patch installation process terminates the CMS daemon. Do not attempt to use cmsconfig (or other CMS utility) until instructed to do so later in this installation procedure. Netra ft 1800 patch installed: [ ] 11. If you backed out the Sun QFE/P patch 107778 as part of Step 3, you can now reinstall the patch. If the patch still resides in the /var/tmp directory, type: # cd /var/sadm/tmp/107778-04 # ./installpatch . If the patch no longer resides in the /var/tmp directory, re-install the patch as described in the Netra ft 1800 Software Release Notes, part no. 805-4527-13. Reinstall QFE/P patch: [ ] 12. Programmable Hardware Upgrade Note - 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 writable device such as a disk before this procedure can be performed. In particular, if the system has just been fully installed from CD-ROM, it should be rebooted from disk before performing this procedure. Note - If the FPGAs were upgraded using version 08 of the upgrade utility during the base software patch installation, it is not necessary to repeat the procedure. If you are not sure of the firmware version, proceed to the next step (Step 13), otherwise you can proceed directly to Step 15. The following procedure upgrades both motherboard A and motherboard B. This procedure assumes that the CPUsets are already in sync. To determine if the CPUsets are in sync, use the procedure described in Note 3, "Determining If In Sync". System in sync: [ ] 13. Type: # cd /usr/platform/SUNW,Ultra-4FT/lib # ./fwupdate.fpga.258-7134-08 You will be prompted: WARNING: This firmware update can only be performed on: 1) The side which is executing this update utility. 2) The other side if its cpuset is powered off. 3) Either side if running in-sync. Please enter the side of the system that you want to update A or B? Type A to upgrade motherboard A,then type yes to confirm. When asked if you want to halt the system, answer no. The power cycle for the FPGA upgrades is performed later FPGA Upgraded on Motherboard A: [ ] 14. Type: # cd /usr/platform/SUNW,Ultra-4FT/lib # ./fwupdate.fpga.258-7134-08 You will be prompted: WARNING: This firmware update can only be performed on: 1) The side which is executing this update utility. 2) The other side if its cpuset is powered off. 3) Either side if running in-sync. Please enter the side of the system that you want to update A or B? Type B to upgrade motherboard B,then type yes to confirm. When asked if you want to halt the system, answer no. The power cycle for the FPGA upgrades is performed later FPGA Upgraded on Motherboard B: [ ] 15. Reboot the system, type: # init 6 System rebooted: [ ] 16. Wait for the machine to come up and into sync. System in sync: [ ] 17. To Upgrade the PROMs. Use cmsconfig to disable the CPUset in A-CPU (i.e. CPU 0). A-CPU Disabled: [ ] 18. Upgrade the PROM of the CPUset in B-CPU using the procedure described below in Note 2, "Upgrading PROM". NOTE: This is a MANDATORY patch, therefore when asked for confirmation, enter 'yes'. Failure to upgrade will leave the system with an unsupported configuration. B-CPU Prom Upgraded: [ ] 19. Use cmsconfig to enable the CPUset in A-CPU (if it has not already been enabled automatically by the CMS), and wait for the system to go into sync using the procedure described below in Note 3, "Determining If In Sync". A-CPU Enabled: [ ] System in sync: [ ] 20. After the CPUsets have gone into sync, use cmsconfig to disable the CPUset in B-CPU (i.e. CPU 1). B-CPU Disabled: [ ] 21. Upgrade the PROM of the CPUset in A-CPU using the procedure described below in Note 2, "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. A-CPU Prom Upgraded: [ ] 22. 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 3, "Determining If In Sync". B-CPU Enabled: [ ] System in sync: [ ] 23. Type the following command at the unix prompt: # eeprom auto-boot?=true 24. Shut down the system to run level 0, type: # init 0 System shutdown to PROM: [ ] 25. If you require the OSdog to be enabled, proceed with steps 26 and 27, if you require the OSdog to be disabled, proceed with step 28. 26. At the 'ok' prompt type: ok setenv auto-boot? false ok reset-all ok 4f set-conf-osdog ok setenv auto-boot? true OSdog enabled: [ ] 27. Proceed with step 29. 28. At the 'ok' prompt type: ok setenv auto-boot? false ok reset-all ok 0 set-conf-osdog ok setenv auto-boot? true OSdog disabled: [ ] 29. If you are at the unix prompt, type: # init 5 System shutdown: [ ] Otherwise, proceed with step 30. 30. Reset Motherboard/side B using one of the following methods. Via the Remote Control Processor (RCP), enter the command: BBoff wait 10 seconds then enter the command: BBon 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. System Power Reset Side B: [ ] 31. Reset Motherboard/side A using one of the following methods. Via the Remote Control Processor (RCP), enter the command: AAoff wait 10 seconds then enter the command: AAon 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. System Power Reset Side B: [ ] 32. Verifying the Upgrade You can use the following instructions to verify that the patch installation procedure has been correctly applied. If any of these verifications fail, you should review the related steps in the procedure or consult your local Sun Enterprise Services representative. To Verify the Patch Installation. Type: # showrev -p | grep 105181-14 The output should be: Patch: 105181-14 Obsoletes: 105214-01, 105636-01, 105776-01, 106031-02, 106308-01 Requires: Incompatibles: Packages: SUNWkvm, SUNWcsr, SUNWcar, SUNWhea Patch: 108145-10 Obsoletes: 108065-03, 107926-03, 107369-16 Requires: 105181-14 Incompatibles: Packages: SUNWcsu, SUNWftcar, SUNWftcau, SUNWcmscu, SUNWcmsr, SUNWcmsu, SUNWcmsdf, SUNWcrash, SUNWftm, SUNWftmur, SUNWftmuu, SUNWftutr, SUNWftutu, SUNWlogr, SUNWlogu, SUNWpnet, SUNWspltr, SUNWspltu, SUNWttymx Type: # showrev -p | grep 108145 The output should be: Patch: 108145-10 Obsoletes: 108065-03, 107926-03, 107369-16 Requires: 105181-14 Incompatibles: Packages: SUNWcsu, SUNWftcar, SUNWftcau, SUNWcmscu, SUNWcmsr, SUNWcmsu, SUNWcmsdf, SUNWcrash, SUNWftm, SUNWftmur, SUNWftmuu, SUNWftutr, SUNWftutu, SUNWlogr, SUNWlogu, SUNWpnet, SUNWspltr, SUNWspltu, SUNWtty Patch Installation Verified: [ ] 33. To Verify FPGA Firmware Levels. For each motherboard type: # cd /usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin # ./cmsfruinfo -l x-MBD -i -s EE_MBD_BRIDGE_FWARE_PARTNO \ EE_MBD_BRIDGE_FWARE_DASH where x is A for motherboard A or B for motherboard B. For both motherboards the output should be: 2587134 08 Both sides should be at the same revision level, that is, both -08. FPGA Upgrade Verified: [ ] 34. To Verify PROM Firmware Levels. For each CPUset type: # cd /usr/platform/SUNW,Ultra-4FT/SUNWcms/sbin # ./cmsfruinfo -l x-CPU -i -s EE_CPU_PROM_PARTNO EE_CPU_PROM_DASH where x is A for A-CPU or B for B-CPU. For both CPUsets the output should be: 2587354 10 Both sides should be at the same revision level, that is, both -10. 35. Type: # prtconf -V The output should be: OBP 3.7.24.0 1999/06/24 14:24 The 24 indicates that the PROM level is 24. PROM Upgrade Verified: [ ] Note 1 - 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 (where is the number of this patch, which can be found by looking at the top of this file): (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 # .//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 - # .//installpatch Where is the identifier of the patch (e.g. 108145-10) Note 2 - Upgrading PROM ----------------------- 1. The PROM update utility shipped with this patch is called: netra_ft_1800.flash.update-10 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-10 The update utility will verify the integrity of the binary delivered and will report the current version of the PROM running and the version available to upgraded to. 3. You will be asked if you wish to upgrade. Answer 'yes' to upgrade. 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. 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 Enterprise Services representative. 6. You will be asked "Do you wish to halt the system now". Answer "no". Note 3 - 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 amber LEDs marked 'Diag' will flash together. Alternatively use the following command to determine if running in-sync: /usr/platform/SUNW,Ultra-4FT/SUNWcms/lib/u4ftvmctl -c which will report "CPUsets running combined" if running in-sync. Patch Backout Procedure ----------------------- This procedure assumes that the CPUsets are already in sync. To determine if the CPUsets are in sync, use the procedure described in Note 3, "Determining If In Sync". Before the patch can be backed out, the cpuset prom firmware must first be regressed to the level appropriate to the previous patch. 1. The level of the previous patch can be ascertained using the following command:- # patchadd -p | grep 'atch: 107926' Patch 107926 Previously installed: (Y/N) [ ] 2. Use cmsconfig to disable the CPUset in A-CPU (i.e. CPU 0). A-CPU Disabled: [ ] 3. At the command line execute the upgrade utility, # cd /usr/platform/SUNW,Ultra-4FT/lib If the PROM version recorded in step 3 of the Patch Install Procedure was 23 then proceed with step 4. If the PROM version recorded in step 3 of the Patch Install Procedure was 21 then proceed with step 6. 4. Update to PROM Version 23. Type: # ./netra_ft_1800.flash.update-09 The update utility will verify the integrity of the binary delivered and will report the current version of the PROM running and the version available to regressed to. PROM Upgraded to version 23: [ ] 5. Proceed with step 7. 6. Update to PROM Version 21. Type: # ./netra_ft_1800.flash.update-07 The update utility will verify the integrity of the binary delivered and will report the current version of the PROM running and the version available to regressed to. PROM Upgraded to version 21: [ ] 7. You will be asked if you wish to upgrade. Answer 'yes' to upgrade. 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. 8. You will be asked if you wish to continue. Answer 'yes' to upgrade. Answering 'yes' will perform the upgrade, and indicate the success or failure of the upgrade, 9. If the update fails note any error messages and contact your Sun Enterprise Services representative. 10. You will be asked "Do you wish to halt the system now". Answer "no". 11. Use cmsconfig to enable the CPUset in A-CPU, and wait for the system to go into sync using the procedure described below in Note 3, "Determining If In Sync". A-CPU Enabled: [ ] 12. After the CPUsets have gone into sync, use cmsconfig to disable the CPUset in B-CPU (i.e. CPU 1). System in sync: [ ] B-CPU Disabled: [ ] 13. At the command line execute the upgrade utility, # cd /usr/platform/SUNW,Ultra-4FT/lib If the PROM version recorded in step 3 of the Patch Install Procedure was 23 then proceed with step 14. If the PROM version recorded in step 3 of the Patch Install Procedure was 21 then proceed with step 16. 14. Update to PROM Version 23. Type: # ./netra_ft_1800.flash.update-09 The update utility will verify the integrity of the binary delivered and will report the current version of the PROM running and the version available to regressed to. PROM Upgraded to version 23: [ ] 15. Proceed with step 17. 16. Update to PROM Version 21. Type: # ./netra_ft_1800.flash.update-07 The update utility will verify the integrity of the binary delivered and will report the current version of the PROM running and the version available to regressed to. PROM Upgraded to version 21: [ ] 17. You will be asked if you wish to upgrade. Answer 'yes' to upgrade. 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. 18. You will be asked if you wish to continue. Answer 'yes' to upgrade. Answering 'yes' will perform the upgrade, and indicate the success or failure of the upgrade, 19. If the update fails note any error messages and contact your Sun Enterprise Services representative. 20. You will be asked "Do you wish to halt the system now". Answer "no". 21. Use cmsconfig to enable the CPUset in B-CPU, and wait for the system to go into sync using the procedure described below in Note 3, "Determining If In Sync". B-CPU Enabled: [ ] System in sync: [ ] 22. If the QFE patch, (107778-04), was previously installed then backout the QFE patch using the following commands:- # cd /var/sadm/patch # ./107778-04/backoutpatch 107778-04 107778 Patch Backed Out: [ ] Otherwise proceed with step 23. 23. If the 107926 patch was previously installed as recorded in step 1, then backout the OSdog patch using the following commands:- # cd /var/sadm/patch # ./107926-04/backoutpatch 107926-04 107926 Patch Backed Out: [ ] Otherwise proceed with step 24. 24. Backout this patch, (108145-10), using the following commands:- # cd /var/sadm/patch # ./108145-10/backoutpatch 108145-10 108145 Patch Backed Out: [ ] 25. Backout the Kernel Update patch, (105181-14), using the following commands:- # cd /var/sadm/patch # ./105181-14/backoutpatch 105181-14 # ./105181-14/backoutpatch 105181-14 The patch must be backed out twice due to a bug in the patch database, the initial attempt will fail with a 'patch not installed' error, the second attempt will succeed. 105181 Patch Backed Out: [ ] 26. If the 107926 patch was previously installed as recorded in step 1, above then the OSdog patch must now be re-installed on the system using the following commands:- # cd /var/tmp/107926-04 # ./installpatch . 107926 Patch Reinstalled: [ ] Otherwise proceed with step 27. 27. If the QFE patch, (107778), was backed out in step 22, the QFE patch must now be reinstalled using the following commands:- # cd /var/tmp/107778-04 # ./installpatch . 107778 Patch Reinstalled: [ ] Otherwise proceed with step 28. 28. The system can now be rebooted and will be returned to the previous patch level:- # init 6 System rebooted: [ ] Failing to establish ICN network on split action ------------------------------------------------ If the system failed to establish icn network connection after a split action, do the following: 1. Using CMS (if necessary) enable the icn_system. 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 Behaviour of CMS CPU object --------------------------- The CMS state of a synchronising CPU has changed from previous releases. When the CMS is establishing a fault tolerant processing core by attempting to get a CPU into synchronisation with a live CPU, the CMS state of the integrating CPU will be "busy" for the entire duration of CPU integration, and will remain "busy" until integration has completed or failed. The CMS state of the relevant CPU will then go to "enabled" (success) or "enable_failed" (failure).