From jrmartin at firstam.com Wed Sep 2 11:58:47 2009 From: jrmartin at firstam.com (Martin, Jeff R) Date: Wed, 2 Sep 2009 08:58:47 -0700 Subject: SUMMARY: how to check status of dd in solaris 10 Message-ID: <05A5BDD1FCAB084EA42C0513CF3ED79501641447@FAHQSNA01VXCH02.corp.firstam.com> Thanks to all the responses... the overall consensus was that Solaris dd cannot do this and to use gnu dd which can have a kill -USR1 sent to it to obtain some information regarding status. Jeff > Running a dd, need to see what the progress is, is this possible in > Solaris 10? > Cmd I ran: > > dd if=/dev/rdsk/c0t0d0s0 of=/dev/rdsk/c0t1d0s0 > Solaris 10 10/08 Jeff Martin First American Title 421 North Main Street Santa Ana, CA 92701 (714) 371-7093 Cell (714) 250-1219 Office ***************************************************************************** ************* This message may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is legally privileged. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message and any copies immediately thereafter. Thank you. ***************************************************************************** ************* FACLD _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From cbarnar1 at earthlink.net Wed Sep 2 22:17:39 2009 From: cbarnar1 at earthlink.net (Christopher Barnard) Date: Wed, 2 Sep 2009 21:17:39 -0500 Subject: SUMMARY: how to force output? In-Reply-To: <9495CA27-A4CB-4EBB-86DE-8F008AFFB6BE@earthlink.net> References: <9495CA27-A4CB-4EBB-86DE-8F008AFFB6BE@earthlink.net> Message-ID: I asked > This is Solaris 10, with the sun-shipped perl (5.8.4) > > I have a perl script and an expect script, both are fairly verbose > about saying what they do. Each runs just fine independently. > > However, when the perl script calls the expect script, the expect > script no longer sends output to the screen. It does what it is > supposed to, but I no longer get the output to the screen showing > status. Does this sound like a Solaris issue or a perl/expect issue? The answer I finally had a chance to go back to this problem this morning and yup, its a perl issue. The `foo`; vs system("foo"); discrepancy. Most people correctly said it sounded like a perl issue and it was. Christopher L. Barnard cbarnar1 at earthlink.net ------------------------------------------------------------------- Comment your code as if the person who will be maintaining it is a homicidal maniac who knows where you live. _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From birgit.ducarroz at unifr.ch Thu Sep 3 09:18:55 2009 From: birgit.ducarroz at unifr.ch (DUCARROZ Birgit) Date: Thu, 3 Sep 2009 15:18:55 +0200 Subject: SUMMARY: X4500 no cd redirection? In-Reply-To: <4A9FB2F4.3030706@unifr.ch> References: <4A9FB2F4.3030706@unifr.ch> Message-ID: <4A9FC23F.4060403@unifr.ch> Thanks to Casper Dik. It seems that my local machine (running Ubuntu Hardy Heron) does not like the java from X4500 (error is generated by the java which is downloaded from the BIOS; it is possible that the java code doesn't like Ubuntu (i.e., it's a problem on the webbrowser's side) Curiousely, on a newer Sun (X6250) it works... I know that the following is not the solution of my problem, but I opened the cd redirection from another machine running solaris and this works. Greetings, Birgit I wrote: > Hi all, > > on a Sun Fire X4500 I try to get Cd redirection. But the message > displaying is "CD-ROM redirection is not supported on this platform" > > Since there is no CD reader in this machine and the machine doc says it > is possible to redirect I am curious why this does not work. > > Yet checked the BIOS, seems that all is ok. > > Please help me, I must install a new OS quickly. > > Greetings, > Birgit _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From tkevans at tkevans.com Fri Sep 4 10:43:30 2009 From: tkevans at tkevans.com (Tim Evans) Date: Fri, 04 Sep 2009 10:43:30 -0400 Subject: SUMMARY: Dead Blade-1500 Message-ID: <4AA12792.3000006@tkevans.com> I wrote: >My Blade-1500 (red) crashed this morning. I was able to reboot it, and >got to a text login prompt, but it crashed again (while starting X) >before >I could log in and look around. > >Now it will not even boot at all, even from CD-ROM. When it's powered on, >the power light comes on; in about 10-15 seconds, it beeps once, then >apparently re-sets; the power light blinks four times (no keyboard >led's), >then comes on steady; after another 10-15 seconds, it repeats. Nothing >ever appears on the monitor. > >Anyone have ideas where to look? Is this something for a Sun tech to >diagnose? And, is it worth fixing? (I don't have hardware support, so >it'd be T&M.) Thanks to: msamy61 at yahoo.com Matthew.Stier at us.fujitsu.com stoffj at taec.toshiba.com i75.bjc at gmail.com Suggestions included removing the disk drives and all adaptor cards, and, of course, connecting a serial terminal. Did the former, with the very same results. Cannot even get to the OBP. Don't have access to a terminal, but since the system apparently re-sets within 10 seconds of being powered up, not sure what I might see if I did. I'm assuming it's going to cost a couple of yards to get a Sun tech on site, plus parts. Looking a used 1500's on eBay suggests these are not worth much more than this. So, looks like new computer time. thanks. _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From sunhux at gmail.com Thu Sep 3 06:12:27 2009 From: sunhux at gmail.com (sunhux G) Date: Thu, 3 Sep 2009 18:12:27 +0800 Subject: SUMMARY: how to force output? In-Reply-To: References: <9495CA27-A4CB-4EBB-86DE-8F008AFFB6BE@earthlink.net> Message-ID: <60f08e700909030312g6c6715a6r8a7ea2a1a6176bf9@mail.gmail.com> Hi Sorry didn't summarize earlier as not certain what's the cause earlier. Since Tomek & me are applying different firmwares (139436-03 & 127580-05 respectively), I guess Tomek probably has spotted that the power cycling and reflashing resolved this problem of "prtdiag -v" gave "segmentation fault" Rgds U =========================================================== Hi, I've manage to fix this. Ive flashed the firmware once again and it worked :) after Flashing Ive powered down the machine totally, even plugged off the power cords. It helped for me. Regards Tomek Tomasz Ostrowski ------------------------------ *From:* ext sunhux G [mailto:sunhux at gmail.com] *Sent:* Thursday, September 03, 2009 11:37 AM *To:* Ostrowski, Tomasz (NSN - CN/Shanghai) *Subject:* Re: "prtdiag -v" segmentation fault after firmware patch 127580-05 Sorry for the late reply. My "segmentation fault" is gone after my colleague applied the latest full Solaris 10 patches, power cycled & it just went away. Regds U On Wed, Sep 2, 2009 at 2:56 AM, Ostrowski, Tomasz (NSN - CN/Shanghai) < tomasz.ostrowski at nsn.com> wrote: Hello, Did you manage to solve your issue? *http://www.sunmanagers.org/pipermail/sunmanagers/2008-April/045587.html* I have T2000 and I have just upgradet the firmware: 139436-03 And now I have this root at comm1> prtdiag -v System Configuration: Sun Microsystems sun4v Netra T2000 Memory size: 16256 Megabytes ================================ Virtual CPUs ================================ CPU ID Frequency Implementation Status ------ --------- ---------------------- ------- ======================= Physical Memory Configuration ======================== Segment Table: -------------------------------------------------------------- Base Segment Interleave Bank Contains Address Size Factor Size Modules -------------------------------------------------------------- 0x0 16 GB 4 2 GB MB/CMP0/CH0/R0/D0 MB/CMP0/CH0/R0/D1 2 GB MB/CMP0/CH0/R1/D0 MB/CMP0/CH0/R1/D1 2 GB MB/CMP0/CH1/R0/D0 MB/CMP0/CH1/R0/D1 2 GB MB/CMP0/CH1/R1/D0 MB/CMP0/CH1/R1/D1 2 GB MB/CMP0/CH2/R0/D0 MB/CMP0/CH2/R0/D1 2 GB MB/CMP0/CH2/R1/D0 MB/CMP0/CH2/R1/D1 2 GB MB/CMP0/CH3/R0/D0 MB/CMP0/CH3/R0/D1 2 GB MB/CMP0/CH3/R1/D0 MB/CMP0/CH3/R1/D1 ========================= IO Configuration ========================= IO Location Type Slot Path Name Model ----------- ----- ---- --------------------------------------------- ------------------------- --------- IOBD/NET0 PCIE IOBD /pci at 780/pci at 0/pci at 1/network at 0 network-pciex8086,105e IOBD/NET1 PCIE IOBD /pci at 780/pci at 0/pci at 1/network at 0,1 network-pciex8086,105e IOBD/PCIE PCIE IOBD /pci at 780/pci at 0/pci at 9/scsi at 0 scsi-pciex1000,56 IOBD/PCIX PCIX IOBD /pci at 7c0/pci at 0/pci at 1/pci at 0/isa at 2 isa IOBD/PCIX PCIX IOBD /pci at 7c0/pci at 0/pci at 1/pci at 0/usb at 5 usb-pciclass,0c0310 IOBD/PCIX PCIX IOBD /pci at 7c0/pci at 0/pci at 1/pci at 0/usb at 6 usb-pciclass,0c0310 IOBD/NET2 PCIE IOBD /pci at 7c0/pci at 0/pci at 2/network at 0 network-pciex8086,105e IOBD/NET3 PCIE IOBD /pci at 7c0/pci at 0/pci at 2/network at 0,1 network-pciex8086,105e ========================= HW Revisions ======================================= System PROM revisions: ---------------------- OBP 4.30.3 2009/06/08 13:29 IO ASIC revisions: ------------------ Location Path Device Revision -------------------- --------------------------------------------- ------------------------------ --------- Segmentation Fault (core dumped) But without -v is ok root at comm1> prtdiag System Configuration: Sun Microsystems sun4v Netra T2000 Memory size: 16256 Megabytes ================================ Virtual CPUs ================================ CPU ID Frequency Implementation Status ------ --------- ---------------------- ------- ======================= Physical Memory Configuration ======================== Segment Table: -------------------------------------------------------------- Base Segment Interleave Bank Contains Address Size Factor Size Modules -------------------------------------------------------------- 0x0 16 GB 4 2 GB MB/CMP0/CH0/R0/D0 MB/CMP0/CH0/R0/D1 2 GB MB/CMP0/CH0/R1/D0 MB/CMP0/CH0/R1/D1 2 GB MB/CMP0/CH1/R0/D0 MB/CMP0/CH1/R0/D1 2 GB MB/CMP0/CH1/R1/D0 MB/CMP0/CH1/R1/D1 2 GB MB/CMP0/CH2/R0/D0 MB/CMP0/CH2/R0/D1 2 GB MB/CMP0/CH2/R1/D0 MB/CMP0/CH2/R1/D1 2 GB MB/CMP0/CH3/R0/D0 MB/CMP0/CH3/R0/D1 2 GB MB/CMP0/CH3/R1/D0 MB/CMP0/CH3/R1/D1 ========================= IO Configuration ========================= IO Location Type Slot Path Name Model ----------- ----- ---- --------------------------------------------- ------------------------- --------- IOBD/NET0 PCIE IOBD /pci at 780/pci at 0/pci at 1/network at 0 network-pciex8086,105e IOBD/NET1 PCIE IOBD /pci at 780/pci at 0/pci at 1/network at 0,1 network-pciex8086,105e IOBD/PCIE PCIE IOBD /pci at 780/pci at 0/pci at 9/scsi at 0 scsi-pciex1000,56 IOBD/PCIX PCIX IOBD /pci at 7c0/pci at 0/pci at 1/pci at 0/isa at 2 isa IOBD/PCIX PCIX IOBD /pci at 7c0/pci at 0/pci at 1/pci at 0/usb at 5 usb-pciclass,0c0310 IOBD/PCIX PCIX IOBD /pci at 7c0/pci at 0/pci at 1/pci at 0/usb at 6 usb-pciclass,0c0310 IOBD/NET2 PCIE IOBD /pci at 7c0/pci at 0/pci at 2/network at 0 network-pciex8086,105e IOBD/NET3 PCIE IOBD /pci at 7c0/pci at 0/pci at 2/network at 0,1 network-pciex8086,105e ============================ Environmental Status ============================ Fan sensors: All fan sensors are OK. Temperature sensors: All temperature sensors are OK. Current sensors: All current sensors are OK. Current indicators: All current indicators are OK. Voltage sensors: All voltage sensors are OK. ============================ FRU Status ============================ All FRUs are enabled. Any help is more that welcome :) Best Regards Tomek ===================================================================== Apr 2008 Hi Sunmanagers, I've just applied patch 127580-05 on our T5120 running Solaris 10. Rebooted the system & this time, "prtdiag -v" would give segmentation fault half through the output. U _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From birgit.ducarroz at unifr.ch Fri Sep 4 16:34:02 2009 From: birgit.ducarroz at unifr.ch (DUCARROZ Birgit) Date: Fri, 4 Sep 2009 22:34:02 +0200 Subject: SUMMARY: patched solaris 10 u7 and no internet again - also pkgadd error In-Reply-To: <4AA171F1.7080307@unifr.ch> References: <4AA171F1.7080307@unifr.ch> Message-ID: <4AA179BA.4020101@unifr.ch> A big big thanks to Anthony D'Atri for his quick response! This worked: pkgadd -d /var/sadm/spool/141415-10 I needed to confirm every package manually, but the kernel patch is now installed. Also I re-checked my /etc/defaultrouter and entered an IP Addr. Don't know why this has been deleted... svcadm -v restart network/physical Now all is ok. Greetings, Birgit I wrote: > Hi all, > > I just installed a new Solaris 10u7. I installed all patches but no > kernel patch (with the GUI). > > Since this update there seems to be something working like a firewall. > When I try to ping, I see there is some network activity, on the Solaris > 10, but no packet transmitting, no packet receiving. > > # uname -a > SunOS hostname.domain.ch 5.10 Generic_139556-08 i86pc i386 i86pc > > nsswitch.conf is configured with > hosts: files dns > > > resolv.conf is configured with > domain domain.ch > nameserver xxx.xx.xxx.xxx > nameserver xxx.xx.xxx.xxx > > All Internet activity and ssh connection worked before the installation > of the patches. > > I tryed also to add the kernel patch using single user mode, but I get a > strange error: > > # pwd > /var/sadm/spool > # pkgadd 141415-10 > pkgadd: ERROR: no packages were found in > > (this appears also when I cp the patch into /var/spool/pkg) > > > > # pwd > /var/sadm/spool > # pkgadd -d /var/sadm/spool 141415-10 > pkgadd: ERROR: no packages were found in > #ls -la > drwxr-xr-x 20 root root 24 Sep 4 17:37 141415-10 > > btw this happens with every patch, so no question that the checksum of > the patch would be wrong. I installed this patch on another machine, > where it has been installed without any difficulties. > > > Please help, I googled around and don't find any answer. > Regards, > Birgit > _______________________________________________ > sunmanagers mailing list > sunmanagers at sunmanagers.org > http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From mymaillists at gmx.at Fri Sep 4 17:25:56 2009 From: mymaillists at gmx.at (Markus Mayer) Date: Fri, 4 Sep 2009 23:25:56 +0200 Subject: SUMMARY: nfs 4 mount returns error on solaris client, is ok on linux client In-Reply-To: <200909041704.05744.mymaillists@gmx.at> References: <200909041704.05744.mymaillists@gmx.at> Message-ID: <200909042325.56481.mymaillists@gmx.at> Thanks for the responses. Nick hindly was the fastest, pointing me to http://blogs.sun.com/macrbg/entry/solaris_nfsv4_client_mount_from as did Paul Kraus. This is the solution I will be using. On Friday 04 September 2009, 17:04 Markus Mayer wrote: > Hi Managers, > > I have an annoying problem that I am unable to solve at the moment. I am > trying to mount an nfs share from a linux server on a solaris 10 update 3 > client. This is failing, although when I mount the share on another linux > client, it works. Both systems are speaking nfs4. I have used wireshark > to see what is being requested and being sent back and seen that the > directory is correctly requested from the solaris client /home/sdd, however > the linux nfs server responds with a NFS4ERR_NOENT meaning no such > directory. I have checked that there are no symbolic links in the path to > the share on the nfs server, as apparently this can make problems under > nfs4. I have checked everything that I can think of, and now I don't know > where else to look. I would be grateful if anyone could help me here. > > Thanks > Markus > > nserv # rpcinfo -p > program vers proto port > 100000 4 tcp 111 portmapper > 100000 3 tcp 111 portmapper > 100000 2 tcp 111 portmapper > 100000 4 udp 111 portmapper > 100000 3 udp 111 portmapper > 100000 2 udp 111 portmapper > 100024 1 udp 60076 status > 100024 1 tcp 60327 status > 100005 1 udp 60228 mountd > 100005 1 tcp 59479 mountd > 100005 2 udp 60228 mountd > 100005 2 tcp 59479 mountd > 100005 3 udp 60228 mountd > 100005 3 tcp 59479 mountd > 100003 2 udp 2049 nfs > 100003 3 udp 2049 nfs > 100003 4 udp 2049 nfs > 100021 1 udp 60263 nlockmgr > 100021 3 udp 60263 nlockmgr > 100021 4 udp 60263 nlockmgr > 100021 1 tcp 55332 nlockmgr > 100021 3 tcp 55332 nlockmgr > 100021 4 tcp 55332 nlockmgr > 100003 2 tcp 2049 nfs > 100003 3 tcp 2049 nfs > 100003 4 tcp 2049 nfs > nserv # > > > nserv tsm # cat /etc/exports > # /etc/exports: NFS file systems being exported. See exports(5). > /home/sdd 192.168.1.117(rw,no_root_squash,async,no_subtree_check) > /home/sdd 192.168.1.64(rw,no_root_squash,async,no_subtree_check) > > > nserv # showmount -e > Export list for nserv: > /home/sdd <192.168.1.64>,<192.168.1.117> > > nserv # ps -ef | grep nfs > root 761 2 0 11:27 ? 00:00:00 [nfsiod] > root 4501 2 0 16:49 ? 00:00:00 [nfsd4] > root 4502 2 0 16:49 ? 00:00:00 [nfsd] > root 4503 2 0 16:49 ? 00:00:00 [nfsd] > root 4504 2 0 16:49 ? 00:00:00 [nfsd] > root 5582 32026 0 17:00 pts/22 00:00:00 grep --colour=auto nfs > > nserv # ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:0e:0c:c1:53:16 > inet addr:192.168.1.89 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::20e:cff:fec1:5316/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:782033650 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1567453259 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:59149876485 (55.0 GiB) TX bytes:2239031736231 (2.0 TiB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:156250 errors:0 dropped:0 overruns:0 frame:0 > TX packets:156250 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:219016865 (208.8 MiB) TX bytes:219016865 (208.8 MiB) > > nserv # uname -a > Linux nserv 2.6.30-gentoo-r4 #1 SMP Mon Jul 27 14:31:34 CEST 2009 x86_64 > Intel(R) Core(TM)2 Extreme CPU X9650 @ 3.00GHz GenuineIntel GNU/Linux > _______________________________________________ > sunmanagers mailing list > sunmanagers at sunmanagers.org > http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From leonardo.cassese at googlemail.com Mon Sep 7 05:18:53 2009 From: leonardo.cassese at googlemail.com (Leonardo Cassese) Date: Mon, 7 Sep 2009 11:18:53 +0200 Subject: SUMMARY: dman/scman issue on Sf 15k Message-ID: Well, I had a problem with I1 network on a Sf15k. Thanks to all the advices I received. We contacted Sun and it turned out to be a problem on the reo chip installed on the I/O board. They changed the board and everything went ok. Here is what the messages file contained before I/O board was changed: dman: [ID 162183 kern.warning] WARNING: man_dossc_switch: mboxsc_putmsg failed, errno = 145 Aug 31 01:45:48 Remed dman: [ID 788692 kern.notice] NOTICE: dman0 Link down Aug 31 01:46:26 Remed dman: [ID 643036 kern.notice] NOTICE: dman0 Link up Aug 31 05:30:18 Remed dman: [ID 162183 kern.warning] WARNING: man_dossc_switch: mboxsc_putmsg failed, errno = 145 _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From birgit.ducarroz at unifr.ch Tue Sep 8 05:41:30 2009 From: birgit.ducarroz at unifr.ch (DUCARROZ Birgit) Date: Tue, 8 Sep 2009 11:41:30 +0200 Subject: SUMMARY: patched solaris 10 u7 and no internet again - also pkgadd error In-Reply-To: <4AA179BA.4020101@unifr.ch> References: <4AA171F1.7080307@unifr.ch> <4AA179BA.4020101@unifr.ch> Message-ID: <4AA626CA.4070304@unifr.ch> Thanks again to Bill, Crist Clark, Richard Wright, Hendrik Visage, Jeff Woolsey, for their additional remarks: route -p show Patches are installed with patchadd I wrote: > A big big thanks to Anthony D'Atri for his quick response! > > This worked: > > pkgadd -d /var/sadm/spool/141415-10 > > I needed to confirm every package manually, but the kernel patch is now installed. > > Also I re-checked my > > /etc/defaultrouter > > and entered an IP Addr. Don't know why this has been deleted... > > svcadm -v restart network/physical > > > Now all is ok. > > Greetings, > Birgit > > > > I wrote: >> Hi all, >> >> I just installed a new Solaris 10u7. I installed all patches but no >> kernel patch (with the GUI). >> >> Since this update there seems to be something working like a firewall. >> When I try to ping, I see there is some network activity, on the Solaris >> 10, but no packet transmitting, no packet receiving. >> >> # uname -a >> SunOS hostname.domain.ch 5.10 Generic_139556-08 i86pc i386 i86pc >> >> nsswitch.conf is configured with >> hosts: files dns >> >> >> resolv.conf is configured with >> domain domain.ch >> nameserver xxx.xx.xxx.xxx >> nameserver xxx.xx.xxx.xxx >> >> All Internet activity and ssh connection worked before the installation >> of the patches. >> >> I tryed also to add the kernel patch using single user mode, but I get a >> strange error: >> >> # pwd >> /var/sadm/spool >> # pkgadd 141415-10 >> pkgadd: ERROR: no packages were found in >> >> (this appears also when I cp the patch into /var/spool/pkg) >> >> >> >> # pwd >> /var/sadm/spool >> # pkgadd -d /var/sadm/spool 141415-10 >> pkgadd: ERROR: no packages were found in >> #ls -la >> drwxr-xr-x 20 root root 24 Sep 4 17:37 141415-10 >> >> btw this happens with every patch, so no question that the checksum of >> the patch would be wrong. I installed this patch on another machine, >> where it has been installed without any difficulties. >> >> >> Please help, I googled around and don't find any answer. >> Regards, >> Birgit >> _______________________________________________ >> sunmanagers mailing list >> sunmanagers at sunmanagers.org >> http://www.sunmanagers.org/mailman/listinfo/sunmanagers > _______________________________________________ > sunmanagers mailing list > sunmanagers at sunmanagers.org > http://www.sunmanagers.org/mailman/listinfo/sunmanagers -- **************************************************** Birgit Ducarroz Unix Systems Administration Department of Informatics (DIUF) University of Fribourg Switzerland Phone +41 (0)26 300 8342 mailto: birgit.ducarroz at unifr.ch http://diuf.unifr.ch **************************************************** Computer Security: "Mein PC ist fu"r Hacker ohnehin vo"llig uninteressant" - wirklich? http://diuf.unifr.ch/people/ducarroz/?Computer_Security ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From dave.markham at fjserv.net Thu Sep 10 09:12:52 2009 From: dave.markham at fjserv.net (Dave Markham) Date: Thu, 10 Sep 2009 14:12:52 +0100 Subject: SUMMARY: fmadm faulty -a showing no output Message-ID: <4AA8FB54.1050701@fjserv.net> Thanks to all who responded. Stuart Saxon, Tim Bradshaw, Peter van Gemert, Dale Whittemore. It seems i've just mis-interpreted the man page -a section. The -a will show output of devices if they are not faulty, but only if they have had a fault in the past. If i run fmadm faulty -a and i have had no faults since server build then nothing will be shown. Regards _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From anepomn at gmail.com Fri Sep 11 23:49:38 2009 From: anepomn at gmail.com (Aleksandr Nepomnyashchiy) Date: Fri, 11 Sep 2009 23:49:38 -0400 Subject: SUMMARY: LUN number too high for VxVM 5 / Solaris 8? 2 nodes crashed... Message-ID: <26924da90909112049v46f0e0c9s4e445be9d40f1d38@mail.gmail.com> Many thanks to those who tried to help especially to Sergey Prilutsky. It turned out that : A) LUN number was too high - I was able to reproduce server crash (on several servers) by adding LUN 200 Adding LUN 35 didn't cause any problems B) Fix was provided by Symantec support - to install the latest Array Policy Module for our Sun 6140 array. This resolved the issue - LUN 200 is not causing server crash. Aleksandr On 8/28/09, Aleksandr Nepomnyashchiy wrote: > Dear All, > Is there a maximum LUN number supported by Solaris 8 (or Veritas 5 MP3) ? > > > 2 node Solaris 8 cluster with VCS 5.0 - both nodes went down when LUN > 200 was added. After the initial crash both nodes were booting up and > panicking / crashing on the way up several times (until LUN 200 was > removed). > > Could it be caused by LUN number being too high? > > Thank you, > Aleksandr _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From Syed.Hosain at aeris.net Sat Sep 12 12:47:25 2009 From: Syed.Hosain at aeris.net (Syed.Hosain at aeris.net) Date: Sat, 12 Sep 2009 10:47:25 -0600 Subject: SUMMARY: Can't get past LOM message to connect to system ("Console is not shared" error) Message-ID: <9BC83CD5BF69F34AB235AD3684F30DF5012652B9@L01SLCXDB01.calltower.com> Ahha, I did not google the *exact* phrase "Console is not shared" before - I should have done that! BTW, I found an old Sun Manager mailing list message with the same error (but no solution mentioned): http://www.sunmanagers.org/pipermail/sunmanagers/2004-April/029776.html No SUMMARY in the mailing list archives ... sidebar: I have not been on this list in a long time, but have people fallen out of the habit of posting a SUMMARY when they fix something? It is always useful to send the fix along for others to search for later! Anyway, I was able to (a) get past the "Console is not shared" message and (b) determine what is wrong with the system. Thanks to this site info: http://blogs.sun.com/fintanr/entry/workaround_for_console_is_not Of course, now I know the drive is faulty ... means a plane trip to that site unfortunately. Argh! :( Here is what did the trick (even a "break" was not working - forgot to mention that before, although I had tried it). Note that I had to wait a bit till the system actually reset - the "console" command did not work initially for a bit of time. lom>break Console is not shared lom>break -f Console is not shared lom>console Console is not shared lom>console -f Console is not shared lom>bootmode reset_nvram lom>reset lom> LOM event: +492d+18h2m52s host reset lom>console Console is not shared lom>console Console is not shared lom>console Drive not ready Can't read disk label. Can't open disk label package Can't open boot device #. lom>break ok setenv boot-device disk ok probe-scsi Target 1 Unit 0 Disk FUJITSU MAN3367M SUN36G 1502 ok boot disk0:a Boot device: /pci at 1f,0/pci at 1/scsi at 8/disk at 0,0:a File and args: Drive not ready Can't read disk label. Can't open disk label package Can't open boot device ok Anyway, I reset the eeprom parameters to what I needed them to be. But, of course, the drive is not functional - so plane flight time ... An interesting sidebar: On a system with an LOM (has the LOMlite functionality), typing "break" also does the equivalent of a "console" as well ... on an Advanced LOM (ALOM), it just sends the break, so if you need to do more than one (depending on where it is in the boot sequence), you don't have to keep entering a "#." to get back to the ALOM prompt for the multiple breaks! Also, if you log out of the LOM, make darn sure that you reset the password first to something that you can use to get back in. :) Thanks to the couple of people who offered suggestions. Z From: Syed Zaeem Hosain (Syed.Hosain at aeris.net) Sent: Friday, September 11, 2009 9:46 PM To: 'sunmanagers at sunmanagers.org' Subject: Can't get past LOM message to connect to system Hi, all. I have a remote system that I am trying to reboot and am having difficulty. We have a console server that I can get to the serial port on the system. This allows me to get to the LOM luckily. But, I am unable to get to the ok> prompt. Here is the screen capture of some information from the LOM: lom>version LOM version: v3.12 LOM checksum: 6a3e LOM firmware part# 258-7871-18 Microcontroller: H8/3437S LOM firmware build Feb 21 2002 13:57:04 Configuration rev. v1.3 lom>show model Netra T1 200 hostname ns22po1-002-node-106 power-on-decline off power-on-delay off ip-address not set ip-netmask not set ip-gateway not set bootmode normal rsc-security on event-reporting on Time since last boot: +492d+6h31m30s But, when I try to get to the boot prom, here is what happens: lom>console Console is not shared lom> Needless to say, attempts to "reset", "poweroff" followed by "poweron" have not brought the system up. It responds to a "ping", but will not give me any response to telnet or rlogin. Meaning that the OS is not really running ... :( So ... how do I get past this "console is not shared" failure to check out things from the ok> boot prompt (like disk or other hardware failures)? A google search has been fruitless, and nothing on www.sun.com or sunsolve.sun.com appears to be relevant. Thanks for any help you all can give me here! The system is a plane flight away, so it is not possible for me to get to it easily. Z _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From sanelson at gmail.com Thu Sep 17 05:59:37 2009 From: sanelson at gmail.com (Stephen Nelson-Smith) Date: Thu, 17 Sep 2009 10:59:37 +0100 Subject: SUMMARY: Routing problem Message-ID: <96911654-AF92-4CDC-B37C-B8227F801936@gmail.com> Resolved: Stuart Saxon suggested to check with dladm, which revealed: bge0 link: up speed: 1000 Mbps duplex: full bge1 link: up speed: 1000 Mbps duplex: full bge2 link: down speed: 0 Mbps duplex: unknown bge3 link: unknown speed: 0 Mbps duplex: unknown The machine was plugged into bge3 not bge2. Thanks! S. ORIGINAL PROBLEM: I have a log server (http://www.balabit.com/network-security/syslog-ng/log-server- appliance/) that I want to use on my network. It is delivered with 192.168.1.1 out of the box. I want to change its IP to go on the network. It can only be configured via a web interface. I've plugged a crossover cable between it's network connection, and one of my servers, plumbed bge2, configured bge2 to be 192.168.1.2, brought it up, and added a host route, but I can't route to it. Here's the diagnostics: # ifconfig -a; netstat -rn lo0: flags=2001000849 mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 bge0: flags=201000843 mtu 1500 index 2 inet 172.19.33.250 netmask ffffff00 broadcast 172.19.33.255 ether 0:14:4f:7b:10:62 bge1: flags=201000843 mtu 1500 index 3 inet 172.20.252.173 netmask fffffc00 broadcast 172.20.255.255 ether 0:14:4f:7b:10:63 bge2: flags=201000803 mtu 1500 index 4 inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255 ether 0:14:4f:7b:10:64 Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ---------- --------- default 172.20.252.2 UG 1 29975 172.19.33.0 172.19.33.250 U 1 373 bge0 172.20.252.0 172.20.252.173 U 1 9879 bge1 192.168.1.1 192.168.1.2 UGH 1 0 224.0.0.0 172.20.252.173 U 1 0 bge1 127.0.0.1 127.0.0.1 UH 20 6110083 lo0 traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 40 byte packets 1 sta-wf-fr.telewest.co.uk (192.168.1.2) 0.167 ms !H 0.185 ms !H 0.049 ms !H ICMP Host Unreachable from gateway fms-kn-t1 (172.20.252.173) for icmp from fms-kn-t1 (172.20.252.173) to 192.168.1.1 Have I missed something obvious? S. _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From hoogendyk at bio.umass.edu Fri Sep 18 17:30:27 2009 From: hoogendyk at bio.umass.edu (Chris Hoogendyk) Date: Fri, 18 Sep 2009 17:30:27 -0400 Subject: SUMMARY - Configuring J4200 with SAS multipathing and ZFS (without CAM) Message-ID: <4AB3FBF3.3070902@bio.umass.edu> This is a very late summary which subsumes a couple of questions, but all relates to the same setup. In the end, it worked beautifully (really fast) and simply. The documentation and release notes just have to catch up and not be tangled in the forest of alternate products and options. --------------- The micro summary is that the hardware documentation clearly shows how to make dual SAS connections between a T5220 and the J4200, and a reconfigure reboot just brings it up. Format shows double entries for all the drives. So you get 24 drives where you have 12. If, at this point, you did `stmsboot -e`, it would coalesce those back down to 12 and assign longer GUID's for each drive (see below). Format shows those, and then a `zpool create . . . ` sets it all up and you're in business. I chose to set up a single raidz2 with one hot spare. So, 9 data drives, 2 parity drives, 1 hot spare. Performance tests were blazing. Since I wanted to exclude my internal drives from multipathing, I had to edit /kernel/drv/mpt.conf (not fp.conf, which is the only thing the documentation explains, and which is only for fiber channel), and then use `stmsboot -u`. Details below. Meanwhile, the StorageTek Common Array Manager (CAM) software is not required. I didn't use it at all, nor install it. Some respondents indicated it might be used for monitoring the health of the array. --------------- Thanks to Bryan Allen, Scott Lawson, Matt R. Clausen, Deborah Crocker, and, most especially, to James McPherson, Senior Kernel Software Engineer for Solaris at Sun. 8-) My original messages and their replies are all posted at the end. In the interest of helping anyone else who encounters the uncertainties I did, I'll summarize a bit more of the actual steps I went through with some comments on what's missing in the documentation. [Note: The part numbers in the following might be edu part numbers. We got the chassis & drives on special edu pricing.] I started with a T5220. Added a J4200 chassis (XTA4200R00A10DISK) filled out with SAS drives (XTA6SS1NJ-300G15K) and a second SAS controller (XTA-4200-IOM). Rack kit (XTA-4200-2URK-19U) is a pretty basic design. You could build one yourself like this one. Then put a dual SAS PCI card (SG-XPCIE8SAS-E-Z) in the T5200. Connected both HBA SAS ports on the T5220 to the SIM boards on the back of the J4200 according to the diagram on p.53 of the J4200 System Overview.pdf (downloaded all pdf docs from http://docs.sun.com/app/docs/prod/j4200.array~j4200?l=en#hic). Did a `touch /reconfigure` before taking the T5220 down to install the SAS HBA and connect everything. When it booted back up, it was just ready to fly, except I had to deal with the multipathing. Patches and updates for SAS multipathing. Solaris 10 should be at U6. I had mine at U7 (5/09) by the time I tackled this. The J4200 Release Notes, on page 4, indicates specific versions of CAM and patches that you must use if you configure multipathing and use the Common Array Manager (CAM) software. Just to put a plug in for Live Update, it was a breeze to get from U6 to U7 installing from a mounted ISO, and I only had a couple of minutes of down time when I restarted with the new boot environment. Getting the multipathing right was the real hangup, although it was simple once I was confident what to do. The documentation (http://docs.sun.com/app/docs/doc/820-1931/gfpva?a=view) refers to SAS several times, but the explicit example of "Per-Port" control of multipathing only mentions /kernel/drv/fp.conf and apparently assumes that you know that fp.conf refers to fiber channel and mpt.conf refers to SAS. The only references to mpt.conf are in the section on automatic configuration with `stmsboot -e`, where it lists several system configuration files that you do not have to edit (stmsboot does it for you). Also, the example listing of the entries in /dev/cfg don't match the details in the edit of fp.conf, so it is not clear how the parent name and port number are derived. Ultimately, in googling around, I stumbled on a Sun engineer who had answered some questions for somone, googled some more to find his email address, and sent a message directly to him. He answered my questions in detail (see below) and provided both some excellent information and reassurances. In looking back over the J4200 documentation, and specifically searching for mpt.conf, I found a one sentance reference (in the 92 page J4200 System Overview document) saying, "To enable multipathing on specific ports and disable multipathing on others, edit the /kernel/drv/mpt.conf file." No details or examples. So. My internal drives had entries like (full list down in one of the messages): /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 2,0 And my external drives (on the J4200) had entries like: /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 5,0 I wanted the SAS multipathing to ignore the internal drives and automatically take care of the external drives. So, I edited /kernel/drv/mpt.conf, adding the line to disable mpxio on the internal drives and setting the default to not disable mpxio. name="mpt" parent="/pci at 0/pci at 0/pci at 2" unit-address="0" mpxio-disable="yes"; mpxio-disable="no"; Then I ran `stmsboot -u`. After that format showed the drives in the J4200 as just 12 with new long GUID's assigned. See http://www.jmcp.homeunix.com/~jmcp/WhatIsAGuid.pdf. That's an excellent document by James McPherson. Also, he pointed out that the parent property is documented in the driver.conf (4) man page, although, I found that to be a bit abstruse. Anyway, format showed me the GUID's, which I then could use in a zpool command. # zpool create -f jpool raidz2 c5t5000C5000F5D37E3d0 c5t5000C5000F5D529Bd0 c5t5000C5000F6CFBFFd0 \ > c5t5000C5000F520E4Fd0 c5t5000C5000F524B4Fd0 c5t5000C5000F523647d0 c5t5000C50004B4B3CFd0 c5t5000C50004B4B7C7d0 \ > c5t5000C50004B4FA1Fd0 c5t5000C50004B49B27d0 c5t5000C50004B49BABd0 spare c5t5000C50004B49973d0 It was interesting that with that many drives and the long GUID's, if I just tried to put it all on one line, I hit some sort of limit and the command wouldn't take any more. Don't know if that was a ksh limit, a term limit, or what. Anyway, using the "\" continuations worked just fine. That's the whole story. After that it's just a ZFS snap. ;-) -- --------------- Chris Hoogendyk - O__ ---- Systems Administrator c/ /'_ --- Biology & Geology Departments (*) \(*) -- 140 Morrill Science Center ~~~~~~~~~~ - University of Massachusetts, Amherst --------------- Erdvs 4 Messages below Original Message #1 to SunManagers: Configuring J4200 with ZFS & not CAM? Reply from Bryan Allen Reply from Scott Lawson Reply from Matt R. Clausen Reply from Tomasz Ostrowski Original Message #2 to SunManagers: stmsboot on t5220 with J4200 Reply from Deborah Crocker Original Message #3 to SunManagers: Re: stmsboot on t5220 with J4200 Follow up to Deborah Crocker: Re: stmsboot on t5220 with J4200 2nd Reply from Deborah Crocker Original Message to James McPherson at Sun: SAS Multipathing configuration in Solaris 10 Reply from James McPherson at Sun Reply back to James McPherson at Sun -------- Original Message #1 to SunManagers -------- Subject: Configuring J4200 with ZFS & not CAM? Date: Fri, 24 Apr 2009 11:59:36 -0400 We've just gotten a J4200 to attach to a T5220. My intention is to configure it with ZFS, which I'm already using for the extra internal drives on the T5220 (I used hardware mirroring for the boot drive). My understanding of the J4200 is that it is supposed to be a JBOD, almost plug and play. However, when I opened the box, it came with the manual and CD for CAM - the StorageTek Common Array Manager software. I am still waiting for some drives, so I'm not setting it up yet. I have a SAS HBA and will be setting it up with SAS drives. If it is just a matter of plugging it all in and doing a reconfigure reboot, whereupon the drives show up in format and can then be configured with zpool and zfs commands, then I'm all set. Can anyone tell me the relationship/difference between CAM and ZFS? Am I going to need CAM at all? Or is it sort of like you don't need raidctl if you are using zfs? Thanks, Chris Hoogendyk -------- Reply from Bryan Allen -------- Subject: Re: Configuring J4200 with ZFS & not CAM? Date: Fri, 24 Apr 2009 13:12:13 -0400 I have a J4200 attached to an X4100 M2 using the LSI SAS card from Sun. No issues. Very happy with it. If you are using a RAID card, you'll need to configure CAM/RAID/et al. If you are using a plain HBA, you don't need to mess with CAM. Note that the Adaptec SAS RAID card you get from Sun cannot do JBOD. It cannot be flashed with Adaptec's firmware (which supports JBOD) and Sun support wouldn't tell me if an update was forthcoming. You also cannot configure each LUN as RAID0, thus exporting each drive to ZFS individually. You would have to create two-disk RAID0s and export the pairs. I returned that card and got the LSI HBA. There was too much complexity for no reason in the RAID configuration given how I wanted to use ZFS. You don't need to do a reconfigure reboot, either: devfsadm -C cfgadm -al zpool create ... -- bda cyberpunk is dead. long live cyberpunk. -------- Reply from Scott Lawson -------- Subject: Re: Configuring J4200 with ZFS & not CAM? Date: Sat, 25 Apr 2009 09:19:00 +1200 Chris, It should just be a matter of inserting the SAS controller and doing a reconfigure boot. I have a T5220 with a J4500 attached in the same way. Works fine for me and was simple to set up. I am not sure why they included CAM at all, it may be that it can be used as an expansion chassis for one of the entry level Storagetek arrays. CAM is used for managing the Storagetek 25xx and 6xxx series hardware RAID arrays. The J4200 is also used with the new open storage appliances but I can't see why it would need CAM.. I don't recall receiving CAM with my J4500. I was also one of the beta testers for the J4500. 'raidctl' is part of the OS and is used for internal controllers. There is also a host hardware RAID controller available for the J series arrays which is made by Adaptec. But if you use ZFS then you really have no need for it. It's more for people that use these JBOD's with Windows or Linux. /Scott. -------- Reply from Matt R. Clausen -------- Subject: RE: Configuring J4200 with ZFS & not CAM? Date: Tue, 28 Apr 2009 17:03:28 -0500 CAM is strictly used for monitoring the J4X00 series arrays. They are nothing more then a JBOD so there's nothing for CAM to configure (you don't even have to install it though it's a good thing to have because it can monitor the array health). Once you get it all hooked up, you will see all the individual drives appear to the operating system from which you can then put them into your respective ZFS pools/volumes/etc. Hope this helps. -------- Reply from Tomasz Ostrowski -------- Subject: Configuring J4200 with ZFS & not CAM? Date: Wed, 24 Jun 2009 08:14:03 +0200 Hello Chris, Did you manage to configure the disk array withou CAM? I'm starting with iscsi tech. and now i wonder how to assing an ip addres tho the SIM controlem on the disk array? Or this is wrong step? Do you have any guide lines? Best Regards Tomek Tomasz Ostrowski NSN Preconfiguration Engineer -------- Original Message #2 to SunManagers -------- Subject: stmsboot on t5220 with J4200 Date: Mon, 03 Aug 2009 17:39:06 -0400 I have a T5220 with an attached J4200. I added a dual SAS PCI card to the T5220 and added a second SAS controller to the J4200. It has 12 300G SAS drives in it. On the T5220, I used hardware raid to mirror the boot drive, have one plain drive, and configured 4 drives with zfs raidz. Those are all in use. When I check format, I see all the internal drives and 2 instances of all of the drives in the J4200 (see at end). I want to configure the J4200 with zpool. As I understand it, I need to do `stmsboot -e` first to set up multiplathing and reboot. Then I should see the renamed drive devices in format and can just feed them in to a zpool create. My problem is that I have never done this before, and I'm afraid of messing up my existing setup on the T5220. What I get is # stmsboot -L stmsboot: MPxIO is not enabled # stmsboot -e WARNING: stmsboot operates on each supported multipath-capable controller detected in a host. In your system, these controllers are /pci at 0/pci at 0/pci at 2/scsi at 0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0 If you do NOT wish to operate on these controllers, please quit stmsboot and re-invoke with -D { fp | mpt } to specify which controllers you wish to modify your multipathing configuration for. Do you wish to continue? [y/n] (default: y) n # It's showing me both the internal scsi (SAS) systems and the external SAS, and I don't see any way to restrict it to just do the external system. The `stmsboot -D mpt -e` option doesn't seem to offer anything different, since it's all SAS. But, since I am telling it to use the mpt driver, it doesn't do the same sort of autodiscovery informing me what it is going to do. It just does # stmsboot -D mpt -e WARNING: This operation will require a reboot. Do you want to continue ? [y/n] (default: y) n # I can imagine that it might look at all the drives and see that I have duplicate instances on all the external ones and multipath them, leaving the others alone; but, I'm just guessing. And, search as I might, I can't find any examples that explain it in enough detail or that show what happens if you say no and then configure something differently (or even continue the example out through the format showing all the internal and external drives without excerpting the list). If anyone who has actually done this could give me some encouragement and/or guidance, I would certainly appreciate it. TIA Chris Hoogendyk AVAILABLE DISK SELECTIONS: 0. c1t0d0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 0,0 1. c1t2d0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 2,0 2. c1t4d0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 4,0 3. c1t5d0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 5,0 4. c1t6d0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 6,0 5. c1t7d0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 7,0 6. c4t0d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 0,0 7. c4t1d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 1,0 8. c4t2d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 2,0 9. c4t3d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 3,0 10. c4t4d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 4,0 11. c4t5d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 5,0 12. c4t6d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 6,0 13. c4t7d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 7,0 14. c4t8d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 8,0 15. c4t9d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 9,0 16. c4t10d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at a,0 17. c4t11d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at b,0 18. c4t13d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at d,0 19. c4t14d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at e,0 20. c4t15d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at f,0 21. c4t16d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 10,0 22. c4t17d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 11,0 23. c4t18d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 12,0 24. c4t19d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 13,0 25. c4t20d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 14,0 26. c4t21d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 15,0 27. c4t22d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 16,0 28. c4t23d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 17,0 29. c4t24d0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 18,0 -------- Reply from Deborah Crocker -------- Subject: Re: stmsboot on t5220 with J4200 Date: Tue, 04 Aug 2009 09:08:02 -0500 Review /kernel/drv/fp.conf. You can exempt controllers from multipathing. For instance, on our T5240 we have: mpxio-disable="no"; [This turns multipathing on] name="fp" parent="/pci at 500/pci at 0/pci at c/SUNW,qlc at 0" port=0 mpxio-disable="yes"; You'll see more comments on configuring this in the fp.conf file Deb C. -------- Original Message #3 to SunManagers -------- Subject: Re: stmsboot on t5220 with J4200 Date: Wed, 12 Aug 2009 17:32:20 -0400 Sorry, I'm getting a bit frustrated with this. Production system. Can't play around. Has to be right. (I got one response from Deborah Crocker indicating that I need to edit the fp.conf, but then ... ) So, from http://docs.sun.com/app/docs/doc/820-1931/gfpva?a=view , halfway down, it describes how to "Configure Multipathing by Port." It says to use `parent="parent name" port=port number`, but the explicit example it gives does not match with the /dev/cfg entries that it starts the explanation with. So, it's not clear how to derive the parent name and the port number, and they don't explain it. I'm guessing that in my case `parent="/pci at 0/pci at 0/pci at 2/scsi at 0" port=0` would designate my internal drives. I also presume that since they have folded SAS in with FC, that the `name="fp"` designation would apply for the internal drives. So, I could exclude them and be ready to go, with: name="fp" parent="/pci at 0/pci at 0/pci at 2/scsi at 0" port=0 mpxio-disable="no"; I've put some output at the very end of this that I extracted from format, /dev/cfg, and prtdiag for reference. again, TIA. Chris Hoogendyk # format /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 0,0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 2,0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 4,0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 5,0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 6,0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 7,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 0,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 1,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 2,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 3,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 4,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 5,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 6,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 7,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 8,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 9,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at a,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at b,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at d,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at e,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at f,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 10,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 11,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 12,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 13,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 14,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 15,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 16,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 17,0 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0/sd at 18,0 # ls -l /dev/cfg c1 -> ../../devices/pci at 0/pci at 0/pci at 2/scsi at 0:scsi <-- internal drives c2 -> ../../devices/pci at 0/pci at 0/pci at 9/pci at 0/scsi at 8:scsi c3 -> ../../devices/pci at 0/pci at 0/pci at 9/pci at 0/scsi at 8,1:scsi <-- tape library? c4 -> ../../devices/pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0:scsi <-- J4200 # prtdiag -v ================================ IO Devices ================================ Slot + Bus Name + Status Type Path ---------------------------------------------------------------------------- MB/NET0 PCIE network-pciex8086,105e /pci at 0/pci at 0/pci at 1/pci at 0/pci at 2/network at 0 MB/NET1 PCIE network-pciex8086,105e /pci at 0/pci at 0/pci at 1/pci at 0/pci at 2/network at 0,1 MB/NET2 PCIE network-pciex8086,105e /pci at 0/pci at 0/pci at 1/pci at 0/pci at 3/network at 0 MB/NET3 PCIE network-pciex8086,105e /pci at 0/pci at 0/pci at 1/pci at 0/pci at 3/network at 0,1 MB/SASHBA PCIE scsi-pciex1000,58 /pci at 0/pci at 0/pci at 2/scsi at 0 <-- internal drives MB/RISER1/PCIE1 PCIE LSILogic,sas-pciex1000,58 /pci at 0/pci at 0/pci at 8/pci at 0/pci at 1/LSILogic,sas at 0 <-- J4200 MB/RISER0/PCIE0 PCIE network-pciex8086,105e /pci at 0/pci at 0/pci at 8/pci at 0/pci at 9/network at 0 MB/RISER0/PCIE0 PCIE network-pciex8086,105e /pci at 0/pci at 0/pci at 8/pci at 0/pci at 9/network at 0,1 MB PCIX usb-pciclass,0c0310 /pci at 0/pci at 0/pci at 1/pci at 0/pci at 1/pci at 0/usb at 0 MB PCIX usb-pciclass,0c0310 /pci at 0/pci at 0/pci at 1/pci at 0/pci at 1/pci at 0/usb at 0,1 MB PCIX usb-pciclass,0c0320 /pci at 0/pci at 0/pci at 1/pci at 0/pci at 1/pci at 0/usb at 0,2 MB/RISER2/PCIE2 PCIE scsi-pci1000,30 /pci at 0/pci at 0/pci at 9/pci at 0/scsi at 8 MB/RISER2/PCIE2 PCIE scsi-pci1000,30 /pci at 0/pci at 0/pci at 9/pci at 0/scsi at 8,1 <-- tape library -------- Follow up to Deborah Crocker -------- Subject: Re: stmsboot on t5220 with J4200 Date: Fri, 14 Aug 2009 13:26:59 -0400 Just a quick followup -- why is it fp.conf and 'name="fp"' rather than mpt.conf? If I do a stmsboot -e (and then say no to stop it), it lists my controllers, but doesn't indicate fp or mpt. If I do stmsboot -D mpt -e, it doesn't list them first, but asks directly if I want to continue. I said no. So I don't know what it would have come up with. Same with -D fp. Also, how do you know port=0? I don't know if you saw my followup on sunmanagers, but the examples in the Sun documents on multiplathing don't follow through from one item to the next. Their listing of /dev/cfg does not match up with their example of editing fp.conf, and there's no explanation of how to derive those items. So, I'm not sure/confident that the following will be correct for my system: mpxio-disable="no"; name="fp" parent="/pci at 0/pci at 0/pci at 2/scsi at 0" port=0 mpxio-disable="yes"; Sorry to email you directly, but no one else has responded to either of my postings on sunmanagers. I pasted some system output at the bottom. Thank you very much. Chris Hoogendyk [Repeat of output that was at the end of the preceding message #3 to SunManagers] -------- 2nd Reply from Deborah Crocker -------- Subject: Re: stmsboot on t5220 with J4200 Date: Fri, 14 Aug 2009 18:16:11 -0500 Sorry for my hastily written note from before. I wanted to give you something to look at to get going but was running between meetings. We use a lot of fiber around here and only turn on multipathing for that, not the mpt controller. So I'll admit, our situation is different. With your SAS driver, you would use mpt.conf. I believe for all your internal devices the port is "0". Only for the external dual port card do you have "0" and "1". It worries me that the drives on the LSI don't show up on different controllers (with 12 on each). You noted that drives on the LSI (SAS) card are all c4. It seems like there has to be a pair of controllers there for mpxio to understand what to multipath over. For example, here is of our cfgadm output (again, for fiber) c2 fc-fabric connected configured unknown c2::50060e8014436901 disk connected configured unknown c4 fc-fabric connected configured unknown c4::50060e8014436911 disk connected configured unknown The disks, however, are in the system under mpxio as c5. What kind of downtime window can you get? You may just have to test this. Deb C. -------- Original Message to James McPherson at Sun -------- Subject: SAS Multipathing configuration in Solaris 10 Date: Mon, 24 Aug 2009 14:24:00 -0400 While researching how to set up SAS multipathing, I've seen a number of your postings on various Solaris related lists. I hope you don't mind my asking you a question directly. Once I've resolved it, I will post a summary back to the Sun Managers list where I have asked for help and received essentially no response. I have a T5220 with a J4200. I added a dual SAS card to the T5220 and connected everything according to page 53 of the J4200 System Overview. I also updated Solaris to u7 (Solaris 10 5/09 s10s_u7wos_08 SPARC) and applied the latest patches, checking to see that I had what was required for SAS multipathing (Live Update is sooo cool). While I see various places where things have been updated to handle SAS multipathing, all the documentation I've been able to find talks about multipathing in terms of fiber channel. I've gotten a few hints that I should be looking at mpt.conf rather than fp.conf, and found one post that specifically referred to configuring SAS multipathing by editing mpt.conf. I would like to exclude the internal drives and have the J4200 multipathed. Then I will configure it with zpool and zfs, probably 9 data drives, 2 parity drives and 1 hot spare (that gives me more safety than 2 raidz, and more data than 2 raidz2). They are all 300G 1500rpm SAS. I gather that what I need is to replace 'mpxio-disable="yes"' in /kernel/drv/mpt.conf with: name="mpt" parent="/pci at 0/pci at 0/pci at 2/scsi" unit-address="0" mpxio-disable="yes"; mpxio-disable="no"; and then do a `stmsboot -u`. Before doing this, the information from format is as it appears at the end of this email. For the internal drives, I've used hardware raid to mirror my boot drive, I have some plain drives for Amanda holding disk space, and the rest are configured as a zpool raidz. I'm slightly concerned that the 12 drives in the J4200 appear as 24 instances numbered sequentially without any distinction of 12 on one port and 12 on another. I presume the multipath software will figure it out. Sorry if I seem too cautious. I don't like breaking production systems, and I don't have room for error in a situation where fixing it could get hairy. Just a confirmation that all of this is correct would be cool. A pointer to any updated documentation that covers these topics would be helpful as well. The documentation on fiber channel, for example, uses port instead of unit-address, and there is no explanation for the derivation of parent and port. In fact, the example showing the devices doesn't correspond to the details of the fp.conf. Apparently someone updated one without bothering to keep the information in sync throughout the example (see http://docs.sun.com/app/docs/doc/820-1931/gfpva?a=view). That makes it difficult to deduce (absent an explanation) how the parent and port are derived. Thanks in advance. I appreciate your consideration. Chris Hoogendyk AVAILABLE DISK SELECTIONS: 0. c1t0d0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 0,0 [etc. repeating format output from message #2 on stmsboot to SunManagers above] -------- Reply from James McPherson at Sun -------- Subject: Re: SAS Multipathing configuration in Solaris 10 Date: Tue, 25 Aug 2009 11:30:41 +1000 Gday Chris, On Mon, 24 Aug 2009 14:24:00 -0400 Chris Hoogendyk wrote: > While researching how to set up SAS multipathing, I've seen a number of > your postings on various Solaris related lists. I hope you don't mind my > asking you a question directly. Once I've resolved it, I will post a > summary back to the Sun Managers list where I have asked for help and > received essentially no response. > > I have a T5220 with a J4200. I added a dual SAS card to the T5220 and > connected everything according to page 53 of the J4200 System Overview. > I also updated Solaris to u7 (Solaris 10 5/09 s10s_u7wos_08 SPARC) and > applied the latest patches, checking to see that I had what was required > for SAS multipathing (Live Update is sooo cool). It is. But pkg image-update is even cooler, gotta say :-) > While I see various places where things have been updated to handle SAS > multipathing, all the documentation I've been able to find talks about > multipathing in terms of fiber channel. I've gotten a few hints that I > should be looking at mpt.conf rather than fp.conf, and found one post > that specifically referred to configuring SAS multipathing by editing > mpt.conf. Yes, that's correct - SAS multipathing at present uses the mpt.conf file. It's never used fp.conf, which is Fibre Channel-specific. The general case, where you turn on MPxIO for all attached devices which are capable, is to run "/usr/sbin/stmsboot -e" - which should definitely be all that you need. > I would like to exclude the internal drives and have the J4200 > multipathed. Then I will configure it with zpool and zfs, probably 9 > data drives, 2 parity drives and 1 hot spare (that gives me more safety > than 2 raidz, and more data than 2 raidz2). They are all 300G 1500rpm SAS. > > I gather that what I need is to replace 'mpxio-disable="yes"' in > /kernel/drv/mpt.conf with: > > name="mpt" parent="/pci at 0/pci at 0/pci at 2/scsi" unit-address="0" > mpxio-disable="yes"; > mpxio-disable="no"; > > and then do a `stmsboot -u`. Not quite - your mpt.conf is incorrect. The example given in /kernel/drv/mpt.conf is # You can also enable or disable MPxIO on a per HBA basis. # Per HBA settings override the global setting for the specified HBAs. # To disable MPxIO on a controller whose parent is /pci at 7c0/pci at 0/pci at 9 # and the unit-address is "0" set: # name="mpt" parent="/pci at 7c0/pci at 0/pci at 9" unit-address="0" mpxio-disable="yes"; So what you would need to do (based on your info above) is to use name="mpt" parent="/pci at 0/pci at 0/pci at 2" unit-address="0" mpxio-disable="yes"; mpxio-disable="no"; You do, however, need to run "/usr/sbin/stmsboot -u" > Before doing this, the information from format is as it appears at the > end of this email. For the internal drives, I've used hardware raid to > mirror my boot drive, I have some plain drives for Amanda holding disk > space, and the rest are configured as a zpool raidz. I'm slightly > concerned that the 12 drives in the J4200 appear as 24 instances > numbered sequentially without any distinction of 12 on one port and 12 > on another. I presume the multipath software will figure it out. Sorry > if I seem too cautious. I don't like breaking production systems, and I > don't have room for error in a situation where fixing it could get hairy. Yes, MPxIO will figure it out. While you've got two physical connectors on the one card, they are not actually two separate controllers. The way that the LSISAS1068 chip is designed, those two physical connectors (PHYs) are each an x4 SAS lane. When you connect a cable to both of them, then they become a single x8 SAS lane instead. You might it helpful to have a look at the info in my What Is A Guid? presentation - http://www.jmcp.homeunix.com/~jmcp/WhatIsAGuid.pdf > Just a confirmation that all of this is correct would be cool. > > A pointer to any updated documentation that covers these topics would be > helpful as well. The documentation on fiber channel, for example, uses > port instead of unit-address, and there is no explanation for the > derivation of parent and port. In fact, the example showing the devices > doesn't correspond to the details of the fp.conf. Apparently someone > updated one without bothering to keep the information in sync throughout > the example (see > http://docs.sun.com/app/docs/doc/820-1931/gfpva?a=view). That makes it > difficult to deduce (absent an explanation) how the parent and port are > derived. That's really quite annoying about the docs.sun.com link, because I was heavily involved with re-writing that exact doc to bring it up to date for SAS MPxIO (and make the FC MPxIO text better). Try the OpenSolaris version instead - http://docs.sun.com/app/docs/doc/820-3070?l=en The parent property is covered in the driver.conf(4) manpage, but I do agree that the description needs an update, especially for the port property. If you'd care to log a bug against the doco, using http://bugs.opensolaris.org, that would be appreciated. Best regards, James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog -------- Reply back to James McPherson at Sun -------- Subject: Re: SAS Multipathing configuration in Solaris 10 Date: Thu, 27 Aug 2009 17:18:24 -0400 Thank you! It worked beautifully. And, it is *really* fast. I've been delayed a little in responding. We have the overload just before school starts. Then on Tuesday we were notified at 4:45pm that there would be a power outage in our server room for 8 hours beginning at 6:30am the next morning. Apparently something in the new building was not wired to code, and they were going to have to re-do it. That was an opportunity to do the `stmsboot -u`, but then I didn't get to play with it for another day. Now I need to post a summary back to the sunmanagers list, have a look at the opensolaris documentation, and post a bug report to encourage an update of that. Chris Hoogendyk _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From anepomn at gmail.com Fri Sep 18 19:24:16 2009 From: anepomn at gmail.com (Aleksandr Nepomnyashchiy) Date: Fri, 18 Sep 2009 19:24:16 -0400 Subject: SUMMARY: Sun 420R disabled CPUs immediately after the reboot Message-ID: <26924da90909181624r6f462ebaj9ec67668d4e85a94@mail.gmail.com> Apologies to everyone - I have found "psradm -f" in one of the startup scripts. Aleksandr On Fri, Sep 18, 2009 at 5:05 PM, Aleksandr Nepomnyashchiy wrote: > Dear Sunmanagers, > I had a crash on Sun 420R with Solaris 8 today. System came up > ~9:20am with 2 CPUs disabled. I wonder why ? prtdiag doesn't show any > problems... > > I searched for any startup script which could purposely do it, but > couldn't find anything. > > root at server2 /etc # psrinfo > 0 off-line since 09/18/09 09:22:58 > 1 on-line since 09/18/09 09:21:12 > 2 on-line since 09/18/09 09:21:12 > 3 off-line since 09/18/09 09:22:58 > root at server2 /etc # > root at server2 /etc # /usr/platform/sun4u/sbin/prtdiag -v > System Configuration: Sun Microsystems sun4u Sun Enterprise 420R (4 > X UltraSPARC-II 450MHz) > System clock frequency: 113 MHz > Memory size: 4096 Megabytes > > ========================= CPUs ========================= > > Run Ecache CPU CPU > Brd CPU Module MHz MB Impl. Mask > --- --- ------- ----- ------ ------ ---- > 0 0 0 450 4.0 US-II 10.0 > 0 1 1 450 4.0 US-II 10.0 > 0 2 2 450 4.0 US-II 10.0 > 0 3 3 450 4.0 US-II 10.0 > > > ========================= IO Cards ========================= > > Bus Freq > Brd Type MHz Slot Name Model > --- ---- ---- ---------- ---------------------------- -------------------- > 0 PCI 33 On-Board network-SUNW,hme > 0 PCI 33 On-Board scsi-glm/disk (block) Symbios,53C875 > 0 PCI 33 On-Board scsi-glm/disk (block) Symbios,53C875 > 0 PCI 33 PCI 1 66 pci-pci1011,25.4/pci108e,100+ pci-bridge > 0 PCI 33 PCI 1 66 SUNW,qfe-pci108e,1001 SUNW,pci-qfe > 0 PCI 33 PCI 1 66 SUNW,qfe-pci108e,1001 SUNW,pci-qfe > 0 PCI 33 PCI 1 66 SUNW,qfe-pci108e,1001 SUNW,pci-qfe > 0 PCI 33 PCI 1 66 SUNW,qfe-pci108e,1001 SUNW,pci-qfe > > No failures found in System > =========================== > > ========================= HW Revisions ========================= > > ASIC Revisions: > --------------- > PCI: pci Rev 4 > PCI: pci Rev 4 > Cheerio: ebus Rev 1 > > System PROM revisions: > ---------------------- > OBP 3.31.0 2001/07/25 20:35 POST 1.2.8 2000/08/22 19:50 > root at server2 /etc # _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From cmcbas at sunguru.com Mon Sep 21 07:01:03 2009 From: cmcbas at sunguru.com (Bhaskar G) Date: Mon, 21 Sep 2009 04:01:03 -0700 Subject: SUMMARY: T2000 shows only 4 CPUs. Message-ID: <20090921040103.A669A8E4@resin11.mta.everyone.net> Hi All, Ldom was configured on the T2000. So did a setdefaults at the sc> prompt, it worked. Thanks On Mon, Sep 21, 2009 at 5:20 PM, Bhaskar G wrote: Hi All, Server Type : T2000 OS : Solaris 10 Server shows only 4 CPU, how to enable all the other CPU's ( it should show 32 Cup's since it is 8 core server) psrinfo 0 on-line since 09/21/2009 12:10:45 1 on-line since 09/21/2009 12:10:47 2 on-line since 09/21/2009 12:10:47 3 on-line since 09/21/2009 12:10:47 There is no hardware error on the system boot or in the messages file or at boot time. thanks _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From hoogendyk at bio.umass.edu Tue Sep 22 13:11:19 2009 From: hoogendyk at bio.umass.edu (Chris Hoogendyk) Date: Tue, 22 Sep 2009 13:11:19 -0400 Subject: SUMMARY - Configuring StorageTek 2510 iSCSI for best ZFS Message-ID: <4AB90537.7030006@bio.umass.edu> hmm. I thought I owed a summary, but I can't seem to find that I ever posted the question. I guess I just hammered my head against the wall for enough days that I was sure I must have posted a question. Anyway, I think it's worth posting a summary, because there were missing links in the documentation, and, finally, a critical blog I found that helped me figure out what to do. It's hard to do a useful micro summary; but, basically, I was able to work with command line only using Common Array Manager (CAM) to configure the 2510 so that each drive was exported as a LUN. Then I could assign drives to individual hosts (I have 2 directly connected to the array), see them in `format`, and use zpool to group them into raidz. -- *Physical setup* -- This configuration is a StorageTek 2510 with SAS drives and 2 T5220's. The 2510 has one controller, and each T5220 is connected directly to one of the iSCSI ports on that controller. The controller on the 2510 has a management port and two data ports. There are stickers on the back near the ports with the Mac addresses printed on them. -- *Management port *-- Originally, I wanted to have command line only management directly over the data lines (in line management). Since I was having trouble figuring out how to set this thing up at all, I decided to just go ahead and expose the management port on the 2510. I set up the Mac address of the management port in our DHCP server, plugged the management port into a switch in our private network, and tried to ping it. No ping and no evidence from the DHCP server that it had requested or been given an address. hmm. Turns out it does it using bootp. So, I added an appropriate entry in /etc/bootptab on our server that does it. Power cycled the 2510. Ping. Then I scanned it with nmap. nmap failed to identify the device and said all ports were closed. OK. Cool. on to the next step. -- *Install CAM* -- Now I needed to install CAM. I thought I should look for the latest. Turns out 6.2 and more recent say that they need a firmware upgrade of the 2510 before they can talk to it. The software for the firmware upgrade seemed to be GUI only. My server has no GUI. Really. Minimal network install with whatever packages I needed beyond that individually installed. No GUI. So. CAM 6.1.1.10 seemed to be the most recent before 6.2. I downloaded that and checked the readme. It had a command line only install option. `./RunMe.bin -c`. I did that. Selected a custom install, command line only with firmware. Somehow that claimed it was installing Java 2 standard edition. There were some differences in where the documentation said I would find the software and where I actually found it. The critical application is sscs and was found at /opt/SUNWstkcam/bin/. Since I was on the machine that was to manage and access the array, I didn't need to do the `sscs login ....`, and I could get basic information on the fly from `sscs --help`. -- *Documentation* -- Ultimately, I found three sources that gave me what I needed. (1) The Sun StorageTek 2500 Series Array Installation Guide gave me the overview of how to set up the array. In particular, the section on Configuring iSCSI Tasks, the Table A-2, iSCSI Configuration Steps, and the section with the Example for Solaris. It fell short in that at a crucial step it simply says, "Follow CAM Documentation to . . . ." But, the CAM documentation is very cursory on iSCSI, assuming, I guess, that you will get it from the GUI. There is a table listing iSCSI commands with no explanation, overview, or examples of how to use them. (2) The man page for sscs was a key reference. However, it is 123 pages long and doesn't really give you an overview of what you need to do or how the different subcommands interact. It's also a bit hard to go scrolling back and forth through it. So, I printed it out to a pdf preview. Then I could search the pdf for "NAME", which was the section title preceding every command. That gave me a sort of table of contents into the commands that I could scan through. I still encountered at least one command whose syntax turned out to be very different from what the man page listed. (3) I found a blog that gave me some critical conceptual overview and details for what I was trying to do. That is referenced further down when I get to that. -- *Registering & Configuring the 2510* -- Following page 95 and forward in the Installation Guide. [Note: I've slightly obscured the IP address in the following] # cd /opt/SUNWstkcam/bin # ./sscs add -i 172.xx.xx.xx registeredarray Name Type Network Address Serial Number --------- ---- --------------- -------------------------- unlabeled 2510 172.xx.xx.xx SUN.540-7198-01.0812BE3D2D # ./sscs modify -N edsel array unlabeled [After setting up a new J4200, this seemed an appropriate name for the 2510] # ./sscs list firmware Analyzing array edsel,(172.xx.xx.xx),200400a0b8490699 Controller: Some FRUs not at baseline. Name Model Current Baseline Tray.85.Controller.A LCSM100_I 06.70.42.10 06.70.54.10 Disk: Some FRUs not at baseline. Name Model Current Baseline Tray.85.Drive.01 HUS1530SBSUN300G SA02 SA04 Tray.85.Drive.02 HUS1530SBSUN300G SA02 SA04 Tray.85.Drive.03 HUS1530SBSUN300G SA02 SA04 Tray.85.Drive.04 HUS1530SBSUN300G SA02 SA04 Tray.85.Drive.05 HUS1530SBSUN300G SA02 SA04 System/NVSRAM: All FRUs at baseline Name Model Current Baseline edsel 2510 N1532-670843-901 N1532-670843-901 # ./sscs modify -a edsel firmware WARNING: This command will load new firmware if needed and may impact array management and data availability. Do you wish to continue? [y,n] : y Started firmware upgrade job Install:task28 # ./sscs list -a edsel jobs Job ID: Install:task28 Status: Done # ./sscs list firmware Analyzing array edsel,(172.28.55.33),200400a0b8490699 Controller: All FRUs at baseline Name Model Current Baseline Tray.85.Controller.A LCSM100_I 06.70.54.10 06.70.54.10 Disk: Some FRUs not at baseline. Name Model Current Baseline Tray.85.Drive.01 HUS1530SBSUN300G SA02 SA04 Tray.85.Drive.02 HUS1530SBSUN300G SA02 SA04 Tray.85.Drive.03 HUS1530SBSUN300G SA02 SA04 Tray.85.Drive.04 HUS1530SBSUN300G SA02 SA04 Tray.85.Drive.05 HUS1530SBSUN300G SA02 SA04 System/NVSRAM: All FRUs at baseline Name Model Current Baseline edsel 2510 N1532-670843-901 N1532-670843-901 [So, it updated the firmware on the controller, but not on the drives. It took a bit of fiddling around to find the correct syntax and details to do that.] # ./sscs modify -a edsel -t disk firmware WARNING: This command will load new firmware if needed and may impact array management and data availability. Do you wish to continue? [y,n] : y Started firmware upgrade job Install:task32 # ./sscs list -a edsel jobs Job ID: Install:task32 Status: Done Job ID: Install:task28 Status: Done # ./sscs list firmware Analyzing array edsel,(172.28.55.33),200400a0b8490699 Controller: All FRUs at baseline Name Model Current Baseline Tray.85.Controller.A LCSM100_I 06.70.54.10 06.70.54.10 Disk: All FRUs at baseline Name Model Current Baseline Tray.85.Drive.01 HUS1530SBSUN300G SA04 SA04 Tray.85.Drive.02 HUS1530SBSUN300G SA04 SA04 Tray.85.Drive.03 HUS1530SBSUN300G SA04 SA04 Tray.85.Drive.04 HUS1530SBSUN300G SA04 SA04 Tray.85.Drive.05 HUS1530SBSUN300G SA04 SA04 System/NVSRAM: All FRUs at baseline Name Model Current Baseline edsel 2510 N1532-670843-901 N1532-670843-901 [All set] -- *Configure data ports on server* -- OK, so now I need to set up data connections between the T5220 and the 2510. They are connected directly with a plain ethernet cable (not a crossover). I get the IP addresses for the 2510 data ports from sscs, and then configure the T5220 with ifconfig. # ./sscs list -a edsel iscsi-port [output truncated] Controller: A iSCSI Port: A/1 Listening Port: 3260 IP Address: 192.168.130.101 Gateway: 0.0.0.0 Netmask: 255.255.255.0 iSCSI Port: A/2 Listening Port: 3260 IP Address: 192.168.131.101 Gateway: 0.0.0.0 Netmask: 255.255.255.0 # ifconfig -a [just to check] # ifconfig e1000g2 plumb # ifconfig e1000g2 192.168.130.88 netmask 255.255.255.0 up # ping 192.168.130.101 192.168.130.101 is alive! # cat > /etc/hostname.e1000g2 192.168.130.101 # cat >> /etc/hosts 192.168.130.88 imladris.scsi.mor.nsm 192.168.130.101 edsel.scsi.mor.nsm # cat >> /etc/netmasks 192.168.130.0 255.255.255.0 In the above, the ifconfig got it running; but, the additions to the /etc files will make sure it comes up if/when the system is ever rebooted. The fully qualified network names are made up to match, in essence, the way we do our private networks. It won't go out on any network, even private, since they are direct connected, but, anyway. Morrill (mor) is our building, and NSM is our College within the University. -- *Set up iSCSI initiators* -- This is basically following the steps in the Installation Guide, in particular the Solaris example on p. 101 in my hard copy. Be sure to check software versions and patches as instructed. I didn't have to mess with any of that, because I was on Solaris 10 u7 (5/09) with the latest recommended and security patches. Anyway. Need to find the IQN (iSCSI Qualified Name) for the initiator associated with the T5220 and the data ports on the 2510, and set up connections between them. # iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:00212813a10c.49188968 [rest of output cut] # iscsiadm modify discovery --static enable # iscsiadm add discovery-address 192.168.130.101:3260 # iscsiadm list discovery-address Discovery Address: 192.168.130.101:3260 Target name: iqn.1986-03.com.sun:2510.600a0b80004906990000000048c13342 Target address: 192.168.130.101:3260, 1 Target name: iqn.1986-03.com.sun:2510.600a0b80004906990000000048c13342 Target address: 192.168.131.101:3260, 1 # iscsiadm add static-config iqn.1986-03.com.sun:2510.600a0b80004906990000000048c13342,192.168.130.101 # iscsiadm list static-config Static Configuration Target: iqn.1986-03.com.sun:2510.600a0b80004906990000000048c13342,192.168.130.101:3260 # format [intention is to check what is there now, before setting up drives on the 2510] Searching for disks...done c6t8d0: configured with capacity of 16.00MB AVAILABLE DISK SELECTIONS: 0. c1t0d0 raidboot /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 0,0 1. c1t3d0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 3,0 2. c6t8d0 /iscsi/disk at 0000iqn.1986-03.com.sun%3A2510.600a0b80004906990000000048c13342FFFF,31 Specify disk (enter its number): 2 selecting c6t8d0 [disk formatted] Disk not labeled. Label it now? no partition> p Current partition table (default): Total disk cylinders available: 8 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 root wm 0 0 (0/0/0) 0 1 swap wu 0 0 (0/0/0) 0 2 backup wu 0 - 7 16.00MB (8/0/0) 32768 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 usr wm 0 - 7 16.00MB (8/0/0) 32768 7 unassigned wm 0 0 (0/0/0) 0 partition> q [hmm. ??? What is that 16MB Thingy ???] -- *Set up hosts & disks* -- OK. Getting there. Now I have to configure the hosts and disks on the 2510 so that the disks will be linked to the host where I want to mount and format them (the T5220). This is where the Installation Guide drops the ball, just saying, "Follow CAM documentation to: ...." The CAM documentation, in turn, doesn't give a conceptual overview, assumes you are using the GUI (which will automate a bunch of stuff), and doesn't say much about iSCSI. This is where I found "Sun StorageTek 2540 / ZFS Performance Summary" by Bob Friesenhahn (http://www.simplesystems.org/users/bfriesen/zfs-discuss/2540-zfs-performance.pdf), which describes setting up the 2540 to present each drive as a separate unit. That gave me enough conceptual overview and detail to then mine my pdf print of the man page for sscs and work out the commands to do it. The basic overview is to create a separate storage pool for each disk. Create a separate volume for each disk within its own separate storage pool. Then link those to a host and set it up in zfs. He was dealing with fiber channel and multipathing, but that doesn't matter. The CAM concepts are the same. First, just some housekeeping. Mining the pdf man page, (& some trial and error) . . . # ./sscs list -a edsel date Date: Tue Sep 15 12:29:58 2009 # ./sscs modify -a edsel date 1755 # ./sscs list -a edsel date Date: Tue Sep 15 17:55:16 2009 # ./sscs list -a edsel os-type SOLARIS_MPXIO - Solaris (with Traffic Manager) [rest of output clipped] # ./sscs create -a edsel host marlin # ./sscs create -a edsel host snapper # ./sscs create -a edsel -h marlin -o solaris -i iqn.1986-03.com.sun:01:00212813a10c.49188968 initiator marlin [creating a couple of hosts and an initiator for the one host, naming the host and the initiator with the same name] # ./sscs list -a edsel disk Tray: 85 Disk: t85d05 Capacity: 279.396 GB Type: SAS Speed (RPM): 15000 Status: Optimal State: Enabled Role: Unassigned Virtual Disk: - Firmware: SA04 Serial number: 000809C69Y7C J8W69Y7C WWN: 50:00:CC:A0:05:43:DC:38 [clipping a bunch of output] Tray: 85 Disk: t85d01 Capacity: 279.396 GB Type: SAS Speed (RPM): 15000 Status: Optimal State: Enabled Role: Unassigned Virtual Disk: - Firmware: SA04 Serial number: 000809C090LC J8W090LC WWN: 50:00:CC:A0:05:38:E5:70 # ./sscs list -a edsel profile Profile: Default # ./sscs list -a edsel profile Default Profile: Default Profile In Use: yes Factory Profile: yes Description: Pre-configured Default profile RAID Level: 5 Segment Size: 512 KB Read Ahead: on Optimal Number of Drives: variable Disk Type: Fibre Channel Dedicated Hot Spare: no Pool: Default Pool: disk1 [hmm. That just won't do. I wonder why they put that on the 2510 as the default profile? So, create a new profile.] # ./sscs create -a edsel -r 0 -s 128K -h on -n 1 -k SAS -H no -d "One SAS disk" profile RAW_SAS [That took a fair bit of trial and error, but it worked. Now create a bunch of pools using that profile.] # ./sscs create -a edsel -p RAW_SAS pool Disk-01 # ./sscs create -a edsel -p RAW_SAS pool Disk-02 # ./sscs create -a edsel -p RAW_SAS pool Disk-03 [etc.] # ./sscs list -a edsel pool Pool: Disk-01 Profile: RAW_SAS Configured Capacity: 0.000 MB Pool: Disk-02 Profile: RAW_SAS Configured Capacity: 0.000 MB Pool: Disk-03 Profile: RAW_SAS Configured Capacity: 0.000 MB [clipped] # ./sscs list -a edsel pool Disk-01 Pool: Disk-01 Description: null Profile: RAW_SAS Total Capacity: 0.000 MB Configured Capacity: 0.000 MB Available Capacity: 278.896 GB [cool. Now create the corresponding volumes.] # ./sscs create -a edsel -p Disk-01 -s 278.896gb -d t85d01 volume Disk-01 # ./sscs list -a edsel pool Disk-01 Pool: Disk-01 Description: null Profile: RAW_SAS Total Capacity: 278.895 GB Configured Capacity: 278.895 GB Available Capacity: 278.896 GB Volume: Disk-01 # ./sscs list -a edsel volume Disk-01 Volume: Disk-01 Type: Standard WWN: 60:0A:0B:80:00:49:06:99:00:00:02:26:4A:B0:EF:52 Pool: Disk-01 Profile: RAW_SAS Virtual Disk: 1 Size: 278.895 GB State: Free Status: Online Action: Initializing... Condition: Optimal Read Only: No Controller: A Preferred Controller: A Modification Priority: High RAID Level: 0 Segment Size: 128 KB Read Cache: Enabled Write Cache: Enabled Write Cache with Replication: Disabled Write Cache without Batteries: Disabled Write Cache Active: True Flush Cache After: 10 s Disk Scrubbing: Enabled Disk Scrubbing with Redundancy: Disabled # ./sscs create -a edsel -p Disk-02 -s 278.896gb -d t85d02 volume Disk-02 # ./sscs create -a edsel -p Disk-03 -s 278.896gb -d t85d03 volume Disk-03 [and so on] [Finally, map the volumes to the host.] # ./sscs map -a edsel -P readwrite -h marlin volume Disk-01 # ./sscs map -a edsel -P readwrite -h marlin volume Disk-02 [etc.] -- *Create iSCSI device link & format drives* -- That's basically it for setting up the 2510. Now, from the T5220's perspective, I have to set up the iSCSI device links. This is straight from the Installation Guide. # devfsadm -i iscsi # format Searching for disks...done c6t8d0: configured with capacity of 16.00MB c7t600A0B8000490699000002264AB0EF52d0: configured with capacity of 275.99GB c7t600A0B8000490699000002284AB0EFB6d0: configured with capacity of 275.99GB [clipped] AVAILABLE DISK SELECTIONS: 0. c1t0d0 raidboot /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 0,0 1. c1t3d0 /pci at 0/pci at 0/pci at 2/scsi at 0/sd at 3,0 2. c6t8d0 /iscsi/disk at 0000iqn.1986-03.com.sun%3A2510.600a0b80004906990000000048c13342FFFF,31 3. c7t600A0B8000490699000002264AB0EF52d0 /scsi_vhci/ssd at g600a0b8000490699000002264ab0ef52 4. c7t600A0B8000490699000002284AB0EFB6d0 /scsi_vhci/ssd at g600a0b8000490699000002284ab0efb6 [clipped] Specify disk (enter its number): 3 selecting c7t600A0B8000490699000002264AB0EF52d0 [disk formatted] Disk not labeled. Label it now? no > quit -- *ZFS* -- So, I'm basically home free now, and I can configure ZFS using the information from the format command. Something like, . . . # zpool create mypool raidz c7t600A0B8000490699000002264AB0EF52d0 [and so on] I also tried setting up email notification, but I don't know if it works. # ./sscs add -e hoogendyk at marlin.mor.net.nsm -m minor notification local_email [which doesn't match the man page, but rather is based on the error messages I got when I entered it according to the man page] -- *in Closing* -- I hope this extended howto turns out to be helpful to someone else. I had a fair bit of trouble finding the information that made this possible and working out the details. It should have been more elementary than that. The Sun sales people said, "sure, you can do that." Then, since we aren't doing things according to their book, it's hard to actually get support and guidance. It is sort of like when you want to do a Solaris install and minimize the OS for security purposes. They actually have a security white paper (somewhat dated now) recommending that. However, it isn't SOP. So you can't get support when you try to do that. Even in a room full of Solaris people and several Sun engineering types (at an OpenSolaris Users Group meeting), they just shrug and say, "do a standard install." Anyway, if your purpose is to use ZFS, and you really just want a JBOD, I would recommend the J4200 and related products over the StorageTek 25xx. I think my multipathed dual SAS J4200 is much faster than my non-multipathed single GigE connection 2510, and it was much easier to set up. I haven't actually done I/O tests yet. We had originally thought we were going to share drives off the 2510 between a couple of servers and maybe even mount them read-only to our backup server, but that's not really possible. Even though it can sit on a network, the drives are basically owned and formatted by a single server. It's probably easier and more featurefull to just have a SAS JBOD, maybe with expansion trays, hanging on a single T5xxx server, using ZFS, and then share that out if other servers want access. Sort of build your own 7000 series. Comments appreciated. If I get comments, and it seems warranted, I'll post a summary-2. -- --------------- Chris Hoogendyk - O__ ---- Systems Administrator c/ /'_ --- Biology & Geology Departments (*) \(*) -- 140 Morrill Science Center ~~~~~~~~~~ - University of Massachusetts, Amherst --------------- Erdvs 4 _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From Zahid.Naqvi at acxiom.com Thu Sep 24 10:16:20 2009 From: Zahid.Naqvi at acxiom.com (Naqvi Zahid - znaqvi) Date: Thu, 24 Sep 2009 09:16:20 -0500 Subject: summary: Solaris 9 and NP value for passwd Message-ID: <6969396F8B05C24DB8DBA8B2A10F559E0A9EC98C@CWYMSX02.Corp.Acxiom.net> Common consensus is that on Solaris 9 you have to vi the shadow file and manually take out the encrypted password and insert NP. As the -N option only came with sol-10, and there is no other option in the password command to make a no password account. Thanks for all who offered their opinions. Zahid *************************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. **************************************************************************** _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From hoogendyk at bio.umass.edu Thu Sep 24 15:18:08 2009 From: hoogendyk at bio.umass.edu (Chris Hoogendyk) Date: Thu, 24 Sep 2009 15:18:08 -0400 Subject: SUMMARY - Multiple Power Supply Replacements in Sun E250 Message-ID: <4ABBC5F0.1000606@bio.umass.edu> Problem resolved. Original email at bottom. Thanks to Sean Walmsley, Francisco Roque, Paul Kraus, Bryan hodgson, Tim Bradshaw, Michael Horton, J.E., Todd A. Cox, and Joseph A. Belford. Todd nailed it, and a couple of others had pieces of the same puzzle. First I took the original "failed" power supplies and put them in a spare E250 that had been set up with adequate hardware components to run. They came up fine and continued to be fine for over 24 hours. Then we took an E250 that we had been gutting for parts and removed the Power Distribution Board (The E250 Owner's Manual has simple directions). Last night, around 8pm, my boss and I both came in, took down the server, replaced the power distribution board, and brought it back up. I had set the eeprom for diag-level=max before we took it down. It came up clean without any trouble. It has remained clean through today. Previously, we had incessant complaints in /var/adm/messages about power supply 1 having failed again. The only slight bit of difficulty we had was that there are a lot of cables connecting to the power distribution board. They all have to be disconnected and reconnected correctly, and where the excess hangs has to be out of the way of things that move during hot swap. First time we tried to slide a power supply back in, part of a cable loop had gotten in the way. We had to rearrange things and then try again. Note: in looking over the internals of several E250's, mostly in the direction of 10 years old, there was no sign of any of the capacitor swelling or leakage that we routinely see in low cost PCs. --------------- Chris Hoogendyk - O__ ---- Systems Administrator c/ /'_ --- Biology & Geology Departments (*) \(*) -- 140 Morrill Science Center ~~~~~~~~~~ - University of Massachusetts, Amherst --------------- Erdvs 4 -------- Original Message -------- Subject: Multiple Power Supply Replacements in Sun E250 Date: Mon, 21 Sep 2009 16:19:49 -0400 From: Chris Hoogendyk To: Sun Managers List I'm tossing this to the list because I'm sure there is something I'm missing here. We have a number of E250's that have been in operation for a number of years. We haven't had any trouble with any of them. A couple of years ago, we also took in 10 used E250's that were being discarded by another department on campus. We put 3 of them into operation, collecting parts from some of the others and adding new disk drives. The rest were set aside in our store room for scavenging. They've just been sitting there for a couple of years now. Now to the problem. Around the beginning of September we noticed a service light on the front of one our E250's. Turns out it was complaining that power supply 1 had faulted. That power supply showed AC in but no DC out on its indicator lights. So, we went back to our store room, pulled a power supply, and hotswapped it. Since the hotswapped supply had been in the off mode when it was put in, we had to turn the switch on the front of the E250 to diagnostic and back to run. That turned off the service light. Cool. That was Sept. 3. Then on the weekend of Sept. 12/13 there were 3 warnings in /var/adm/messages on Saturday night saying first that power supply 0 was faulting and then that power supply 1 was faulting. However, they seemed to be separated in time in some way so that it didn't take down the server. Then, on Sunday around 4pm, the server went down. The indicator lights pointed to power supply 0. My boss swapped that out. Weird. Then, same E250, started reporting power supply 1 faulted midweek the following week. We've been under an onslaught of other work, so we didn't notice it right away. Anyway, when we did notice it, I did an inventory of our stored E250's, picked the newest one based on serial numbers, that had been stored above ground level (paranoia about water leakage), and pulled its upper power supply 1, and replaced that for the "faulted 1" in our running E250. That gave us about 10 minutes of respite from the warnings. Then the warnings resumed, saying power supply 1 not ok. This just doesn't make sense. Is there something we are doing wrong? Is flipping the switch to diagnostic and back to run inadequate to really set the power supply to be in the on mode? Is there likely something more serious wrong with this E250? Should we be looking at swapping out the whole box? Have these additional power supplies just gone stale from sitting idle for a couple of years? And, can anyone give any guidance on how to authoritatively diagnose what the problem really is? This happens to be the one department that has the most trouble coming up with money for any kind of equipment updates/additions/repairs. Thanks, -- --------------- Chris Hoogendyk - O__ ---- Systems Administrator c/ /'_ --- Biology & Geology Departments (*) \(*) -- 140 Morrill Science Center ~~~~~~~~~~ - University of Massachusetts, Amherst --------------- Erdvs 4 _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From warren.liang at cox.net Fri Sep 25 13:55:06 2009 From: warren.liang at cox.net (Warren Liang) Date: Fri, 25 Sep 2009 13:55:06 -0400 Subject: SUMMARY: Install Sun Studio 11 Message-ID: <20090925135506.Q71VB.355468.imail@fed1rmwml42> Hello: I installed jdk1.5.0_16 and Sun Studio 11 installation completes successfully. Following is a rely from Sun Support: this is a known problem and it has come about because Sun Studio 11 was released a long time before Java SE 6 was released and hence it could not be certified for installation with Java SE 6. this is a known problem and it has come about because Sun Studio 11 was released a long time before Java SE 6 was released and hence it could not be certified for installation with Java SE 6. After Sun Studio 11 has succesfully installed with Java 1.4.2 or Java 5, you may use Java SE 1.6.0_11 for your other Java related activities. My original post: Entered # bzcat studio11-sol-sparc.tar.bz2 | tar xvf b /opt/Sun_Studio11# ./installer -nodisplay Installing Solaris patches |-1%--------------25%-----------------50%-----------------75%--------------10 0%| Installing Sun Studio Software Exception in thread "Thread-65" java.lang.NoClassDefFoundError: com/sun/install/panels/ComponentSelectionListener at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.getDeclaredMethod(Class.java:1935) b& The installation hangs. Thanks. Warren _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From Zahid.Naqvi at acxiom.com Thu Sep 24 16:02:23 2009 From: Zahid.Naqvi at acxiom.com (Naqvi Zahid - znaqvi) Date: Thu, 24 Sep 2009 15:02:23 -0500 Subject: summary: Solaris 9 and NP value for passwd In-Reply-To: <6969396F8B05C24DB8DBA8B2A10F559E0A9EC98C@CWYMSX02.Corp.Acxiom.net> Message-ID: <6969396F8B05C24DB8DBA8B2A10F559E0A9ECBAB@CWYMSX02.Corp.Acxiom.net> Correction, courtesy of John Horne. The -N option works for Sol-9 as well even though it is not listed in the man pages. So disregard the message below try the -N option to add the NP password (I knew SUN would never officially support vi'ing the shadow file) -----Original Message----- From: sunmanagers-bounces at sunmanagers.org [mailto:sunmanagers-bounces at sunmanagers.org] On Behalf Of Naqvi Zahid - znaqvi Sent: Thursday, September 24, 2009 9:16 AM To: sunmanagers at sunmanagers.org Subject: summary: Solaris 9 and NP value for passwd Common consensus is that on Solaris 9 you have to vi the shadow file and manually take out the encrypted password and insert NP. As the -N option only came with sol-10, and there is no other option in the password command to make a no password account. Thanks for all who offered their opinions. Zahid ************************************************************************ *** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. ************************************************************************ **** _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers From aluoor at gmail.com Tue Sep 29 12:50:26 2009 From: aluoor at gmail.com (Sven Aluoor) Date: Tue, 29 Sep 2009 18:50:26 +0200 Subject: SUMMARY: encryption files/folders with standard Solaris 10 tools (non-root user) Message-ID: <6317d8990909290950t46a919acy7b0d86200e4e52cf@mail.gmail.com> Hi folks thanks to all special good contributions from Francisco Roque (frisco at blackant.net): ------------------------- You can use openssl, and that will be as secure as the cipher you select. For example: $ openssl aes-128-cbc -e -out passwords.encrypted < passwords $ openssl aes-128-cbc -d -out passwords.unencrypted < passwords.encrypted ------------------------- and Todd A. Cox (toddc at ehsmed.com) ------------------------- This wouldn't be compatible with other zip programs (as far as I know), but you can encrypt any file with encrypt: zip -r test.zip testfolder cat test.zip | encrypt -a 3des -k mykey >test.zip.encrypted Or using tar: tar cf - testfolder | encrypt -a 3des -k mykey >test.tar.encrypted Then, use decrypt to decrypt. decrypt -a 3des -k mykey Date: Tue, Sep 29, 2009 at 4:17 PM Subject: Info-zip encryption on Solaris fails To: sunmanagers at sunmanagers.org Hi folks Howto encryt a file/folder on Solaris 10 (without root password)? $ zip -re test.zip testfolder zip error: Invalid command arguments (encryption not supported) cheers Sven _______________________________________________ sunmanagers mailing list sunmanagers at sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers