Apuntes de Solaris

Desasignar System Board en 25k

2012-01-10T12:26:00.000-03:00

Para desasignar una System Board con el sistema operativo ejecutandose, realizar desde la system controller :
**** OJO que esto me freeza el Sistema Operativo por unos minutos ***
e25k> deleteboard -c unconfigure SB12
System may be temporarily suspended, proceed
(yes/no)? yes
request suspend SUNW_OS
request suspend SUNW_OS done
request delete capacity (8 cpus)
request delete capacity (4194304 pages)
request delete capacity SB12 done
request offline SUNW_cpu/cpu384
request offline SUNW_cpu/cpu388
request offline SUNW_cpu/cpu385
request offline SUNW_cpu/cpu389
request offline SUNW_cpu/cpu386
request offline SUNW_cpu/cpu390
request offline SUNW_cpu/cpu387
request offline SUNW_cpu/cpu391
request offline SUNW_cpu/cpu384 done
request offline SUNW_cpu/cpu388 done
request offline SUNW_cpu/cpu385 done
request offline SUNW_cpu/cpu389 done
request offline SUNW_cpu/cpu386 done
request offline SUNW_cpu/cpu390 done
request offline SUNW_cpu/cpu387 done
request offline SUNW_cpu/cpu391 done
unconfigure SB12
unconfigure SB12 done
notify remove SUNW_cpu/cpu384
notify remove SUNW_cpu/cpu388
notify remove SUNW_cpu/cpu385

request offline SUNW_cpu/cpu389 done
request offline SUNW_cpu/cpu386 done
request offline SUNW_cpu/cpu390 done
request offline SUNW_cpu/cpu387 done
request offline SUNW_cpu/cpu391 done
unconfigure SB12
unconfigure SB12 done
notify remove SUNW_cpu/cpu384
notify remove SUNW_cpu/cpu388
notify remove SUNW_cpu/cpu385
notify remove SUNW_cpu/cpu389
notify remove SUNW_cpu/cpu386
notify remove SUNW_cpu/cpu390
notify remove SUNW_cpu/cpu387
notify remove SUNW_cpu/cpu391
notify remove SUNW_cpu/cpu384 done
notify remove SUNW_cpu/cpu388 done
notify remove SUNW_cpu/cpu385 done
notify remove SUNW_cpu/cpu389 done
notify remove SUNW_cpu/cpu386 done
notify remove SUNW_cpu/cpu390 done
notify remove SUNW_cpu/cpu387 done
notify remove SUNW_cpu/cpu391 done
notify capacity change (8 cpus)
notify capacity change (4194304 pages)
notify capacity change SB12 done
notify resume SUNW_OS
notify resume SUNW_OS done
e25k>

Del lado del sistema operativo ( parado en la consola) muestra estos mensajes ( me freezo unos 5 o 10 minutos el OS )
root@psun5ads #
DR: suspending user threads...

DR: checking devices...
DR: suspending drivers...
suspending scsa,00.bvhci@g60050768019901b400000000000004dd (aka ssd)
suspending scsa,00.bvhci@g60050768019901b400000000000004e1 (aka ssd)
suspending scsa,00.bvhci@g60050768019901b400000000000004e0 (aka ssd)
suspending scsa,00.bvhci@g60050768019901b400000000000004df (aka ssd)
suspending scsa,00.bvhci@g60050768019901b400000000000004de (aka ssd)
suspending memory-controller@140,400000 (aka mc-us3)
suspending memory-controller@141,400000 (aka mc-us3)
suspending memory-controller@142,400000 (aka mc-us3)
suspending memory-controller@143,400000 (aka mc-us3)
suspending pci108e,c416@2 (aka sbbc)
suspending pci100b,35@0 (aka ce)
suspending pci100b,35@1 (aka ce)
suspending sd@8,0
suspending sd@9,0
suspending sd@a,0
suspending sd@b,0
suspending ses@5,0
suspending pci1000,b@2 (aka glm)
suspending pci1000,b@2,1 (aka glm)
suspending pciclass,060400@1 (aka pci_pci)
suspending pci108e,1101@3,1 (aka eri)
suspending pciclass,0c0310@3,3 (aka ohci)
suspending pciclass,060400@1 (aka pci_pci)
suspending pci108e,8002@15c,700000 (aka pcisch)
suspending pci108e,8002@15c,600000 (aka pcisch)
suspending pci100b,35@0 (aka ce)
suspending pci100b,35@1 (aka ce)
suspending pci100b,35@2 (aka ce)
suspending pci100b,35@3 (aka ce)
suspending pciclass,060400@1 (aka pci_pci)
suspending pci108e,8002@15d,700000 (aka pcisch)
suspending fp@0,0
suspending pci1077,2422@1 (aka qlc)
suspending scsiclass,01@w500507630f415635,0 (aka st)
suspending scsiclass,01@w500507630f415632,0 (aka st)
suspending scsiclass,01@w500507630f415643,0 (aka st)
suspending scsiclass,01@w500507630f415634,0 (aka st)
suspending scsiclass,01@w500507630f415644,0 (aka st)
suspending scsiclass,01@w500507630f415633,0 (aka st)
suspending pci1077,2422@1,1 (aka qlc)
suspending pci108e,8002@15d,600000 (aka pcisch)
suspending memory-controller@180,400000 (aka mc-us3)
suspending memory-controller@181,400000 (aka mc-us3)
suspending memory-controller@182,400000 (aka mc-us3)
suspending memory-controller@183,400000 (aka mc-us3)
suspending pci108e,c416@2 (aka sbbc)
suspending pci108e,1101@3,1 (aka eri)
suspending pciclass,0c0310@3,3 (aka ohci)
suspending pciclass,060400@1 (aka pci_pci)
suspending pci108e,8002@19c,700000 (aka pcisch)
suspending pci108e,8002@19c,600000 (aka pcisch)
suspending pci108e,8002@19d,700000 (aka pcisch)
suspending fp@0,0
suspending pci1077,2422@1 (aka qlc)
suspending fp@0,0
suspending pci1077,2422@1,1 (aka qlc)
suspending pci108e,8002@19d,600000 (aka pcisch)
suspending wrsm@ffff,0
suspending wrsm@100
suspending wrsm@101
suspending wrsm@102
suspending wrsm@103
suspending wrsm@104
suspending wrsm@105
suspending wrsm@106
suspending wrsm@107
suspending wrsm@108
suspending wrsm@109
suspending wrsm@110
suspending wrsm@111
suspending wrsm@112
suspending wrsm@113
suspending wrsm@114
suspending wrsm@115
suspending iosram@10,900000 (aka iosram)
suspending iosram@10,900000 (aka iosram)
suspending SUNW,axq@15e,0 (aka axq)
suspending SUNW,axq@15f,0 (aka axq)
suspending SUNW,axq@19e,0 (aka axq)
suspending SUNW,axq@19f,0 (aka axq)
resuming SUNW,axq@19f,0 (aka axq)
resuming SUNW,axq@19e,0 (aka axq)
resuming SUNW,axq@15f,0 (aka axq)
resuming SUNW,axq@15e,0 (aka axq)
resuming iosram@10,900000 (aka iosram)
resuming iosram@10,900000 (aka iosram)
resuming wrsm@115
resuming wrsm@114
resuming wrsm@113
resuming wrsm@112
resuming wrsm@111
resuming wrsm@110
resuming wrsm@109
resuming wrsm@108
resuming wrsm@107
resuming wrsm@106
resuming wrsm@105
resuming wrsm@102
resuming wrsm@101
resuming wrsm@100
resuming wrsm@ffff,0
resuming pci108e,8002@19d,600000 (aka pcisch)
resuming pci1077,2422@1,1 (aka qlc)
resuming fp@0,0
resuming pci1077,2422@1 (aka qlc)
resuming fp@0,0
resuming pci108e,8002@19d,700000 (aka pcisch)
resuming pci108e,8002@19c,600000 (aka pcisch)
resuming pci108e,8002@19c,700000 (aka pcisch)
resuming pciclass,060400@1 (aka pci_pci)
resuming pciclass,0c0310@3,3 (aka ohci)
resuming pci108e,1101@3,1 (aka eri)
resuming pci108e,c416@2 (aka sbbc)
resuming memory-controller@183,400000 (aka mc-us3)
resuming memory-controller@182,400000 (aka mc-us3)
resuming memory-controller@181,400000 (aka mc-us3)
resuming memory-controller@180,400000 (aka mc-us3)
resuming pci108e,8002@15d,600000 (aka pcisch)
resuming pci1077,2422@1,1 (aka qlc)
resuming fp@0,0
resuming scsiclass,01@w500507630f415642,0 (aka st)
resuming scsiclass,01@w500507630f415641,0 (aka st)
resuming scsiclass,01@w500507630f415631,0 (aka st)
resuming scsiclass,01@w500507630f415645,0 (aka st)
resuming scsiclass,01@w500507630f415633,0 (aka st)
resuming scsiclass,01@w500507630f415644,0 (aka st)
resuming scsiclass,01@w500507630f415634,0 (aka st)
resuming scsiclass,01@w500507630f415643,0 (aka st)
resuming pci1077,2422@1 (aka qlc)
resuming fp@0,0
resuming pci108e,8002@15d,700000 (aka pcisch)
resuming pciclass,060400@1 (aka pci_pci)
resuming pci100b,35@3 (aka ce)
resuming pci100b,35@2 (aka ce)
resuming pci100b,35@1 (aka ce)
resuming pci100b,35@0 (aka ce)
resuming pci108e,8002@15c,600000 (aka pcisch)
resuming pci108e,8002@15c,700000 (aka pcisch)
resuming pciclass,060400@1 (aka pci_pci)
resuming pciclass,0c0310@3,3 (aka ohci)
resuming pci108e,1101@3,1 (aka eri)
resuming pciclass,060400@1 (aka pci_pci)
resuming pci1000,b@2,1 (aka glm)
resuming pci1000,b@2 (aka glm)
resuming ses@5,0
resuming sd@b,0
resuming sd@a,0
resuming sd@9,0
resuming sd@8,0
resuming pci100b,35@1 (aka ce)
resuming pci100b,35@0 (aka ce)
Jan 9 20:33:11 psun5ads eri: SUNW,eri0 : No response from Ethernet network : Link down -- cable problem?
Jan 9 20:33:29 psun5ads eri: SUNW,eri1 : 100 Mbps half duplex link up
resuming pci108e,c416@2 (aka sbbc)
resuming memory-controller@143,400000 (aka mc-us3)
resuming memory-controller@142,400000 (aka mc-us3)
resuming memory-controller@141,400000 (aka mc-us3)
resuming memory-controller@140,400000 (aka mc-us3)
resuming scsa,00.bvhci@g60050768019901b400000000000004de (aka ssd)
resuming scsa,00.bvhci@g60050768019901b400000000000004df (aka ssd)
resuming scsa,00.bvhci@g60050768019901b400000000000004e0 (aka ssd)
resuming scsa,00.bvhci@g60050768019901b400000000000004e1 (aka ssd)
resuming scsa,00.bvhci@g60050768019901b400000000000004dd (aka ssd)
DR: resuming user threads...
Jan 9 20:33:49 psun5ads scsi: ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
DR: resume COMPLETED
Jan 9 20:33:57 psun5ads dman: NOTICE: dman0 Link up

Luego , desde la SC con un showboards -d F ( donde F es el dominio que le voy a sacar la SB )
SB12 On V3CPU Active Passed F

e25k-5-sc0:sms-svc:12> deleteboard SB12

disconnect SB12
disconnect SB12 done
poweroff SB12
poweroff SB12 done
SB12 successfully unassigned.
e25k-5-sc0:sms-svc:13>
showboards -d F ( recien ahora muestra la SB12 apagada y lista para ser usada o extraida )
SB12 Off V3CPU Available Unknown Isolated

Un saludo para cerrar este año 2011

2011-12-29T12:05:00.000-03:00

Para cerrar este año 2011, quiero mostrar un orgullo y satisfaccion personal que fue la mencion de mi blog en la web de oracle.

Favorite Bloggers of OTN Latin America

By rickramsey on Sep 06, 2011

image courtesy of wikipedia

By now you've probably heard of OTN Latinoamerica, the Spanish- and Portuguese-language version of the Oracle Technology Network. It provides resources similar to those on the English-language version, but in the local languages. And it focuses on the needs of Latin America's OTN members.

They just had an update worthy of noting: their list of favorite bloggers. It categorizes Spanish- and Portuguese-language bloggers by application and region. If you live or work in Latin America, or just want to read something in your native language. Check it out.

And, if you're interested in Oracle Solaris, be sure to check out Apuntes de Solaris, Diego Aguirre's blog. Diego brought this list of bloggers to my attention.

- Rick

La mencion de este Blog en Oracle Technology Network

http://www.oracle.com/technetwork/es/index.html

Algunos Articulos tecnicos publicados

http://www.oracle.com/technetwork/es/articles/index.html

Articulos tecnicos para Administradores de Sistemas

http://www.oracle.com/technetwork/es/articles/servers-storage-admin/configurar-sun-cluster-3-2-rac-asm-521494-esa.html

Quiero Agradecer por toda la ayuda y buena onda y predisposicion a las siguientes personas:

Rick Ramsey ( un genio)

Pablo Ciccarello ( por la buena onda )

Nicolas Morono ( compañero de trinchera )

Carlos Lazarte ( un referente en Solaris )

Migrar / Clonar disco de Sistema Operativo Solaris

2011-12-20T08:49:00.000-03:00

Procedmiento realizado por Nicolas Morono, para migrar / clonar un solaris 10 con ufsdump | ufsrestore.
Despues de varios intentos el resultado final es este.

bootear de cdrom o de red ( boot cdrom -s o boot net -s)

#con format generar los slice de los discos para el / y para el swap y crear el fs

newfs /dev/dsk/c0t8d0s0

#configurar la ip y agregar ruta para poder montar por nfs la imagen a restorear.

ifconfig ce2 10.77.100.124 netmask 255.255.255.0

route add default 10.77.100.1

mount 10.11.33.114:/BACKUPS /mnt

mount /dev/dsk/c0t8d0s0 /a

cd /a

ufsrestore -rf /mnt/exdsunp002/BARRA.DMP

#### Selectivamente modificamos los archivos de configuracion necesarios

/mnt/etc/hosts

/mnt/etc/hostname.*

/mnt/etc/nodename

/mnt/etc/vfstab

/mnt/etc/shadow

/mnt/etc/netmasks

/mnt/etc/defaultrouter

/a/usr/sbin/installboot /a/usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t8d0s0

cd /

umount /a

init 0

#### Aca viene lo complicado

### Booteamos en failsafe ( Esta opcion funciona con los ultimos release de solaris 10 )

boot rootdisk -F failsafe

nos deberia de reconocer el disco y montarlo en /a

rm -rf /a/devices/*

rm -rf /a/dev/*

rm -rf /a/dev/.*

cp -p /tmp/root/etc/path_to_inst /a/etc/

devfsadm -r /a -p /a/etc/path_to_inst

init 0

boot -r

Importante: Recordar que en OBP este seteado correctamente el boot-device

Que Servidores usan ILOM, ALOM4v, ALOM, LOM, ELOM, SP o RSC

2011-12-01T11:15:00.000-03:00

Aca va una lista de equipos ,de un articulo tecnico de Sun, con cuales sistemas usan ILOM/ALOM4v/ALOM/LOM/ELOM/SP o RSC.

LOM
Sun Netra[TM] X1
Sun Netra[TM] T1400/1405
Sun Netra[TM] T1 AC200
Sun Netra[TM] T1 DC200
Sun Fire[TM] V100
Sun Fire[TM] V120
Sun Fire[TM] E2900
Sun Netra[TM] 20
Sun Fire[TM] V1280

ALOM
Sun Fire[TM] V125
Sun Fire[TM] V210
Sun Fire[TM] V215
Sun Fire[TM] V240
Sun Fire[TM] V245
Sun Fire[TM] V250
Sun Fire[TM] V440
Sun Fire[TM] V445

ALOM4v
Sun Fire[TM] T1000
Sun Fire[TM] T2000
Sun SPARC[TM] Enterprise T1000
Sun SPARC[TM] Enterprise T2000
Sun Netra[TM] T2000
Sun Blade[TM] T6300

ILOM
Sun Fire[TM] X4100
Sun Fire[TM] X4200
Sun Fire[TM] X4500
Sun Fire[TM] X4600
Sun Fire[TM] X4100 M2
Sun Fire[TM] X4200 M2
Sun Fire[TM] X4600 M2
Sun Blade[TM] 6000
Sun Blade[TM] 8000
Sun Netra[TM] X4200 M2
Sun SPARC[TM] Enterprise T5120
Sun SPARC[TM] Enterprise T5220
Sun Blade[TM] X6220
Sun Blade[TM] T6320

ELOM
Sun Fire[TM] X2100 M2
Sun Fire[TM] X2200 M2
Sun Blade[TM] X6250
Sun Blade[TM] X6450

SP
Sun Fire[TM] V20z
Sun Fire[TM] V40z

RSC
Sun Fire[TM] V890
Sun Fire[TM] V490
Sun Fire[TM] V880
Sun Fire[TM] V480
Sun Fire[TM] 280R
Sun Enterprise[TM] 250

Solaris 2.6 a un Solaris 10 con container con solaris 8... Si, se puede.

2011-11-18T10:21:00.000-03:00

Equipo Origen :
Enterprise 450 con solaris 2.6
Discos Internos
Oracle 8.1.5
Connect Direct 3303
Java 1.3

Equipo Destino :
Dominio de 25k solaris 10 release 09/10
Parches del EIS-DVD marzo 2011
Discos Internos Mirroreados con SVM
Storage Externo manejados con Veritas 5.0 Service Pack 3

Por obsolesencia de hardware y Software, tuvimos que migrar/upgradear del equipo origen (descripto mas arriba en este documento) al nuevo Hardware y Software.
Instale desde la imagen de un ufsdump deun equipo con solaris 8, una branded zone, en el equipo con la global con solaris 10.
Luego en la zona con solaris 8, pase con un ufsdump|ufsrestore remoto, pase del equipo origen a esta zona, los filesystems que contienen el motor de oracle, los datafiles y el connect direct.
Probamos levantar la base de datos, y la misma, funciono perfecto.
Probamos el Connect Direct con el mismo resultado.Antes tuve que modificarle a la zona con solaris 8, el hostid y cambiarlo por el que tenia el viejo equipo (esto es porque el Connect Direct, licencia por hostid)
El primer inconveniente que tuve, fue que el /etc/TIMEZONE estaba seteado en GMT-3 y la hora real estaba 6 horas adelantada.
Quize levantar el xntpd pero cuando se instala la braded zone, el script p2v ( physical to virtual) modifica el script de inicio del xntpd y no lo deja levantar.
Asi que fui por lo que pense que era la mejor opcion... compilarle un huso horario nuevo, con el comando /usr/sbin/zic

A continuacion, el paso a paso para la instalacion de la zona con solaris 8, el cambio de hostid, y la compilacion del nuevo huso horario.

root@GlobalZone # zonecfg -z ZONA1
ZONA1: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:ZONA1> create -t SUNWsolaris8
zonecfg:ZONA1> set zonepath=/export/zona1
zonecfg:ZONA1> set autoboot=true
zonecfg:ZONA1> add net
zonecfg:ZONA1:net> set address=10.XX.33.90
zonecfg:ZONA1:net> set physical=ce2
zonecfg:ZONA1:net> end
zonecfg:ZONA1>
zonecfg:ZONA1> exit
solaris8_support error: The Solaris 8 Containers right-to-use package
has not been installed
ZONA1: Brand-specific error
Configuration not saved; really quit (y/[n])? y
root@GlobalZone #
*******Cuando me dio ese error le instale este paquete
root@GlobalZone # ls
SUNWs8brandk
root@GlobalZone # pkgadd -d .

The following packages are available:
1 SUNWs8brandk Solaris 8 Containers: solaris8 brand support RTU
(sparc) 11.10.0,REV=2008.09.20.18.50

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:

Processing package instance from

Solaris 8 Containers: solaris8 brand support RTU(sparc) 11.10.0,REV=2008.09.20.18.50

Use is subject to license terms.

Using as the package base directory.

## Processing package information.

## Processing system information.

8 package pathnames are already properly installed.

## Verifying package dependencies.

## Verifying disk space requirements.

## Checking for conflicts with packages already installed.

The following files are already installed on the system and are being

used by another package:

/usr/share/man/man5/solaris8.5

Do you want to install these conflicting files [y,n,?,q] y

## Checking for setuid/setgid programs.

Installing Solaris 8 Containers: solaris8 brand support RTU as

## Installing part 1 of 1.

/usr/lib/brand/solaris8/files/patches/109147-44.zip

/usr/lib/brand/solaris8/files/patches/109221-01.zip

/usr/lib/brand/solaris8/files/patches/111023-03.zip

/usr/lib/brand/solaris8/files/patches/111431-01.zip

/usr/lib/brand/solaris8/files/patches/112050-04.zip

/usr/lib/brand/solaris8/files/patches/112605-04.zip

/usr/lib/brand/solaris8/files/patches/order

/usr/share/man/man5/solaris8.5

[ verifying class ]Installation of was successful.

root@GlobalZone #

y luego la volvi a crear y salio joya

root@GlobalZone # zonecfg -z ZONA1

ZONA1: No such zone configured

Use 'create' to begin configuring a new zone.

zonecfg:ZONA1> create -t SUNWsolaris8

zonecfg:ZONA1> set zonepath=/export/zona1

zonecfg:ZONA1> set autoboot=true

zonecfg:ZONA1> add net

zonecfg:ZONA1:net> set address=10.XX.33.90

zonecfg:ZONA1:net> set physical=ce2

zonecfg:ZONA1:net> end

zonecfg:ZONA1> exit

root@GlobalZone #

root@GlobalZone # zoneadm list -cv

ID NAME STATUS PATH BRAND IP

0 global running / native shared

- ZONA1 configured /export/zona1 solaris8 shared

root@GlobalZone # chmod 700 /export/zona1

root@GlobalZone #

root@GlobalZone # zoneadm -z ZONA1 install -p -v -a /mnt/solaris8/BARRA.DMP

Log File: /var/tmp/ZONA1.install.9915.log

Product: Solaris 8 Containers 1.0

Installer: solaris8 brand installer 1.3

Zone: ZONA1

Path: /export/zona1

Source: /mnt/solaris8/BARRA.DMP

Media Type: ufsdump archive Installing: This may take several minutes...

Postprocess: Gathering information about zone ZONA1

Postprocess: Creating mount points

Postprocess: Processing /etc/system

Postprocess: Booting zone to single user mode

Postprocess: Applying p2v module S20_apply_patches

S20_apply_patches: Unpacking patch: 109147-44

S20_apply_patches: Installing patch: 109147-44

S20_apply_patches: Unpacking patch: 111023-03

S20_apply_patches: Installing patch: 111023-03

S20_apply_patches: Unpacking patch: 111431-01

S20_apply_patches: Installing patch: 111431-01

S20_apply_patches: Unpacking patch: 112605-04

S20_apply_patches: Installing patch: 112605-04

S20_apply_patches: Unpacking patch: 112050-04

S20_apply_patches: Installing patch: 112050-04

S20_apply_patches: Unpacking patch: 109221-01

S20_apply_patches: Installing patch: 109221-01

Postprocess: Applying p2v module S31_fix_net

Postprocess: Applying p2v module S32_fix_nfs

Postprocess: Applying p2v module S33_fix_vfstab

Postprocess: Applying p2v module S34_fix_inittab

Postprocess: Applying p2v module S35_fix_crontab

Postprocess: Applying p2v module S36_fix_pam_conf

Postprocess: Applying p2v module S40_setup_preload

Postprocess: Halting zone

Postprocess: Postprocessing successful.

Result: Postprocessing complete.

Service Tag: Gathering information about zone ZONA1

Service Tag: Adding service tag: urn:st:e8ea730c-8115-6af5-8e12-9590388aa6c6

Service Tag: Operation successful.

Result: Installation completed successfully.

Log File: /export/zona1/root/var/log/ZONA1.install.9915.log

root@GlobalZone #

Pasos realizados para cambiar el hostid en la zona.

root@GlobalZone # zonecfg -z ZONA1

zonecfg:ZONA1> add attr

zonecfg:ZONA1:attr> set name=hostid

zonecfg:ZONA1:attr> set type=string

zonecfg:ZONA1:attr> set value=80f05bad

zonecfg:ZONA1:attr> end

zonecfg:ZONA1> exit

root@GlobalZone #

Pasos realizados para cambiar el huso horario.

1) Crear en /var/tmp el archivo newbsas con el siguiente contenido

Zone America/Buenos_Aires -3:00 - ART 2011 Nov 15 00:00

-2:00 - ART

2) Luego se compila el archivo

/usr/sbin/zic /var/tmp/newbsas

No requiere reboot, el cambio es instantaneo

chequeo el archivo generado por la compilacion

ls -ltr /usr/share/lib/zoneinfo/America|grep Buen

date y date -u para terminar con los chequeos

y todos contentos.

Malditos Parches

2011-10-30T02:32:00.000-03:00

Tenia que actualizar los parches en Sun Solaris 10 release 1/06
Al intentar ejecutar el script install_all_patches, que viene en el DVD del EIS de marzo del 2011, el misma abortaba con el siguiente error.

Oct 30 01:03:35 2011
Oct 30 01:03:35 2011 This script will install the following patches:
Oct 30 01:03:35 2011 - Solaris 10 Recommended Patches
Oct 30 01:03:35 2011 - Solaris 10 Extra Patches
Oct 30 01:03:35 2011
Oct 30 01:03:35 2011 ONLY if your system has a graphics display:
Oct 30 01:03:35 2011 - You are advised not to have a graphics display active whilst patching!
Oct 30 01:03:35 2011 - Suggestion: Exit from CDE etc. & log back in on command line!
Oct 30 01:03:35 2011
Oct 30 01:03:44 2011 Are you ready to continue with install? [y/n]: y
Oct 30 01:03:44 2011
Oct 30 01:03:44 2011 ************************************************************
Oct 30 01:03:44 2011 ** INFO: Solaris 10 KU 118833-36 is currently installed. **
Oct 30 01:03:44 2011 ************************************************************
Oct 30 01:03:44 2011
Oct 30 01:03:44 2011 Now the Solaris 10 Recommended Patches...
Oct 30 01:03:44 2011
Oct 30 01:03:44 2011 ERROR: Target boot environment not validated as Solaris 10 by INST_RELEASE file.
Oct 30 01:03:44 2011 Failed

Oct 30 01:03:44 2011
Oct 30 01:03:44 2011 ***********************************************************************
Oct 30 01:03:44 2011 * Installation of the Recommended OS patch cluster failed (see above) *
Oct 30 01:03:44 2011 ***********************************************************************

La solucion es la siguiente, Modificar el archivo INST_RELEASE la primer linea,
donde dice OS=Solaris4 cambiarla por OS=Solaris
[coneja] /var/sadm/system/admin # cp INST_RELEASE INST_RELEASE.ANTESdeloParches
[coneja] /var/sadm/system/admin #
[coneja] /var/sadm/system/admin # ls -ltr
total 6
drwxr-xr-x 2 root sys 512 Nov 8 2006 services
-rw-r--r-- 1 root root 30 Nov 8 2006 INST_RELEASE
-rw-r--r-- 1 root root 18 Nov 8 2006 CLUSTER
[coneja] /var/sadm/system/admin # more INST_RELEASE
OS=Solaris_4 Reemplazar , esta linea por esta OS=Solaris
VERSION=10
REV=0
[coneja] /var/sadm/system/admin #

Tambien, puede o no pedirlo, en este caso el script se fija tambien si esta instalado el patch=118833-36 y en base a ese dato hace unas verificaciones, para que no chequee esto y siga su curso, sugiero sacarlo del script install_all_patches.
Y... va como Piña

Error al agregar una SB con DR.

2011-10-25T17:19:00.000-03:00

Habia que agregar una System Board a un dominio, con el sistema operativo levantado.
Al loguearnos a la SC, y querer asignar la SB12 al dominio coneja nos da un error de comunicacion, esto fue lo que hicimos, con Nico.
El Dominio tiene Solaris 10 y no hacia falta realizar un upgrade o downgrade de firmware porque la sb estaba instalada en otro dominio de la misma 25k.

e25k-2-sc0:sms-svc:18> addboard -d e sb12

ERROR: Unable to configure SB12 into domain: E
addboard: DCA/DCS communication error

Este error de comunicacion es porque no esta levantado el demonio dca en la System controler o el dcs en el dominio a asignar la SB.
Chequeo en la SC y efectivamente esta levantado
e25k-2-sc0:sms-svc:19> ps -ef|grep dca
sms-dca 130 696 0 Jan 12 ? 0:00 dca -d C
sms-dca 16160 696 0 Sep 27 ? 0:00 dca -d B
sms-dca 24394 696 0 Aug 19 ? 0:00 dca -d J
sms-dca 11039 696 0 Sep 10 ? 0:00 dca -d A
sms-dca 12590 696 0 Sep 13 ? 0:00 dca -d F
sms-dca 18983 696 0 Apr 10 ? 0:00 dca -d G
sms-dca 8266 696 0 Mar 09 ? 0:00 dca -d D
sms-dca 19674 696 0 May 31 ? 0:00 dca -d I
sms-dca 22635 696 0 Oct 13 ? 0:00 dca -d E

Dentro del equipo, el demonio estaba en estado maintenance

[coneja] # svcs -a|grep dcs
maintenance Sep_04 svc:/platform/sun4u/dcs:default
[coneja] #

Existe un bug al upgradear la versión de solaris (en 10/2010 habiamos instalado parches)

Solucion, borrar el servicio y volver a crearlo desde cero

[coneja] # inetadm -l dcs

SCOPE NAME=VALUE
Error: Required property name is missing.
Error: Required property endpoint_type is missing.
Error: Required property proto is missing.
Error: Required property isrpc is missing.
Error: Required property wait is missing.
Error: Required property exec is missing.
Error: Required property user is missing.
default bind_addr=""
default bind_fail_max=-1
default bind_fail_interval=-1
default max_con_rate=-1
default max_copies=-1
default con_rate_offline=-1
default failrate_cnt=40
default failrate_interval=60
default inherit_env=TRUE
default tcp_trace=FALSE
default tcp_wrappers=FALSE
default connection_backlog=10

[coneja] # svcs dcs
STATE STIME FMRI
maintenance 14:40:17 svc:/platform/sun4u/dcs:default
[coneja] # svcadm disable dcs

[coneja] # svcs dcs

STATE STIME FMRI
disabled 14:52:29 svc:/platform/sun4u/dcs:default

[coneja] # svccfg -v delete dcs
svccfg: Expected property external of property group svc:/platform/sun4u/dcs/:properties/network is missing.
svccfg: Expected property external of property group svc:/platform/sun4u/dcs/:properties/cryptosvc is missing.
svccfg: Expected property external of property group svc:/platform/sun4u/dcs/:properties/filesystem_usr is missing.
svccfg: Expected property external of property group svc:/platform/sun4u/dcs/:properties/nodename is missing.
svccfg: Expected property external of property group svc:/platform/sun4u/dcs/:properties/sckmd is missing.

[coneja] # svcs dcs

svcs: Pattern 'dcs' doesn't match any instances
STATE STIME FMRI

[coneja] # svccfg -v import /var/svc/manifest/platform/sun4u/dcs.xml
svccfg: Taking "initial" snapshot for svc:/platform/sun4u/dcs:default.
svccfg: Taking "last-import" snapshot for svc:/platform/sun4u/dcs:default.
svccfg: Refreshed svc:/platform/sun4u/dcs:default.
svccfg: Successful import.

[coneja] /var # svcs dcs

STATE STIME FMRI

disabled 14:53:12 svc:/platform/sun4u/dcs:default

[coneja] # svcadm enable dcs

[coneja] # svcs dcs

STATE STIME FMRI
online 14:53:30 svc:/platform/sun4u/dcs:default

Y ahora si, a agregar la SB

e25k-2-sc0:sms-svc:20> addboard -d e sb12
assign SB12
.
assign SB12 done
poweron SB12
........................
poweron SB12 done
test SB12
............
test SB12 done
connect SB12
...........
connect SB12 done
configure SB12
.........
configure SB12 done
.
notify online SUNW_cpu/cpu384
notify online SUNW_cpu/cpu388
notify online SUNW_cpu/cpu385
notify online SUNW_cpu/cpu389
notify online SUNW_cpu/cpu386
notify online SUNW_cpu/cpu390
notify online SUNW_cpu/cpu387
notify online SUNW_cpu/cpu391
.
notify add capacity (8 cpus)
notify add capacity (4194304 pages)
notify add capacity SB12 done
.

Lo atamos con alambre

2011-10-13T11:07:00.001-03:00

Pequeña historia con algunas conclusiones :

El equipo XXX No Responde al ping.
Bueno, vamos a ver el equipo al Centro de Computos, con mi compañero Nicolas Morono.
El equipo habia entrado en un booteo en loop.
Uhhh , aca empieza la historia, el equipo es un Enterprise 450 con Solaris 2.6, de donde sacamos un cd de esa epoca?
y bueno, lo conseguimos

Ahi nomas un STOP + A
desde el OBP , un boot cdrom -s y a intentar un fsck
pero .... Se rompio la lectora de CD.
A esta altura , ya teniamos 2 problemas, Disco Roto y Lectora de CD Rota.
Intentamos bootear via OBP a un servidor remoto con
setenv network-boot-arguments host-ip=ip_de_server,router-ip=gw_del_server,subnet-mask=255.255.255.0,hostname=hostname-server,file=http://10.11.33.106/cgi-bin/wanboot-cgi
pero la version de OBP era muy vieja y no tenia la opcion de network boot, obviamente tampoco podiamos actualizar la OBP, porque no teniamos lectora de CD.
No nos queda mas remedio, llamamos a Soporte Oracle/Sun para que nos envien un repuesto de disco y lectora de cd ( el ingeniero que tomo el caso todavia se debe estar cagando de risa de la version de Sistema Operativo y Hardware )
Mientras tanto, vamos por la opcion bien Argentina, desarmemos otro equipo, revisemos a ver que hay por ahi.
Encontramos un V210 con 2 discos internos, mirroreados con Solaris Volume Manager , con Solaris 10. Perfecto.
Destornillador y manos a la obra,
Antes de sacar el disco del v210, le editamos el /etc/shadow, y el /etc/system , para que no pida passwd y que no arroje errores por la parte de Solaris Volume Manager.
Insertamos el disco del v210 en el E450, y el que tenia el Solaris 2.6 lo ponemos en otra bahia.
boot -s desde el disco con solaris 10

El boot con el disco de solaris 10 no anduvo bien en single user porque no detectaba/reconfiguraba correctamente el hardware y no veiamos los discos internos.

Booteamos con opcion de solaris 10 "boot -F failsafe", esta opcion busca en los discos instalaciones de solaris y te da la opcion de montarlas en /a (se toma su tiempo)

Desde esa opcion montando el solaris 10, conseguimos hacer un ufsrestore desde cinta dds3 de filesystems /, /var, /usr y /home.

reconstruimos el bootblk desde el solaris 10 y booteamos (esta opcion No funciona.)

Volvimos a bootear con boot -F failsafe otra vez con solaris 10 y esta vez montamos el /usr viejo (solaris 2.6 ) en /mnt y ejecutamos

/mnt/usr/sbin/installboot /mnt/usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/dsk/c0t1d0s0

Reboot y salio andando.

Cerramos el caso con Oracle.

Conclusion nro1 : el disco interno del v210 entra perfectamente en el E450

Conclusion nro 2: el installboot bootblk debe hacerse con la misma version de OS

Cambiar el nombre del host

2011-10-11T08:42:00.000-03:00

Para cambiar el nombre del hosts permanentemente, existen 2 modos.
con el menu del sys-unconfig ( requiere reboot)
o modificando los siguientes archivos manualmente :
/etc/hosts
/etc/hostname*
/ec/nodename
En versiones previas a solaris 10, inlcuir estos archivos tambien
/etc/net/ticlts/hosts
/etc/net/ticots/hosts
/etc/net/ticotsord/hosts

y Luego reboot

Container con solaris 8

2011-10-11T08:12:00.001-03:00

La idea era traer de un equipo viejo, con hardware obsoleto a otro que al menos tenga soporte. Para eso utilize un v210 con solaris 10 y me traje con ufsdump el backup del sistema operativo del solaris 8.
Aca esta el paso a paso de la creacion del container :

Pasos previos a la instalacion de la zona
En el equipo viejo , realizo un backup del solaris 8
ufsdump 0uf /backup/BARRA.DMP /
luego me traigo el BARRA.DMP al v210 nuevo.
en el V210, genero el fs donde residira la zona con el solaris 8
newfs /dev/rdsk/c2t1d0s0 /ZONAS
mkdir /ZONAS
chmod 700 /ZONAS

En viejos releases de solaris 10, hay que bajar un package s8containers-bundle-solaris10-sparc.tar.gz

gzip -d s8containers-bundle-solaris10-sparc.tar.gz
tar xvf s8containers-bundle-solaris10-sparc.tar
cd s8containers-bundle/1.0.1/Product
[skol] /usr/scripts/s8containers-bundle/1.0.1/Product # pkgadd -d .

The following packages are available:
1 SUNWs8brandk Solaris 8 Containers: solaris8 brand support RTU
(sparc) 11.10.0,REV=2008.09.20.18.50

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:

Processing package instance from
## Installing package in global zone

Solaris 8 Containers: solaris8 brand support RTU(sparc) 11.10.0,REV=2008.09.20.18.50
Copyright 2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Using as the package base directory.
## Processing package information.
## Processing system information.
8 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.

The following files are already installed on the system and are being
used by another package:
/usr/share/man/man5/solaris8.5

Do you want to install these conflicting files [y,n,?,q] y
## Checking for setuid/setgid programs.

Installing Solaris 8 Containers: solaris8 brand support RTU as

## Installing part 1 of 1.
/usr/lib/brand/solaris8/files/patches/109147-44.zip
/usr/lib/brand/solaris8/files/patches/109221-01.zip
/usr/lib/brand/solaris8/files/patches/111023-03.zip
/usr/lib/brand/solaris8/files/patches/111431-01.zip
/usr/lib/brand/solaris8/files/patches/112050-04.zip
/usr/lib/brand/solaris8/files/patches/112605-04.zip
/usr/lib/brand/solaris8/files/patches/order
/usr/share/man/man5/solaris8.5
[ verifying class ]

Installation of was successful

y Aca viene la instalacion

[skol] /ZONAS # zonecfg -z SOLARIS8
SOLARIS8: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:SOLARIS8> create -t SUNWsolaris8
zonecfg:SOLARIS8> set zonepath=/ZONAS/SOLARIS8
zonecfg:SOLARIS8> set autoboot=true
zonecfg:SOLARIS8> add net
zonecfg:SOLARIS8:net> set address=10.71.100.98
zonecfg:SOLARIS8:net> set physical=bge0
zonecfg:SOLARIS8:net> end
zonecfg:SOLARIS8> exit
[skol] /ZONAS # zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
- SOLARIS8 configured /ZONAS/SOLARIS8 solaris8 shared
[skol] /ZONAS #
[skol] /ZONAS # zonecfg -z SOLARIS8
zonecfg:SOLARIS8> info
zonename: SOLARIS8
zonepath: /ZONAS/SOLARIS8
brand: solaris8
autoboot: true
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
net:
address: 10.71.100.98
physical: bge0
defrouter not specified
zonecfg:SOLARIS8>exit

[skol] /ZONAS # zoneadm -z SOLARIS8 install -p -v -a /ZONAS/BARRA.DMP
Log File: /var/tmp/SOLARIS8.install.17125.log
Product: Solaris 8 Containers 1.0
Installer: solaris8 brand installer 1.3
Zone: SOLARIS8
Path: /ZONAS/SOLARIS8
Source: /ZONAS/BARRA.DMP
Media Type: ufsdump archive
Installing: This may take several minutes...
Sanity Check: Passed. Looks like a Solaris 8 system.
Postprocessing: This may take several minutes...
Postprocess: Gathering information about zone SOLARIS8
Postprocess: Creating mount points
Postprocess: Processing /etc/system
Postprocess: Booting zone to single user mode
Postprocess: Applying p2v module S20_apply_patches
S20_apply_patches: Unpacking patch: 109147-44
S20_apply_patches: Installing patch: 109147-44
S20_apply_patches: Unpacking patch: 111023-03
S20_apply_patches: Installing patch: 111023-03
S20_apply_patches: Unpacking patch: 111431-01
S20_apply_patches: Installing patch: 111431-01
S20_apply_patches: Unpacking patch: 112605-04
S20_apply_patches: Installing patch: 112605-04
S20_apply_patches: Unpacking patch: 112050-04
S20_apply_patches: Installing patch: 112050-04
S20_apply_patches: Unpacking patch: 109221-01
S20_apply_patches: Installing patch: 109221-01
Postprocess: Applying p2v module S31_fix_net
Postprocess: Applying p2v module S32_fix_nfs
Postprocess: Applying p2v module S33_fix_vfstab
Postprocess: Applying p2v module S34_fix_inittab
Postprocess: Applying p2v module S35_fix_crontab
Postprocess: Applying p2v module S36_fix_pam_conf
Postprocess: Applying p2v module S40_setup_preload
Postprocess: Halting zone
Postprocess: Postprocessing successful.
Result: Postprocessing complete.
Service Tag: Gathering information about zone SOLARIS8
Service Tag: Adding service tag: urn:st:02760bc1-0f12-4af8-f7be-82b17da0378d
Service Tag: Operation successful.

Result: Installation completed successfully.
Log File: /ZONAS/SOLARIS8/root/var/log/SOLARIS8.install.17125.log
[skol] /ZONAS #

[skol] /ZONAS # zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
- SOLARIS8 installed /ZONAS/SOLARIS8 solaris8 shared
[skol] /ZONAS #

[skol] /ZONAS # zoneadm -z SOLARIS8 ready
[skol] /ZONAS # zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
4 SOLARIS8 ready /ZONAS/SOLARIS8 solaris8 shared
[skol] /ZONAS # zoneadm -z SOLARIS8 boot

En Medio de esto, entre a /ZONAS/SOLARIS8/root/etc/shadow y modifique para que root no pida password
[skol] /ZONAS/SOLARIS8/root/etc # zlogin SOLARIS8
[Connected to zone 'SOLARIS8' pts/2]
Last login: Wed Sep 16 16:28:06 from 10.71.100.100
Sun Microsystems Inc. SunOS 5.8 Generic Patch February 2004
You have new mail.
[angra] / # df -k
Filesystem kbytes used avail capacity Mounted on
/ 30982173 9643911 21028441 32% /
/.SUNWnative/lib 18354602 4276990 13894066 24% /.SUNWnative/lib
/.SUNWnative/platform
18354602 4276990 13894066 24% /.SUNWnative/platform
/.SUNWnative/usr 18354602 4276990 13894066 24% /.SUNWnative/usr
/dev 30982173 9643911 21028441 32% /dev
proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
swap 5562192 16 5562176 1% /etc/svc/volatile
/dev/ksyms 18354602 4276990 13894066 24% /dev/ksyms
fd 0 0 0 0% /dev/fd
swap 5562240 64 5562176 1% /tmp
[angra] / #

NFS LOCO

2011-08-11T12:06:00.000-03:00

Problema del NFS
Tenia que hacer un servidor centralizadode backups, en el cual compartiera por NFS, un FS /BACKUP , y ahi alojar los ufsdump de distintos equipos.
La idea era que por cron una vez por semana, desde los solaris que no tenian unidad de cinta, hiciera un ufsdump del fs barra ( / ) a este
servidor que exportaba el NFS.
Pero... cuando queria sobreescribir el archivo me daba un error, abajo lo describo en detalle y como lo solucione.
Equipo Anfitrion: ( Solaris 10 rel 8/07 )
Desde este equipo, exporto un fs /BACKUP por nfs
share -F nfs -o anon=0 -d "Fs Backups" /BACKUPS

Desde otros solaris, con distintos releases, incluso con distintas versiones, monto el fs /BACKUP en /mnt

Hago el ufsdump 0uf /BACKUP/”nombredelequipoclienteNFS”/BARRA.DMP

Esto lo hace perfecto. Graba el archivo sin inconvenientes.
El problema es cuando, a la semana siguiente se ejecuta de nuevo el script, y este va a sobreescribir el archivo BARRA.DMP, me dice que
No puede sobreescribirlo porque el usuario no es uid 0 or 0 .
Este error solo me lo da con el release 1/06 de Solaris 10.

Me fije, en unos de los que si funcionaba, y tenia comentada esa variable (NFSMAPID_DOMAIN=domain ).

Lo que hice fue lo siguiente :

En los equipos que serian los clientes de nfs con Solaris 10, comente esa variable en /etc/default/nfs y ahora funcionan ok.

prstat : not enough memory : Not enough space ( encontre la solucion al problema de la resaca)

2011-08-10T09:51:00.000-03:00

prstat not enough memory ??? si hay un monton de memoria libre, swap libre, que raro, bueno, el problema eran los fucking file descriptors
coneja] / # prstat
prstat: not enough memory: Not enough space
Tenia 4096 fd y lo cambie para probar en 1024 ( que es el default)
[coneja] / # ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        8192
coredump(blocks)     unlimited
nofiles(descriptors) 4096
vmemory(kbytes)      unlimited
[coneja] / # ulimit -n 1024
[coneja] / # ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        8192
coredump(blocks)     unlimited
nofiles(descriptors) 1024
vmemory(kbytes)      unlimited

Y.... Arranco

[coneja] / # prstat
   PID USERNAME SIZE   RSS STATE PRI NICE      TIME CPU PROCESS/NLWP
26465 x300106   651M 613M sleep   60    0   1:17:33 8.0% oracle/11
14553 x300106   638M 610M sleep    0    0   0:45:13 7.4% oracle/11
14549 20443050   51M   45M sleep    0    0   0:29:12 4.7% m_clonacion/1
14165 sshd      981M 967M cpu33    0    0   0:00:55 3.7% oracle/1
20669 2046      544M 516M sleep   60    4   0:00:44 3.0% oracle/1
10331 2046      549M 521M sleep   60    4   0:05:20 1.9% oracle/1
24179 20443085 621M 176M sleep   59    0   6:10:30 1.5% hedgehog/5
13536 20443082 817M 368M sleep   59    0 12:43:26 0.9% hedgehog/5
12723 2015     2003M 1957M sleep   26    0   0:04:28 0.6% oracle/11
1068 784      1050M 110M sleep   59    0 17:52:57 0.5% hedgehog/5
22401 784      1081M 247M sleep   59    0   2:28:27 0.5% hedgehog/5
7764 root       18M 5560K sleep   40    0 33:06:19 0.5% scopeux/1
1064 784      1049M 185M sleep   59    0 13:47:23 0.4% hedgehog/5
19111 sshd      983M 957M sleep   40    0   2:07:08 0.4% oracle/1
20081 2016      942M 320M sleep   59    0 13:44:33 0.4% hedgehog/5
26495 20443085 657M   88M sleep   59    0   9:01:23 0.3% hedgehog/5
12870 x300106   647M 565M sleep   59    0   3:09:33 0.2% oracle/14
26350 2016     1953M 100M sleep   59    0   0:01:26 0.2% hedgehog/5
12862 x300106   641M 558M sleep   51    0   0:51:01 0.2% oracle/258
12866 x300106   641M 557M sleep   59    0   0:50:02 0.2% oracle/258
    30 2016      561M   59M sleep   59    0   0:16:58 0.2% hedgehog/5
12868 x300106   641M 557M sleep   56    0   0:50:06 0.2% oracle/258
1067 784       569M   94M sleep   59    0   5:57:39 0.2% hedgehog/5
12860 x300106   641M 570M sleep   59    0   0:50:05 0.2% oracle/258
18619 2046      545M 474M sleep   42    4   0:02:33 0.1% oracle/258
21887 sshd      985M 962M sleep   51    0   0:08:52 0.1% oracle/29
19597 2035      937M 821M sleep   59    0 21:19:20 0.1% oracle/1
18617 2046      545M 478M sleep   41    4   0:02:38 0.1% oracle/258
18621 2046      551M 478M sleep   47    4   0:12:33 0.1% oracle/13
7737 root     1256K 136K sleep   49    0   7:16:29 0.1% perf64/1
18675 2046      562M 502M sleep   41    4   0:02:21 0.1% oracle/11
18677 2046      551M 488M sleep   43    4   0:02:00 0.1% oracle/18
3073 root       15M   11M sleep   59    0   4:44:48 0.1% discusge/1
12872 x300106   646M 578M sleep   59    0   0:07:04 0.1% oracle/20
12878 x300106   636M 588M sleep   55    0   0:11:12 0.1% oracle/1
22683 root     2528K 2128K cpu32   50    0   0:00:00 0.1% prstat/1
   892 sshd      981M 950M sleep   59    0   0:14:33 0.1% oracle/1
19715 2035      933M 870M sleep   59    0   9:29:46 0.1% oracle/1
18633 2046      539M 490M sleep   47    4   0:11:06 0.0% oracle/1
16193 sshd      981M 951M sleep   59    0   0:02:29 0.0% oracle/1
19571 2035      935M 850M sleep   59    0   5:36:40 0.0% oracle/1
8075 root       66M 5256K sleep   59    0   1:59:37 0.0% seosd/1
22644 2015     1877M 1845M sleep   52    0   0:00:00 0.0% oracle/1
8933 root       66M 5096K sleep   59    0   1:38:38 0.0% seosd/1
18623 2046      550M 491M sleep   47    4   0:03:50 0.0% oracle/15
17055 sshd      981M 960M sleep   59    0   0:00:46 0.0% oracle/1
16185 sshd      982M 952M sleep   59    0   0:01:26 0.0% oracle/1
2810 root       66M 6696K sleep   59    0   2:13:10 0.0% seosd/1
17051 sshd      982M 961M sleep   59    0   0:00:27 0.0% oracle/1
22738 root       48M   17M sleep   43    0   0:13:30 0.0% opcmona/8
4237 sshd      534M 504M sleep   59    0   0:10:41 0.0% oracle/1
18831 root       48M   16M sleep   54    0   0:11:36 0.0% opcmona/8
19665 root      215M   10M sleep   59    0   2:21:47 0.0% coda/9
Total: 767 processes, 6676 lwps, load averages: 3.84, 4.56, 4.67
[coneja] / #

El equipo donde tirana el error era :
[coneja] / # prtdiag -v|more
System Configuration: Sun Microsystems sun4u Sun Fire E25K
System clock frequency: 150 MHz
Memory size: 32768 Megabytes

Prtdiag ( cortito y al pie )

2011-08-08T22:06:00.000-03:00

Cuando no refresca el prtdiag -v , se debe restartear el picld

svcadm restart picld

doc id que avala esto es 212205

Problema instalando una zona

2011-08-05T19:22:00.000-03:00

Instalando una zona desde cero , me encontre con este error y la solucion es artesanal, aca dejo el paso a paso.
[coneja]# zonecfg -z zona1 -f /usr/scripts/creaZONA1.ksh
[coneja]# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
- zona1 configured /export/zona1 native shared
[coneja]# chmod 700 /export/zona1
[coneja]# zoneadm -z zona1 install
Preparing to install zone .
Creating list of files to copy from the global zone.
Copying <139425> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1171> packages on the zone.
Initialized <1171> packages on zone. [[2;5~
Zone is initialized.
Installation of <12> packages was skipped.
The file contains a log of the zone installation.
HASTA ACA VENIA TODO PERFECTO........
[coneja]# zoneadm -z zona1 ready
[coneja] # zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
1 zona1 ready /export/zona1 native shared
[coneja] # zoneadm -z zona1 boot
[coneja]# zlogin zona1 ( Cuando Quiero loguearme a la zona, que instale recien, no levantaban servicios)
# svcs -xv
svc:/system/sysidtool:net (sysidtool)
State: offline since Mon May 18 10:02:53 2009
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: man -M /usr/man -s 1M sysidtool
See: /var/svc/log/system-sysidtool:net.log
Impact: 28 dependent services are not running:
svc:/network/rpc/bind:default
Recorté la salida de los logs del svcs -xv
See: /var/svc/log/application-print-ppd-cache-update:default.log
Impact: This service is not running.
#
LO UNICO LOCO QUE VEO ES en el /ETC
-rw-r--r-- 1 root other 0 May 18 09:44 .UNCONFIGURED
-rw-r--r-- 1 root other 40 May 18 09:51 .sysidconfig.apps
# more .sysidconfig.apps
/usr/sbin/sysidkbd
/lib/svc/method/sshd
LUEGO APLICO la SOLUCION de la Ing SCIARRILLO
# rm .UNCONFIGURED
# rm .sysidconfig.apps
# reboot ( reboot de la zona)
[Connection to zone 'zona1' pts/2 closed]
[coneja]# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
2 zona1 running /export/zona1 native shared
[coneja] /usr/scripts #
Ejecuto esto
/usr/sbin/sysidnet
/usr/sbin/sysidns
/usr/sbin/sysidsys
/usr/sbin/sysidroot
/usr/sbin/sysidpm
/usr/sbin/sysidnfs4
/usr/sbin/sysidkbd

y Salio Andando 10 PuntoS

Problemas con el boot de Solaris x86

2011-07-07T12:47:00.000-03:00

Me paso un par de veces con los solaris 10 x86 sobre blades IBM y HP.
Luego de un reboot , forzado o no, quedando el equipo en modo mantenimiento.
Generalmente lo arreglo con la opcion 1, pero en alguna oportunidad tuve que usar la opcion 2, que es cuando me da el sig error : Error 3 bad or corrupt data while decompressing file.
Ingresar a la ILOM y loguearme a la consola del equipo
Solucion 1 )
Desde el grub de solaris
Ingresar a la opcion de Solaris Failsafe
svcadm clear system/boot-archive (Esto repara el fs si es necesario )

Solucion 2 )
La solucion es
Ingresar a la opcion de Solaris Failsafe
svcadm clear system/boot-archive (Esto repara el fs si es necesario )
Montar el disco de booteo con la opcion de lectura/escritura en /a
rm -f /a/platform/i86pc/boot_archive
bootadm update-archive -R /a
reboot
y sale andando.

Modificar Diskgroup Sun Cluster 3.3

2011-07-04T10:35:00.000-03:00

La finalidad es sacar un filesystem (/archives ) de un DiskGroup existente y que esta bajo el control del cluster
Crear un Diskgroup ( ARCHDG), agregarle el filesystem (/archives ) que saque anteriormente y que este nuevo DG quede bajo el control del cluster.
Aca va el Paso a Paso.
1) Descubrir el Disco que me asignaron y Labelearlo
cfgadm -f -c configure c(nro de controladora)
devfsadm -C ( -C significa modo Clean Up )
devfsadm ( crea special files en el /devices y logical links en /dev )
scdidadm -C ( remueve todas las referencias DID de todos los dispositivos Detachados )
scdidadm -r ( reconfiguro los DID ) (en ambos nodos )
scgdevs ( updatea el /globaldevices )
scdpm -p all:all ( chequea que este bien el did en ambos nodos del cluster, suele demorar un rato , no menos de 5 minutos dependiendo la cantidad de discos que tenga)
vxdctl enable
OJO: Los comandos arriba mencionados,Deben ser ejecutados en AMBOS nodos del cluster
vxdisk -e list ( tomar nota del disco nuevo a agregar al veritas)
vxdiskadm ( opcion 1 ) con esto agrego el disco nuevo y creo el nuevo Diskgroup (ARCHDG)
Chequeo que Diskgroup esta bajo el control del cluster, Solo hay uno.
sunrac1 # cldg list
Interdg
sunrac1 #
Ahora agrego el nuevo DiskGRoup ARCHDG al control del Cluster.
cldg create -t vxvm -n sunrac1,sunrac2 -p preferenced=true ARCHDG
Vuelvo a Chequear y Quedo Joya.
sunrac1 # cldg list
ARCHDG
Interdg
sunrac1 #
Ahora creo el nuevo volumen
sunrac1 # vxassist -g ARCHDG maxsize layout=concat Archdg01
Maximum volume size: 314472448 (153551Mb)
sunrac1 # vxassist -g ARCHDG make vol01 153551M layout=concat Archdg01
Ahora, debo sincronizar el DG , caso contrario cuando quiera hacer el newfs, me va a decir que no puede.
sunrac1 # cldevicegroup sync Archdg
sunrac1 # newfs /dev/vx/rdsk/Archdg/vol01
Luego , Modificar el /etc/vfstab en AMBOS NODOS, para luego montar el fs creado.

Direct IO y la p......

2011-06-13T17:42:00.000-03:00

El escenario era el siguiente :
Teniamos un dominio del 10.000, conectado directamente a 2 storage externos un EMC y un SHARK, el s.o era solaris 7, con oracle 9.2.01
Migramos dicho servidor a un 4900, con solaris 10 , veritas 4.0 y oracle 10, conectado a el mismo storage pero a travez de una SAN ( switch brocade 24K ), con placa qlogic 2340.
El problema era el siguiente :

Luego de migrar, la gente de base de datos decia que :
Las aplicaciones que hacen acceso random a los datafiles de oracle, tienen mucha mas demora que en la maquina anterior.
Las operaciones que realizan un acceso secuencial sobre los datafiles, funcionan mucho mejor. ( fullscan).

Teniamos hasta el momento,segun estos datos, 2 lugares hacia donde apuntar, los discos de la SAN o quizas los parametros de la placa qlogic.

Por ejemplo, uno de los parametros a modificar en el /kernel/drv/qlc.conf , podria llegar a ser el hba1-execution-throttle=256 ( donde el actual es 1 )
LUEGO, tocamos los siguientes parametros en el /etc/system :

El dba, me dijo que bajaron los tiempos con este parametro
* Tamanio fisico maximo de un I/O con VM
* Unidad=sector (de 512 bytes)

set vxio:vol_maxio=32768

Tocamos parametros de Veritas de io

Luego de esto ultimo, El DBA me dijo que ya estaba solucionado el problema y que el resto seria un bug de Oracle, por lo cual pedi cerrar el caso en sun.

A los 2 o 3 dias, seguimos con los mismos problemas.

El escenario sigue siendo el mismo que detalle al comienzo .
El tema es que el error los da en forma aleatoria. ya sea en forma secuencial o random.

Lo que probe hacer fue bajar desde veritas con el vxtunefs bajar el parametro discover_direct_ioz a 64 k, segun me guie en el siguiente blue print
http://www.sun.com/blueprints/0400/ram-vxfs.pdf

Pero se sigue dando el error en forma aleatoria y mas seguido cuando se trabaja con lectura random.

Abreviando muchismo, aca fue donde afinamos la punteria :
1) Generamos 2 filesystems para probar, ellos son /interfaz y /carga.
al filesystem /carga le sacamos el parametro directio de las opciones del mount.
y al filesystem /interfaz, le dejamos la opcion directio en el vfstab, que es como esta en el ambiente productivo.
/dev/vx/dsk/SOS/vol01 /dev/vx/rdsk/SOS/vol01 /carga vxfs 3 yes largefiles
/dev/vx/dsk/SOS/vol02 /dev/vx/rdsk/SOS/vol02 /interfaz vxfs 3 yes largefiles,convosync=direct
Realizamos las siguientes pruebas.
En el fs /carga, ejecutamos un vxbench con opciones , write, read, random write,
random read sin direct i/o y un vxbench con las mismas opciones pero con directio.

A continuacion muestro la salida de los vxbench que hicimos en el fs /carga, Observemos los tiempos de
la primer columna , como se pegan un viaje cuando los tiras con directio.

Write SIN Directio
/carga/PRUEBA # /usr/sbin/vxbench -w write -i iosize=16,iocount=10000,nrep=

10 test1
total: 5.088 sec 314448.66 KB/s cpu: 4.84 sys 0.21 user
Read SIN Directio
/carga/PRUEBA # /usr/sbin/vxbench -w read -i iosize=16,iocount=10000,nrep=10 test1
total: 2.830 sec 565335.87 KB/s cpu: 2.65 sys 0.17 user
Write CON Directio
/carga/PRUEBA #/usr/sbin/vxbench -w write -i iosize=16,iocount=10000,nrep=10 -c direct test2
total: 101.390 sec 15780.62 KB/s cpu: 12.01 sys 0.47 user
READ CON Directio
/carga/PRUEBA # /usr/sbin/vxbench -w read -i iosize=16,iocount=10000,nrep=10 -c direct test2
total: 88.032 sec 18175.25 KB/s cpu: 10.05 sys 0.45 user
Randon Write SIN Directio
/carga/PRUEBA # /usr/sbin/vxbench -w rand_write -i iosize=16,iocount=10000,nrep=10 test3
total: 19.299 sec 82906.56 KB/s cpu: 18.09 sys 0.43 user
Randon READ SIN Directio
/carga/PRUEBA # /usr/sbin/vxbench -w rand_read -i iosize=16,iocount=10000,nrep=10 test3
total: 6.507 sec 245873.36 KB/s cpu: 6.17 sys 0.32 user
Random Write CON Directio
/carga/PRUEBA # /usr/sbin/vxbench -w rand_write -i iosize=16,iocount=10000,nrep=10 -c directio
total: 362.794 sec 4410.21 KB/s cpu: 53.67 sys 0.77 user
Random READ CON Directio
/carga/PRUEBA # /usr/sbin/vxbench -w rand_read -i iosize=16,iocount=10000,nrep=10 -c directio
total: 663.139 sec 2412.77 KB/s cpu: 12.64 sys 0.56 user
/carga/PRUEBA #

Hicimos las mismas pruebas sobre el filesystem /interfaz, es decir el que esta montado con directio
y la conclusion fue ....................:
En el /etc/vfstab, sacamos la opcion convosync=direct de los filesystems de la Base de Datos y anduvo Perfecto.

I/O Error Sobre Storage Externo

2011-06-13T12:46:00.000-03:00

Me llamaron diciendo que les daba IO error algunos filesystems, el error que mostraba el /var/adm/messages era este :
Aug 17 16:29:17 coneja fctl: [ID 517869 kern.warning] WARNING: 942=>fp(3)::GPN_ID for D_ID=64a200 failed
Aug 17 16:29:17 coneja fctl: [ID 517869 kern.warning] WARNING: 943=>fp(3)::N_x Port with D_ID=64a200, PWWN=5005076801403680 disappeared from fabric
Aug 17 16:29:17 coneja fctl: [ID 517869 kern.warning] WARNING: 952=>fp(3)::GPN_ID for D_ID=64e200 failed
Aug 17 16:29:17 coneja fctl: [ID 517869 kern.warning] WARNING: 953=>fp(3)::N_x Port with D_ID=64e200, PWWN=5005076801303680 disappeared from fabric
Aug 17 16:29:18 coneja fctl: [ID 517869 kern.warning] WARNING: 964=>fp(1)::GPN_ID for D_ID=64a900 failed
Aug 17 16:29:18 coneja fctl: [ID 517869 kern.warning] WARNING: 965=>fp(1)::N_x Port with D_ID=64a900, PWWN=5005076801103680 disappeared from fabric
Aug 17 16:29:18 coneja fctl: [ID 517869 kern.warning] WARNING: 974=>fp(1)::GPN_ID for D_ID=64e900 failed
Aug 17 16:29:18 coneja fctl: [ID 517869 kern.warning] WARNING: 975=>fp(1)::N_x Port with D_ID=64e900, PWWN=5005076801203680 disappeared from fabric
Aug 17 17:03:28 coneja mpxio: [ID 669396 kern.info] /scsi_vhci/ssd@g60050768019901b4000000000000002a (ssd107) multipath status: optimal, path /pci@8,600000/SUN
W,qlc@2/fp@0,0 (fp3) to target address: 5005076801403680,0 is offline. Load balancing: round-robin
Aug 17 17:03:28 coneja scsi: [ID 243001 kern.info]    Target 0x64e200: Device type=0x1f Nonzero pqual=0x1

El storage externo , tuvo problemas y los fs quedaron con IO error
chequeo el metastat |grep -i Errored
los filesystems quedan doblados, lo que hay que hacer es un umount del filesystem y montarlo, sino chilla, lo dejo asi.
Si putea por io error le corro un fsck y luego lo monto.

[coneja] /var/adm # umount /u18
[coneja] /var/adm # mount /u18
mount: I/O error
mount: cannot mount /dev/md/dsk/d58
[coneja] /var/adm # fsck /dev/md/dsk/d58
** /dev/md/rdsk/d58
** Last Mounted on /u18
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3a - Check Connectivity
** Phase 3b - Verify Shadows/ACLs
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cylinder Groups

CORRECT BAD CG SUMMARIES FOR CG 0? y

CORRECTED SUPERBLOCK SUMMARIES FOR CG 0
CORRECTED SUMMARIES FOR CG 0
FRAG BITMAP WRONG
FIX? y

CORRECT GLOBAL SUMMARY
SALVAGE? y

Log was discarded, updating cyl groups
10 files, 12582971 used, 5358831 free (7 frags, 669853 blocks, 0.0% fragmentation)

***** FILE SYSTEM WAS MODIFIED *****
[coneja] /var/adm #

Algunos filesystems que NO tiraron IO error pero daban Errored en el status del metastat, no hizo falta correrles el fsck, solo umount y mount
[coneja] /var/adm # umount /u01
umount: /u01 busy
[coneja] /var/adm # metastat d41
d41: Soft Partition
    Device: d40
    State: Errored
    Size: 41943040 blocks (20 GB)
        Extent              Start Block              Block count
             0                     2080                 41943040

coneja] /var/adm # umount -f /u01
[coneja] /var/adm # mount /u01
[coneja] /var/adm # metastat d41
d41: Soft Partition
    Device: d40
    State: Okay
    Size: 41943040 blocks (20 GB)
        Extent              Start Block              Block count
             0                     2080                 41943040

Device Relocation Information:
Device                                  Reloc   Device ID
c6t60050768019901B4000000000000002Ad0   Yes     id1,ssd@w60050768019901b4000000000000002a
c6t60050768019901B4000000000000002Bd0   Yes     id1,ssd@w60050768019901b4000000000000002b
c6t60050768019901B4000000000000002Cd0   Yes     id1,ssd@w60050768019901b4000000000000002c
[coneja] /var/adm #

Por lo que estuve viendo en sunsolve, hay un parche mas nuevo para la SAN, que es el 113039-25 (requiere REBOOT) quizas solucione esto.

Verificar Errores de hardware

2011-05-03T08:58:00.000-03:00

Para ver si hay errores de hardware en solaris x86 .

# fmdump

TIME UUID SUNW-MSG-ID

Jan 17 15:08:04.4536 4868ef14-b7a7-43ac-86a5-856b8c4d292c AMD-8000-3K

Jan 17 19:57:49.6819 4868ef14-b7a7-43ac-86a5-856b8c4d292c AMD-8000-3K

Jan 19 12:51:43.9301 4868ef14-b7a7-43ac-86a5-856b8c4d292c AMD-8000-3K

Jan 19 13:17:37.6284 4868ef14-b7a7-43ac-86a5-856b8c4d292c AMD-8000-3K

Jun 24 15:26:45.2892 4868ef14-b7a7-43ac-86a5-856b8c4d292c AMD-8000-3K

Jun 24 21:42:32.6692 4868ef14-b7a7-43ac-86a5-856b8c4d292c AMD-8000-3K

Jun 24 22:59:35.5318 4868ef14-b7a7-43ac-86a5-856b8c4d292c AMD-8000-3K

# fmdump -v -u 4868ef14-b7a7-43ac-86a5-856b8c4d292c

Jun 24 22:59:35.5318 4868ef14-b7a7-43ac-86a5-856b8c4d292c AMD-8000-3K

100% fault.memory.dimm_ck

Problem in: hc:///motherboard=0/chip=1/memory-controller=0/dimm=1

Affects: mem:///motherboard=0/chip=1/memory-controller=0/dimm=1

FRU: hc:///motherboard=0/chip=1/memory-controller=0/dimm=1

# fmadm faulty

STATE RESOURCE / UUID

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

degraded mem:///motherboard=0/chip=1/memory-controller=0/dimm=1

4868ef14-b7a7-43ac-86a5-856b8c4d292c

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

Luego de que el tecnico de hardware haga el reemplazo de la parte que se rompio, hacer lo siguiente

# fmadm repair 4868ef14-b7a7-43ac-86a5-856b8c4d292c

fmadm: recorded repair to 4868ef14-b7a7-43ac-86a5-856b8c4d292c

Resetear los errores

# fmadm reset eft

fmadm: eft module has been reset

# fmadm faulty

STATE RESOURCE / UUID

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

Modificar Parametros del Kernel en Solaris 10

2011-04-28T12:36:00.000-03:00

Para modificar la cantidad maxima de files descriptors, o la cantidad maxima de semaforos para oracle, tipear, como root :

projmod -s -K "process.max-file-descriptor=(basic,10000,deny)" group.dba

projmod -s -K "project.max-shm-memory=(priv,8192MB,deny)" group.dba

en este caso group.dba es el proyecto que tengo creado en el /etc/project .

No es necesario bootear, ya que el cambio es permanente, pero si, es necesario desloguearse como oracle y volver a loguear.

Movimiento de zonas entre equipos

2011-03-28T15:56:00.000-03:00

En el siguiente escenario :

Equipo A, un dominio con 5 zonas , tuve que mover una de las zonas a un nuevo equipo ( equipo B ) con distinto storage.

Equipo B, tiene un release nuevo de solaris, asi que tengo que actualizar la zona.

En el equipo B

mkdir -p /export/zona3

mount /dev/md/dsk/d103 /export/zona3

chmod 700 /export/zona3

crear la zona,

zonecfg -z zona3

create -b

set zonepath=/export/zona3

set autoboot=true

add net

set address=10.78.1xx.144

set physical=ce2

end

Luego, en el equipo A copio el sistema operativo de la zona, a la zona global del equipo B

ufsdump 0f - /export/zona3/ |ssh 10.78.1xx.143 "(cd /export/zona3; ufsrestore -rf -)"

Vuelvo al equipo B

zoneadm list -cv

ID NAME STATUS PATH

0 global running /

- zona3 installed /export/zona3

Actualizo la zona 3, porque la zona global del equipo original, tiene un release mas viejo que la zona global del nuevo.

zoneadm -z zona3 attach -u

Luego en la global del equipo B,montar los filesystems en cualquier punto de montaje, para poder hacer la copia

Luego parado en equipo A,
Bajar todos los procesos de la zona 3 ( no apagarla )
Copiar a la zona global del equipo B

ufsdump 0f - /export/zona3/ |ssh 10.78.1xx.143 "(cd /export/zona3; ufsrestore -rf -)"

ufsdump 0f - /export/zona3/root/u00 |ssh 10.78.1xx.143 "(cd /ZONA3_u00; ufsrestore -rf -)"

ufsdump 0f - /export/zona3/root/u01 |ssh 10.78.1xx.143 "(cd /ZONA3_u01; ufsrestore -rf -)"

ufsdump 0f - /export/zona3/root/u02 |ssh 10.78.1xx.143 "(cd /ZONA3_u02; ufsrestore -rf -)"

ufsdump 0f - /export/zona3/root/u03 |ssh 10.78.1xx.143 "(cd /ZONA3_u03; ufsrestore -rf -)"

ufsdump 0f - /export/zona3/root/u04 |ssh 10.78.1xx.143 "(cd /ZONA3_u04; ufsrestore -rf -)"

ufsdump 0f - /export/zona3/root/u05 |ssh 10.78.1xx.143 "(cd /ZONA3_u05; ufsrestore -rf -)"

ufsdump 0f - /export/zona3/root/u06 |ssh 10.78.1xx.143 "(cd /ZONA3_u06; ufsrestore -rf -)"

ufsdump 0f - /export/zona3/root/u07 |ssh 10.78.1xx.143 "(cd /ZONA3_u07; ufsrestore -rf -)"

ufsdump 0f - /export/zona3/root/u08 |ssh 10.78.1xx.143 "(cd /ZONA3_u08; ufsrestore -rf -)"

ufsdump 0f - /export/zona3/root/u09 |ssh 10.78.1xx.143 "(cd /ZONA3_u09; ufsrestore -rf -)"

ufsdump 0f - /export/zona3/root/u10 |ssh 10.78.1xx.143 "(cd /ZONA3_u10; ufsrestore -rf -)"

Una vez finalizada la copia , en el equipo A :
zlogin zona3 y APAGAR la ZONA3.

Luego comentar en el /etc/zones/index, la linea que dice zona3 ( para evitar que en un booteo del equipo levante esta zona)

En el equipo B

desmontar todos los /ZONA3* porque estos deben montar dentro de la zona

luego

zoneadm -z zona3 boot

zlogin zona3

chequear que este todo levantado

Problemas con los que me encontre.

Al intentar levantarla, a zona quedaba parada con los servicios del sysidnet. y no seguia.

Solucion :

touch /etc/.UNCONFIGURED

puse en 0 (cero) la opcion # System previously configured? del archivo /etc/.sysIDtool.state

y corri en forma manual todo lo que hace el sysidtool

/usr/sbin/sysidnet

/usr/sbin/sysidns

/usr/sbin/sysidsys

/usr/sbin/sysidroot

/usr/sbin/sysidpm

/usr/sbin/sysidnfs4

/usr/sbin/sysidkbd

Luego de eso, la zona siguio levantando en forma normal.

Otro problemita ,
Tenia 9 instancias de oracle ejecutandose originalmente, pero en esta nueva zona,solo levantaba 7 instancias,y abortaba por falta de memoria.

Asi que desde la zona global le corrimos un

projmod -s -K "project.max-shm-memory=(priv,8192MB,deny)" oracle_SIEBEL
y levantaron todas las bases como lo esperaba.
Hasta este punto, anduvo todo perfecto, pero... cuando quisimos instalar oracle 11g, el instalador hace un chequeo para ver que release de solaris tiene instalado, pero NO usa el /etc/release sino que usa este comando
/usr/bin/pkginfo -l SUNWsolnm | /usr/bin/nawk -F= '/VERSION/ {"/usr/bin/uname -r" | getline uname; print uname "-" $2}'
es decir, chequea el paquete SUNWsolnm, que es el encargado de actualizar el release, y el zoneadm attach -u NO upgradea este paquete.
Solucion :
Backup de la zona.
dentro de la zona, ejecutar un init 0
zoneadm -z zona3 uninstall -F ( esto borra Toda la zona )
Genero la zona desde cero, como esta descripto al principio.
y luego
zoneadm -z zona3 install
luego un restore selectivo de algunos archivos de configuracion, passwd, shadow, group, todo el home de los usuarios, resolv.conf , hosts, y scripts de inicio residentes en el /etc/init.d
zoneadm -z zona3 boot
y listo

Balanceador de discos de IBM

2011-03-23T09:15:00.000-03:00

A continuacion un ejemplo de instalacion del balanceador de discos de Ibm, el IBMsdd :
Se instala con el pkgadd -d
# pkgadd -d .

The following packages are available:
1 IBMsdd IBMsdd Driver 64-bit Solaris 10 Version: 1.6.5.0-0 Oct-01-2008 16:10
(sparc) 1.6.5.0-0

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:

Processing package instance from

IBMsdd Driver 64-bit Solaris 10 Version: 1.6.5.0-0 Oct-01-2008 16:10(sparc) 1.6.5.0-0
Copyright IBM Corporation 2001
## Processing package information.
## Processing system information.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of [y,n,?] y

Installing IBMsdd Driver 64-bit Solaris 10 Version: 1.6.5.0-0 Oct-01-2008 16:10 as

## Executing preinstall script.
/var/sadm/pkg/IBMsdd/install/preinstall: pre install running
## Installing part 1 of 1.
/etc/cfgvpath
/etc/defvpath
/etc/sample_sddsrv.conf
/kernel/drv/sparcv9/vpathdd
/kernel/drv/vpathdd.conf
/lib/svc/method/ibmsddinit
/opt/IBMsdd/bin/cfgvpath
/opt/IBMsdd/bin/datapath
/opt/IBMsdd/bin/defvpath
/opt/IBMsdd/bin/get_root_disk
/opt/IBMsdd/bin/pathtest
/opt/IBMsdd/bin/rmvpath
/opt/IBMsdd/bin/sddgetdata
/opt/IBMsdd/bin/sddgetwwpn
/opt/IBMsdd/bin/sddprutil
/opt/IBMsdd/bin/setlicense
/opt/IBMsdd/bin/showvpath
/opt/IBMsdd/bin/vpathmkdev
/opt/IBMsdd/devlink.vpath.tab
/opt/IBMsdd/etc.profile
/opt/IBMsdd/etc.system
/opt/IBMsdd/vpath.msg
/opt/IBMsdd/vpathexcl.cfg
/sbin/sddsrv
/usr/lib/sddlib.so
/usr/sbin/vpathmkdev
/var/svc/manifest/system/ibmsdd/ibmsdd-init.xml
[ verifying class ]
## Executing postinstall script.
Vpath: Configuring 0 devices (0 disks * 8 slices)

Installation of was successful.

cfgadm -f -c configure c1 y c2 ( como siempre )
luego ejecuto estos comandos para generar los devices balanceados:
/opt/IBMsdd/bin/cfgvpath
/opt/IBMsdd/bin/vpathmkdev ( este es el que genera los devices en el format )

Para agregar un disco a un volumen concatenado hice lo siguiente:
[asun005] /opt/IBMsdd/bin # metastat -p d100
d100 2 1 /dev/dsk/vpath1a \
1 /dev/dsk/vpath2a
[asun005] /opt/IBMsdd/bin # metattach d100 /dev/dsk/vpath3a
d100: component is attached
[asun005] /opt/IBMsdd/bin # metastat -p d100
d100 3 1 /dev/dsk/vpath1a \
1 /dev/dsk/vpath2a \
1 /dev/dsk/vpath3a
[asun005] /opt/IBMsdd/bin # df -h /BACKUPS
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d100 504G 482G 17G 97% /BACKUPS

[asun005] /opt/IBMsdd/bin # growfs -M /BACKUPS /dev/md/rdsk/d100
Warning: 2048 sector(s) in last cylinder unallocated
/dev/md/rdsk/d100: 1597898752 sectors in 260075 cylinders of 48 tracks, 128 sectors
780224.0MB in 16255 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
...............................................................................
...............................................................................
........
super-block backups for last 10 cylinder groups at:
1596955296, 1597053728, 1597152160, 1597250592, 1597349024, 1597447456,
1597545888, 1597644320, 1597742752, 1597841184
[asun005] /opt/IBMsdd/bin # df -h /BACKUPS
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d100 750G 482G 263G 65% /BACKUPS
[asun005] /opt/IBMsdd/bin #

Notas :
/opt/IBMsdd/bin/datapath query device (sacamos el numero de serie que tiene el UID )
A continuacion, un detallado paso a paso de asignacion y creacion de nuevos metadevices y un problema y solucion con un vpath.

Me asignaron 6 discos de 209gb 1 disco de 32gb y 1 de 12gb
[coneja] /opt/IBMsdd/bin # format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
0. c0t9d0
/pci@19c,700000/pci@1/pci@1/scsi@2/sd@9,0
1. c0t10d0
/pci@19c,700000/pci@1/pci@1/scsi@2/sd@a,0
2. c0t11d0
/pci@19c,700000/pci@1/pci@1/scsi@2/sd@b,0
Specify disk (enter its number): ^C
[coneja] /opt/IBMsdd/bin # cfgadm -la
Ap_Id Type Receptacle Occupant Condition
IO4 unknown empty unconfigured unknown
IO5 unknown empty unconfigured unknown
IO6 unknown empty unconfigured unknown
IO7 unknown empty unconfigured unknown
IO8 unknown empty unconfigured unknown
IO10 HPCI+ disconnected unconfigured unknown
IO12 HPCI+ connected configured ok
IO12::pci0 io connected configured ok
IO12::pci1 io connected configured ok
IO12::pci2 io connected configured ok
IO12::pci3 io connected configured ok
IO12_C3V0 fibre/hp connected configured ok
IO12_C3V1 fibre/hp connected configured ok
IO12_C3V2 pci-pci/hp connected configured ok
IO13 unknown empty unconfigured unknown
IO16 unknown empty unconfigured unknown
IO17 unknown empty unconfigured unknown
SB4 unknown empty unconfigured unknown
SB5 unknown empty unconfigured unknown
SB6 unknown empty unconfigured unknown
SB7 unknown empty unconfigured unknown
SB8 unknown empty unconfigured unknown
SB12 V3CPU connected configured ok
SB12::cpu0 cpu connected configured ok
SB12::cpu1 cpu connected configured ok
SB12::cpu2 cpu connected configured ok
SB12::cpu3 cpu connected configured ok
SB12::memory memory connected configured ok
SB13 unknown empty unconfigured unknown
SB16 unknown empty unconfigured unknown
SB17 unknown empty unconfigured unknown
c0 scsi-bus connected configured unknown
c0::dsk/c0t9d0 disk connected configured unknown
c0::dsk/c0t10d0 disk connected configured unknown
c0::dsk/c0t11d0 disk connected configured unknown
c0::es/ses0 processor connected configured unknown
c1 fc-fabric connected configured unknown
c1::5005076801303680 disk connected configured unknown
c1::50050768013036a1 disk connected configured unknown
c1::5005076801403680 disk connected configured unknown
c1::50050768014036a1 disk connected configured unknown
c2 fc-fabric connected configured unknown
c2::5005076801103680 disk connected configured unknown
c2::50050768011036a1 disk connected configured unknown
c2::5005076801203680 disk connected configured unknown
c2::50050768012036a1 disk connected configured unknown
c3 scsi-bus connected configured unknown
c3::rmt/0 tape connected configured unknown
c4 fc connected unconfigured unknown
c5 fc connected unconfigured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb0/3 unknown empty unconfigured ok
usb0/4 unknown empty unconfigured ok
[coneja] /opt/IBMsdd/bin #
[coneja] /opt/IBMsdd/bin # cfgadm -f -c configure c1
[coneja] /opt/IBMsdd/bin # cfgadm -f -c configure c2
[coneja] /opt/IBMsdd/bin # format
Searching for disks...done

c1t50050768013036A1d0: configured with capacity of 12.00GB
c1t50050768014036A1d0: configured with capacity of 12.00GB
c1t50050768013036A1d1: configured with capacity of 31.98GB
c1t50050768014036A1d1: configured with capacity of 31.98GB
c1t50050768014036A1d2: configured with capacity of 209.98GB
c1t50050768013036A1d2: configured with capacity of 209.98GB
c1t50050768013036A1d3: configured with capacity of 209.98GB
c1t50050768014036A1d3: configured with capacity of 209.98GB
c1t50050768014036A1d4: configured with capacity of 209.98GB
c1t50050768013036A1d4: configured with capacity of 209.98GB
c1t50050768013036A1d5: configured with capacity of 209.98GB
c1t50050768014036A1d5: configured with capacity of 209.98GB
c1t50050768013036A1d6: configured with capacity of 209.98GB
c1t50050768014036A1d6: configured with capacity of 209.98GB
c1t50050768013036A1d7: configured with capacity of 209.98GB
c1t50050768014036A1d7: configured with capacity of 209.98GB
c1t5005076801303680d0: configured with capacity of 12.00GB
c1t5005076801403680d0: configured with capacity of 12.00GB
c1t5005076801403680d1: configured with capacity of 31.98GB
c1t5005076801303680d1: configured with capacity of 31.98GB
c1t5005076801303680d2: configured with capacity of 209.98GB
c1t5005076801403680d2: configured with capacity of 209.98GB
c1t5005076801303680d3: configured with capacity of 209.98GB
c1t5005076801403680d3: configured with capacity of 209.98GB
c1t5005076801403680d4: configured with capacity of 209.98GB
c1t5005076801303680d4: configured with capacity of 209.98GB
c1t5005076801303680d5: configured with capacity of 209.98GB
c1t5005076801403680d5: configured with capacity of 209.98GB
c1t5005076801403680d6: configured with capacity of 209.98GB
c1t5005076801303680d6: configured with capacity of 209.98GB
c1t5005076801403680d7: configured with capacity of 209.98GB
c1t5005076801303680d7: configured with capacity of 209.98GB
c2t50050768012036A1d0: configured with capacity of 12.00GB
c2t50050768011036A1d0: configured with capacity of 12.00GB
c2t50050768012036A1d1: configured with capacity of 31.98GB
c2t50050768011036A1d1: configured with capacity of 31.98GB
c2t50050768011036A1d2: configured with capacity of 209.98GB
c2t50050768012036A1d2: configured with capacity of 209.98GB
c2t50050768011036A1d3: configured with capacity of 209.98GB
c2t50050768012036A1d3: configured with capacity of 209.98GB
c2t50050768011036A1d4: configured with capacity of 209.98GB
c2t50050768012036A1d4: configured with capacity of 209.98GB
c2t50050768011036A1d5: configured with capacity of 209.98GB
c2t50050768012036A1d5: configured with capacity of 209.98GB
c2t50050768012036A1d6: configured with capacity of 209.98GB
c2t50050768011036A1d6: configured with capacity of 209.98GB
c2t50050768011036A1d7: configured with capacity of 209.98GB
c2t50050768012036A1d7: configured with capacity of 209.98GB
c2t5005076801103680d0: configured with capacity of 12.00GB
c2t5005076801203680d0: configured with capacity of 12.00GB
c2t5005076801103680d1: configured with capacity of 31.98GB
c2t5005076801203680d1: configured with capacity of 31.98GB
c2t5005076801203680d2: configured with capacity of 209.98GB
c2t5005076801103680d2: configured with capacity of 209.98GB
c2t5005076801103680d3: configured with capacity of 209.98GB
c2t5005076801203680d3: configured with capacity of 209.98GB
c2t5005076801203680d4: configured with capacity of 209.98GB
c2t5005076801103680d4: configured with capacity of 209.98GB
c2t5005076801203680d5: configured with capacity of 209.98GB
c2t5005076801103680d5: configured with capacity of 209.98GB
c2t5005076801103680d6: configured with capacity of 209.98GB
c2t5005076801203680d6: configured with capacity of 209.98GB
c2t5005076801203680d7: configured with capacity of 209.98GB
c2t5005076801103680d7: configured with capacity of 209.98GB

AVAILABLE DISK SELECTIONS:
0. c0t9d0
/pci@19c,700000/pci@1/pci@1/scsi@2/sd@9,0
1. c0t10d0
/pci@19c,700000/pci@1/pci@1/scsi@2/sd@a,0
2. c0t11d0
/pci@19c,700000/pci@1/pci@1/scsi@2/sd@b,0
3. c1t50050768013036A1d0
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768013036a1,0
4. c1t50050768014036A1d0
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768014036a1,0
5. c1t50050768013036A1d1
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768013036a1,1
6. c1t50050768014036A1d1
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768014036a1,1
7. c1t50050768014036A1d2
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768014036a1,2
8. c1t50050768013036A1d2
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768013036a1,2
9. c1t50050768013036A1d3
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768013036a1,3
10. c1t50050768014036A1d3
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768014036a1,3
11. c1t50050768014036A1d4
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768014036a1,4
12. c1t50050768013036A1d4
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768013036a1,4
13. c1t50050768013036A1d5
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768013036a1,5
14. c1t50050768014036A1d5
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768014036a1,5
15. c1t50050768013036A1d6
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768013036a1,6
16. c1t50050768014036A1d6
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768014036a1,6
17. c1t50050768013036A1d7
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768013036a1,7
18. c1t50050768014036A1d7
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768014036a1,7
19. c1t5005076801303680d0
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801303680,0
20. c1t5005076801403680d0
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801403680,0
21. c1t5005076801403680d1
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801403680,1
22. c1t5005076801303680d1
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801303680,1
23. c1t5005076801303680d2
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801303680,2
24. c1t5005076801403680d2
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801403680,2
25. c1t5005076801303680d3
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801303680,3
26. c1t5005076801403680d3
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801403680,3
27. c1t5005076801403680d4
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801403680,4
28. c1t5005076801303680d4
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801303680,4
29. c1t5005076801303680d5
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801303680,5
30. c1t5005076801403680d5
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801403680,5
31. c1t5005076801403680d6
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801403680,6
32. c1t5005076801303680d6
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801303680,6
33. c1t5005076801403680d7
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801403680,7
34. c1t5005076801303680d7
/pci@19c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801303680,7
35. c2t50050768012036A1d0
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768012036a1,0
36. c2t50050768011036A1d0
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768011036a1,0
37. c2t50050768012036A1d1
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768012036a1,1
38. c2t50050768011036A1d1
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768011036a1,1
39. c2t50050768011036A1d2
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768011036a1,2
40. c2t50050768012036A1d2
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768012036a1,2
41. c2t50050768011036A1d3
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768011036a1,3
42. c2t50050768012036A1d3
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768012036a1,3
43. c2t50050768011036A1d4
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768011036a1,4
44. c2t50050768012036A1d4
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768012036a1,4
45. c2t50050768011036A1d5
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768011036a1,5
46. c2t50050768012036A1d5
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768012036a1,5
47. c2t50050768012036A1d6
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768012036a1,6
48. c2t50050768011036A1d6
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768011036a1,6
49. c2t50050768011036A1d7
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768011036a1,7
50. c2t50050768012036A1d7
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w50050768012036a1,7
51. c2t5005076801103680d0
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801103680,0
52. c2t5005076801203680d0
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801203680,0
53. c2t5005076801103680d1
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801103680,1
54. c2t5005076801203680d1
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801203680,1
55. c2t5005076801203680d2
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801203680,2
56. c2t5005076801103680d2
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801103680,2
57. c2t5005076801103680d3
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801103680,3
58. c2t5005076801203680d3
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801203680,3
59. c2t5005076801203680d4
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801203680,4
60. c2t5005076801103680d4
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801103680,4
61. c2t5005076801203680d5
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801203680,5
62. c2t5005076801103680d5
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801103680,5
63. c2t5005076801103680d6
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801103680,6
64. c2t5005076801203680d6
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801203680,6
65. c2t5005076801203680d7
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801203680,7
66. c2t5005076801103680d7
/pci@19d,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076801103680,7
Specify disk (enter its number):
ACA viene el tema, porque hasta ahora no veo los discos por VPATH, despues de estos comandos locos, recien los empiezo a ver.
[coneja] /opt/IBMsdd/bin # cfgvpath
Vpath: Configuring 64 devices (8 disks * 8 slices)
[coneja] /opt/IBMsdd/bin #
[coneja] /opt/IBMsdd/bin # vpathmkdev
[coneja] /opt/IBMsdd/bin #
Hago un extracto de la salida del format, para hacerlo mas corto.
[coneja] /opt/IBMsdd/bin # format
Searching for disks...done

c1t50050768014036A1d0: configured with capacity of 12.00GB
c1t50050768013036A1d0: configured with capacity of 12.00GB
c1t50050768014036A1d1: configured with capacity of 31.98GB
c1t50050768013036A1d1: configured with capacity of 31.98GB
c1t50050768014036A1d2: configured with capacity of 209.98GB
c1t50050768013036A1d2: configured with capacity of 209.98GB
c1t50050768013036A1d3: configured with capacity of 209.98GB
c1t50050768014036A1d3: configured with capacity of 209.98GB
c1t50050768014036A1d4: configured with capacity of 209.98GB
c1t50050768013036A1d4: configured with capacity of 209.98GB
c1t50050768013036A1d5: configured with capacity of 209.98GB
c1t50050768014036A1d5: configured with capacity of 209.98GB
c1t50050768014036A1d6: configured with capacity of 209.98GB
c1t50050768013036A1d6: configured with capacity of 209.98GB
c1t50050768014036A1d7: configured with capacity of 209.98GB
c1t50050768013036A1d7: configured with capacity of 209.98GB
c1t5005076801403680d0: configured with capacity of 12.00GB
c1t5005076801303680d0: configured with capacity of 12.00GB
c1t5005076801403680d1: configured with capacity of 31.98GB
c1t5005076801303680d1: configured with capacity of 31.98GB
c1t5005076801303680d2: configured with capacity of 209.98GB
c1t5005076801403680d2: configured with capacity of 209.98GB
c1t5005076801303680d3: configured with capacity of 209.98GB
c1t5005076801403680d3: configured with capacity of 209.98GB
c1t5005076801403680d4: configured with capacity of 209.98GB
c1t5005076801303680d4: configured with capacity of 209.98GB
c1t5005076801303680d5: configured with capacity of 209.98GB
c1t5005076801403680d5: configured with capacity of 209.98GB
c1t5005076801403680d6: configured with capacity of 209.98GB
c1t5005076801303680d6: configured with capacity of 209.98GB
c1t5005076801303680d7: configured with capacity of 209.98GB
c1t5005076801403680d7: configured with capacity of 209.98GB
c2t50050768012036A1d0: configured with capacity of 12.00GB
c2t50050768011036A1d0: configured with capacity of 12.00GB
c2t50050768011036A1d1: configured with capacity of 31.98GB
c2t50050768012036A1d1: configured with capacity of 31.98GB
c2t50050768012036A1d2: configured with capacity of 209.98GB
c2t50050768011036A1d2: configured with capacity of 209.98GB
c2t50050768011036A1d3: configured with capacity of 209.98GB
c2t50050768012036A1d3: configured with capacity of 209.98GB
c2t50050768011036A1d4: configured with capacity of 209.98GB
c2t50050768012036A1d4: configured with capacity of 209.98GB
c2t50050768012036A1d5: configured with capacity of 209.98GB
c2t50050768011036A1d5: configured with capacity of 209.98GB
c2t50050768012036A1d6: configured with capacity of 209.98GB
c2t50050768011036A1d6: configured with capacity of 209.98GB
c2t50050768011036A1d7: configured with capacity of 209.98GB
c2t50050768012036A1d7: configured with capacity of 209.98GB
c2t5005076801203680d0: configured with capacity of 12.00GB
c2t5005076801103680d0: configured with capacity of 12.00GB
c2t5005076801203680d1: configured with capacity of 31.98GB
c2t5005076801103680d1: configured with capacity of 31.98GB
c2t5005076801203680d2: configured with capacity of 209.98GB
c2t5005076801103680d2: configured with capacity of 209.98GB
c2t5005076801103680d3: configured with capacity of 209.98GB
c2t5005076801203680d3: configured with capacity of 209.98GB
c2t5005076801203680d4: configured with capacity of 209.98GB
c2t5005076801103680d4: configured with capacity of 209.98GB
c2t5005076801203680d5: configured with capacity of 209.98GB
c2t5005076801103680d5: configured with capacity of 209.98GB
c2t5005076801103680d6: configured with capacity of 209.98GB
c2t5005076801203680d6: configured with capacity of 209.98GB
c2t5005076801103680d7: configured with capacity of 209.98GB
c2t5005076801203680d7: configured with capacity of 209.98GB
vpath1a: configured with capacity of 209.98GB
vpath2h: configured with capacity of 209.98GB con este tuve problemas despues
vpath3a: configured with capacity of 209.98GB
vpath4a: configured with capacity of 209.98GB
vpath5a: configured with capacity of 209.98GB
vpath6a: configured with capacity of 209.98GB
vpath7a: configured with capacity of 31.98GB
vpath8a: configured with capacity of 12.00GB

[coneja] /opt/IBMsdd/bin #
Me encontre con u problema, me creo un vpath2h en lugar de un vpath1a, me di cuenta cuando le hice el metainit , que me puteo, lo solucione borrando y recreando los vpath.

[coneja] /opt/IBMsdd/bin # metainit d301 1 3 vpath1a vpath2h vpath3a
metainit: coneja: vpath2h: No space left on device

[coneja] /opt/IBMsdd/bin #

coneja] /opt/IBMsdd/bin # rmvpath -b -all
Continuing will remove IBMsdd vpath device binding with serial number.
Do you want to continue (y/n)?: y
Continuing will remove all IBMsdd vpath devices.
Do you want to continue (y/n)?: y
Removing all vpath devices...
[coneja] /opt/IBMsdd/bin # cfgvpath
Vpath: Configuring 64 devices (8 disks * 8 slices)
[coneja] /opt/IBMsdd/bin # vpathmkdev
[coneja] /opt/IBMsdd/bin #
Luego, me genero todo ok .
[coneja] /opt/IBMsdd/bin # metainit d301 1 3 vpath1a vpath2a vpath3a
d301: Concat/Stripe is setup
[coneja] /opt/IBMsdd/bin # metastat d301
d301: Concat/Stripe
Size: 1321058304 blocks (629 GB)
Stripe 0: (interlace: 32 blocks)
Device Start Block Dbase Reloc
/dev/dsk/vpath1a 0 No Yes
/dev/dsk/vpath2a 16384 No Yes
/dev/dsk/vpath3a 16384 No Yes

Device Relocation Information:
Device Reloc Device ID
/dev/dsk/vpath1a Yes id1,thdd@n60050768019901b400000000000002ba
/dev/dsk/vpath2a Yes id1,thdd@n60050768019901b400000000000002b8
/dev/dsk/vpath3a Yes id1,thdd@n60050768019901b400000000000002b7
[coneja] /opt/IBMsdd/bin #

Configurar MPXIO con NETAPP en Solaris 10

2011-02-28T16:30:00.000-03:00

La gente que administra el storage debemos pedirle que habilite la opción ALUA en el storage para que pueda balancear el MPXIO.

Instalar la toolkit de netapp: NETAPSANTool ( pkgadd -d nomredelpaquete)

Ejecutar: /opt/NTAP/SANToolkit/mpxio_set –d “ con este comando se elimina las opciones del scsi_vhci.conf, que no las utiliza”

Ejecutar: /opt/NTAP/SANToolkit/basic_config –ssd_set “esto es para SPARC, para x86 la opcion es –sd_set”

Touch /reconfigure

Verificar UPDATE de la versión del SOLARIS

Ejecutar: stmsboot –e (para versiones anteriores al UPDATE 5) “aceptar cambios, cuando termina pide bootear”

Ejecutar: stmsboot –D fp –e (para versiónes UPDATE 5 y posteriores)

Para este caso, anduvo perfecto, pero hubo otras oportunidades donde se tuvo que tocar el ssd.conf, fp.conf, y mpt.conf

Panic +Aplicacion de Patches + Panic debido a los patches.

2011-02-16T13:20:00.000-03:00

Debido a un panic en un solaris 10 sparc, causado por el BUG ID: 6696124
- Null mutex pointer crashing from ip_wput_ioctl() el cual fue solucionado en la versión de Kernel 141444-02 (S10 sparc) y que Sun recomendo instalar como mínimo el parche 141444-09, debido a que se trata de un parche de Kernel, me puse a bajar los recommended and security patches
ACA EMPIEZAN LOS OTROS PROBLEMITAS (PANIC )
Cuando instale los parches recomendados, al finalizar al hacer un reboot , me daba panic.
/platform/SUNW,Sun-Fire-15000/kernel/drv/sparcv9/dr: undefined symbol 'tod_status_set' WARNING: mod_load: cannot load module
'dr' WARNING: dr failed to load /kernel/misc/sparcv9/strplumb: undefined symbol 'iscsiboot_prop'
WARNING: mod_load: cannot load module 'strplumb' panic[cpu480]/thread=180e000: mod_hold_stub: Couldn't load stub module
misc/strplumb 000000000180b890 genunix:mod_hold_stub+1f0 (0, 18ed000, 193c2d0, 60022de1c70, 1839810, 0)
%l0-3: 00000000018ba598 0000060023180000 00000000018337f0 0000000000000000 %l4-7: 0000000000000000 0000000000000064
0000000000000064 0000000000000000 000000000180b940 unix:stubs_common_code+30 (0, 1ed437, 193ec00, 1941c00, 1263c00, 183c400)
%l0-3: 000000000180b209 000000000180b2e1 000001e3f5000000 0000000000000001 %l4-7: 0000000000000000 0000000001839820
0000000000000000 0000060022ccf258 000000000180ba10 genunix:main+f8 (1835f78, 0, 18883e0, 193c000, 183c378, 1835c00) %l0-3:
0000000001015400 0000000000000001 0000000070002000 0000000000000000 %l4-7: 0000000001893400 00000000000001e0
000000000180c000 0000000000000000 syncing file systems... done skipping system dump - no dump device configured rebooting...
Resetting...
Vi por ahi, que hay un bug id, que cuando tenes SVM en los dicos internos ( por ejemplo el mirror del os ) con solaris 10 y update 8 tiene el mismo problema que me dio a mi.
Antes de instalar los parches en este dominio de la 25k.
Los instale en una v215, con misma version de solaris 10. El error no se reprodujo, pienso yo, porque NO tenia los discos mirroreados con SVM, porque para lo unico que uso en ese equipo el SVM es para concatenar unas luns y crear un fs.
Los pasos que realize para que el equipo quede operativo y con los parches instalados fueron :
Desencapsule el disco de booteo ( usando el procedimiento descripto en este blog) que tenia con SVM.
fsck al disco primario.
borre las replicas del disco secundario.
bootee con el disco primario y levanto todo.
Luego lo que hice, fue volver a encapsular el disco de booteo

Configurando Sun Cluster 3.2 con Oracle 10g RAC y ASM

2011-02-15T08:25:00.000-03:00

Mi articulo publicado en bigadmin http://www.sun.com/bigadmin/content/submitted/es/span_cluster_rac.jsp

Configurar NTP

2011-02-07T11:07:00.000-03:00

Crear el archivo /etc/inet/ntp.conf con el siguiente contenido :
server NOMBREDELSERVERNTP prefer
driftfile /var/ntp/ntp.drift
statsdir /var/ntp/ntpstats
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable

/var/ntp # more ntp.drift
-11.305

svcadm enable svc:/network/ntp
svcadm refresh svc:/network/ntp
svcadm restart svc:/network/ntp

Actualizar Firmware de ALOM

2011-01-12T08:56:00.000-03:00

sc-asun0005> flashupdate -s 10.11.33.114 -f /firmware/alomfw
Username: ********
Password: *sc-asun0005> flashupdate -s 10.11.33.114 -f /firmware/alomfw
Username: root
Password: *******

..................................................................................................................................
Update complete. Reset device to use new image.
sc-asun0005>
SC Alert: SC firmware was reloaded

sc-asun0005>

sc-asun0005> resetsc
Are you sure you want to reset the SC [y/n]? y
User Requested SC Shutdown

coneja:/coneja # ssh 10.71.100.216

Copyright 2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.

Sun(tm) Advanced Lights Out Manager 1.6.10 (asun005)

Please login: admin
Please Enter password: *******

sc-asun0005> showsc -v
Advanced Lights Out Manager v1.6.10

El Firmware que instale es ALOM_1.6.10_fw_hw8.tar.gz que lo baje del dvd del EISCD.

Error : No se puede asignar Recursos a los proyectos

2010-11-23T13:30:00.000-03:00

Problema : No se puede asignar recursos a los proyectos.

Ejemplo de error mostrado:
project.max-shm-memory resource control assignment failed for project "user.oracle"
su:
unable to set credentials

Releases en lo que se presento el problema :
Solaris 10
Release 01/06 y 06/06
.

Solucion :
Requiere el siguiente patch instalado 120473-12 .
El problema es que dicho parche tiene muchas dependencias, entonces conviene instalar el cluster recomended and security patches.
Si se opta por este ultimo, se debe correr el install_patches, rebootear y volver a ejecutar la instalacion del install_patches con su posterior reboot.

Copia de fs con cpio

2010-10-06T13:03:00.000-03:00

cd /u00
time find . -print -depth |cpio -pdm /u00.NEW

Agregar Filesystem al Sun Cluster 3.2

2010-10-04T11:08:00.000-03:00

La finalidad es agregar el filesystem /u07 al Cluster ( conviene hacerlo con la BD baja)
1) Descubro los discos en Solaris
cfgadm -f -c configure c(nro de controladora)
devfsadm -C ( -C significa modo Clean Up )
devfsadm ( crea special files en el /devices y logical links en /dev )
scdidadm -C ( remueve todas las referencias DID de todos los dispositivos Detachados )
scdidadm -r ( reconfiguro los DID ) (en ambos nodos )
scgdevs ( updatea el /globaldevices )
scdpm -p all:all ( chequea que este bien el did en ambos nodos del cluster, suele demorar un rato , no menos de 5 minutos dependiendo la cantidad de discos que tenga)

OJO: Los comandos arriba mencionados,Deben ser ejecutados en AMBOS nodos del cluster

vxdctl enable
agrego los discos en el Veritas ( uso por ejemplo el vxdiskadm menu opcion 1 )

# vxdisk list
# vxassist -g CCtdg make vol25 51687m layout=stripe CCtdg16 CCtdg17 CCtdg18

cldevicegroup sync CCtdg

newfs /dev/vx/rdsk/CCtdg/vol25
Poner el NUEVO FILESYSTEM en el /etc/vfstab de AMBOS NODOS
Conviene poner el cluster en modo mantenimiento, para poder bajar y subir la base de datos, las veces que se necesite y que no se migre el cluster.

clrg suspend cct-rg

Ahora puedo agregar el nuevo filesystem al control del cluster
clrs set -g cct-rg -p FileSystemMountPoints="/u04,/u05,/u00,/archive/u01,/u03,/u02\
,/u06,/u07" cct-hastp-rs

En los parametros del FileSystemMountPoints, dentro e las comillas, hay que poner todos los FS, los que habia antes mas los que estamos agregando.

NO DEJAR ESPACIOS EN BLANCO ENTRE LA COMA ( , ) Y EL NOMBRE DE LOS FILESYSTEMS.

Luego , poner el cluster en modo normal
clrg resume cct-rg

~

Identificar Modelo y Revision de Firmware en Placas de Fibra

2010-09-27T10:26:00.000-03:00

Este comando me muestra el modelo de placa de fibra y la revision de firmware
# luxadm fcode_download -p

Found Path to 0 FC/S Cards
Complete

Found Path to 0 FC100/S Cards
Complete

Found Path to 4 FC100/P, ISP2200, ISP23xx Devices

Opening Device: /devices/pci@9c,600000/SUNW,qlc@1/fp@0,0:devctl
Detected FCode Version: ISP2312 Host Adapter fcode version 1.17 08/09/07

Opening Device: /devices/pci@9c,600000/SUNW,qlc@1,1/fp@0,0:devctl
Detected FCode Version: ISP2312 Host Adapter fcode version 1.17 08/09/07

Opening Device: /devices/pci@9d,600000/SUNW,qlc@1/fp@0,0:devctl
Detected FCode Version: ISP2312 Host Adapter fcode version 1.16 11/15/06

Opening Device: /devices/pci@9d,600000/SUNW,qlc@1,1/fp@0,0:devctl
Detected FCode Version: ISP2312 Host Adapter fcode version 1.16 11/15/06
Complete

Found Path to 0 JNI1560 Devices.
Complete

Found Path to 0 Emulex Devices.
Complete
#

Configurar MPXIO en Solaris 10 x86

2010-09-21T16:57:00.000-03:00

Para Configurar MPXIO , con discos de NETAPP n5600 se debe.
editar y modificar ( en el caso que existiese) en el archivo /kernel/drv/fp.conf la sig linea
mpxio-disable="no";

y en el archivo /kernel/drv/scsi_vhci.conf las siguientes 3 lineas generalmente al final del archivo.
device-type-scsi-options-list =
"NETAPP LUN", "symmetric-option";
symmetric-option = 0x1000000;

***ES IMPORTANTE RESPETAR LOS ESPACIOS EN BLANCO en LA LINEA "NETAPP LUN", "symmetric-option"; ***

Desencapsular disco de booteo con SVM

2010-09-21T10:53:00.000-03:00

Bootear en single user con cd o desde la red

Montar la particion root
# mount /dev/dsk/c0t0d0s0 /a

Hacer backup del /etc/vfstab y del /etc/system
# cp /a/etc/vfstab /a/etc/vfstab.orig
# cp /a/etc/system /a/etc/system.orig

Editar y modificar el vfstab y el system que montamos en /a
# vi /a/etc/vfstab

( Cambiar los metadevices del disco de booteo por las particiones como ser .
donde dice /dev/md/dsk/d10 poner /dev/dsk/c0t0d0s0 idem para los raw device y tanto para root, swap, /var si es que hubiese etc )
/dev/dsk/c0t10d0s0 /dev/rdsk/c0t10d0s0 / ufs 1 no nologging
/dev/dsk/c0t10d0s5 /dev/rdsk/c0t10d0s5 /var/crash ufs 2 yes nologging
/dev/dsk/c0t10d0s1 - - swap - no -

Comentar el resto de los filesystems que sean metadevices y que no correspondan al S.O.

# vi /a/etc/system

( Comentar las lineas de rootdev , recordar que en el /etc/system se comenta con * )

**set md:mirrored_root_flag = 1

** rootdev:/pseudo/md@0:0,0,blk

Desmontar el /a

# init 6 ( reboot del servidor)

Inmediatamente encapsular y rearmar el mirror. dado que las replicas estan vivas todavia y pueden generar algun problema.

Agradecimiento a Charly

Como Asignar una System Board a un 25k

2010-08-05T14:36:00.001-03:00

La tarea solicitada aca, es.. agregar la System Board 6 al dominio B .
OJO, si las CPU son de distintas velocidades entre la SB actual y la que quiero agregar, hay que Rebootear.
Nota: Las IO Boards NO tienen flashprom para ser actualizados.

Una vez que inserte fisicamente la placa, vamos a agregar con Dynamic Reconfiguration la Nueva SB al dominio , con su paso previo de upgrade o downgrade como en este caso, del firmware de la placa.

e25k-sc0:sms-svc:1> showboards -v
Retrieving board information. Please wait.
.............
Location Pwr Type of Board Board Status Test Status Domain
-------- --- ------------- ------------ ----------- ------
SC0 On SC Main - -
SC1 On SC Spare - -
PS0 On PS-A196 - - -
PS1 On PS-A196 - - -
PS2 On PS-A196 - - -
PS3 On PS-A196 - - -
PS4 On PS-A196 - - -
PS5 On PS-A196 - - -
FT0 On FANTRAY - - -
FT1 On FANTRAY - - -
FT2 On FANTRAY - - -
FT3 On FANTRAY - - -
FT4 On FANTRAY - - -
FT5 On FANTRAY - - -
FT6 On FANTRAY - - -
FT7 On FANTRAY - - -
CS0 On CSB - - -
CS1 On CSB - - -
EX0 On EXB - - -
EX1 On EXB - - -
EX2 On EXB - - -
EX3 On EXB - - -
EX4 On EXB - - -

EX5 On EXB - - -

EX6 Off EXB - - -

EX7 Off EXB - - -

EX8 Off EXB - - -

EX9 On EXB - - -

EX10 On EXB - - -

EX11 On EXB - - -

EX12 On EXB - - -

EX13 On EXB - - -

EX14 On EXB - - -

EX15 On EXB - - -

EX16 Off EXB - - -

EX17 Off EXB - - -

IO0/C3V0 On C3V - - e25k-2-A

IO0/C5V0 On C5V - - e25k-2-A

IO0/C3V1 On C3V - - e25k-2-A

IO0/C3V2 On C3V - - e25k-2-A

IO1/C3V0 On C3V - - e25k-2-B

IO1/C5V0 On C5V - - e25k-2-B

IO1/C3V1 On C3V - - e25k-2-B

IO1/C3V2 On C3V - - e25k-2-B

IO2/C3V0 On C3V - - e25k-2-C

IO2/C5V0 On C5V - - e25k-2-C

IO2/C3V1 On C3V - - e25k-2-C

IO2/C3V2 On C3V - - e25k-2-C

IO3/C3V0 On C3V - - e25k-2-D

IO3/C5V0 On C5V - - e25k-2-D

IO1/C3V1 On C3V - - e25k-2-B

IO1/C3V2 On C3V - - e25k-2-B

IO2/C3V0 On C3V - - e25k-2-C

IO2/C5V0 On C5V - - e25k-2-C

IO2/C3V1 On C3V - - e25k-2-C

IO2/C3V2 On C3V - - e25k-2-C

IO3/C3V0 On C3V - - e25k-2-D

IO3/C5V0 On C5V - - e25k-2-D

IO3/C3V1 On C3V - - e25k-2-D

IO3/C3V2 On C3V - - e25k-2-D

IO4/C3V0 On C3V - - e25k-2-J

IO4/C5V0 On C5V - - e25k-2-J

IO4/C3V1 On C3V - - e25k-2-J

IO4/C3V2 On C3V - - e25k-2-J

IO9/C3V0 On C3V - - e25k-2-E

IO9/C5V0 On C5V - - e25k-2-E

IO9/C3V1 On C3V - - e25k-2-E

IO9/C3V2 On C3V - - e25k-2-E

IO10/C3V0 On C3V - - e25k-2-F

IO10/C5V0 On C5V - - e25k-2-F

IO10/C3V1 On C3V - - e25k-2-F

IO10/C3V2 On C3V - - e25k-2-F

IO11/C3V0 On C3V - - e25k-2-G

IO11/C5V0 On C5V - - e25k-2-G

IO11/C3V1 On C3V - - e25k-2-G

IO11/C3V2 On C3V - - e25k-2-G

IO12/C3V0 On C3V - - e25k-2-H

IO12/C5V0 On C5V - - e25k-2-H

IO12/C3V1 On C3V - - e25k-2-H

IO12/C3V2 On C3V - - e25k-2-H

IO13/C3V0 On C3V - - e25k-2-H

IO13/C5V0 On C5V - - e25k-2-H

IO13/C3V1 On C3V - - e25k-2-H

IO13/C3V2 On C3V - - e25k-2-H

IO14/C3V0 On C3V - - I

IO14/C5V0 On C5V - - I

IO14/C3V1 On C3V - - I

IO14/C3V2 On C3V - - I

IO15/C3V0 Off Unknown - - Isolated

IO15/C5V0 Off Unknown - - Isolated

IO15/C3V1 Off Unknown - - Isolated

IO15/C3V2 Off Unknown - - Isolated

SB0 On V3CPU Active Passed e25k-2-A

SB1 On V3CPU Active Passed e25k-2-B

SB2 On V3CPU Active Passed e25k-2-C

SB3 On V3CPU Active Passed e25k-2-D

SB4 On V3CPU Active Passed e25k-2-J

SB5 On V3CPU Active Passed e25k-2-E

SB6 Off V3CPU Available Unknown Isolated

SB7 - Empty Slot Available - Isolated

SB8 - Empty Slot Available - Isolated

SB9 On V3CPU Active Passed e25k-2-E

SB10 On V3CPU Active Passed e25k-2-F

SB11 On V3CPU Active Passed e25k-2-G

SB12 On V3CPU Active Passed e25k-2-H

SB13 On V3CPU (COD) Active Passed e25k-2-H

SB14 On V3CPU Active Passed I

SB15 On V3CPU Active Passed e25k-2-A

SB16 - Empty Slot Available - Isolated

SB17 - Empty Slot Available - Isolated

IO0 On HPCI+ Active Passed e25k-2-A

IO1 On HPCI+ Active Passed e25k-2-B

IO2 On HPCI+ Active Passed e25k-2-C

IO3 On HPCI+ Active Passed e25k-2-D

IO4 On HPCI+ Active Passed e25k-2-J

IO5 - Empty Slot Available - Isolated

IO6 - Empty Slot Available - Isolated

IO7 - Empty Slot Available - Isolated

IO8 - Empty Slot Available - Isolated

IO9 On HPCI+ Active Passed e25k-2-E

IO10 On HPCI+ Active Passed e25k-2-F

IO11 On HPCI+ Active Passed e25k-2-G

IO12 On HPCI+ Active Passed e25k-2-H

IO13 On HPCI+ Active Passed e25k-2-H

IO14 On HPCI+ Active Passed I

IO15 Off HPCI+ Available Unknown Isolated

IO16 - Empty Slot Available - Isolated

IO17 - Empty Slot Available - Isolated

e25k-sc0:sms-svc:2>
Primero Enciendo el Expander, sino falla el encedido de la SB.

e25k-sc0:sms-svc:3> poweron EX6

e25k-sc0:sms-svc:4>

e25k-sc0:sms-svc:4> poweron SB6

e25k-sc0:sms-svc:5> showboards

Retrieving board information. Please wait.

..............................

Location Pwr Type of Board Board Status Test Status Domain

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

SB0 On V3CPU Active Passed e25k-2-A

SB1 On V3CPU Active Passed e25k-2-B

SB2 On V3CPU Active Passed e25k-2-C

SB3 On V3CPU Active Passed e25k-2-D

SB4 On V3CPU Active Passed e25k-2-J

SB5 On V3CPU Active Passed e25k-2-E

SB6 On V3CPU Available Unknown Isolated

SB7 - Empty Slot Available - Isolated

SB8 - Empty Slot Available - Isolated

SB9 On V3CPU Active Passed e25k-2-E

SB10 On V3CPU Active Passed e25k-2-F

SB11 On V3CPU Active Passed e25k-2-G

SB12 On V3CPU Active Passed e25k-2-H

SB13 On V3CPU Active Passed e25k-2-H

SB14 On V3CPU Active Passed I

SB15 On V3CPU Active Passed e25k-2-A

SB16 - Empty Slot Available - Isolated

SB17 - Empty Slot Available - Isolated

IO0 On HPCI+ Active Passed e25k-2-A

IO1 On HPCI+ Active Passed e25k-2-B

IO2 On HPCI+ Active Passed e25k-2-C

IO3 On HPCI+ Active Passed e25k-2-D

IO4 On HPCI+ Active Passed e25k-2-J

IO5 - Empty Slot Available - Isolated

IO6 - Empty Slot Available - Isolated

IO7 - Empty Slot Available - Isolated

IO8 - Empty Slot Available - Isolated

IO9 On HPCI+ Active Passed e25k-2-E

IO10 On HPCI+ Active Passed e25k-2-F

IO11 On HPCI+ Active Passed e25k-2-G

IO12 On HPCI+ Active Passed e25k-2-H

IO13 On HPCI+ Active Passed e25k-2-H

IO14 On HPCI+ Active Passed I

IO15 Off HPCI+ Available Unknown Isolated

IO16 - Empty Slot Available - Isolated

IO17 - Empty Slot Available - Isolated

e25k-sc0:sms-svc:6>
Ahora voy a actualizar el firmware, en este caso voy a hacer un downgrade, porque las placas que ya tenia el dominio estan con un nivel inferior

e25k-sc0:sms-svc:18> flashupdate -f /opt/SUNWSMS/hostobjs/sgcpu.flash SB6

Current System Board FPROM Information

========================================

V3CPU at SB6, FPROM 0:

POST 05/23/07 08:54:00 Release 5.20.6 Build 2.0 I/F 12

OBP 05/23/07 08:53:00 Release 5.20.6 Build 2.0

Ver 05/23/07 08:56:00 Release 5.20.6 Build 2.0

V3CPU at SB6, FPROM 1:

POST 05/23/07 08:54:00 Release 5.20.6 Build 2.0 I/F 12

OBP 05/23/07 08:53:00 Release 5.20.6 Build 2.0

Ver 05/23/07 08:56:00 Release 5.20.6 Build 2.0

Flash Image Information

==========================

POST 04/04/06 17:32:00 Release 5.20.0 Build 15.1 I/F 12

OBP 04/04/06 17:31:00 Release 5.20.0 Build 15.1

Ver 04/04/06 17:33:00 Release 5.20.0 Build 15.1

Do you wish to update the FPROM (yes/no)? yes

Update V3CPU at SB6, FPROM 0:

Erasing...

Done.

Writing and verifying ...

Done.

Update V3CPU at SB6, FPROM 1:

Erasing...

Done.

Writing and verifying ...

Done.

e25k-sc0:sms-svc:19>

e25k-sc0:sms-svc:23> addboard -d b SB6

assign SB6

assign SB6 done

poweron SB6

...

poweron SB6 done

test SB6

.....................

test SB6 done

connect SB6

....................

connect SB6 done

configure SB6

........

configure SB6 done

notify online SUNW_cpu/cpu192

notify online SUNW_cpu/cpu196

notify online SUNW_cpu/cpu193

notify online SUNW_cpu/cpu197

notify online SUNW_cpu/cpu194

notify online SUNW_cpu/cpu198

notify online SUNW_cpu/cpu195

notify online SUNW_cpu/cpu199

notify add capacity (8 cpus)

notify add capacity (4194304 pages)

notify add capacity SB6 done

e25k-sc0:sms-svc:24>

Comandos ZONAS

2010-07-14T14:40:00.000-03:00

Chequear zona

zoneadm list -cv (lista las zonas y sus estados)
zoneadm -z zona1 ready (de estado install a ready)
zoneadm -z zona1 boot (de estado ready a running)
zlogin -C zona1 (logueo en la zona para levantar servicios ...
..despues de esto , se puede entrar con telnet ssh)
Nota: si es la primera vez,hay que ingresar varios datos de configuracion TZ,hostaname etc)

Otros chequeos zona

zoneadm -z zona1 reboot (funciona si la zona esta running)
zoneadm -z zona1 halt
zoneadm -z zona1 verify
zoneadm -z zona1 uninstall (desinstalar zona)
zoneadm -z zona1 uninstall -F (desinstalar zona)
zonecfg -z zona1 delete (debe estar desinstalada previamente)
zonecfg -z zona1 info

Backup configuracion zona

zonecfg -z zona1 export >zona1.config

Configuracion zona

Restore de Zona

Caso 1 Se perdio la configuracion

zonecfg -z zona1 -f zona1.config
zoneadm list -cv (debe aparecer la zona como configurada)
zoneadm -z zona1 install (debe aparecer la zona como instalada)(Ir a paso 2)
rm /export/zona1/root/etc/.UNCONFIGURED (para evitar preguntas al ingresar por consola)

Caso 2 La zona esta en estado instalada)

ufsrestore -ivf zona1.DMP
mv dev /export/zona1/
mv root /export/zona1/
zoneadm list -cv
zoneadm -z zona1 ready
zoneadm list -cv
zoneadm -z zona1 boot
zoneadm list -cv
telnet 10.71.100.99
ssh -l root 10.71.100.99
zlogin -C zona1

Borrar / Agregar IP en zonas

2010-07-14T14:36:00.000-03:00

# zonecfg -z zona1
zonecfg:zona1> info
zonepath: /export/zona1
autoboot: true
net:
address: 10.27.33.43
physical: ce2
zonecfg:zona1> remove net address=10.27.33.43
zonecfg:zona1> info
zonepath: /export/zona1
zonecfg:zona1> add net
zonecfg:zona1:net> set address=10.27.33.49
zonecfg:zona1:net> set physical=ce2
zonecfg:zona1:net> end

Paso a Paso para crear Zonas

2010-07-14T14:32:00.000-03:00

1) formatear los discos todo el slice 0
2) crear los metadb
[ SKOL ] / # metainit d60 3 1 c2t50060E800456EE02d0s0 1 c2t50060E800456EE02d1s0 1 c2t50060E800456EE02d2s0
d60: Concat/Stripe is setup
[ SKOL ] / # metastat d60
d60: Concat/Stripe
Size: 100346880 blocks (47 GB)
Stripe 0:
Device Start Block Dbase Reloc
/dev/dsk/c2t50060E800456EE02d0s0 0 No Yes
Stripe 1:
Device Start Block Dbase Reloc
/dev/dsk/c2t50060E800456EE02d1s0 7680 No Yes
Stripe 2:
Device Start Block Dbase Reloc
/dev/dsk/c2t50060E800456EE02d2s0 7680 No Yes

Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c2t50060E800456EE02d0 Yes id1,ssd@n60060e800456ee00000056ee00000020
/dev/dsk/c2t50060E800456EE02d1 Yes id1,ssd@n60060e800456ee00000056ee00000021
/dev/dsk/c2t50060E800456EE02d2 Yes id1,ssd@n60060e800456ee00000056ee00000022
[ SKOL ] / # metainit d61 -p d60 6g
d61: Soft Partition is setup
[ SKOL ] / # metainit d62 -p d60 10g
d62: Soft Partition is setup
[ SKOL ] / # metainit d63 -p d60 30g
d63: Soft Partition is setup
[ SKOL ] / #

LUEGO creo los FS
[ SKOL ] / # newfs /dev/md/rdsk/d61
newfs: construct a new file system /dev/md/rdsk/d61: (y/n)? y
[ SKOL ] / # newfs /dev/md/rdsk/d62
newfs: construct a new file system /dev/md/rdsk/d62: (y/n)? y
[ SKOL ] / # newfs /dev/md/rdsk/d63
newfs: construct a new file system /dev/md/rdsk/d63: (y/n)? y
[ SKOL ] / #

mkdir -p /export/zona1
cd /export/
chmod 700 zona1
mkdir /u00
mkdir /u01
mount /export/zona1

zonecfg -z zona1 -f /usr/scripts/SOL10/CREAR.ZONAS/crea.zona1.SKOL.ksh
[ SKOL ] / # zoneadm list -cv
ID NAME STATUS PATH
0 global running /
- zona1 configured /export/zona1
[ SKOL ] / #
[ SKOL ] /usr/scripts/SOL10/CREAR.ZONAS # chmod 700 /export/zona1
[ SKOL ] /usr/scripts/SOL10/CREAR.ZONAS # zoneadm list -cv
[ SKOL ] /usr/scripts/SOL10/CREAR.ZONAS # ls -ld /export/zona1
drwx------ 3 root root 512 Apr 10 08:53 /export/zona1
[ SKOL ] /usr/scripts/SOL10/CREAR.ZONAS # zoneadm -z zona1 install
Preparing to install zone .
Checking file system on device to be mounted at
Checking file system on device to be mounted at
Creating list of files to copy from the global zone.
Copying 124550 files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize 1021 packages on the zone.
Initializing package 49 of 1021 : percent complete: 4%
[ SKOL ] /usr/scripts/SOL10/CREAR.ZONAS # zoneadm list -cv
ID NAME STATUS PATH
0 global running /
- zona1 installed /export/zona1
[ SKOL ] /usr/scripts/SOL10/CREAR.ZONAS # zoneadm -z zona1 ready
[ SKOL ] /usr/scripts/SOL10/CREAR.ZONAS # zoneadm list -cv
ID NAME STATUS PATH
0 global running /
1 zona1 ready /export/zona1
[ SKOL ] /usr/scripts/SOL10/CREAR.ZONAS #

[ SKOL ] /usr/scripts/SOL10/CREAR.ZONAS # zoneadm -z zona1 boot

Este es el script que uso para crear la zona
create -b
set zonepath=/export/zona1
set autoboot=true
add fs
set dir=/bea
set special=/dev/md/dsk/d92
set raw=/dev/md/rdsk/d92
set type=ufs
end
add fs
set dir=/u01
set special=/dev/md/dsk/d99
set raw=/dev/md/rdsk/d99
set type=ufs
end
add fs
set dir=/u02
set special=/dev/md/dsk/d100
set raw=/dev/md/rdsk/d100
set type=ufs
end
add net
set address=10.67.133.144
set physical=ce2
end

Usando fsnap para backupear zonas

2010-07-14T14:06:00.000-03:00

Normalmente uso ufsdump ,pero esta es otra opcion valida.
Aca va un ejemplo.

[asun0001] /space # fssnap -F ufs -o bs=/space /
/dev/fssnap/0
[asun0001] /space # ls -lh /space
total 3442
drwxrwxrwx 2 root root 8.0K Jul 3 12:02 lost+found
-rw------- 1 root root 11G Oct 10 11:47 snapshot0
[asun0001] /space #
[asun0001] /space # fssnap -i
0 /
[asun0001] /space # /usr/lib/fs/ufs/fssnap -i /
Snapshot number : 0
Block Device : /dev/fssnap/0
Raw Device : /dev/rfssnap/0
Mount point : /
Device state : idle
Backing store path : /space/snapshot0
Backing store size : 1472 KB
Maximum backing store size : Unlimited
Snapshot create time : Tue Oct 10 11:45:11 2006
Copy-on-write granularity : 32 KB

[asun0001] / # mount -F ufs -o ro /dev/fssnap/0 /space/KKK
[asun0001] / # df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c0t0d0s0 11G 7.3G 3.1G 71% /
/dev/dsk/c0t0d0s5 5.8G 1.2G 4.5G 22% /var
swap 3.3G 40K 3.3G 1% /tmp
swap 3.3G 72K 3.3G 1% /var/run
/dev/dsk/c0t1d0s0 9.8G 4.4G 5.3G 46% /export/big-zone
/dev/dsk/c0t0d0s7 49G 52M 49G 1% /space
/dev/fssnap/0 11G 7.3G 3.1G 71% /space/KKK
[asun0001] / #

[asun0001] / # zonecfg -z small-zone export >/space/small-zone.config
[asun0001] / # zonecfg -z big-zone export >/space/big-zone.config
asun0001] / # zoneadm list -cv
ID NAME STATUS PATH
0 global running /
4 big-zone running /export/big-zone
- small-zone configured /export/small-zone
[asun0001] / #
[asun0001] / # zlogin -S small-zone init 0
[asun0001] / # zoneadm list -cv
ID NAME STATUS PATH
0 global running /
4 big-zone running /export/big-zone
- small-zone installed /export/small-zone
[asun0001] / #
[asun0001] /export # zoneadm -z small-zone uninstall -F
[asun0001] /export # zonecfg -z small-zone delete -F
[asun0001] /export #
[asun0001] / # zoneadm list -cv
ID NAME STATUS PATH
0 global running /
4 big-zone running /export/big-zone
[asun0001] / #
[asun0001] / # zonecfg -z small-zone -f /space/small-zone.config
[asun0001] / # zoneadm list -cv
ID NAME STATUS PATH
0 global running /
4 big-zone running /export/big-zone
- small-zone configured /export/small-zone
[asun0001] / # zoneadm -z small-zone verify
[asun0001] / # zoneadm list -cv
ID NAME STATUS PATH
0 global running /
4 big-zone running /export/big-zone
- small-zone configured /export/small-zone
[asun0001] / #

[asun0001] / # zoneadm -z small-zone install
Preparing to install zone .
Creating list of files to copy from the global zone.
Copying 3186 files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize 1605 packages on the zone.
Initialized 1605 packages on zone.
Zone is initialized.
Installation of 2 packages was skipped.
Installation of these packages generated warnings:
The file contains a log of the zone installation.
[asun0001] / #

Cambio de Storage/Mirror/Unmirror con Veritas

2010-07-14T10:28:00.000-03:00

La finalidad es cambiar el Storage SAN de Ibm Tipo Shark y cambiarlo por Ibm DS8000.
Para realizarlo, voy a agregar al DiskGRoup ya existente, de nombre BGT, 4 discos de igual capacidad.
Primero los voy a labelear con el Format, luego un vxdctl enable para que los vea Veritas.
Luego con el vxdiskadm voy a agregar esos discos al DG existente BGT.
Despues Mirroreo los volumenes con el vxassist, chequeo el status con vxtask list.
Cuando finalize, corto el mirror y saco las referencias a los discos viejos dentro del veritas.
Toda la tarea me Llevo 40 minutos aproximadamente, eltotal ocupado de los vol/fs era de 120 gb.
[SKOL] /usr/scripts # format
Searching for disks...done

c10t6005076306FFC600000000000000F203d0: configured with capacity of 65.98GB
c10t6005076306FFC600000000000000F204d0: configured with capacity of 65.98GB
c10t6005076306FFC600000000000000F205d0: configured with capacity of 65.98GB
c10t6005076306FFC600000000000000F300d0: configured with capacity of 65.98GB

AVAILABLE DISK SELECTIONS:
0. c0t8d0
/pci@7c,700000/pci@1/pci@1/scsi@2/sd@8,0
1. c0t9d0
/pci@7c,700000/pci@1/pci@1/scsi@2/sd@9,0
2. c0t10d0
/pci@7c,700000/pci@1/pci@1/scsi@2/sd@a,0
3. c0t11d0
/pci@7c,700000/pci@1/pci@1/scsi@2/sd@b,0
4. c2t5006048C52A66167d0
/pci@7c,600000/SUNW,qlc@1/fp@0,0/ssd@w5006048c52a66167,0
5. c3t5005076300C9AF0Dd0
/pci@7c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076300c9af0d,0
6. c3t5005076300C9AF0Dd1
/pci@7c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076300c9af0d,1
7. c3t5005076300C9AF0Dd2
/pci@7c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076300c9af0d,2
8. c3t5005076300C9AF0Dd3
/pci@7c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076300c9af0d,3
9. c3t5005076300C9AF0Dd4
/pci@7c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076300c9af0d,4
10. c3t5005076300C9AF0Dd5
/pci@7c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w5005076300c9af0d,5
Specify disk (enter its number): 261
selecting c10t6005076306FFC600000000000000F203d0
Disk not labeled. Label it now? y
Specify disk (enter its number): 262
selecting c10t6005076306FFC600000000000000F204d0
Disk not labeled. Label it now? y
Specify disk (enter its number)[262]: 263
selecting c10t6005076306FFC600000000000000F205d0
Disk not labeled. Label it now? y
Specify disk (enter its number)[263]: 264
selecting c10t6005076306FFC600000000000000F300d0
Disk not labeled. Label it now? y
[SKOL] # vxdctl enable
[SKOL] # vxdiskadm
Volume Manager Support Operations
Menu: VolumeManager/Disk

1 Add or initialize one or more disks
2 Encapsulate one or more disks
3 Remove a disk
4 Remove a disk for replacement
5 Replace a failed or removed disk
6 Mirror volumes on a disk
7 Move volumes from a disk
8 Enable access to (import) a disk group
9 Remove access to (deport) a disk group
10 Enable (online) a disk device
11 Disable (offline) a disk device
12 Mark a disk as a spare for a disk group
13 Turn off the spare flag on a disk
14 Unrelocate subdisks back to a disk
15 Exclude a disk from hot-relocation use
16 Make a disk available for hot-relocation use
17 Prevent multipathing/Suppress devices from VxVM's view
18 Allow multipathing/Unsuppress devices from VxVM's view
19 List currently suppressed/non-multipathed devices
20 Change the disk naming scheme
21 Get the newly connected/zoned disks in VxVM view
22 Change/Display the default disk layouts
23 Mark a disk as allocator-reserved for a disk group
24 Turn off the allocator-reserved flag on a disk
list List disk information

? Display help about menu
?? Display help about the menuing system
q Exit from menus

Select an operation to perform: 1

Add or initialize disks
Menu: VolumeManager/Disk/AddDisks
........
.......
Select disk devices to add: [,all,list,q,?] IBM_DS8x000_3
Here is the disk selected. Output format: [Device_Name]

IBM_DS8x000_3

Continue operation? [y,n,q,?] (default: y) y
Which disk group [,none,list,q,?] (default: none) BGT
Use a default disk name for the disk? [y,n,q,?] (default: y) y
Add disk as a spare disk for BGT? [y,n,q,?] (default: n) n
Exclude disk from hot-relocation use? [y,n,q,?] (default: n) n
Add site tag to disk? [y,n,q,?] (default: n) n
The selected disks will be added to the disk group BGT with
default disk names.
IBM_DS8x000_3
Continue with operation? [y,n,q,?] (default: y) y
IBM_DS8x000_3
Encapsulate this device? [y,n,q,?] (default: y) n
IBM_DS8x000_3
Instead of encapsulating, initialize? [y,n,q,?] (default: n) y
Initializing device IBM_DS8x000_3.
Enter desired private region length
[,q,?] (default: 65536)
Adding disk device IBM_DS8x000_3 to disk group BGT with disk
name BGT05.
Add or initialize other disks? [y,n,q,?] (default: n) y
Select disk devices to add: [,all,list,q,?] IBM_DS8x000_4
Here is the disk selected. Output format: [Device_Name]

IBM_DS8x000_4

Continue operation? [y,n,q,?] (default: y)
Which disk group [,none,list,q,?] (default: none) BGT
Use a default disk name for the disk? [y,n,q,?] (default: y)
Add disk as a spare disk for BGT? [y,n,q,?] (default: n)
Exclude disk from hot-relocation use? [y,n,q,?] (default: n)
Add site tag to disk? [y,n,q,?] (default: n)
IBM_DS8x000_4
Continue with operation? [y,n,q,?] (default: y)
IBM_DS8x000_4
Encapsulate this device? [y,n,q,?] (default: y) n
IBM_DS8x000_4
Instead of encapsulating, initialize? [y,n,q,?] (default: n) y
Initializing device IBM_DS8x000_4.
Enter desired private region length
[,q,?] (default: 65536)
Adding disk device IBM_DS8x000_4 to disk group BGT with disk
name BGT06.
Add or initialize other disks? [y,n,q,?] (default: n) y
Select disk devices to add: [,all,list,q,?] IBM_DS8x000_5
IBM_DS8x000_5
Which disk group [,none,list,q,?] (default: none) BGT
Use a default disk name for the disk? [y,n,q,?] (default: y)
Add disk as a spare disk for BGT? [y,n,q,?] (default: n)
Exclude disk from hot-relocation use? [y,n,q,?] (default: n)
Add site tag to disk? [y,n,q,?] (default: n)
IBM_DS8x000_5
Continue with operation? [y,n,q,?] (default: y)
IBM_DS8x000_5
Encapsulate this device? [y,n,q,?] (default: y) n
IBM_DS8x000_5
Instead of encapsulating, initialize? [y,n,q,?] (default: n) y
Initializing device IBM_DS8x000_5.
Enter desired private region length
[,q,?] (default: 65536)
Adding disk device IBM_DS8x000_5 to disk group BGT with disk
name BGT07.
Add or initialize other disks? [y,n,q,?] (default: n) y
Select disk devices to add: [,all,list,q,?] IBM_DS8x000_6
IBM_DS8x000_6
Continue operation? [y,n,q,?] (default: y)
Which disk group [,none,list,q,?] (default: none) BGT
Use a default disk name for the disk? [y,n,q,?] (default: y)
Add disk as a spare disk for BGT? [y,n,q,?] (default: n)
Exclude disk from hot-relocation use? [y,n,q,?] (default: n)
Add site tag to disk? [y,n,q,?] (default: n)
IBM_DS8x000_6
Continue with operation? [y,n,q,?] (default: y)
IBM_DS8x000_6
Encapsulate this device? [y,n,q,?] (default: y) n
IBM_DS8x000_6
Instead of encapsulating, initialize? [y,n,q,?] (default: n) y
Initializing device IBM_DS8x000_6.
Enter desired private region length
[,q,?] (default: 65536)
Adding disk device IBM_DS8x000_6 to disk group BGT with disk
name BGT08.
Add or initialize other disks? [y,n,q,?] (default: n) n
Select an operation to perform: q
Goodbye.
[SKOL] # AHORA VEO LOS DISCOS NUEVOS AGREGADOS AL DG
[SKOL] # vxprint -ht -g BGT
DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATE

dg BGT default default 49000 1242237191.240.SKOL

dm BGT01 IBM_SHARK0_121 auto 65536 128794368 -
dm BGT02 IBM_SHARK0_122 auto 65536 128794368 -
dm BGT03 IBM_SHARK0_123 auto 65536 128794368 -
dm BGT04 IBM_SHARK0_124 auto 65536 128794368 -
dm BGT05 IBM_DS8x000_3 auto 65536 138313472 -
dm BGT06 IBM_DS8x000_4 auto 65536 138313472 -
dm BGT07 IBM_DS8x000_5 auto 65536 138313472 -
dm BGT08 IBM_DS8x000_6 auto 65536 138313472 -

v vol01 - ENABLED ACTIVE 140392448 SELECT vol01-01 fsgen
pl vol01-01 vol01 ENABLED ACTIVE 140392448 STRIPE 4/128 RW
sd BGT01-01 vol01-01 BGT01 0 35098112 0/0 IBM_SHARK0_121 ENA
sd BGT02-01 vol01-01 BGT02 0 35098112 1/0 IBM_SHARK0_122 ENA
sd BGT03-01 vol01-01 BGT03 0 35098112 2/0 IBM_SHARK0_123 ENA
sd BGT04-01 vol01-01 BGT04 0 35098112 3/0 IBM_SHARK0_124 ENA

v vol02 - ENABLED ACTIVE 374784000 SELECT vol02-01 fsgen
pl vol02-01 vol02 ENABLED ACTIVE 374784000 STRIPE 4/128 RW
sd BGT01-02 vol02-01 BGT01 35098112 93696000 0/0 IBM_SHARK0_121 ENA
sd BGT02-02 vol02-01 BGT02 35098112 93696000 1/0 IBM_SHARK0_122 ENA
sd BGT03-02 vol02-01 BGT03 35098112 93696000 2/0 IBM_SHARK0_123 ENA
sd BGT04-02 vol02-01 BGT04 35098112 93696000 3/0 IBM_SHARK0_124 ENA

[SKOL] /usr/scripts # vxassist -g BGT maxsize BGT05 BGT06 BGT07 BGT08
Maximum volume size: 553252864 (270143Mb)
########## Comienzo el mirror de los volumenes vol01 y vol02
[SKOL] /usr/scripts # vxassist -g BGT mirror vol01 BGT05 BGT06 BGT07 BGT08
[SKOL] /usr/scripts # vxassist -g BGT mirror vol02 BGT05 BGT06 BGT07 BGT08
[SKOL] /usr/scripts # vxprint -ht -g BGT
DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATE

dg BGT default default 49000 1242237191.240.SKOL

dm BGT01 IBM_SHARK0_121 auto 65536 128794368 -
dm BGT02 IBM_SHARK0_122 auto 65536 128794368 -
dm BGT03 IBM_SHARK0_123 auto 65536 128794368 -
dm BGT04 IBM_SHARK0_124 auto 65536 128794368 -
dm BGT05 IBM_DS8x000_3 auto 65536 138313472 -
dm BGT06 IBM_DS8x000_4 auto 65536 138313472 -
dm BGT07 IBM_DS8x000_5 auto 65536 138313472 -
dm BGT08 IBM_DS8x000_6 auto 65536 138313472 -

v vol01 - ENABLED ACTIVE 140392448 SELECT - fsgen
pl vol01-01 vol01 ENABLED ACTIVE 140392448 STRIPE 4/128 RW
sd BGT01-01 vol01-01 BGT01 0 35098112 0/0 IBM_SHARK0_121 ENA
sd BGT02-01 vol01-01 BGT02 0 35098112 1/0 IBM_SHARK0_122 ENA
sd BGT03-01 vol01-01 BGT03 0 35098112 2/0 IBM_SHARK0_123 ENA
sd BGT04-01 vol01-01 BGT04 0 35098112 3/0 IBM_SHARK0_124 ENA
pl vol01-02 vol01 ENABLED ACTIVE 140392448 STRIPE 4/128 RW
sd BGT05-01 vol01-02 BGT05 0 35098112 0/0 IBM_DS8x000_3 ENA
sd BGT06-01 vol01-02 BGT06 0 35098112 1/0 IBM_DS8x000_4 ENA
sd BGT07-01 vol01-02 BGT07 0 35098112 2/0 IBM_DS8x000_5 ENA
sd BGT08-01 vol01-02 BGT08 0 35098112 3/0 IBM_DS8x000_6 ENA

v vol02 - ENABLED ACTIVE 374784000 SELECT - fsgen
pl vol02-01 vol02 ENABLED ACTIVE 374784000 STRIPE 4/128 RW
sd BGT01-02 vol02-01 BGT01 35098112 93696000 0/0 IBM_SHARK0_121 ENA
sd BGT02-02 vol02-01 BGT02 35098112 93696000 1/0 IBM_SHARK0_122 ENA
sd BGT03-02 vol02-01 BGT03 35098112 93696000 2/0 IBM_SHARK0_123 ENA
sd BGT04-02 vol02-01 BGT04 35098112 93696000 3/0 IBM_SHARK0_124 ENA
pl vol02-02 vol02 ENABLED ACTIVE 374784000 STRIPE 4/128 RW
sd BGT05-02 vol02-02 BGT05 35098112 93696000 0/0 IBM_DS8x000_3 ENA
sd BGT06-02 vol02-02 BGT06 35098112 93696000 1/0 IBM_DS8x000_4 ENA
sd BGT07-02 vol02-02 BGT07 35098112 93696000 2/0 IBM_DS8x000_5 ENA
sd BGT08-02 vol02-02 BGT08 35098112 93696000 3/0 IBM_DS8x000_6 ENA
######### Corto el mirror con los discos Viejos
[SKOL] # vxplex -g BGT -o rm dis vol01-01
[SKOL] # vxplex -g BGT -o rm dis vol02-01
[SKOL] # vxprint -ht -g BGT
DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATE

dg BGT default default 49000 1242237191.240.SKOL

dm BGT01 IBM_SHARK0_121 auto 65536 128794368 -
dm BGT02 IBM_SHARK0_122 auto 65536 128794368 -
dm BGT03 IBM_SHARK0_123 auto 65536 128794368 -
dm BGT04 IBM_SHARK0_124 auto 65536 128794368 -
dm BGT05 IBM_DS8x000_3 auto 65536 138313472 -
dm BGT06 IBM_DS8x000_4 auto 65536 138313472 -
dm BGT07 IBM_DS8x000_5 auto 65536 138313472 -
dm BGT08 IBM_DS8x000_6 auto 65536 138313472 -

v vol01 - ENABLED ACTIVE 140392448 SELECT vol01-02 fsgen
pl vol01-02 vol01 ENABLED ACTIVE 140392448 STRIPE 4/128 RW
sd BGT05-01 vol01-02 BGT05 0 35098112 0/0 IBM_DS8x000_3 ENA
sd BGT06-01 vol01-02 BGT06 0 35098112 1/0 IBM_DS8x000_4 ENA
sd BGT07-01 vol01-02 BGT07 0 35098112 2/0 IBM_DS8x000_5 ENA
sd BGT08-01 vol01-02 BGT08 0 35098112 3/0 IBM_DS8x000_6 ENA

v vol02 - ENABLED ACTIVE 374784000 SELECT vol02-02 fsgen
pl vol02-02 vol02 ENABLED ACTIVE 374784000 STRIPE 4/128 RW
sd BGT05-02 vol02-02 BGT05 35098112 93696000 0/0 IBM_DS8x000_3 ENA
sd BGT06-02 vol02-02 BGT06 35098112 93696000 1/0 IBM_DS8x000_4 ENA
sd BGT07-02 vol02-02 BGT07 35098112 93696000 2/0 IBM_DS8x000_5 ENA
sd BGT08-02 vol02-02 BGT08 35098112 93696000 3/0 IBM_DS8x000_6 ENA
##### Saco la referencia de los discos viejos al DG BGT, quedando de esta manera solo los nuevos
[SKOL] # vxdg -g BGT rmdisk BGT01
[SKOL] # vxdg -g BGT rmdisk BGT02
[SKOL] # vxdg -g BGT rmdisk BGT03
[SKOL] # vxdg -g BGT rmdisk BGT04
[SKOL] /usr/scripts # vxprint -ht -g BGT
DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATE

dg BGT default default 49000 1242237191.240.SKOL

dm BGT05 IBM_DS8x000_3 auto 65536 138313472 -
dm BGT06 IBM_DS8x000_4 auto 65536 138313472 -
dm BGT07 IBM_DS8x000_5 auto 65536 138313472 -
dm BGT08 IBM_DS8x000_6 auto 65536 138313472 -

v vol01 - ENABLED ACTIVE 140392448 SELECT vol01-02 fsgen
pl vol01-02 vol01 ENABLED ACTIVE 140392448 STRIPE 4/128 RW
sd BGT05-01 vol01-02 BGT05 0 35098112 0/0 IBM_DS8x000_3 ENA
sd BGT06-01 vol01-02 BGT06 0 35098112 1/0 IBM_DS8x000_4 ENA
sd BGT07-01 vol01-02 BGT07 0 35098112 2/0 IBM_DS8x000_5 ENA
sd BGT08-01 vol01-02 BGT08 0 35098112 3/0 IBM_DS8x000_6 ENA

v vol02 - ENABLED ACTIVE 374784000 SELECT vol02-02 fsgen
pl vol02-02 vol02 ENABLED ACTIVE 374784000 STRIPE 4/128 RW
sd BGT05-02 vol02-02 BGT05 35098112 93696000 0/0 IBM_DS8x000_3 ENA
sd BGT06-02 vol02-02 BGT06 35098112 93696000 1/0 IBM_DS8x000_4 ENA
sd BGT07-02 vol02-02 BGT07 35098112 93696000 2/0 IBM_DS8x000_5 ENA
sd BGT08-02 vol02-02 BGT08 35098112 93696000 3/0 IBM_DS8x000_6 ENA
[SKOL] # df -h|grep BGT
/dev/vx/dsk/BGT/vol01 67G 34G 32G 52% /carga
/dev/vx/dsk/BGT/vol02 179G 96G 82G 54% /interfaz
# exit

Algo de ZFS

2010-07-13T11:50:00.001-03:00

[nuve] / # df -h

Filesystem size used avail capacity Mounted on

rpool/ROOT/s10x_u6wos_07b 67G 3.4G 62G 6% /
rpool/export 67G 19K 62G 1% /export
rpool/export/home 67G 18K 62G 1% /export/home
rpool 67G 35K 62G 1% /rpool
[nuve] / # zfs create rpool/SOFT
[nuve] / # df -h
Filesystem size used avail capacity Mounted on
rpool/ROOT/s10x_u6wos_07b 67G 3.4G 62G 6% /
rpool/export 67G 19K 62G 1% /export
rpool/export/home 67G 18K 62G 1% /export/home
rpool 67G 35K 62G 1% /rpool
rpool/SOFT 67G 18K 62G 1% /rpool/SOFT
[nuve] / # zfs set quota=10G rpool/SOFT
[nuve] / # df -h
Filesystem size used avail capacity Mounted on
rpool/ROOT/s10x_u6wos_07b 67G 3.4G 62G 6% /
rpool/export 67G 19K 62G 1% /export
rpool/export/home 67G 18K 62G 1% /export/home
rpool 67G 36K 62G 1% /rpool
rpool/SOFT 10G 18K 10G 1% /rpool/SOFT
[nuve] / #

[nuve] / # zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 6.56G 60.4G 36.5K /rpool
rpool/ROOT 3.42G 60.4G 18K legacy
rpool/ROOT/s10x_u6wos_07b 3.42G 60.4G 3.42G /
rpool/SOFT 1.13G 8.87G 1.13G /rpool/SOFT
rpool/dump 1.00G 60.4G 1.00G -
rpool/export 37K 60.4G 19K /export
rpool/export/home 18K 60.4G 18K /export/home
rpool/swap 1G 61.4G 16K -
[nuve] / #

Para Cambiar el punto de montaje del Filesystems
[nuve] / # zfs set mountpoint=/SOFT rpool/SOFT
[nuve] / # df -h
Filesystem size used avail capacity Mounted on
rpool/ROOT/s10x_u6wos_07b 67G 3.4G 60G 6% /
rpool/export 67G 19K 60G 1% /export
rpool/export/home 67G 18K 60G 1% /export/home
rpool 67G 36K 60G 1% /rpool
rpool/SOFT 10G 1.9G 8.1G 20% /SOFT
[nuve] / #

Restaurar la base de Servicios SVC ( Repositorio )

2010-07-13T11:47:00.000-03:00

Para cuando muere la base del SVC en solaris 10 ejecutar:
/lib/svc/bin/restore_repository
La opción que hay que elegir es la del booteo que aparece.

Mensaje de error con el problema:
svc.configd: Fatal error: /etc/svc/volatile/svc_nonpersist.db: integrity check failed. Details in /etc/svc/volatile/db_errors

Cambio IP Solaris 10

2010-07-13T11:34:00.000-03:00

PARA CAMBIAR LA IP , tener en cuenta ( en los primeros releases de solaris 10 no estaba linkeado el ipnodes al hosts ) :
que no solo se debe cambiar el /etc/inet/hosts, sino tambien el archivo /etc/inet/ipnodes
ejemplo :
skol] / # more /etc/inet/ipnodes
#
# Internet host table
#
::1 localhost
127.0.0.1 localhost
10.67.33.115 skol loghost
[skol ] / # more /etc/inet/hosts
#
# Internet host table
#
127.0.0.1 localhost
10.67.33.115 skol skol. loghost
10.67.33.55 mail mail. mailhost mailhost.

Procesos que consumen mas Memoria

2010-07-13T11:29:00.000-03:00

ps -efo vsz,pid,comm | sort -rn
Para pasarlo a MB la primer columna se divide por 1024

Configurar Syslog remoto

2010-07-13T10:48:00.000-03:00

En el /etc/syslog.conf , hay que agregar al final
*.info;mail.none;kern.none;daemon.none @10.67.33.115
auth.notice @10.67.33.115
daemon.info @10.67.33.115

Tambien es conveniente agregar la direccion ip del host que va a recibir los logs en el /etc/host local,
10.67.33.115 loghost

y reiniciar /etc/init.d/syslog stop/start

Habilitar X en Suse

2010-07-13T10:45:00.001-03:00

vi /etc/sysconfig/displaymanager
habilitarle el port 6000
# TCP port 6000 of Xserver. When set to "no" (default) Xserver is
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN="yes"
/sbin/SuSEconfig
/usr/sbin/rcxdm restart
reboot

Agrandar un fs con SVM que esta dentro de un Disk Set

2010-07-12T16:25:00.000-03:00

Para Agrandar un fs con SVM que esta dentro de un Disk Set, se debe por ejemplo en este caso queremos
agrandar el fs /u/app/oracle/admin/SKOL/arch perteneciente al d74
# df -h
Filesystem size used avail capacity Mounted on
/dev/md/SKOL/dsk/d74 10.0G 90M 9.8G 1% /u/app/oracle/admin/SKOL/arch
# metastat -s SKOL
SKOL/d74: Soft Partition
Device: SKOL/d70
State: Okay
Size: 20971520 blocks (10 GB)
Extent Start Block Block count
0 482345472 20971520

SKOL/d70: Concat/Stripe
Size: 628838400 blocks (299 GB)
Stripe 0: (interlace: 128 blocks)
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c6t60060E800456EE00000056EE000000F4d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000F5d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000F6d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000F7d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000F8d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000F9d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000FAd0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000FBd0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000FCd0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000FDd0s0 0 No Okay Yes

SKOL/d73: Soft Partition
Device: SKOL/d70
State: Okay
Size: 157286400 blocks (75 GB)
Extent Start Block Block count
0 325058944 157286400

SKOL/d72: Soft Partition
Device: SKOL/d70
State: Okay
Size: 157286400 blocks (75 GB)
Extent Start Block Block count
0 167772416 157286400

SKOL/d71: Soft Partition
Device: SKOL/d70
State: Okay
Size: 167772160 blocks (80 GB)
Extent Start Block Block count
0 128 167772160

Con este comando Agrego 15 gb al filesystem que ya tenia 10gb, es decir lo llevare a 25 gb totales.
# metattach -s SKOL d74 15g
SKOL/d74: Soft Partition has been grown

# metastat -s SKOL d74
SKOL/d74: Soft Partition
Device: SKOL/d70
State: Okay
Size: 52428800 blocks (25 GB)
Extent Start Block Block count
0 482345472 52428800

SKOL/d70: Concat/Stripe
Size: 628838400 blocks (299 GB)
Stripe 0: (interlace: 128 blocks)
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c6t60060E800456EE00000056EE000000F4d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000F5d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000F6d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000F7d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000F8d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000F9d0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000FAd0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000FBd0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000FCd0s0 0 No Okay Yes
/dev/dsk/c6t60060E800456EE00000056EE000000FDd0s0 0 No Okay Yes

Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c6t60060E800456EE00000056EE000000F4d0 Yes id1,ssd@n60060e800456ee00000056ee000000f4
/dev/dsk/c6t60060E800456EE00000056EE000000F5d0 Yes id1,ssd@n60060e800456ee00000056ee000000f5
/dev/dsk/c6t60060E800456EE00000056EE000000F6d0 Yes id1,ssd@n60060e800456ee00000056ee000000f6
/dev/dsk/c6t60060E800456EE00000056EE000000F7d0 Yes id1,ssd@n60060e800456ee00000056ee000000f7
/dev/dsk/c6t60060E800456EE00000056EE000000F8d0 Yes id1,ssd@n60060e800456ee00000056ee000000f8
/dev/dsk/c6t60060E800456EE00000056EE000000F9d0 Yes id1,ssd@n60060e800456ee00000056ee000000f9
/dev/dsk/c6t60060E800456EE00000056EE000000FAd0 Yes id1,ssd@n60060e800456ee00000056ee000000fa
/dev/dsk/c6t60060E800456EE00000056EE000000FBd0 Yes id1,ssd@n60060e800456ee00000056ee000000fb
/dev/dsk/c6t60060E800456EE00000056EE000000FCd0 Yes id1,ssd@n60060e800456ee00000056ee000000fc
/dev/dsk/c6t60060E800456EE00000056EE000000FDd0 Yes id1,ssd@n60060e800456ee00000056ee000000fd

# df -h |grep d74
/dev/md/SKOL/dsk/d74 10.0G 90M 9.8G 1% /u/app/oracle/admin/SKOL/arch

# growfs -M /u/app/oracle/admin/SKOL/arch /dev/md/SKOL/rdsk/d74
Warning: 4096 sector(s) in last cylinder unallocated
/dev/md/SKOL/rdsk/d74: 52428800 sectors in 8534 cylinders of 48 tracks, 128 sectors
25600.0MB in 534 cyl groups (16 c/g, 48.00MB/g, 128 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
..........
super-block backups for last 10 cylinder groups at:
51512864, 51611296, 51709728, 51808160, 51906592, 52005024, 52103456,
52201888, 52300320, 52398752
# df -h |grep d74
/dev/md/SKOL/dsk/d74 25G 105M 25G 1% /u/app/oracle/admin/SKOL/arch
#

Sacar estado STOP_FAILED ( sun cluster 3.0 )

2010-07-12T16:21:00.000-03:00

Para Limpiar el estado STOP FAILED un resource group de un Sun Cluster 3.0 se debe realizar lo descripto en este ejemplo.

Con el comando scstat -g identifico los resource group que debo limpiar
scstat -g |more
-- Resource Groups and Resources -
Group Name Resources
---------- ---------
Resources: oracle-rg cluster1 oracle-server-rs oracle-hastorage-rs servicios-hastorage-rs servicios-rs oracle-LSN_
PR01-rs oracle-LSN_PR02-rs oracle-LSN_PR03-rs oracle-LSN_PR04-rs oracle-LSN_PR05-rs

-- Resource Groups --

Group Name Node Name State
---------- --------- -----

Group: oracle-rg server1 Error--stop failed
Group: oracle-rg server2 Offline

# scswitch -c -h server1 -j oracle-server-rs -f STOP_FAILED
scswitch: NOTICE: Operation succeeded, but resource group oracle-rg remains in ERROR_STOP_FAILED state on node server1 because some resources in the group remain
online while others are offline. To clear this condition, switch the resource group offline.

# scswitch -F -g oracle-rg
# scstat -g |more

-- Resource Groups and Resources --

Group Name Resources
---------- ---------
Resources: oracle-rg cluster1 oracle-server-rs oracle-hastorage-rs servicios-hastorage-rs servicios-rs oracle-LSN_
PR01-rs oracle-LSN_PR02-rs oracle-LSN_PR03-rs oracle-LSN_PR04-rs oracle-LSN_PR05-rs

-- Resource Groups --

Group Name Node Name State
---------- --------- -----
Group: oracle-rg server1 Online
Group: oracle-rg server2 Offline

Ahora debo realizar un scswitch con cada uno de los recursos asociados al resource group oracle-rg

# scswitch -n -j oracle-hastorage-rs
# scswitch -e -j oracle-hastorage-rs
# scswitch -F -g oracle-rg
# scswitch -n -j oracle-LSN_PR05-rs
# scswitch -n -j oracle-LSN_PR04-rs
# scswitch -n -j oracle-LSN_PR03-rs
# scswitch -n -j oracle-LSN_PR02-rs
# scswitch -n -j oracle-LSN_PR01-rs
# scswitch -n -j oracle-server-rs
# scswitch -n -j oracle-hastorage-rs

Solaris Volume Manager

2010-07-12T16:07:00.000-03:00

Crear un Filesystem CONCATENADO

Creo el d50 compuesto por 2 hd y 1 stripe, especificando los discos a usar
# metainit d50 2 1 c2t50060E800456EE10d0s0 1 c2t50060E800456EE10d1s0
d50: Concat/Stripe is setup
#
Ahora creo La soft Partition d51 sobre el d50 que cree recien, con un tamanio de 10gb
# metainit d51 -p d50 10g
d51: Soft Partition is setup
#
Por Ultimo creo el filesystem
# newfs /dev/md/rdsk/d51
newfs: construct a new file system /dev/md/rdsk/d51: (y/n)? y
Warning: 4096 sector(s) in last cylinder unallocated
/dev/md/rdsk/d51: 20971520 sectors in 3414 cylinders of 48 tracks, 128 sectors
10240.0MB in 214 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
20055584, 20154016, 20252448, 20350880, 20449312, 20547744, 20646176,
20744608, 20843040, 20941472
#
######################################################
Para crear un fs STRIPEADO de 7 discos realizar los sig pasos :

Creo el d60 y le indico que sera 1 stripe de 7 discos con un interleace de 48k

metainit d60 1 7 c2t50060E800456EE10d2s0 c2t50060E800456EE10d3s0 c2t50060E800456EE10d4s0 c2t5060E80456EE10d5s0 c2t5060E80456EE10d6s0 c2t5060E80456EE10d7s0 c2t5060E80456EE10d8s0 -i 48kb
d60: Concat/Stripe is setup
#
# newfs /dev/md/rdsk/d60
newfs: construct a new file system /dev/md/rdsk/d60: (y/n)? y
Warning: 1536 sector(s) in last cylinder unallocated
/dev/md/rdsk/d60: 123271680 sectors in 20064 cylinders of 48 tracks, 128 sectors
60191.2MB in 1254 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
........................
super-block backups for last 10 cylinder groups at:
122293792, 122392224, 122490656, 122589088, 122687520, 122785952, 122884384,
122982816, 123081248, 123179680
#

##################################################
Crear un fs CONCATENADO y Agregarle luego un disco y agrandarle el fs ONLINE

# metainit d70 2 1 c2t50060E800456EE10d9s0 1 c2t50060E800456EE10d10s0
d70: Concat/Stripe is setup
#

# metattach d70 /dev/dsk/c2t50060E800456EE10d11s0
d70: component is attached
#
# metastat d70
d70: Concat/Stripe
Size: 52838400 blocks (25 GB)
Stripe 0:
Device Start Block Dbase Reloc
/dev/dsk/c2t50060E800456EE10d9s0 0 No Yes
Stripe 1:
Device Start Block Dbase Reloc
/dev/dsk/c2t50060E800456EE10d10s0 7680 No Yes
Stripe 2:
Device Start Block Dbase Reloc
/dev/dsk/c2t50060E800456EE10d11s0 7680 No Yes

Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c2t50060E800456EE10d9 Yes id1,ssd@n60060e800456ee00000056ee000000eb
/dev/dsk/c2t50060E800456EE10d10 Yes id1,ssd@n60060e800456ee00000056ee000000ec
/dev/dsk/c2t50060E800456EE10d11 Yes id1,ssd@n60060e800456ee00000056ee000000ed

# growfs -M /interfaz /dev/md/rdsk/d70
/dev/md/rdsk/d70: 52838400 sectors in 8600 cylinders of 48 tracks, 128 sectors
25800.0MB in 538 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
..........
super-block backups for last 10 cylinder groups at:
51906592, 52005024, 52103456, 52201888, 52300320, 52398752, 52497184,
52595616, 52694048, 52792480
# df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d70 25G 25M 25G 1% /interfaz

Mirror boot con Solaris Volume Manager

2010-07-12T16:01:00.000-03:00

El equipo tiene 2 discos internos de 72 gb.
Vamos a usar el disco c1t0d0 como disco primario y el c1t1d0 como disco de mirror
[SKOL] /etc/init.d # format
AVAILABLE DISK SELECTIONS:
0. c1t0d0
/pci@1c,600000/scsi@2/sd@0,0
1. c1t1d0
/pci@1c,600000/scsi@2/sd@1,0
Specify disk (enter its number): ^D

El disco c1t0d0, tiene 3 particiones usadas, el slice 0 para el fs /, el slice 1 para el swap y el slice 3 para el fs /u00.
Se necesita como minimo 2 State Database REplicas por disco. que es donde DiskSuite va a almacenar los datos de
configuracion e informacion de Disksuite.
Por eso voy a usar el slice 4 y 5 del disco, con 15 mb para cada slice. Para esta tarea uso el comando format.

Posteriormente, voy a copiar toda la informacion contenida en el disco c1t0d0 (slices,tamanio,etc) en el disco que se
usara como mirror, en este caso el c1t1d0
prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2
Chequeo que lo haya hecho con el comando format.

Luego de eso, creo los state databse replicas, de la siguiente manera

[SKOL] / # metadb -a -f -c 2 /dev/dsk/c1t0d0s4 /dev/dsk/c1t1d0s4
[SKOL] / # metadb -a -f -c 2 /dev/dsk/c1t0d0s5 /dev/dsk/c1t1d0s5

donde -a significa adding
-f significa force, porque es la primera vez que se esta creando las bases.
-c 2 ( con espacio entre la c y el 2), significa que crea 2 databases en cada slices.

[SKOL] / # metainit -f d10 1 1 c1t0d0s0
d10: Concat/Stripe is setup
[SKOL] / # metainit -f d20 1 1 c1t1d0s0
d20: Concat/Stripe is setup
[SKOL] / # metainit d30 -m d10
d30: Mirror is setup
[SKOL] / # cd /etc
[SKOL] /etc # cp vfstab vfstab.antesdeponer.DiskSuite
[SKOL] /etc # more vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c1t0d0s1 - - swap - no -
/dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no -
swap - /tmp tmpfs - yes -
[SKOL] /etc # metaroot d30
[SKOL] /etc # cat /etc/vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c1t0d0s1 - - swap - no -
/dev/md/dsk/d30 /dev/md/rdsk/d30 / ufs 1 no -
swap - /tmp tmpfs - yes -
[SKOL] /etc # metainit -f d11 1 1 c1t0d0s1
d11: Concat/Stripe is setup
[SKOL] /etc # metainit -f d21 1 1 c1t1d0s1
d21: Concat/Stripe is setup
[SKOL] /etc # metainit d31 -m d11
d31: Mirror is setup
[SKOL] /etc # metainit -f d12 1 1 c1t0d0s3
d12: Concat/Stripe is setup
[SKOL] /etc # metainit -f d22 1 1 c1t1d0s3
d22: Concat/Stripe is setup
[SKOL] /etc # metainit d32 -m d12
d32: Mirror is setup
[SKOL] /etc # metainit hsp001
hsp001: Hotspare pool is setup
[SKOL] /etc #
Agrego en el vfstab todos los fs que quedaron con disk suite como por ejemplo el slice 3 q2ue es el u00
/dev/md/dsk/d32 5271150 9 5218430 1% /u00

[SKOL] / # lockfs -fa
[SKOL] / # init 6

[SKOL] / # metattach d30 d20
d30: submirror d20 is attached
[SKOL] / # metattach d31 d21
d31: submirror d21 is attached
[SKOL] / # metattach d32 d22
d32: submirror d22 is attached
[SKOL] / #
[SKOL] / # metastat
d30: Mirror
Submirror 0: d10
State: Okay
Submirror 1: d20
State: Resyncing
Resync in progress: 0 % done
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 18876480 blocks

d10: Submirror of d30
State: Okay
Size: 18876480 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Okay

d20: Submirror of d30
State: Resyncing
Size: 18876480 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Okay

d31: Mirror
Submirror 0: d11
State: Okay
Submirror 1: d21
State: Resyncing
Resync in progress: 0 % done
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 25175424 blocks

d11: Submirror of d31
State: Okay
Size: 25175424 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s1 0 No Okay

d21: Submirror of d31
State: Resyncing
Size: 25175424 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s1 0 No Okay

d32: Mirror
Submirror 0: d12
State: Okay
Submirror 1: d22
State: Resyncing
Resync in progress: 0 % done
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 10705152 blocks

d12: Submirror of d32
State: Okay
Size: 10705152 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s3 0 No Okay

d22: Submirror of d32
State: Resyncing
Size: 10705152 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s3 0 No Okay

hsp001: is empty

[SKOL] / #
[SKOL] / # installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t1d0s0
[SKOL] / #
[SKOL] / # eeprom "boot-device=disk0 disk1"
[SKOL] / # eeprom use-nvramrc?=false

IPC en Solaris 10

2010-07-12T15:58:00.000-03:00

id -p ( para saber el id del project )

# prctl -n project.max-shm-memory -i project 3
project: 3: default
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-memory
privileged 248MB - deny -
system 16.0EB max deny -
#

LUEGO LO SETEO en por ejemplo 4.0 gb
prctl -n project.max-shm-memory -r -v 4096mb -i project 3

# prctl -n project.max-shm-memory -i project 3
project: 3: default
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-memory
privileged 4.00GB - deny -
system 16.0EB max deny -
#

prctl $$ > archivo , me muestra los valores seteados

Agregar Raw Devices al Sun Cluster 3.2 con Oracle Rac

2010-07-12T15:50:00.000-03:00

La finalidad es agregarle 5 raw devices al Disk Group DatosDG del Oracle RAC.
Estos son los paso a paso que realize
devfsadm -C ( -C significa modo Clean Up )
devfsadm ( crea special files en el /devices y logical links en /dev )
scdidadm -C ( remueve todas las referencias DID de todos los dispositivos Detachados )
scdidadm -r ( reconfiguro los DID )
scgdevs ( updatea el /globaldevices )
scdpm -p all:all ( chequea que este bien el did en ambos nodos del cluster )

vxdctl enable
agrego los discos en el Veritas ( uso por ejemplo el vxdiskadm menu opcion 1 )

EMC0_18 auto - - online c2t60060480000290101637533031364230d0s2
EMC0_19 auto - - online c2t60060480000290101637533031364138d0s2
EMC0_20 auto - - online c2t60060480000290101637533031364330d0s2
EMC0_21 auto - - online c2t60060480000290101637533031364130d0s2
EMC0_22 auto - - online c2t60060480000290101637533031364238d0s2

# vxassist -g Datosdg -U gen make datos7 133g Datosdg01
# vxassist -g Datosdg -U gen make datos8 133g Datosdg02
# vxassist -g Datosdg -U gen make datos9 133g Datosdg03
# vxassist -g Datosdg -U gen make datos10 133g Datosdg04
# vxassist -g Datosdg -U gen make datos11 133g Datosdg05
#
# vxedit -g Datosdg set group=dba user=oracle mode=660 datos7
# vxedit -g Datosdg set group=dba user=oracle mode=660 datos8
# vxedit -g Datosdg set group=dba user=oracle mode=660 datos9
# vxedit -g Datosdg set group=dba user=oracle mode=660 datos10
# vxedit -g Datosdg set group=dba user=oracle mode=660 datos11

OJO: Todos estos comandos Deben ser ejecutados en el nodo que tiene el control del cluster, esto lo chequeo con vxdctl -c mode

Estado placas de red

2010-07-12T15:43:00.000-03:00

Si tiene link:

# kstat -p ce:::link_up

ce:0:ce0:link_up 1
ce:1:ce1:link_up 0
ce:2:ce2:link_up 1
ce:3:ce3:link_up 1
ce:4:ce4:link_up 1
ce:5:ce5:link_up 1

A cuanto negocia:

# kstat -p ce:::link_speed

ce:0:ce0:link_speed 100
ce:1:ce1:link_speed 0
ce:2:ce2:link_speed 1000
ce:3:ce3:link_speed 1000
ce:4:ce4:link_speed 100
ce:5:ce5:link_speed 1000

Detalle por nro de placa :

# kstat -m ce -i 3 -s link_speed
module: ce instance: 3
name: ce3 class: net
link_speed 1000

Montar Cdrom sin el vold

2010-07-12T15:42:00.000-03:00

este es el comando para montar un cd en solaris cuando no nos da bola el vold.
mount -F hsfs -o ro /dev/dsk/c2t6d0s2 /mnt

pkgadd en otro directorio distinto al default

2010-07-12T15:40:00.000-03:00

Para Instalar packages en otro directorio que no sea el default, se debe realizar los siguientes pasos :
1) copiar el /var/sadm/install/admin/default como /var/sadm/install/admin/TITO
2) editar el archivo /var/sadm/install/admin/TITO
( hay 11 opciones que se pueden modificar, en este caso la opcion que vamos a cambiar es la ultima, la opcion basedir )
Cambiar la opcion basedir por el parametro ask
el archivo TITO quedaria asi :
#ident "@(#)default 1.4 92/12/23 SMI" /* SVr4.0 1.5.2.1 */
mail=
instance=unique
partial=ask
runlevel=ask
idepend=ask
rdepend=ask
space=ask
setuid=ask
conflict=ask
action=ask
basedir=ask

3) ejecutar el pkgadd , asi :
pkgadd -a /var/sadm/install/admin/TITO -d

Buscar un string dentro de archivos

2010-07-12T15:37:00.000-03:00

FIND + GREP
find . -type f -print | xargs grep -i "nombre"

Para cuando NO tengo el lsof instalado

2010-07-12T15:36:00.000-03:00

cd /proc;pfiles * | egrep "^[0-9]|sockname" | more

Comandos para Importar y Deportar un Disk Group ( en Veritas )

2010-07-12T15:09:00.000-03:00

vxdg deport dg01 ( Previamente desmontar los fs correspondientes a este dg )
vxdg import dg01 ( start volume luego montar los fs )
vxvol -g dg01 startall
montar los fs

Generar Clave de ssh a un usuario

2010-07-12T15:06:00.000-03:00

Equipo A
logueado como el usuario x....
ssh-keygen -T dsa
Esto me crea un id_dsa.pub en el home directory del usuario, en un directorio .ssh

Equipo A
ssh-keygen -t dsa
cd .ssh
scp id_dsa.pub equipoB:/home/usuario/.ssh

Equipo B
cd /home/usuario
mkdir .ssh
mv id_dsa.pub authorized_keys

Ufsdump remoto

2010-07-12T15:05:00.000-03:00

ufsdump 0f - /opt/Tivoli |ssh 10.xx.xx.xx "(cd /prueba; ufsrestore -xf -)"

2010-07-12T14:43:00.000-03:00

Primero agrego el disco con vxdiskadm con las siguientes opciones:
-------------------------------------------------------------------

Here are the disks selected. Output format: [Device_Name]

c3t0d0 c3t0d1 c3t0d2 c3t0d3

Continue operation? [y,n,q,?] (default: y) y

Which disk group [,none,list,q,?] (default: rootdg) z_shark
Use default disk names for these disks? [y,n,q,?] (default: y) y
Add disks as spare disks for z_shark? [y,n,q,?] (default: n) n
The selected disks will be added to the disk group z_shark with
default disk names.

c3t0d0 c3t0d1 c3t0d2 c3t0d3

Continue with operation? [y,n,q,?] (default: y) y

The following disk devices have a valid VTOC, but do not appear to have
been initialized for the Volume Manager. If there is data on the disks
that should NOT be destroyed you should encapsulate the existing disk
partitions as volumes instead of adding the disks as new disks.
Output format: [Device_Name]

c3t0d0 c3t0d1 c3t0d2 c3t0d3

Encapsulate these devices? [Y,N,S(elect),q,?] (default: Y)N

c3t0d0 c3t0d1 c3t0d2 c3t0d3

Instead of encapsulating, initialize?
[Y,N,S(elect),q,?] (default: N) Y
Initializing device c3t0d0.
Initializing device c3t0d1.
Initializing device c3t0d2.
Initializing device c3t0d3.

Adding disk device c3t0d0 to disk group z_shark with disk
name z_shark50.
Adding disk device c3t0d1 to disk group z_shark with disk
name z_shark51.
Adding disk device c3t0d2 to disk group z_shark with disk
name z_shark52.
Adding disk device c3t0d3 to disk group z_shark with disk
name z_shark53.

Luego crear el VOLUMEN con los discos que asigne.
Por ejemplo voy a crear un volumen vol06 de 55 gb con 4 discos stripeados :
NOTA: PUEDO STRIPEAR UN VOLUMEN CON UN MAXIMO DE HASTA 7 DISCOS.

vxassist -g z_shark make vol06 55g layout=stripe z_shark50 z_shark51 z_shark52 z_shark53

CREO FS VXFS CON MKFS

mkfs -F vxfs -o bsize=8192,largefiles /dev/vx/rdsk/z_shark/vol08
version 4 layout
115343360 sectors, 7208960 blocks of size 8192, log size 128 blocks
unlimited inodes, largefiles supported
7208960 data blocks, 7208528 free data blocks
220 allocation units of 32768 blocks, 32768 data blocks

SI QUIERO CREAR UN FS CON UN MAXIMO DE 30000 INODES HACER :

mkfs -F vxfs -o ninode=30000 -o bsize=8192,largefiles /dev/vx/rdsk/z_shark/vol43
version 4 layout
106954752 sectors, 6684672 blocks of size 8192, log size 128 blocks
30000 inodes, largefiles supported
6684672 data blocks, 6684264 free data blocks
204 allocation units of 32768 blocks, 32768 data blocks

SI QUIERO CREAR UN FS UFS CON VERITAS :

# vxassist -g cone maxsize cone08 cone09 cone10
Maximum volume size: 44619776 (21787Mb)
# vxassist -g cone make vol08 21785m cone08 cone09 cone10
# newfs /dev/vx/rdsk/cone/vol08
newfs: construct a new file system /dev/vx/rdsk/cone/vol08: (y/n)? y

AGRANDO EL FS

/etc/vx/bin/vxresize -b -F vxfs -g z_shark volumen disco1 disco2 disco3

/etc/vx/bin/vxresize -b -F ufs -g cone vol06 +4100m cone08

PARA AGREGAR UN DISCO ( z_shark36 ) AL VOLUMEN vol08 ( OJO SOLO PUEDO AGREGAR UN DISCO SI EL VOLUMEN NO ESTA STRIPEADO )
vxassist -g z_shark maxgrow vol08 z_shark36
/etc/vx/bin/vxresize -b -F vxfs -g z_shark vol08 +8000m z_shark54 z_shark55 z_shark56 z_shark57 z_shark59 z_shark60 z_shark61 z_shark36

PARA BORRAR un VOLUMEN
vxassist -g z_shark remove volume vol04