Sun Fire V120 as NAS part 8: Now with UFS filesystem (ZFS to UFS)

Before the summer I did a lot of test with a Sun Fire V120 Sparc server. At the time I used Solaris 10/09 installed in a 37GB disk and a ZFS array of three 18GB disk ia a Storedge S1. The results were bad in terms of network file transfer and I was thinking to reinstall everyrhin with a new UFS configuration.

Thats seems an easy job but The first step was so difficult: Solaris didn't want to changue the ZFS filesystem to UFS. After a lt of searching a I fund the good solution for Sparc Solaris (usually all the information was for x86 Solaris with a different format utility) here. Just a few steps are necessary.

1. We need to use the format utility once with each disc. Here how I re-labeled the first hd (SMI label needed):

# format -e c1t1d0
selecting c1t1d0
[disk formatted]

FORMAT MENU:
        disk       - select a disk
        type       - select (define) a disk type
        partition  - select (define) a partition table
        current    - describe the current disk
        format     - format and analyze the disk
        repair     - repair a defective sector
        label      - write label to the disk
        analyze    - surface analysis
        defect     - defect list management
        backup     - search for backup labels
        verify     - read and display labels
        inquiry    - show vendor, product and revision
        scsi       - independent SCSI mode selects
        cache      - enable, disable or query SCSI disk cache
        volname    - set 8-character volume name
        !     - execute , then return
        quit
format> label
[0] SMI Label
[1] EFI Label
Specify Label type[1]: 0
Auto configuration via format.dat[no]? no
format> quit
#

Now repeat with the next 4 hd's.

2. Partitioning is more complicated.

• Start the format utility: # format c1t1d0.
• Select in the menu: partition, an then  modify.
• Select All free hog:

Select partitioning base:

        0. Current partition table (unnamed)

        1. All Free Hog

Choose base (enter number) [0]? 1

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 - 7505       16.86GB    (7506/0/0) 35368272
  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               0         (0/0/0)           0
  7 unassigned    wm       0               0         (0/0/0)          

• At this stage we can change the partition sizes (this is a 18GB hd):

Do you wish to continue creating a new partition
table based on above table[yes]?
Free Hog partition[6]? 7
Enter size of partition '0' [0b, 0c, 0.00mb, 0.00gb]: 16gb
Enter size of partition '1' [0b, 0c, 0.00mb, 0.00gb]:
Enter size of partition '3' [0b, 0c, 0.00mb, 0.00gb]:
Enter size of partition '4' [0b, 0c, 0.00mb, 0.00gb]:
Enter size of partition '5' [0b, 0c, 0.00mb, 0.00gb]:
Enter size of partition '6' [0b, 0c, 0.00mb, 0.00gb]:


Part      Tag    Flag     Cylinders        Size            Blocks
  0       root    wm       0 - 7121       16.00GB    (7122/0/0) 33558864
  1       swap    wu       0               0         (0/0/0)           0
  2     backup    wu       0 - 7505       16.86GB    (7506/0/0) 35368272
  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               0         (0/0/0)           0
  7 unassigned    wm    7122 - 7505      883.50MB    (384/0/0)   1809408

Okay to make this the current partition table[yes]?
Enter table name (remember quotes): array

Ready to label disk, continue? yes

partition> quit
format> quit
#

3. Now is time to copy the partition table to the other hd's using:

# prtvtoc /dev/rdsk/c1t1d0s2 | fmthard -s - /dev/rdsk/c2t1d0s2

Here I had an small problem because one of the hard disks is different, also 18 GB and Seagate but different model. I had to do all the partitioning one more time but with the same zise partitions.

Total disk cylinders available: 14076 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
  0 unassigned    wm       0 - 13283       16.00GB    (13284/0/0) 33555384
  1 unassigned    wm       0                0         (0/0/0)            0
  2     backup    wu       0 - 14075       16.95GB    (14076/0/0) 35555976
  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 unassigned    wm       0                0         (0/0/0)            0
  7 unassigned    wm   13284 - 14072      973.15MB    (789/0/0)    1993014

4. This step is easy, copy the metadata:

# metadb -a -f c1t1d0s7 c2t1d0s7 c2t2d0s7 c2t3d0s7

5. And create the Raid 5 array!!!

# metainit d0 -r c1t1d0s0 c2t1d0s0 c2t2d0s0 c2t3d0s0
d0: RAID configurado (RAID is setup)

Now the array is created but is not ready. Using metastat several times we can check the status of the build:

# metastat d0
d0: RAID
    Estado: Inicializando
    Inicialización en progreso:  0.4% terminado
    Entrelazado: 32 bloques
    Tamaño: 100653032 bloques (47 GB)
Dispositivo original:
     Tamaño: 100657536 bloques (47 GB)
        Dispositivo   Bloque de in Base        Estado Reubi  Repuesto en marcha
        c1t1d0s0          5042        No Inicializand    Sí
        c2t1d0s0          5042        No Inicializand    Sí
        c2t2d0s0          2856        No Inicializand    Sí
        c2t3d0s0          5042        No Inicializand    Sí

Device Relocation Information:
Device   Reloc  Device ID
c1t1d0   Sí     id1,sd@SFUJITSU_MAN3184M_SUN18G_02Z33997____
c2t1d0   Sí     id1,sd@SFUJITSU_MAN3184M_SUN18G_02Z35960____
c2t2d0   Sí     id1,sd@SSGI_____ST318404LC______3BT2FCQL0000V121048Z
c2t3d0   Sí     id1,sd@SFUJITSU_MAN3184M_SUN18G_02Z35919____

6. Finished!!!

# metastat d0
d0: RAID
    Estado: Correcto
    Entrelazado: 32 bloques
    Tamaño: 100653032 bloques (47 GB)
Dispositivo original:
     Tamaño: 100657536 bloques (47 GB)
        Dispositivo   Bloque de in Base        Estado Reubi  Repuesto en marcha
        c1t1d0s0          5042        No     Correcto    Sí
        c2t1d0s0          5042        No     Correcto    Sí
        c2t2d0s0          2856        No     Correcto    Sí
        c2t3d0s0          5042        No     Correcto    Sí

Device Relocation Information:
Device   Reloc  Device ID
c1t1d0   Sí     id1,sd@SFUJITSU_MAN3184M_SUN18G_02Z33997____
c2t1d0   Sí     id1,sd@SFUJITSU_MAN3184M_SUN18G_02Z35960____
c2t2d0   Sí     id1,sd@SSGI_____ST318404LC______3BT2FCQL0000V121048Z
c2t3d0   Sí     id1,sd@SFUJITSU_MAN3184M_SUN18G_02Z35919____

7. When the array is finished we can create the filesystem (and wait a lot more time):

# newfs -i 8192 /dev/md/rdsk/d0
newfs: construir un nuevo sistema de archivos /dev/md/rdsk/d0: (y/n)? y 

Advertencia: 4120 sector(es) en el último cilindro sin asignar
/dev/md/rdsk/d0:        100653032 sectores en 16383 cilindros de 48 pistas, 128 sectores
        49147,0MB en 1024 grupos de cilindros (16 c/g, 48,00MB/g, 5824 i/g)
copias de seguridad super-bloque (para fsck -F ufs -o b=#) en:
 32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Inicializando grupos de cilindros:
....................
copias de seguridad del superbloque de los últimos 10 grupos de cilindros en:
 99687200, 99785632, 99884064, 99982496, 100080928, 100179360, 100277792, 100376224, 100474656, 100573088

Sorry, I installed Solaris in Spanish but....

9. Now we can mount the filesystem in a directory and it will be ready for use. The same name as my first atempt with ZFS:

# mkdir /fsshared
# mount -F ufs /dev/md/dsk/d0 /fsshared

10. The final step is to make the mount persistent.we need to insert a new line in the /etc/vfstab (data separated with tabs)

/etc/vfstab
#device         device          mount           FS      fsck    mount   mount
#to mount       to fsck         point           type    pass    at boot options
#
fd      -       /dev/fd fd      -       no      -
/proc   -       /proc   proc    -       no      -
/dev/dsk/c1t0d0s1       -       -       swap    -       no      -
/dev/dsk/c1t0d0s0       /dev/rdsk/c1t0d0s0      /       ufs     1       no
-
/dev/dsk/c1t0d0s7       /dev/rdsk/c1t0d0s7      /export/home    ufs     2
yes     -
/devices        -       /devices        devfs   -       no      -
sharefs -       /etc/dfs/sharetab       sharefs -       no      -
ctfs    -       /system/contract        ctfs    -       no      -
objfs   -       /system/object  objfs   -       no      -
/dev/md/dsk/d0  /dev/md/rdsk/d0 /fsshared       ufs     2       yes     -
swap    -       /tmp    tmpfs   -       yes     -

Sun Fire V120 as NAS part 7: Gigabit networking

Well, one week ago I received a new Sun Quad GigaSwift PCI card for this server. It's a full lenght PCI card with 64 bits PCI bus, but works in 32 bits PCI bus also.

As you can see in the pictures, the card installation is very easy. Only take out the blank bracket and the small grey plastic, then mount the card in th server slot. Finally return to set the grey plastic which locks the rear part of the GigaSiwft.

The network cards can be configured via the ifconfig utility in Solaris but to make this configurations stored we have to do some more file editting:

1.- The first step is to check if the server detects the GigaSwift card:

# grep ce /etc/path_to_inst
"/pci@1f,0/pci@1/pci@5/pci@0/network@0" 0 "ce"
"/pci@1f,0/pci@1/pci@5/pci@0/network@1" 1 "ce"
"/pci@1f,0/pci@1/pci@5/pci@4/network@2" 2 "ce"
"/pci@1f,0/pci@1/pci@5/pci@4/network@3" 3 "ce"

2.- Second step: create the /etc/hostname.ce0 file containing the name of the server. This name can't be the same in two different ethernet ports. In the 100MB port I'm using v120 as hostname, now I added a 'g' to the name:

# cat /etc/hostname.ce0
v120g

ce0 is the instance number for the port I'm going to use. I only need one port of the four installed with this card. If we want to use more port, more hostname.ce'instance_number' are needed.

3.- Now we have to edit the /etc/inet/hosts file but the vi editor says it's write protected (and I'm doing it beeing root). Like other changes I did before, I uploaded this file to my laptop via FTP, modified with a text editor and then downloaded to the server.

# cd /etc/inet
# cp /export/home/admin/hosts .

# cat /etc/inet/hosts
#
# Internet host table
#
::1     localhost
127.0.0.1       localhost
192.168.2.120   v120    loghost
192.168.5.120   v120g
~

4.- With the two configuration files ready, the card can be turned on:

# ifconfig ce0 plumb 192.168.5.120 up

Unfortunately the trasfer speed is the same as the speed obtained with the 100MB onboard port. Yes, I know there is a lot of parameters to tune, but I will look on the next days. Another problem I found is that: with both Ethernet ports configured (onboard an GigaSwift), when I unplug the onboard port cable, I have a lot of problems to connect with the Gigaswift (well, I can't connect). I think this is because Solaris uses the main port to check against DNS server. Then, I disconfigured the onboard ethernet port:

1.- Unplumb the card:

# ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
ce0: flags=1000843 mtu 1500 index 2
        inet 192.168.5.120 netmask ffffff00 broadcast 192.168.5.255
        ether 0:3:ba:5c:2b:7d
eri0: flags=1000843 mtu 1500 index 3
        inet 192.168.2.120 netmask ffffff00 broadcast 192.168.2.255
        ether 0:3:ba:5c:2b:7d

# ifconfig eri0 unplumb

# ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
ce0: flags=1000843 mtu 1500 index 2
        inet 192.168.5.120 netmask ffffff00 broadcast 192.168.5.255
        ether 0:3:ba:5c:2b:7d

2.- Delete the /etc/hosts entry (I modified the file in my laptop):

# cd /etc/inet
# cp hosts hosts.old
# cp /export/home/admin/hosts .
# cat hosts

#
# Internet host table
#
::1     localhost
127.0.0.1       localhost
192.168.5.120   v120g   loghost

3. Delete the /etc/hostname.eri0 file (here I moved it):

# cd /etc
# ls hostname*
hostname.ce0   hostname.eri0
# mv hostname.eri0 hostname.ri0.old

4.- Unplumb the ethernet port (and reboot):

# ifconfig eri0 unplumb
# reboot

Now everything works good with only the GigaSwift port 0 attached to the network. Something that is killing me is the low speed transfer via FTP. I can only reach 4.5 MB/s. This is a very low value. While doing a file tranfer I checked the server status with iostat:

# iostat
   tty        sd0           sd3           sd16          sd17           cpu
 tin tout kps tps serv  kps tps serv  kps tps serv  kps tps serv   us sy wt id
   0    1   2   0    4  439   8   28  789   8   26  758   8   31   60 26  0 14

Here I can see that the CPU is hard working. Maybe all the calculations needed by Samba, ftp and the other services joined by the ZFS filesystem are eating a lot of resources. I think I will check to optimize the network parameters for play and then I will reformat the hard disks using SVM instead of ZFS.

P.D.: Do you know what is this? (Check picture)

Sun Fire V120 as NAS part 6: Network shares and RAM upgrade

Ok. Time to start some file sharing protocols.

First the easy part: NFS.
Solaris comes with NFS4 (backwards compatible with NFS2 and NFS3). Not very important in a normal home but in my case, this is the best option to share information with my SGI boxes. Only three steps are needed to start sharing, Fantastic!

1. Make writable to everybody the folder where I want to share. I use the same array than before:

# chmod 777 /fsshared

2. Add the share information to the file /etc/dfs/dfstab

#       Place share(1M) commands here for automatic execution
#       on entering init state 3.
#
#       Issue the command 'svcadm enable network/nfs/server' to
#       run the NFS daemon processes and the share commands, after adding
#       the very first entry to this file.
#
#       share [-F fstype] [ -o options] [-d ""] [resource]
#       .e.g,
#       share  -F nfs  -o rw=engineering  -d "home dirs"  /export/home2
share -F nfs -o rw -d "fsshared V120" /fsshared

3. Start sharing:

# shareall

The dfstab entry goes:

• -F nfs .- Type of sharing.
• -o rw .- The options. Here I only used read-write but there is a lot more (including loggin), but I just don't need.
• -d "fsshared V120" .- Obviously is only a comment.
• /fsshared .- Here comes the folder I want to export.

Here some captures from my Fuel mounting the exported folder of the Sun Fure V120:

Second part is SAMBA!
This is the standard Windows protocol. At the time the most important in any home or company. From a lot of time ago samba.org is publising the source code and it's widely used but all the test I did before (and some test done by friends) are telling Samba is slow, in Solaris and in Linux.

Configure Samba in Solaris is not as easy as I was thinking before to use it.
1. Check if Samba is installed. Well, installing Solaris with OEM option, Samba must be installed:

# /usr/sfw/sbin/smbd -V
Version 3.0.35

2. Now we have to create the smb.conf file. I copied the exampled provided with the Solaris installation:

# cd /etc/sfw
# cp smb.conf-example smb.conf

3. Edit the configuratin file. I modified three parts: The allowed ip ranges (my network subnet and localhost):

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
   hosts allow = 192.168.2. 127.

 Set the Windows workgroup name:

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = WORKGROUP

And the last one, the shared folder. I want the folder open read-write to everybody, then the guest ok option must be set and the guest only option must be removed! The docs says guest only is discarded with guest ok but in my case guest ok was discarded with both options in the configuration of the folder.

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
[public]
   path = /fsshared
   public = yes
   guest ok = yes
   writable = yes
   printable = no
   browseable = yes

4. Test the configuration file:

# /usr/sfw/bin/testparm

Load smb config files from /etc/sfw/smb.conf
Processing section "[homes]"
Processing section "[printers]"
Processing section "[public]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

5. Add a user to the Samba database:

#  /usr/sfw/bin/smbpasswd -a admin
New SMB password:
Retype new SMB password:
Added user admin.

6. The last part must be start the samba service:

# svcadm enable samba

----------------------------------------------------------------------------------------------------------
UPDATE: 2010/09/08
7. Now Samba is working but I can't see the computer in the Windows Explorer (or other smb bowsers): The last step is activate WINS:

# svcadm enable wins

Here you have the old post part (italic letter). NOT NECESSARY.
A new test showed that I don't need to do the next part. At the end 
but in my case it didn't work. After some googling I found this guide related to Solaris u4, and I followed. Samba didn't start and after a new search I found a fault in my smb.conf: I writed /fssaredc instead of the name of my shared folder.
Now I have two commands to start samba:

# svcadm enable samba:smbd
# svcadm enable samba:nmbd

End of the update
----------------------------------------------------------------------------------------------------------
But it's working:

And here comes the bad part. I only get 4.3 MB/s downloading the test file via FTP and 1.9 MB/s via Samba! The V120 is connected to my main router via a non manageable HP ProCurve gigabit switch and the client is a Dell Precsion 390 with the onboard Broadcom gigabit network chipset. I did some checks in the V120 network port configuration but I didn't find anything wrong. Well, I will check later. Anyway I have a Quad GigaSwift PCI card at the mail coming home.

RAM tests.
Thursday arrived some more RAM sticks, 4x1GB ECC registered sticks!!!

I did various test with different amount of memory: 512 MB (one stick that came with the server), 2 GB and 4 GB.

                                 512MB         2 GB        4GB

-----------------------------------------------------------------------

From RAID5 to system disk.      12.8 MB/s    17.8 MB/s   26.9 MB/s

From system disk to RAID5.      11.3 MB/s    18.6 MB/s   21.6 MB/s

From RAID5 to disk 2.           12,5 MB/s    20.9 MB/s   32.0 MB/s

I was expecting a great improvement from 512 MB to 2 Gb, but I also discovered a great rise in performance with 4 GB using the RAID5 array. Yes, ZFS needs a lot of memory!
Note that tests are done by hand and I only did the test one or two times but are enough for comparision. At least for me!

Sun Fire V120 as NAS part 5: Users, rows and some tips

Well, I had some problems with the screen rows (lines) when using the vi editor. Some time surfing the net later I found a good solution: the TERM environment variable. The /etc/profile script only can set this variable only in two ways: sun-color or sun:

(...)
if [ "$TERM" = "" ]
then
        if /bin/i386
        then
                TERM=sun-color
        else
                TERM=sun
        fi
        export TERM
(...)

This could be changed at the Solaris prompt typing:

# TERM=vt100
# export TERM

But with this commands the values are lost when the user logouts. Due all the connections to the server console or terminal will use a vt100 terminal simulator I decided to modify the /etc/profile script as follows:

(...)
if [ "$TERM" = "" ]
then
        if /bin/i386
        then
                TERM=sun-color
        else
                TERM=vt100
        fi
        export TERM
(...)

One problem solved. Go to the second one: with only the root account nobody can login into the server via ftp, smb or something like that. I decided to create an admin account like my linux servers:

# useradd -d /export/home/admin -m -s /bin/ksh -c admin admin
# passwd admin
New password:
(...)

Ok now I can open a FTP session. -d specifies the user folder, -s sets the shell he will use and -c specifies the full name of the user (use " to enclose the name if it has spaces). Obviously the las word is the account name.

Another problem I had was that the man pages were not working. Man seemed installed but not the documentation files. I tried adding the routes to the path but finally the solution is more easy: the package SUNWman was not installed while the package SUNWdoc was perfectly on the hard disk:

# cd /cdrom/sol_10_1009_sparc/Solaris_10/Product
# pkgadd -d . SUNWman

One more thing: How to complete shutdown (well in this server it means 'put the server on standby'):

# shutdown -y -g 0 -i 5

Sun Fire V120 as NAS part 2: SSM

Before I create a ZFS array I decided to check the RAID 5 software with the standard UFS configuration to get some performance results and, then, compare with a RAID-Z. But before everything, to install the Sun Storage Subsystem Manager 2.0 (SSM) is a good idea. This software monitors the status of the atthached StorEdge S1 SCSI array writing messages to the system log and can be accessed from diferent clients utside the main server.

The SSM can be downloaded form the Sun downloads page here or, like me, it can be installed with the CDROM supplied with the disk array.

Fortunately, the lasts versions of the Solaris operating system come with the Solaris Volume Manager (SVM) loaded by default and the cdrom is mounted as soon as the disc is in the drive:

# cd /cdrom/cdrom0
# ls
Copyright FR_Copyright License.ps Packages
# cd Packages
# ls
SUNWssmr SUNWssmu
# pkgadd -d /cdrom/cdrom0/Packages SUNWssmu SUNWssmr

Just type 'y' when the wizard ask to follow with the intallation. Now the status of the array can be followed with the help of the ssmadmin utility:

# /opt/SUNWssmu/bin/ssmadmin -view

At first time the server didn't show the status of my disk because I had the array turned off and for this reason the configuration file was bad. I have to recreated the disk configuration booting the system with thr '-r' flag at the ok prompt. To create a new one if you change any of the disk or insert a new one:

lom>poweroff
LOM event: +0h26m56s host power off
lom>bootmode forth
lom>poweron
lom>
LOM event: +0h27m19s host power on
ok setenv auto-boot? off
auto-boot? = false
ok reset-all

Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard
OpenBoot 4.0, 512 MB memory installed, Serial #56372093.
Ethernet address 0:3:ba:5c:2b:7d, Host ID: 835c2b7d.

ok boot -r
Boot device: /pci@1f,0/pci@1/scsi@8/disk@0,0:a File and args: -r
SunOS Release 5.10 Version Generic_141444-09 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.

v120 console login: root
password:

Last login: Mon Mar 29 21:10:49 on console
Mar 29 21:32:56 v120 login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.10 Generic January 2005

# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
0. c1t0d0
/pci@1f,0/pci@1/scsi@8/sd@0,0
1. c1t1d0
/pci@1f,0/pci@1/scsi@8/sd@1,0
2. c2t1d0
/pci@1f,0/pci@1/scsi@8,1/sd@1,0
3. c2t2d0
/pci@1f,0/pci@1/scsi@8,1/sd@2,0
4. c2t3d0
/pci@1f,0/pci@1/scsi@8,1/sd@3,0

# /opt/SUNWssmu/bin/ssmadmin -c /etc/opt/SUNWssmu/ssmon.conf
Reading configuration file: /etc/opt/SUNWssmu/ssmon.conf

Searching for disks...done.


NOTE: A disk drive must be physically installed in the
base target slot of each storage unit.

Press enter to continue:

Disks found on the system:

Disk
Number Bus Target Disk
1 1 0 c1t0d0s0
2 1 1 c1t1d0s0
3 2 1 c2t1d0s0
4 2 2 c2t2d0s0
5 2 3 c2t3d0s0


Please enter the disk number of the base target address of
the storage unit. NOTE: An asterisk denotes a selected disk.

Just press enter when finished: 3
Disks found on the system:

Disk
Number Bus Target Disk
1 1 0 c1t0d0s0
2 1 1 c1t1d0s0
* 3 2 1 c2t1d0s0
* 4 2 2 c2t2d0s0
* 5 2 3 c2t3d0s0


Please enter the disk number of the base target address of
the storage unit. NOTE: An asterisk denotes a selected disk.

Just press enter when finished:


The following disks have been selected:

/dev/rdsk/c2t1d0s0
/dev/rdsk/c2t2d0s0
/dev/rdsk/c2t3d0s0

Save configuration? (yes,no): yes


The SSM daemon must be stopped and restarted after re-creating
the configuration file. Use the /etc/init.d/ssmgmt script to
stop and start the daemon:
# /etc/init.d/ssmgmt stop
# /etc/init.d/ssmgmt start

# /etc/init.d/ssmgmt stop
stopping SSM server.
# /etc/init.d/ssmgmt start
starting SSM server.
ssmond: Failed to open message catalog.
#

You can see the error message but the SSM works nice:

# /opt/SUNWssmu/bin/ssmadmin -view
ssmond: Failed to open message catalog.

Number of S1-D130 Units: 1
Critical Temperature Threshold: 60 Degrees Celsius
Warning Temperature Threshold: 50 Degrees Celsius

TIME: 29 de marzo de 2010 21:40:12 CEST
*****************************************************************

v120::S1-D130-1: Online
-------------------

DISK1[c2t1d0s0]:
Serial Number: 0224Z35960
Vendor: FUJITSU
Model: SUN18G
Status: Online
Current Temperature: 26 Degrees Celsius
DISK2[c2t2d0s0]:
Serial Number: 3BT2FCQL
Vendor: SGI
Model: C
Status: Online
DISK3[c2t3d0s0]:
Serial Number: 0224Z35919
Vendor: FUJITSU
Model: SUN18G
Status: Online
Current Temperature: 28 Degrees Celsius

#