Yet another Solaris user

If you see something like this when you poweron you server: memory error detect 80000008, address 000002d0 data 55555555 -> fbefaaaa capture_data hi fbefaaaa lo deadbeef ecc 1b1b capture_attributes 01113001 address 000002d0 memory error detect 80000008, address 000002d4 data aaaaaaaa -> deadbeef capture_data hi fbefaaaa lo deadbeef ecc 1b1b capture_attributes 01113001 address 000002d4 memXSCF uboot  01070000  (Feb  8 2008 - 11:12:19) XSCF uboot  01070000  (Feb  8 2008 - 11:12:19) SCF board boot factor = 7180     DDR Real size: 256 MB     DDR: 224 MB Than your XSCF card is broked. Replace it with new one. After that it will ask you for enter chassis number - located at front of the server XSCF promt to enter your chasses number ( is a S/N of your server ): Please input the chassis serial number : XXXXXXX 1:PANEL Please select the number : 1 Restoring data from PANEL to XSCF#0. Please wait for se...

login as: eis-installer eis-installer@172.28.134.35's password:   XCP version of Panel EEPROM and XSCF FMEM mismatched,         Panel EEPROM=1072, XSCF FMEM=1102 XCP version of Panel EEPROM and XSCF FMEM mismatched,         Panel EEPROM=1072, XSCF FMEM=1102 XSCF> version -c xcp XSCF#0 (Active ) XCP0 (Current): 1102 XCP1 (Reserve): 1102   XSCF> getflashimage -u anonymous ftp://10.10.10.10/FFXCP1111.tar.gz Existing versions:         Version                Size  Date         FFXCP1102.tar.gz   44063324  Wed May 16 15:17:13 UTC 2012 Warning: About to delete existing versions. Continue? [y|n]: y Removing FFXCP1102.tar.gz. Password:   0MB received   1MB received   2MB received   3MB received   4MB received  .......

Sun Cluster 3.2 & SCSI Reservation Issues If you have worked with luns and Sun Cluster 3.2, you may have discovered that if you ever want to remove a lun from a system, it may not be possible because of the scsi3 reservation that Sun Cluster places on the disks.  The example scenario below walks you through how to overcome this issue and proceed as though Sun Cluster is not even installed. Example:  We had a 100GB lun off of a Hitachi disk array that we were using in a metaset that was controlled by Sun Cluster. We had removed the resource from the Sun Cluster configuration and removed the device with configadm/devfsadm, however when the storage admin attempted to remove the lun id from the Hitachi array zone, the Hitach array indicated the lun was still in use.  From the Solaris server side, it did not appear to be in use, however Sun Cluster has set the scsi3 reservations on the disk. Clearing the Sun Cluster scsi reservation steps: 1) Determ...

bash-3.2# cd /cdrom bash-3.2# cd sol_10_811_sparc/ bash-3.2# cd Solaris_10/Tools/ bash-3.2# cd /opt/ bash-3.2# mkdir solaris bash-3.2# cd /cdrom/sol_10_811_sparc/Solaris_10/Tools/ bash-3.2# ./setup_install_server /opt/solaris Verifying target directory... Calculating the required disk space for the Solaris_10 product Calculating space required for the installation boot image Copying the CD image to disk... Copying Install Boot Image hierarchy... Copying /boot netboot hierarchy... Install Server setup complete   bash-3.2# cd / bash-3.2# mkdir jumpstart bash-3.2# cp -r /opt/solaris/Solaris_10/Misc/jumpstart_sample /jumpstart bash-3.2# cp -R /jumpstart/jumpstart_sample/* /jumpstart/ bash-3.2# cd /jumpstart bash-3.2# rm -rf jumpstart_sample bash-3.2# vi /etc/dfs/dfstab share -F nfs -o ro,anon=0 /jumpstart   bash-3.2# shareall bash-3.2# cd /jumpstart/ bash-3.2# ./check Validating rules... Validating profile host_class... Validating profile zfsrootsimple... Validating profile ...