Error in StorEdge 3510 connected to V880 Server

Hi Friends
My V880 server's /var/adm/messages file is showing the below error
Sep 21 08:33:41 mum1pp1-a-fixed SUNW,UltraSPARC-III: [ID 332531 kern.info] [AFT2] errID 0x00000709.621043d0 PA=0x000000c0.f9d6a9c0
Sep 21 08:33:41 mum1pp1-a-fixed E$tag 0x00000181.f3400080 E$state_7 Exclusive
Sep 21 08:33:41 mum1pp1-a-fixed SUNW,UltraSPARC-III: [ID 819380 kern.info] [AFT2] E$Data (0x00) 0x40000000.00000000 0x09000000.00000000 ECC 0x1c9 Bad Esynd=0x0cc
Sep 21 08:33:41 mum1pp1-a-fixed SUNW,UltraSPARC-III: [ID 895151 kern.info] [AFT2] E$Data (0x10) 0x40000000.00000000 0x00000000.00000000 ECC 0x1c9
Sep 21 08:33:41 mum1pp1-a-fixed SUNW,UltraSPARC-III: [ID 895151 kern.info] [AFT2] E$Data (0x20) 0x40000000.00000000 0x00000000.00000000 ECC 0x1c9
Sep 21 08:33:41 mum1pp1-a-fixed SUNW,UltraSPARC-III: [ID 895151 kern.info] [AFT2] E$Data (0x30) 0x40000000.00000000 0x00000000.00000000 ECC 0x1c9
Sep 21 08:33:41 mum1pp1-a-fixed SUNW,UltraSPARC-III: [ID 929717 kern.info] [AFT2] D$ data not available
Sep 21 08:33:41 mum1pp1-a-fixed unix: [ID 836849 kern.notice]
Sep 21 08:33:41 mum1pp1-a-fixed ^Mpanic[cpu4]/thread=30010c5d440:
Sep 21 08:33:41 mum1pp1-a-fixed unix: [ID 144365 kern.notice] [AFT1] errID 0x00000709.621043d0 UE Error(s)
Sep 21 08:33:41 mum1pp1-a-fixed See previous message(s) for details
Sep 21 08:33:42 mum1pp1-a-fixed unix: [ID 100000 kern.notice]
Sep 21 08:33:42 mum1pp1-a-fixed genunix: [ID 723222 kern.notice] 000002a100eb1510 SUNW,UltraSPARC-III:cpu_aflt_log+55c (2a100eb15ce, 101578a8, 10157880, 0, 2a100eb1758, 2a100eb161b)
Sep 21 08:33:42 mum1pp1-a-fixed genunix: [ID 179002 kern.notice] %l0-3: 0000000010339b38 000002a100eb1818 0000000000000003 0000000000000010
Sep 21 08:33:42 mum1pp1-a-fixed %l4-7: 0000000000010009 0000030010c59580 0000000000000000 0000000000000003
Sep 21 08:33:42 mum1pp1-a-fixed genunix: [ID 723222 kern.notice] 000002a100eb1760 SUNW,UltraSPARC-III:cpu_deferred_error+4cc (400000000, 980c00000000, 1, 40100004232000cc, 2a100eb1ba0, 40100004232000cc)
Sep 21 08:33:42 mum1pp1-a-fixed genunix: [ID 179002 kern.notice] %l0-3: 0000000000000001 000002a100eb1818 0000000000000000 0000000000000001
Sep 21 08:33:42 mum1pp1-a-fixed %l4-7: 0000000010030208 000000c0f9d6a9c0 0000000000000000 0000000000000003
Sep 21 08:33:42 mum1pp1-a-fixed unix: [ID 100000 kern.notice]
Sep 21 08:33:42 mum1pp1-a-fixed genunix: [ID 672855 kern.notice] syncing file systems...
Sep 21 08:33:43 mum1pp1-a-fixed genunix: [ID 733762 kern.notice] 482
Sep 21 08:34:15 mum1pp1-a-fixed last message repeated 20 times
Sep 21 08:34:16 mum1pp1-a-fixed genunix: [ID 622722 kern.notice] done (not all i/o completed)
Sep 21 08:34:17 mum1pp1-a-fixed genunix: [ID 353387 kern.notice] dumping to /dev/dsk/c1t0d0s1, offset 65536
Sep 21 08:34:57 mum1pp1-a-fixed genunix: [ID 409368 kern.notice] ^M100% done: 104068 pages dumped, compression ratio 5.36,
Sep 21 08:34:57 mum1pp1-a-fixed genunix: [ID 851671 kern.notice] dump succeeded
Sep 21 08:35:51 mum1pp1-a-fixed genunix: [ID 540533 kern.notice] ^MSunOS Release 5.8 Version Generic_117350-26 64-bit
Sep 21 08:35:51 mum1pp1-a-fixed genunix: [ID 913632 kern.notice] Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Sep 21 08:35:51 mum1pp1-a-fixed genunix: [ID 678236 kern.info] Ethernet address = 0:3:ba:b:37:99
Sep 21 08:35:51 mum1pp1-a-fixed swapgeneric: [ID 370176 kern.warning] WARNING: forceload of drv/SUNW,qlc failed
Sep 21 08:35:51 mum1pp1-a-fixed unix: [ID 389951 kern.info] mem = 12582912K (0x300000000)
Sep 21 08:35:51 mum1pp1-a-fixed unix: [ID 930857 kern.info] avail mem = 12348809216
Sep 21 08:35:51 mum1pp1-a-fixed rootnex: [ID 466748 kern.info] root nexus = Sun Fire 880
Sep 21 08:35:51 mum1pp1-a-fixed rootnex: [ID 349649 kern.info] pcisch0 at root: SAFARI 0x8 0x700000
Sep 21 08:35:51 mum1pp1-a-fixed genunix: [ID 936769 kern.info] pcisch0 is /pci@8,700000
Sep 21 08:35:51 mum1pp1-a-fixed rootnex: [ID 349649 kern.info] pcisch1 at root: SAFARI 0x8 0x600000
Sep 21 08:35:51 mum1pp1-a-fixed genunix: [ID 936769 kern.info] pcisch1 is /pci@8,600000
Sep 21 08:35:51 mum1pp1-a-fixed rootnex: [ID 349649 kern.info] pcisch2 at root: SAFARI 0x9 0x700000
Sep 21 08:35:51 mum1pp1-a-fixed genunix: [ID 936769 kern.info] pcisch2 is /pci@9,700000
Sep 21 08:35:51 mum1pp1-a-fixed rootnex: [ID 349649 kern.info] pcisch3 at root: SAFARI 0x9 0x600000
Sep 21 08:35:51 mum1pp1-a-fixed genunix: [ID 936769 kern.info] pcisch3 is /pci@9,600000
Sep 21 08:35:51 mum1pp1-a-fixed qlc: [ID 171021 kern.info] Qlogic FCA Driver v20050209-1.40 (0)
Sep 21 08:35:51 mum1pp1-a-fixed qlc: [ID 637753 kern.info] NOTICE: qlc(0): Firmware version 2.1.140
Sep 21 08:35:52 mum1pp1-a-fixed qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop OFFLINE
Sep 21 08:35:52 mum1pp1-a-fixed pcisch: [ID 370704 kern.info] PCI-device: SUNW,qlc@2, qlc0
Sep 21 08:35:52 mum1pp1-a-fixed genunix: [ID 936769 kern.info] qlc0 is /pci@8,600000/SUNW,qlc@2
Sep 21 08:35:52 mum1pp1-a-fixed qlc: [ID 171021 kern.info] Qlogic FCA Driver v20050209-1.40 (1)
Sep 21 08:35:52 mum1pp1-a-fixed qlc: [ID 637753 kern.info] NOTICE: qlc(1): Firmware version 3.2.110
Sep 21 08:35:52 mum1pp1-a-fixed qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(1): Loop OFFLINE
Sep 21 08:35:52 mum1pp1-a-fixed pcisch: [ID 370704 kern.info] PCI-device: SUNW,qlc@3, qlc1
Sep 21 08:35:52 mum1pp1-a-fixed genunix: [ID 936769 kern.info] qlc1 is /pci@9,700000/SUNW,qlc@3
Sep 21 08:35:52 mum1pp1-a-fixed qlc: [ID 171021 kern.info] Qlogic FCA Driver v20050209-1.40 (2)
Sep 21 08:35:52 mum1pp1-a-fixed qlc: [ID 637753 kern.info] NOTICE: qlc(2): Firmware version 3.2.110
Sep 21 08:35:52 mum1pp1-a-fixed qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(2): Loop OFFLINE
Sep 21 08:35:52 mum1pp1-a-fixed pcisch: [ID 370704 kern.info] PCI-device: SUNW,qlc@4, qlc2
Sep 21 08:35:52 mum1pp1-a-fixed genunix: [ID 936769 kern.info] qlc2 is /pci@9,700000/SUNW,qlc@4
Sep 21 08:35:52 mum1pp1-a-fixed genunix: [ID 936769 kern.info] fp0 is /pci@8,600000/SUNW,qlc@2/fp@0,0
Sep 21 08:35:52 mum1pp1-a-fixed genunix: [ID 936769 kern.info] fp1 is /pci@9,700000/SUNW,qlc@3/fp@0,0
Sep 21 08:35:52 mum1pp1-a-fixed genunix: [ID 936769 kern.info] fp2 is /pci@9,700000/SUNW,qlc@4/fp@0,0
Sep 21 08:35:52 mum1pp1-a-fixed qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(1): Loop ONLINE
Sep 21 08:35:52 mum1pp1-a-fixed qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(2): Loop ONLINE
Sep 21 08:35:54 mum1pp1-a-fixed qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
Sep 21 08:35:54 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ssd13 at fp2: name w256000c0ffd05e18,2, bus address 9e
Sep 21 08:35:54 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ssd13 is /pci@9,700000/SUNW,qlc@4/fp@0,0/ssd@w256000c0ffd05e18,2
Sep 21 08:35:54 mum1pp1-a-fixed scsi: [ID 365881 kern.info] <SUN-StorEdge3510-327P cyl 53138 alt 2 hd 127 sec 127>
Sep 21 08:35:54 mum1pp1-a-fixed genunix: [ID 408114 kern.info] /pci@9,700000/SUNW,qlc@4/fp@0,0/ssd@w256000c0ffd05e18,2 (ssd13) online
Sep 21 08:35:54 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ssd12 at fp1: name w226000c0ffa05e18,2, bus address a5
Sep 21 08:35:54 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ssd12 is /pci@9,700000/SUNW,qlc@3/fp@0,0/ssd@w226000c0ffa05e18,2
Sep 21 08:35:54 mum1pp1-a-fixed scsi: [ID 365881 kern.info] <SUN-StorEdge3510-327P cyl 53138 alt 2 hd 127 sec 127>
Sep 21 08:35:54 mum1pp1-a-fixed genunix: [ID 408114 kern.info] /pci@9,700000/SUNW,qlc@3/fp@0,0/ssd@w226000c0ffa05e18,2 (ssd12) online
Sep 21 08:35:54 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ssd2 at fp0: name w21000004cf99cee6,0, bus address e0
Sep 21 08:35:54 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ssd2 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99cee6,0
Sep 21 08:35:54 mum1pp1-a-fixed scsi: [ID 365881 kern.info] <SUN36G cyl 24620 alt 2 hd 27 sec 107>
Sep 21 08:35:54 mum1pp1-a-fixed genunix: [ID 408114 kern.info] /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99cee6,0 (ssd2) online
Sep 21 08:35:54 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ssd5 at fp0: name w21000004cf99d007,0, bus address ef
Sep 21 08:35:54 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ssd5 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99d007,0
Sep 21 08:35:54 mum1pp1-a-fixed scsi: [ID 365881 kern.info] <SUN36G cyl 24620 alt 2 hd 27 sec 107>
Sep 21 08:35:55 mum1pp1-a-fixed genunix: [ID 408114 kern.info] /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99d007,0 (ssd5) online
Sep 21 08:35:55 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ssd3 at fp0: name w21000004cf99cf71,0, bus address e8
Sep 21 08:35:55 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ssd3 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99cf71,0
Sep 21 08:35:55 mum1pp1-a-fixed scsi: [ID 365881 kern.info] <SUN36G cyl 24620 alt 2 hd 27 sec 107>
Sep 21 08:35:55 mum1pp1-a-fixed genunix: [ID 408114 kern.info] /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99cf71,0 (ssd3) online
Sep 21 08:35:55 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ssd4 at fp0: name w21000004cf99cdf5,0, bus address e1
Sep 21 08:35:55 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ssd4 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99cdf5,0
Sep 21 08:35:55 mum1pp1-a-fixed scsi: [ID 365881 kern.info] <SUN36G cyl 24620 alt 2 hd 27 sec 107>
Sep 21 08:35:55 mum1pp1-a-fixed genunix: [ID 408114 kern.info] /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99cdf5,0 (ssd4) online
Sep 21 08:35:55 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ssd1 at fp0: name w21000004cf99d05a,0, bus address e4
Sep 21 08:35:55 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ssd1 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99d05a,0
Sep 21 08:35:55 mum1pp1-a-fixed scsi: [ID 365881 kern.info] <SUN36G cyl 24620 alt 2 hd 27 sec 107>
Sep 21 08:35:55 mum1pp1-a-fixed genunix: [ID 408114 kern.info] /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99d05a,0 (ssd1) online
Sep 21 08:35:55 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ssd0 at fp0: name w21000004cf99d140,0, bus address e2
Sep 21 08:35:55 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ssd0 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99d140,0
Sep 21 08:35:55 mum1pp1-a-fixed scsi: [ID 365881 kern.info] <SUN36G cyl 24620 alt 2 hd 27 sec 107>
Sep 21 08:35:55 mum1pp1-a-fixed genunix: [ID 408114 kern.info] /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf99d140,0 (ssd0) online
Sep 21 08:35:55 mum1pp1-a-fixed scsi: [ID 365881 kern.info] /pci@8,700000/scsi@1 (glm0):
Sep 21 08:35:55 mum1pp1-a-fixed Rev. 4 Symbios 53c875 found.
Sep 21 08:35:55 mum1pp1-a-fixed pcisch: [ID 370704 kern.info] PCI-device: scsi@1, glm0
Sep 21 08:35:55 mum1pp1-a-fixed genunix: [ID 936769 kern.info] glm0 is /pci@8,700000/scsi@1
Sep 21 08:35:56 mum1pp1-a-fixed scsi: [ID 243001 kern.info] /pci@9,700000/SUNW,qlc@4/fp@0,0 (fcp2):
Sep 21 08:35:56 mum1pp1-a-fixed ndi_devi_online: failed for scsiclass,0d: target=9e lun=0 ffffffff
Sep 21 08:35:56 mum1pp1-a-fixed scsi: [ID 243001 kern.info] /pci@9,700000/SUNW,qlc@4/fp@0,0 (fcp2):
Sep 21 08:35:56 mum1pp1-a-fixed ndi_devi_online: failed for scsiclass,0d: target=9f lun=0 ffffffff
Sep 21 08:35:56 mum1pp1-a-fixed scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@2/fp@0,0 (fcp0):
Sep 21 08:35:56 mum1pp1-a-fixed ndi_devi_online: failed for scsiclass,0d: target=dc lun=0 ffffffff
Sep 21 08:35:56 mum1pp1-a-fixed scsi: [ID 243001 kern.info] /pci@9,700000/SUNW,qlc@3/fp@0,0 (fcp1):
Sep 21 08:35:56 mum1pp1-a-fixed ndi_devi_online: failed for scsiclass,0d: target=a5 lun=0 ffffffff
Sep 21 08:35:56 mum1pp1-a-fixed scsi: [ID 243001 kern.info] /pci@9,700000/SUNW,qlc@3/fp@0,0 (fcp1):
Sep 21 08:35:56 mum1pp1-a-fixed ndi_devi_online: failed for scsiclass,0d: target=a3 lun=0 ffffffff
Sep 21 08:35:58 mum1pp1-a-fixed scsi: [ID 193665 kern.info] sd6 at glm0: target 6 lun 0
Sep 21 08:35:58 mum1pp1-a-fixed genunix: [ID 936769 kern.info] sd6 is /pci@8,700000/scsi@1/sd@6,0
Sep 21 08:36:01 mum1pp1-a-fixed swapgeneric: [ID 308332 kern.info] root on /pseudo/vxio@0:0 fstype ufs
Sep 21 08:36:01 mum1pp1-a-fixed genunix: [ID 370176 kern.warning] WARNING: forceload of drv/SUNW,qlc failed
Sep 21 08:36:01 mum1pp1-a-fixed genunix: [ID 370176 kern.warning] WARNING: forceload of drv/pci failed
Sep 21 08:36:01 mum1pp1-a-fixed pcisch: [ID 370704 kern.info] PCI-device: ebus@1, ebus0
Sep 21 08:36:09 mum1pp1-a-fixed ebus: [ID 521012 kern.info] todds12870 at ebus0: offset 1,300070
Sep 21 08:36:09 mum1pp1-a-fixed genunix: [ID 936769 kern.info] todds12870 is /pci@9,700000/ebus@1/rtc@1,300070
Sep 21 08:36:09 mum1pp1-a-fixed rootnex: [ID 349649 kern.info] mc-us30 at root: SAFARI 0x0 0x400000 ...
Sep 21 08:36:09 mum1pp1-a-fixed genunix: [ID 936769 kern.info] mc-us30 is /memory-controller@0,400000
Sep 21 08:36:09 mum1pp1-a-fixed rootnex: [ID 349649 kern.info] mc-us31 at root: SAFARI 0x1 0x400000 ...
Sep 21 08:36:09 mum1pp1-a-fixed genunix: [ID 936769 kern.info] mc-us31 is /memory-controller@1,400000
Sep 21 08:36:09 mum1pp1-a-fixed rootnex: [ID 349649 kern.info] mc-us32 at root: SAFARI 0x2 0x400000 ...
Sep 21 08:36:09 mum1pp1-a-fixed genunix: [ID 936769 kern.info] mc-us32 is /memory-controller@2,400000
Sep 21 08:36:09 mum1pp1-a-fixed rootnex: [ID 349649 kern.info] mc-us33 at root: SAFARI 0x3 0x400000 ...
Sep 21 08:36:09 mum1pp1-a-fixed genunix: [ID 936769 kern.info] mc-us33 is /memory-controller@3,400000
Sep 21 08:36:09 mum1pp1-a-fixed rootnex: [ID 349649 kern.info] mc-us34 at root: SAFARI 0x4 0x400000 ...
Sep 21 08:36:09 mum1pp1-a-fixed genunix: [ID 936769 kern.info] mc-us34 is /memory-controller@4,400000
Sep 21 08:36:09 mum1pp1-a-fixed rootnex: [ID 349649 kern.info] mc-us35 at root: SAFARI 0x6 0x400000 ...
Sep 21 08:36:09 mum1pp1-a-fixed genunix: [ID 936769 kern.info] mc-us35 is /memory-controller@6,400000
Sep 21 08:36:10 mum1pp1-a-fixed ebus: [ID 521012 kern.info] se0 at ebus0: offset 1,400000
Sep 21 08:36:10 mum1pp1-a-fixed genunix: [ID 936769 kern.info] se0 is /pci@9,700000/ebus@1/serial@1,400000
Sep 21 08:36:10 mum1pp1-a-fixed unix: [ID 270833 kern.info] cpu6: UltraSPARC-III (portid 6 impl 0x14 ver 0x34 clock 750 MHz)
Sep 21 08:36:10 mum1pp1-a-fixed unix: [ID 270833 kern.info] cpu0: UltraSPARC-III (portid 0 impl 0x14 ver 0x34 clock 750 MHz)
Sep 21 08:36:10 mum1pp1-a-fixed unix: [ID 721127 kern.info] cpu 0 initialization complete - online
Sep 21 08:36:10 mum1pp1-a-fixed unix: [ID 270833 kern.info] cpu1: UltraSPARC-III (portid 1 impl 0x14 ver 0x34 clock 750 MHz)
Sep 21 08:36:10 mum1pp1-a-fixed unix: [ID 721127 kern.info] cpu 1 initialization complete - online
Sep 21 08:36:10 mum1pp1-a-fixed unix: [ID 270833 kern.info] cpu2: UltraSPARC-III (portid 2 impl 0x14 ver 0x34 clock 750 MHz)
Sep 21 08:36:10 mum1pp1-a-fixed unix: [ID 721127 kern.info] cpu 2 initialization complete - online
Sep 21 08:36:10 mum1pp1-a-fixed unix: [ID 270833 kern.info] cpu3: UltraSPARC-III (portid 3 impl 0x14 ver 0x34 clock 750 MHz)
Sep 21 08:36:10 mum1pp1-a-fixed unix: [ID 721127 kern.info] cpu 3 initialization complete - online
Sep 21 08:36:10 mum1pp1-a-fixed unix: [ID 270833 kern.info] cpu4: UltraSPARC-III (portid 4 impl 0x14 ver 0x34 clock 750 MHz)
Sep 21 08:36:10 mum1pp1-a-fixed unix: [ID 721127 kern.info] cpu 4 initialization complete - online
Sep 21 08:36:11 mum1pp1-a-fixed ebus: [ID 521012 kern.info] su0 at ebus0: offset 1,3062f8
Sep 21 08:36:11 mum1pp1-a-fixed genunix: [ID 936769 kern.info] su0 is /pci@9,700000/ebus@1/rsc-control@1,3062f8
Sep 21 08:36:11 mum1pp1-a-fixed ebus: [ID 521012 kern.info] su1 at ebus0: offset 1,3083f8
Sep 21 08:36:11 mum1pp1-a-fixed genunix: [ID 936769 kern.info] su1 is /pci@9,700000/ebus@1/rsc-console@1,3083f8
Sep 21 08:36:13 mum1pp1-a-fixed pseudo: [ID 129642 kern.info] pseudo-device: fcp0
Sep 21 08:36:13 mum1pp1-a-fixed genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
Sep 21 08:36:17 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ses85 at fp2: name w256000c0ffd05e18,0, bus address 9e
Sep 21 08:36:17 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ses85 is /pci@9,700000/SUNW,qlc@4/fp@0,0/ses@w256000c0ffd05e18,0
Sep 21 08:36:17 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ses86 at fp2: name w256000c0ffc05e18,0, bus address 9f
Sep 21 08:36:17 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ses86 is /pci@9,700000/SUNW,qlc@4/fp@0,0/ses@w256000c0ffc05e18,0
Sep 21 08:36:17 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ses48 at fp0: name w5080020000195699,0, bus address dc
Sep 21 08:36:17 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ses48 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ses@w5080020000195699,0
Sep 21 08:36:17 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ses88 at fp1: name w226000c0ffa05e18,0, bus address a5
Sep 21 08:36:17 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ses88 is /pci@9,700000/SUNW,qlc@3/fp@0,0/ses@w226000c0ffa05e18,0
Sep 21 08:36:17 mum1pp1-a-fixed scsi: [ID 799468 kern.info] ses87 at fp1: name w226000c0ffb05e18,0, bus address a3
Sep 21 08:36:17 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ses87 is /pci@9,700000/SUNW,qlc@3/fp@0,0/ses@w226000c0ffb05e18,0
Sep 21 08:36:20 mum1pp1-a-fixed scsi: [ID 365881 kern.info] /pci@8,700000/scsi@1/st@5,0 (st5):
Sep 21 08:36:20 mum1pp1-a-fixed <HP DDS-4 DAT (Sun)>
Sep 21 08:36:20 mum1pp1-a-fixed scsi: [ID 193665 kern.info] st5 at glm0: target 5 lun 0
Sep 21 08:36:20 mum1pp1-a-fixed genunix: [ID 936769 kern.info] st5 is /pci@8,700000/scsi@1/st@5,0
Sep 21 08:36:20 mum1pp1-a-fixed pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Sep 21 08:36:20 mum1pp1-a-fixed genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Sep 21 08:36:21 mum1pp1-a-fixed vxdmp: [ID 220011 kern.notice] NOTICE: vxvm:vxdmp: added disk array 005E18, datype = SUN3510
Sep 21 08:36:22 mum1pp1-a-fixed eri: [ID 517527 kern.info] SUNW,eri0 : Local Ethernet address = 0:3:ba:b:37:99
Sep 21 08:36:22 mum1pp1-a-fixed eri: [ID 517527 kern.info] SUNW,eri0 : Using local MAC address
Sep 21 08:36:22 mum1pp1-a-fixed pcisch: [ID 370704 kern.info] PCI-device: network@1,1, eri0
Sep 21 08:36:22 mum1pp1-a-fixed genunix: [ID 936769 kern.info] eri0 is /pci@9,700000/network@1,1
Sep 21 08:36:22 mum1pp1-a-fixed hme: [ID 517527 kern.info] SUNW,hme0 : PCI IO 2.0 (Rev Id = c1) Found
Sep 21 08:36:22 mum1pp1-a-fixed hme: [ID 517527 kern.info] SUNW,hme0 : Local Ethernet address = 0:3:ba:1c:e4:c8
Sep 21 08:36:22 mum1pp1-a-fixed hme: [ID 517527 kern.info] SUNW,hme0 : Using local MAC address
Sep 21 08:36:22 mum1pp1-a-fixed pcisch: [ID 370704 kern.info] PCI-device: SUNW,hme@1,1, hme0
Sep 21 08:36:22 mum1pp1-a-fixed genunix: [ID 936769 kern.info] hme0 is /pci@9,600000/SUNW,hme@1,1
Sep 21 08:36:27 mum1pp1-a-fixed hme: [ID 517527 kern.info] SUNW,hme0 : Internal Transceiver Selected.
Sep 21 08:36:27 mum1pp1-a-fixed hme: [ID 517527 kern.info] SUNW,hme0 : 100 Mbps Full-Duplex Link Up
Sep 21 08:36:28 mum1pp1-a-fixed eri: [ID 517527 kern.info] SUNW,eri0 : 100 Mbps full duplex link up
Sep 21 08:39:04 mum1pp1-a-fixed pcisch: [ID 370704 kern.info] PCI-device: usb@1,3, ohci0
Sep 21 08:39:04 mum1pp1-a-fixed genunix: [ID 936769 kern.info] ohci0 is /pci@9,700000/usb@1,3
Sep 21 08:39:15 mum1pp1-a-fixed genunix: [ID 454863 kern.info] dump on /dev/dsk/c1t0d0s1 size 16000 MB
Sep 21 08:39:32 mum1pp1-a-fixed ipf: [ID 920137 kern.notice] IP Filter: attach to [eri0,0] - IPv4
Sep 21 08:39:32 mum1pp1-a-fixed ipf: [ID 920137 kern.notice] IP Filter: attach to [hme0,0] - IPv4
Sep 21 08:39:32 mum1pp1-a-fixed ipf: [ID 989912 kern.notice] IP Filter: v3.4.28, attaching complete.
Sep 21 08:39:38 mum1pp1-a-fixed savecore: [ID 570001 auth.error] reboot after panic: [AFT1] errID 0x00000709.621043d0 UE Error(s)
Sep 21 08:39:38 mum1pp1-a-fixed See previous message(s) for details
Sep 21 08:39:38 mum1pp1-a-fixed savecore: [ID 662545 auth.error] not enough space in /var/crash/mum1pp1-a-fixed (40 MB avail, 818 MB needed)
Sep 21 08:39:38 mum1pp1-a-fixed savecore: [ID 570001 auth.error] reboot after panic: [AFT1] errID 0x00000709.621043d0 UE Error(s)
Sep 21 08:39:38 mum1pp1-a-fixed See previous message(s) for details
Sep 21 08:39:38 mum1pp1-a-fixed savecore: [ID 662545 auth.error] not enough space in /var/crash/mum1pp1-a-fixed (40 MB avail, 818 MB needed)
Sep 21 08:39:41 mum1pp1-a-fixed pseudo: [ID 129642 kern.info] pseudo-device: tod0
Sep 21 08:39:41 mum1pp1-a-fixed genunix: [ID 936769 kern.info] tod0 is /pseudo/tod@0
Sep 21 08:39:41 mum1pp1-a-fixed pseudo: [ID 129642 kern.info] pseudo-device: pm0
Sep 21 08:39:41 mum1pp1-a-fixed genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
Sep 21 08:39:42 mum1pp1-a-fixed There are no devices (controllers) in the system; nvutil terminated.
Sep 21 08:39:43 mum1pp1-a-fixed Array Monitor initiated
Sep 21 08:39:43 mum1pp1-a-fixed /usr/lib/osa/bin/arraymon: [ID 712306 user.error] No RAID devices found to check.
Sep 21 08:39:43 mum1pp1-a-fixed /usr/lib/osa/bin/arraymon: [ID 712306 user.error] No RAID devices found to check.
Sep 21 08:39:43 mum1pp1-a-fixed RDAC daemons initiated
Sep 21 08:39:43 mum1pp1-a-fixed rdriver: [ID 400281 kern.notice] ID[RAIDarray.rdaemon.1001] RDAC Resolution Daemon locked in memory
Sep 21 08:39:44 mum1pp1-a-fixed pseudo: [ID 129642 kern.info] pseudo-device: vol0
Sep 21 08:39:44 mum1pp1-a-fixed genunix: [ID 936769 kern.info] vol0 is /pseudo/vol@0
Sep 21 08:39:44 mum1pp1-a-fixed pseudo: [ID 129642 kern.info] pseudo-device: fcode0
Sep 21 08:39:44 mum1pp1-a-fixed genunix: [ID 936769 kern.info] fcode0 is /pseudo/fcode@0
Sep 21 08:39:50 mum1pp1-a-fixed ntpdate[612]: [ID 558275 daemon.notice] adjust time server 61.1.128.45 offset -0.002149 sec
Sep 21 08:39:53 mum1pp1-a-fixed xntpd[982]: [ID 702911 daemon.notice] xntpd 3-5.93e Mon Sep 20 15:47:11 PDT 1999 (1)
Sep 21 08:39:53 mum1pp1-a-fixed xntpd[982]: [ID 301315 daemon.notice] tickadj = 5, tick = 10000, tvu_maxslew = 495, est. hz = 100
Sep 21 08:39:53 mum1pp1-a-fixed xntpd[982]: [ID 798731 daemon.notice] using kernel phase-lock loop 0041
Sep 21 08:39:54 mum1pp1-a-fixed last message repeated 1 time
Sep 21 08:45:35 mum1pp1-a-fixed pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Sep 21 08:45:35 mum1pp1-a-fixed genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
I suspect there was a problem with memory
Any help
Thanks in Advance
Jai

All the log entries that you seem to be concerned about
occurred as the system crashed then booted booted back up.
Your Solaris was trying to turn on all the devices.
"forceload" entries are usually result from having a line-entry
in your /etc/system file.
All they mean is that a driver was told to launch before it was
actually needed. They're harmless. Ignore such things.
The driver will engage when it's needed.
You had a cpu ecache error that your Solaris could not overcome.
Rather than leave the computer in an unstable state,
and rather than have the possibility of data corruption,
the computer did exactly what it's designed to do ...
crash the OS, attempt to save the corefiles, and clear out
whatever was causing that unstable and bad data in the ecache data registers.
The crash occurred at Sep 21 08:33:41
The reboot began at Sep 21 08:35:51
If this is the only recent crash, then ignore the event.
However, since /VAR was full, I fear you have many corefile sets already.
Another possibility was that the full filesystem gave you no swap space.
The only way to get an accurate analysis, is to open a Sun service case.
You may need to replace some hardware, or you may need to do
some extensive Solaris patching, or you may need to do both of those.
Get proper advice from Sun's techsupport.
This is just a generic user-to-user discussion forum.

Similar Messages

HT4436 When trying to sign in I keep getting the error message, "iCloud encounterd a error while trying to connect to the server". How can I get signed in?

When trying to sign in to iCloud, I always get the message, iCloud has encountered a error while trying to connect to the server. How do I get in????

Hello,
Try following step and check if issue gets resolved or not.
Find Acrobat.exe on your computer. Right click the program and click 'Troubleshoot Compatibility'. Set the compatibility to Windows XP service pack 3.
Regards,
Anoop

Apple Mail The server error encountered was: The connection to the server "

I have had my apple mail set up for some time now, through Gmail, and it has worked fine. I recently moved into a college dorm and now my apple mail gives me this error message
There may be a problem with the mail server or network. Check the settings for account "POP Account" or try again.
The server error encountered was: The connection to the server "pop.gmail.com" on port 995 timed out.
I've tried everything I could think to try, including taking the SSL off, restarting, quitting apple mail, redoing all the settings, and nothing seems to be helping me connect. I did the connectivity test and it says it's connected to the internet, it's just not getting the mail from my Gmail account. Thanks,
Aaron

What are the settings for both your Incoming and Outgoing servers, including port number, authentication method, and whether or not SSL is enabled for both?
Also, it's possible your college is blocking traffiic from Google, so you might try changing the DNS Servers by going to System Preferences > Network > Configure > TCP/IP and enter these two:
208.67.222.222
208.67.220.220
then click Apply Now, quit System Preferences and restart Mail and any other Internet applications you were running. Check to see if Mail still gives you problems.
Mulder

Trying to setup new iCloud in system preferences and get error message: "iCloud encountered an error while trying to connect to the server."

Here's the sequence of events:
Setting up a new iMac.
Migration Assistant was aborted during setup and a normal setup was completed.
Then ran Migration Assistant from the newly setup account.
It ran fine, but put all the data in a new account called "user".
Renamed "user" to a new name, renamed the home folder to a new name following these instructions: OS X: How to change your account name or home directory name
Delete the account we originally created, so just have one account with the name we want and all the data, email. Works fine.
Sign into the App Store with the account we share for purchases.
Now, the problem:
Go to System Preferences to setup iCloud with a new Apple ID
Get this error: "iCloud encountered an error while trying to connect to the server."
So I'm unable to setup iCloud for photo stream, FaceTime, etc.
Internet works fine, we can get mail, etc.
Rebooting doesn't help
Ideas?

never mind the problem is gone this morning.

On my Mac Mini, I keep getting this error message: "iCloud encountered an error while trying to connect to the server". I don't have any problems with iCloud on my laptop / PC. It works fine... Does anyone know what the problem could be?

On my Mac Mini, I keep getting this error message: "iCloud encountered an error while trying to connect to the server". I don't have any problems with iCloud on my laptop / PC. It works fine... Does anyone know what the problem could be?

Your Mac must be on Lion (10.7) to run iCloud. Apple had to change the operating system to fully support it. Nevertheless, it is possible to get emails from iCloud without having Lion. Please tell me if this interests you.
Anyways, here is the link to buy Lion (30 dollars, totally worth the upgrade ): http://itunes.apple.com/be/app/os-x-lion/id444303913?mt=12
Franklin

I keep getting an error that "iCloud encountered an error while trying to connect to the server". What's up?

I've been getting an error most of the day that says "iCloud encountered an error while trying to connect to the server" on my pc. Also, anything I update on either iPad or iPhone does not update on the other device. What's up?

Hello pongo19,
Thanks for using Apple Support Communities.
For more information on this, take a look at:
How to restart the Apple Mobile Device Service (AMDS) on Windows
http://support.apple.com/kb/ts1567
Close iTunes and disconnect the iPhone, iPad, or iPod touch.
Click the Windows Start button .
In the Start Search field type Services.
In the Programs section of the search results, Click "Services".
Select Apple Mobile Device and click Stop the service as shown below:
After the service has stopped, click Start the service.
After the Apple Mobile Device service has started again, open iTunes and connect the device.
Set the Apple Mobile Device Service Startup type to Automatic
Remove and reinstall iTunes and AMDS
Best of luck,
Mario

Database error #2002 can not connect local mysql server to socket through '/var/run/mysqld/mysqld.sock'(2) on mac os x 10.9.2

Dear Fellas:
I received "database error #2002 can not connect local mysql server to socket through '/var/run/mysqld/mysqld.sock'(2)" on mac os x 10.9.2.
mysql info:
ps -ef | grep mysql
    0    66     1   0 11:06AM ??         0:00.04 /bin/sh /usr/local/mysql/bin/mysqld_safe --user=mysql
   74   225    66   0 11:06AM ??         0:02.50 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysql/lib/plugin --user=mysql --log-error=/usr/local/mysql/data/Chuans-MacBook-Pro-2.local.err --pid-file=/usr/local/mysql/data/Chuans-MacBook-Pro-2.local.pid --socket=/var/run/mysqld/mysqld.sock
501   952   947   0 3:52PM ttys000    0:00.00 grep mysql
Please help!!

Fascinated and guessing:
Something related to sock(2) because that's not part of your copied info. I'm thinking you've doubled up on sockets and the second socket doesn't exist, meaning you should be connecting to the first socket "mysqld.sock" whether automatic or not.
I've only used GUI tools on purpose, so does this mean you've already got MySQL running and you tried to launch it again manually? Perhaps you already have one instance of a db and you're trying to launch a second instance, and the two can't coexist with a single user local db?
Assuming this is all local, I'd shut down the db service and restart it, out of hand. I've seen similar messages when I set the db to start up on boot, and it didn't finish shutting down when I tried to restart it manually. Usually the GUI won't let me turn it on because it reports it's already running, but in that case it hadn't finished performing what the GUI was reporting.
Just speculating.

Adobe Reader 9.1 - Fatal Error : Acrobat failed to connect a DDE server

Hi Everyone,
I have some users telling me that when they try to open a pdf attachment in Outlook 2007. Nothing happens. The system just sits there as if you did not click on the attachment. If you wait long enought a popup box from adobe reader comes up and says:
Fatal Error
Acrobat failed to connect a DDE server.
All the PDFs are very simple, just simple scanned images or converted over from a document into a PDF.
I've tried repairing the install and still had no luck - same behaviour. The only way the pdf opens is if we go into task manager and close the AcroRd32.exe process or logoff and log back in.
If it helps, the most recent system change was the upgrade to IE7 and a new anti-virus software.
Thanks,
KEvin

No solution I am afraid but same problem, running full version of AVG and problem hit immediately after Adobe Reader 9.1 upgrade. Pretty darn sure problem is in the upgrade but the relevant Restore Point was overwritten before I figured it out. Any advice welcome.

How to fix ipad error -1004 "could not connect to the server"

I am trying to access the tablet edition of Vanity Fair. I already have a subscription and when I click on the "Tap here for acces to the tablet edition" it takes me to a screen & this error message pops up:
Cannot Open Page
This page cannot be opended because of an error
This error is "Could not connect to the server."(-1004).
I have deleted, reinstalled via itunes on my mac, done a hard restart and nothing seems to be working. I can browse the web using safari and am connected to the internet via wifi.
Any suggestions?

I have the same issue, too. My New Yorker subscription is fine, always has been. But my Conde Nast Traveler subscription won't work. I can get to the screen where you enter your information (either with name and address or subscription number and zip code), but once I press Continue I get the error.
I emailed Conde Nast's customer service, and this is what they said:
Dear Subscriber:
Please accept our sincere apologies for the inconvenience you have
experienced.
We have applied a fix to the app for the server error and you will need
to close and re-open your app. To do so, please double click the "home"
button to close the running app and then re-open your app.
Please let us know if you still experience any problems.
If you should need further assistance, please be sure to include all
previous e-mail correspondence.
Thank you for your interest in Conde Nast Traveler.
Sincerely,
Shar
That didn't work. I tried the restarting the iPad, as someone here suggested, but that didn't work, either. Interesting that this seems to be a Conde Nast issue - my NY Times and National Geographic subscriptions are just fine, too.
I'm afraid I'm not sure what the guidance in this knowledge base article means: "Check security software. Ensure that communication to gs.apple.com is allowed. Follow this article for assistance with security software." How does one do that on one's iPad?
I actually wonder if it's a firewall issue. Are any of you attempting to enter this information at work, for example? I am, and my company has a firewall/proxy that gives me issues sometimes. I'm going to try to find a wifi hotspot at lunch to see if it'll work there.

HT204053 How to resolve "error while trying to connect to the server."

Receive "error while trying to connect to the server" on my PC when using iCloud. How to resolve?

check the below link.
/people/stephen.johannes/blog/2005/08/18/external-data-loads-for-crm-40-using-xif-adapter

Why am I getting this error trying to sign into icloud encountered an error while trying to connect to the server????

I am trying to sign into my mail and keep getting this error encountered an error while trying to connect to the server????

I'm having the same issue. Did you resolve it?

TS3988 I can't sign in to iCloud, message pops up stating that "iCloud encountered an error while trying to connect to the server". How do I sign in to iCloud now?

Was using iCloud just fine on Mac and iPad and suddenly can't access it from either devices.
When reviewing the settings on iPad a "verification failed, could not communicate with the server" message pops up.
When trying to access iCloud account on icloud.com a "iCloud encountered an error while trying to connect to the server" message pops up.
Meanwhile iCloud no longer works on both devices. (Apple ID works fine on Manage my Account)
I don't remember changing any iCloud settings but I was working on email account settings when this happened....Any ideas??

I have the same problem. This happens multiple times a day. I answer some questions and then unlock my account and then before long it all happens again. Extremely frustrating as I don't have a clue how to solve the problem.

Connection Error iCloud encountered an error while trying to connect to the server

Hi iCloud users
For the first time I have experienced errors while attempting to connect to iCloud via my PC. Never had any problems previously.
The first error I received was:
     "Connection Error - iCloud encountered an error while trying to connect to the server"
After a few attempts I was able to connect to iCloud. However I was unable to access my Calendar and Contacts. I received the following error messages:
     "Can't load Calendar - There was a problem loading the application"
     "Can't load Contacts - There was a problem loading the application"
Has anyone out there experienced this? If so could you offer an solutions/suggestions? Is iCloud not working properly today?
Many thanks & cheers,
Sue

Hi
I am sorry can't help you because I have same problem when login to icloude.com and try insert to Contacts!
Many times happen.
what is issues ?

ICloud encountered an error while trying to connect to the server

My iMac 27 inch ( Mid 2011) running OSX 10.9.4. Suddenly i have this problem "iCloud encountered an error while trying to connect to the server"
Please help what has happened and how to solve the problem.

You might want to just give it some time as there are a number of iCloud system issues effecting some users right now (see http://www.apple.com/support/systemstatus/).

Icloud encountered an error while trying to connect to the server' what does that mean?

icloud encountered an error while trying to connect to the server' what does that mean?
I am trying to get my contacts back by following a step by step guide online, but the falling at the first hurdle! trying to get into my icloud account on my pc?
Can anyone help?

never mind the problem is gone this morning.

Error in StorEdge 3510 connected to V880 Server

Similar Messages

Maybe you are looking for