L'Imp'Rock Scénette (by @_daffyduke_)

Lire la température d'un serveur

Olivier Duquesne aka DaffyDuke — 2006-01-20T01:13:54Z

Sur une Netra X1 / SunFire V100 ....

– Installer la LOM (Lights Out Management), ce sont les trois packages SUNWlomm , SUNWlomr & SUNWlomu disponibles sur le cd additionnel de Sun Solaris .
– Rebooter pour créer le device /dev/lom (reboot -- -r)
– Puis lire la LOM :

lom -t System Temperature Sensors: 1 Enclosure 27 degC : warning 67 degC : shutdown 72 degC System Over-temperature Sensors: 1 CPU status=ok

D'autres options sont disponibles pour voir l'état des CPUs, des ventilateurs et de l'eventlog

[daffy@admin ~/etc]$ ./read_lom hostname 11/20/2005 08:11:58 host reset 11/15/2005 12:06:36 host reset 04/24/2005 12:38:09 host reset 12/29/2004 20:11:50 host power off 12/29/2004 20:11:40 host power on 09/21/2004 11:32:36 host power off 09/21/2004 11:28:34 host power on 1/18/2006 18:15:11 GMT LOM time reference 01/19/2006 00:40:43 host reset 1/19/2006 8:56:26 GMT LOM time reference ======================================== LOMlite alarm states: Alarm1=off Alarm2=off Alarm3=on Fault LED=off ======================================== Fans: 1 OK speed 72% ======================================== Supply voltages: 1 5V status=ok 2 3V3 status=ok 3 +12V status=ok 4 VDD core status=ok System status flags (circuit breakers): 1 USB0 status=ok 2 USB1 status=ok 3 SCC status=ok ======================================== System Temperature Sensors: 1 Enclosure 27 degC : warning 67 degC : shutdown 72 degC System Over-temperature Sensors: 1 CPU status=ok ========================================

read_lom est un petit shell à moi qui permet d'afficher la date du jour de l'évènement au lieu de +643j21h etc ...

Sur une Netra T1 105 / AC 200

Dommage, la sonde de température n'est pas fournie. Néanmoins, la commande LOM détaillée ci-dessus donne tout de même quelques informations non négligeables :

lwinf1101:root} lom -a PSUs: 1 OK Fans: 1 OK speed 95% 2 OK speed 92% 3 OK speed 94% LOMlite configuration settings: serial escape character=# serial event reporting=off alarm3 mode=user controlled firmware version=2.1 firmware checksum=7ca3 product revision=0.0 product ID=Netra t1 105 LOMlite Event Log: Fault LED OFF wdog trig Fault LED ON power off power on power off power on power off power on Fault LED OFF first fatal error Fan 1 failed LOMlite alarm states: Alarm1=off Alarm2=off Alarm3=on Fault LED=off LOMlite watchdog (ASR) settings: Watchdog=on Hardware reset=off Timeout=40 s

C'est clairement dit, pas de degré à lire ici :

lwinf1101:root} lom -t Temperature monitoring not supported by this device

Et pourtant, l'info est renseignée dans l'eeprom , zarbi non ?

lwinf1101:root} eeprom [...] shutdown-temperature=74 warning-temperature=69 [...]

Sur un DL-380 G4 et autres serveurs HP/Compaq

– Installer hpasm (rpm disponible depuis le site hp.com) :
Description : The hp System Health Application and Insight Management Agents package provides extended capabilities to ProLiant Servers. These capabilities include monitoring of temperature thresholds, fan, processor and memory failures. Should a parameter be out of normal operating conditions, the Linux operating system will be automatically shutdown. The hp Advanced Server Management Application(hpasmd) is the interface to the Advanced Server Management (ASM) ASIC. This application will work with both the ProLiant ASM (0x0E11A0F1) and the ProLiant iLO Advance Server Management (0x0E11B203) ASICs. The hpasmd also provides an interface so other software can log events to the hp ProLiant Integrated Management Log (IML).
hp Server, Storage and Foundation Agents for Linux provide a full spectrum of management data. This package includes the Server Standard Equipment and Health Agent for hp Servers. It also contains the hp Web Agent. This information is available using the hp Insight Manager Console, any Internet browser, or other management applications using SNMP.
– Il n'est pas nécessaire de rebooter mais il faut démarrer le démon hpasm :

[root@mwinf1801 ~]# /etc/init.d/hpasm start Starting Proliant System Health Monitor (hpasmd): Starting Foundation Agents (cmafdtn): cmathreshd cmahostd cmapeerd Starting Threshold agent (cmathreshd): Starting Host agent (cmahostd): Starting SNMP Peer (cmapeerd): Starting Server Agents (cmasvr): cmastdeqd cmahealthd Starting Standard Equipment agent (cmastdeqd): Starting Health agent (cmahealthd): Starting Storage Agents (cmastor): cmaeventd cmaidad cmafcad cmaided cmascsid Starting Storage Event Logger (cmaeventd): Starting IDA agent (cmaidad): Starting FCA agent (cmafcad): Starting IDE agent (cmaided): Starting SCSI agent (cmascsid): hpasm: Server Management is enabled

La définition des modules se trouve dans le fichier /opt/compaq/cma.conf .
– Pour lire l'information, il faut utiliser le client HP :

[root@mwinf1801 ~]# hpasmcli -s "show temp" Sensor Location Temp Threshold ------ -------- ---- --------- #0 SYSTEM_BD - - #1 PROCESSOR_ZONE 34C/93F 62C/143F #2 CPU#1 37C/98F 80C/176F #3 I/O_ZONE 37C/98F 60C/140F #4 CPU#2 40C/104F 80C/176F #5 POWER_SUPPLY_BAY 28C/82F 53C/127F

On peut lire l'Eventlog avec la commande

[root@mwinf1801 ~]#hpasmcli -s "show iml" Event: 0 Added: 08/26/2004 00:03 CAUTION: POST Messages - POST Error: 1785-Drive Array not Configured. Event: 1 Added: 05/18/2005 15:45 CAUTION: POST Messages - POST Error: 1726-Drive Array - Array Accelerator Memory Size Change Detected. Event: 2 Added: 05/18/2005 15:45 CAUTION: POST Messages - POST Error: 1794-Drive Array - Array Accelerator Battery Charge Low. Event: 3 Added: 05/20/2005 06:20 CRITICAL: ASR - ASR Detected by System ROM.

Sur une machine quelconque sous Linux

– La solution, c'est l'ACPI (Advanced Configuration and Power Interface), sous Debian : apt-get install acpi acpid
– Il faut ensuite charger les modules kernels pour gérer la thempérature (modprobe thermal). On peut en charger d'autres , en démarrant le démon acpid :

daffy@colerpia:~$ sudo /etc/init.d/acpid start Loading ACPI modules: battery ac processor button fan thermal Starting Advanced Configuration and Power Interface daemon:

– Pour lire ensuite les information :

daffy@colerpia:~$ acpi -t Thermal 1: ok, 51.0 degrees C

D'autres informations sont disponibles suivant le firmware, les possibilités du kernel, la gestion de la carte mère de la machine :

daffy@colerpia:~$ acpi -V Battery 1: charged, 100%, rate information unavailable. Thermal 1: ok, 50.0 degrees C AC Adapter 1: on-line

– L'avantage de Linux, c'est le système de fichier virtuel /proc (exemple) :

daffy@colerpia:~$ more /proc/acpi/thermal_zone/TZN0/* :::::::::::::: /proc/acpi/thermal_zone/TZN0/cooling_mode :::::::::::::: cooling mode: active :::::::::::::: /proc/acpi/thermal_zone/TZN0/polling_frequency ::::::::::::::  :::::::::::::: /proc/acpi/thermal_zone/TZN0/state :::::::::::::: state: ok :::::::::::::: /proc/acpi/thermal_zone/TZN0/temperature :::::::::::::: temperature: 49 C :::::::::::::: /proc/acpi/thermal_zone/TZN0/trip_points :::::::::::::: critical (S5): 90 C passive: 80 C: tc1=4 tc2=3 tsp=100 devices=0xcf7ee560 active[0]: 70 C: devices=0xcf67ce60

Apendix

– Sur les vieilles machines, l'ACPI ne fonctionne pas, c'est alors l'APM (Advanced Power Management). Les informations de température ne sont alors pas disponibles :

daffy@ebola:~$ apm --verbose APM BIOS 1.2 (kernel driver 1.16ac) On-line, no system battery

– D'autres outils de monitoring de la gestion de l'énergie sont disponible, notamment pour les disques durs IDE , avec hdparm

daffy@ebola:~$ sudo hdparm -t /dev/hde /dev/hde: Timing buffered disk reads: 68 MB in 3.09 seconds = 22.03 MB/sec daffy@ebola:~$ sudo hdparm -i /dev/hde /dev/hde: Model=QUANTUM FIREBALLP LM20.5, FwRev=A35.0700, SerialNo=884013362901 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=32256, SectSize=21298, ECCbytes=4 BuffType=DualPortCache, BuffSize=1900kB, MaxMultSect=16, MultSect=off CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=40132503 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 *udma4 AdvancedPM=no WriteCache=enabled Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1: ATA/ATAPI-1 ATA/ATAPI-2 ATA/ATAPI-3 ATA/ATAPI-4 ATA/ATAPI-5 * signifies the current active mode

Ou encore les lsmensors , mais si quelqu'un arrive à faire marcher ça , qu'il me fasse signe :-)

Tips & Tricks Sun Clusters

Olivier Duquesne aka DaffyDuke — 2006-01-17T13:06:57Z

Cas concret : un disque défaillant

Etat : Le disque défaillant (c2t0d0), après unplug/replug, reboot sans sds + drvconfig+disks+devlinks => a été revu OK par "iostat -En" après reboot.

Mais l'état des metadevices était pitoyable.

disque c2t0d0 malade /pci@6,4000/scsi@4,1/sd@0,0 (sd75) corrupt label - wrong magic number
On l'a dépluggé, puis repluggé + drvconfig + disks + devlinks, il faudrait maintenant rebooter.

cmapqlf01:root} metastat d50 d50: Mirror Submirror 0: d51 State: Needs maintenance Submirror 1: d52 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 308826 blocks d51: Submirror of d50 State: Needs maintenance Invoke: metareplace d50 c2t0d0s0  Size: 308826 blocks Stripe 0: Device Start Block Dbase State Hot Spare c2t0d0s0 0 No Maintenance d52: Submirror of d50 State: Okay Size: 308826 blocks Stripe 0: Device Start Block Dbase State Hot Spare c2t1d0s0 0 No Okay cmapqlf01:root} metadb -i flags first blk block count a m c luo 16 1034 /dev/dsk/c1t0d0s7 a c luo 1050 1034 /dev/dsk/c1t0d0s7 a c luo 2084 1034 /dev/dsk/c1t0d0s7 a c luo 16 1034 /dev/dsk/c1t1d0s7 a c luo 1050 1034 /dev/dsk/c1t1d0s7 a c luo 2084 1034 /dev/dsk/c1t1d0s7 M c unknown unknown /dev/dsk/c2t0d0s7 M c unknown unknown /dev/dsk/c2t0d0s7 M c unknown unknown /dev/dsk/c2t0d0s7 o - replica active prior to last mddb configuration change u - replica is up to date l - locator for this replica was read successfully c - replica's location was in /etc/lvm/mddb.cf p - replica's location was patched in kernel m - replica is master, this is replica selected as input W - replica has device write errors a - replica is active, commits are occurring to this replica M - replica had problem with master blocks D - replica had problem with data blocks F - replica had format problems S - replica is too small to hold current data base R - replica had device read errors cmapqlf01:root} metadb -d /dev/dsk/c2t0d0s7 cmapqlf01:root} metadb flags first blk block count a m c luo 16 1034 /dev/dsk/c1t0d0s7 a c luo 1050 1034 /dev/dsk/c1t0d0s7 a c luo 2084 1034 /dev/dsk/c1t0d0s7 a c luo 16 1034 /dev/dsk/c1t1d0s7 a c luo 1050 1034 /dev/dsk/c1t1d0s7 a c luo 2084 1034 /dev/dsk/c1t1d0s7 cmapqlf01:root} metastat d20 d20: Mirror Submirror 0: d21 State: Needs maintenance Submirror 1: d22 State: Needs maintenance Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 1231713 blocks d21: Submirror of d20 State: Needs maintenance Invoke: metareplace d20 c1t0d0s4  Size: 1231713 blocks Stripe 0: Device Start Block Dbase State Hot Spare c1t0d0s4 0 No Maintenance d22: Submirror of d20 State: Needs maintenance Invoke: after replacing "Maintenance" components: metareplace d20 c1t1d0s4  Size: 1231713 blocks Stripe 0: Device Start Block Dbase State Hot Spare c1t1d0s4 0 No Last Erred cmapqlf01:root} metareplace -e d20 c1t0d0s4 metareplace: cmapqlf01: c1t0d0s4: is mounted on /var cmapqlf01:root} metareplace -e d20 c1t1d0s4 metareplace: cmapqlf01: d20: c1t1d0s4: component in invalid state to replace - Replace "Maintenance" components first cmapqlf01:root} metadetach -f d20 d22 metadetach: cmapqlf01: d20: operation would result in no readable submirrors cmapqlf01:root} metadetach -f d20 d21 d20: submirror d21 is detached cmapqlf01:root} metaclear d20 metaclear: cmapqlf01: d20: attempted to clear mirror with submirror(s) in invalid state cmapqlf01:root} metastat d20 d20: Mirror Submirror 1: d22 State: Needs maintenance Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 1231713 blocks d22: Submirror of d20 State: Needs maintenance Invoke: after replacing "Maintenance" components: metareplace d20 c1t1d0s4  Size: 1231713 blocks Stripe 0: Device Start Block Dbase State Hot Spare c1t1d0s4 0 No Last Erred destruction cmapqlf01:root} metaclear -f d20 d20: Mirror is cleared cmapqlf01:root} metastat d20 metastat: cmapqlf01: d20: unit not set up cmapqlf01:root} metastat d21 d21: Concat/Stripe Size: 1231713 blocks Stripe 0: Device Start Block Dbase c1t0d0s4 0 No cmapqlf01:root} metastat d22 d22: Concat/Stripe Size: 1231713 blocks Stripe 0: Device Start Block Dbase c1t1d0s4 0 No cmapqlf01:root} metainit d20 -m d21 d20: Mirror is setup cmapqlf01:root} metastat d20 d20: Mirror Submirror 0: d21 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 1231713 blocks d21: Submirror of d20 State: Okay Size: 1231713 blocks Stripe 0: Device Start Block Dbase State Hot Spare c1t0d0s4 0 No Okay cmapqlf01:root} df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c1t0d0s0 771110 352347 364786 50% / /dev/dsk/c1t0d0s3 1018382 178193 779087 19% /usr /proc 0 0 0 0% /proc fd 0 0 0 0% /dev/fd mnttab 0 0 0 0% /etc/mnttab /dev/dsk/c1t0d0s4 578351 365642 154874 71% /var swap 4653176 24 4653152 1% /var/run swap 4653160 8 4653152 1% /tmp /dev/dsk/c1t0d0s5 4492386 1979687 2467776 45% /sybase cmapqlf01:root} metastat d50 d50: Mirror Submirror 0: d51 State: Needs maintenance Submirror 1: d52 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 308826 blocks d51: Submirror of d50 State: Needs maintenance Invoke: metareplace d50 c2t0d0s0  Size: 308826 blocks Stripe 0: Device Start Block Dbase State Hot Spare c2t0d0s0 0 No Maintenance d52: Submirror of d50 State: Okay Size: 308826 blocks Stripe 0: Device Start Block Dbase State Hot Spare c2t1d0s0 0 No Okay cmapqlf01:root} metadetach -f d50 d51 d50: submirror d51 is detached cmapqlf01:root} metaclear d50 d50: Mirror is cleared cmapqlf01:root} metastat d51 d51: Concat/Stripe Size: 308826 blocks Stripe 0: Device Start Block Dbase c2t0d0s0 0 No cmapqlf01:root} metastat d52 d52: Concat/Stripe Size: 308826 blocks Stripe 0: Device Start Block Dbase c2t1d0s0 0 No

A l'iostat -En, on voit que le disque c2t0d0 est OK
Mais au format, il demande à être labellé. => il faut y virer d'abord tous les metadevices

cmapqlf01:root} metaclear -f d51 d51: Concat/Stripe is cleared cmapqlf01:root} metastat d60 d60: Mirror Submirror 0: d61 State: Needs maintenance Submirror 1: d62 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 308826 blocks d61: Submirror of d60 State: Needs maintenance Invoke: metareplace d60 c2t0d0s1  Size: 308826 blocks Stripe 0: Device Start Block Dbase State Hot Spare c2t0d0s1 0 No Maintenance d62: Submirror of d60 State: Okay Size: 308826 blocks Stripe 0: Device Start Block Dbase State Hot Spare c2t1d0s1 0 No Okay cmapqlf01:root} metadetach -f d60 d61 d60: submirror d61 is detached cmapqlf01:root} metaclear d60 d60: Mirror is cleared cmapqlf01:root} metaclear -f d61 d61: Concat/Stripe is cleared cmapqlf01:root} metastat d62 d62: Concat/Stripe Size: 308826 blocks Stripe 0: Device Start Block Dbase c2t1d0s1 0 No

Idem : d71 need maintenance

cmapqlf01:root} metadetach -f d70 d71 d70: submirror d71 is detached cmapqlf01:root} metaclear d70 d70: Mirror is cleared cmapqlf01:root} metaclear -f d71 d71: Concat/Stripe is cleared cmapqlf01:root} metastat d72 d72: Concat/Stripe Size: 2050461 blocks Stripe 0: Device Start Block Dbase c2t1d0s3 0 No Idem: d81 need maint cmapqlf01:root} metadetach -f d80 d81 d80: submirror d81 is detached cmapqlf01:root} metaclear d80 d80: Mirror is cleared cmapqlf01:root} metaclear -f d81 d81: Concat/Stripe is cleared Idem d90 need maint cmapqlf01:root} metadetach -f d90 d91 d90: submirror d91 is detached cmapqlf01:root} metaclear d90 d90: Mirror is cleared cmapqlf01:root} metaclear -f d91 d91: Concat/Stripe is cleared cmapqlf01:root} metastat d92 d92: Concat/Stripe

Reformatage du disque c2t0d0

cmapqlf01:root} metainit d51 1 1 /dev/dsk/c2t0d0s0 d51: Concat/Stripe is setup cmapqlf01:root} metainit d61 1 1 /dev/dsk/c2t0d0s1 d61: Concat/Stripe is setup cmapqlf01:root} metainit d71 1 1 /dev/dsk/c2t0d0s3 d71: Concat/Stripe is setup cmapqlf01:root} metainit d81 1 1 /dev/dsk/c2t0d0s4 d81: Concat/Stripe is setup cmapqlf01:root} metainit d91 1 1 /dev/dsk/c2t0d0s5 d91: Concat/Stripe is setup metinit d50 -m d51 metattach d50 d52

idem d60, d70, d80, d90 + attente synchro
refaire les newfs des d70 et d80, peut-être malmenés ?
Modif vfstab pour ré-intégrer tous les miroirs sauf pour / et swap
On prévoit de rebooter....

Avant : mise aux droits sybase des devices correspondants aux miroirs + aux sub-miroirs des
raw qu'utilisera sybase

cmapqlf01:root} ls -l /dev/ASE* total 12 lrwxrwxrwx 1 sybase sybase 16 Sep 30 16:19 log_rdev01 -> /dev/md/rdsk/d90 lrwxrwxrwx 1 root other 18 Oct 7 09:18 master -> /dev/rdsk/c2t0d0s0 lrwxrwxrwx 1 sybase sybase 16 Sep 30 16:08 master_1 -> /dev/md/rdsk/d50 lrwxrwxrwx 1 root other 18 Oct 7 09:19 sybsystem -> /dev/rdsk/c2t0d0s1 lrwxrwxrwx 1 sybase sybase 16 Sep 30 16:17 sybsystem_1 -> /dev/md/rdsk/d60 lrwxrwxrwx 1 sybase sybase 17 Sep 30 16:29 user_rdev01 -> /dev/md/rdsk/d110 cmapqlf01:root} metastat -p d50 d50 -m d51 d52 1 d51 1 1 c2t0d0s0 d52 1 1 c2t1d0s0 cmapqlf01:root} ls -l /dev/rdsk/c2t0d0s0 lrwxrwxrwx 1 root root 46 Aug 20 18:56 /dev/rdsk/c2t0d0s0 -> ../../devices/pci@6,4000/scsi@4,1/sd@0,0:a,raw cmapqlf01:root} ls -l /devices/pci@6,4000/scsi@4,1/sd@0,0:a,raw crw-r----- 1 sybase sybase 32,600 Oct 7 09:21 /devices/pci@6,4000/scsi@4,1/sd@0,0:a,raw cmapqlf01:root} ls -l /dev/rdsk/c2t1d0s0 lrwxrwxrwx 1 root root 46 Aug 20 18:56 /dev/rdsk/c2t1d0s0 -> ../../devices/pci@6,4000/scsi@4,1/sd@1,0:a,raw cmapqlf01:root} ls -l /devices/pci@6,4000/scsi@4,1/sd@1,0:a,raw crw-r----- 1 root sys 32,608 Aug 20 18:56 /devices/pci@6,4000/scsi@4,1/sd@1,0:a,raw cmapqlf01:root} chown sybase:sybase /devices/pci@6,4000/scsi@4,1/sd@1,0:a,raw cmapqlf01:root} ls -l /devices/pci@6,4000/scsi@4,1/sd@1,0:a,raw crw-r----- 1 sybase sybase 32,608 Aug 20 18:56 /devices/pci@6,4000/scsi@4,1/sd@1,0:a,raw cmapqlf01:root} metastat -p d60 d60 -m d61 d62 1 d61 1 1 c2t0d0s1 d62 1 1 c2t1d0s1 cmapqlf01:root} ls -l /dev/rdsk/c2t0d0s1 /dev/rdsk/c2t1d0s1 lrwxrwxrwx 1 root root 46 Aug 20 18:56 /dev/rdsk/c2t0d0s1 -> ../../devices/pci@6,4000/scsi@4,1/sd@0,0:b,raw lrwxrwxrwx 1 root root 46 Aug 20 18:56 /dev/rdsk/c2t1d0s1 -> ../../devices/pci@6,4000/scsi@4,1/sd@1,0:b,raw cmapqlf01:root} ls -l /devices/pci@6,4000/scsi@4,1/sd@0,0:b,raw /devices/pci@6,4000/scsi@4,1/sd@1,0:b,raw crw-r----- 1 sybase sybase 32,601 Aug 20 18:56 /devices/pci@6,4000/scsi@4,1/sd@0,0:b,raw crw-r----- 1 root sys 32,609 Aug 20 18:56 /devices/pci@6,4000/scsi@4,1/sd@1,0:b,raw cmapqlf01:root} chown sybase:sybase /devices/pci@6,4000/scsi@4,1/sd@1,0:b,raw cmapqlf01:root} metastat -p d90 d90 -m d91 d92 1 d91 1 1 c2t0d0s5 d92 1 1 c2t1d0s5 cmapqlf01:root} ls -l /dev/rdsk/c2t0d0s5 /dev/rdsk/c2t1d0s5 lrwxrwxrwx 1 root root 46 Aug 20 18:56 /dev/rdsk/c2t0d0s5 -> ../../devices/pci@6,4000/scsi@4,1/sd@0,0:f,raw lrwxrwxrwx 1 root root 46 Aug 20 18:56 /dev/rdsk/c2t1d0s5 -> ../../devices/pci@6,4000/scsi@4,1/sd@1,0:f,raw cmapqlf01:root} ls -l /devices/pci@6,4000/scsi@4,1/sd@0,0:f,raw /devices/pci@6,4000/scsi@4,1/sd@1,0:f,raw crw-r----- 1 root sys 32,605 Aug 20 18:56 /devices/pci@6,4000/scsi@4,1/sd@0,0:f,raw crw-r----- 1 root sys 32,613 Aug 20 18:56 /devices/pci@6,4000/scsi@4,1/sd@1,0:f,raw cmapqlf01:root} chown sybase:sybase /devices/pci@6,4000/scsi@4,1/sd@0,0:f,raw /devices/pci@6,4000/scsi@4,1/sd@1,0:f,raw cmapqlf01:root} ls -l /devices/pci@6,4000/scsi@4,1/sd@0,0:f,raw /devices/pci@6,4000/scsi@4,1/sd@1,0:f,raw crw-r----- 1 sybase sybase 32,605 Aug 20 18:56 /devices/pci@6,4000/scsi@4,1/sd@0,0:f,raw crw-r----- 1 sybase sybase 32,613 Aug 20 18:56 /devices/pci@6,4000/scsi@4,1/sd@1,0:f,raw cmapqlf01:root} metastat -p d110 d110 -m d111 d112 1 d111 1 1 c3t0d0s1 d112 1 1 c3t1d0s1 cmapqlf01:root} ls -l /dev/rdsk/c3t0d0s1 /dev/rdsk/c3t1d0s1 lrwxrwxrwx 1 root other 45 Sep 29 17:59 /dev/rdsk/c3t0d0s1 -> ../../devices/pci@1f,4000/scsi@3/sd@0,0:b,raw lrwxrwxrwx 1 root other 45 Sep 29 17:59 /dev/rdsk/c3t1d0s1 -> ../../devices/pci@1f,4000/scsi@3/sd@1,0:b,raw cmapqlf01:root} ls -l /devices/pci@1f,4000/scsi@3/sd@0,0:b,raw /devices/pci@1f,4000/scsi@3/sd@1,0:b,raw crw-r----- 1 root sys 32, 1 Sep 29 17:59 /devices/pci@1f,4000/scsi@3/sd@0,0:b,raw crw-r----- 1 root sys 32, 9 Sep 29 17:59 /devices/pci@1f,4000/scsi@3/sd@1,0:b,raw cmapqlf01:root} chown sybase:sybase /devices/pci@1f,4000/scsi@3/sd@0,0:b,raw /devices/pci@1f,4000/scsi@3/sd@1,0:b,raw cmapqlf01:root} cmapqlf01:root} ls -l /dev/md/rdsk/d50 lrwxrwxrwx 1 root other 37 Sep 30 11:01 /dev/md/rdsk/d50 -> ../../../devices/pseudo/md@0:0,50,raw cmapqlf01:root} ls -l /devices/pseudo/md@0:0,50,raw crw-r----- 1 sybase sybase 85, 50 Oct 7 09:16 /devices/pseudo/md@0:0,50,raw cmapqlf01:root} ls -l /dev/md/rdsk/d60 lrwxrwxrwx 1 root other 37 Sep 30 11:01 /dev/md/rdsk/d60 -> ../../../devices/pseudo/md@0:0,60,raw cmapqlf01:root} ls -l /devices/pseudo/md@0:0,60,raw crw-r----- 1 sybase sybase 85, 60 Sep 30 11:01 /devices/pseudo/md@0:0,60,raw cmapqlf01:root} ls -l /dev/md/rdsk/d90 lrwxrwxrwx 1 root other 37 Sep 30 11:01 /dev/md/rdsk/d90 -> ../../../devices/pseudo/md@0:0,90,raw cmapqlf01:root} ls -l /devices/pseudo/md@0:0,90,raw crw-r----- 1 sybase sybase 85, 90 Sep 30 11:01 /devices/pseudo/md@0:0,90,raw cmapqlf01:root} ls -l /dev/md/rdsk/d110 lrwxrwxrwx 1 root other 38 Sep 30 11:01 /dev/md/rdsk/d110 -> ../../../devices/pseudo/md@0:0,110,raw cmapqlf01:root} ls -l /devices/pseudo/md@0:0,110,raw crw-r----- 1 sybase sybase 85,110 Sep 30 11:01 /devices/pseudo/md@0:0,110,raw

=> tout est bien à sybase !
Et rétablissement des bons liens vers les miroirs :

cmapqlf01:root} ls -l /dev/ASE01 total 12 lrwxrwxrwx 1 sybase sybase 16 Sep 30 16:19 log_rdev01 -> /dev/md/rdsk/d90 lrwxrwxrwx 1 sybase sybase 16 Sep 30 16:08 master -> /dev/md/rdsk/d50 lrwxrwxrwx 1 root other 18 Oct 7 09:18 old_master -> /dev/rdsk/c2t0d0s0 lrwxrwxrwx 1 root other 18 Oct 7 09:19 old_sybsystem -> /dev/rdsk/c2t0d0s1 lrwxrwxrwx 1 sybase sybase 16 Sep 30 16:17 sybsystem -> /dev/md/rdsk/d60 lrwxrwxrwx 1 sybase sybase 17 Sep 30 16:29 user_rdev01 -> /dev/md/rdsk/d110

Ajout d'un replica

cmapqlf01:root} metadb flags first blk block count a m pc luo 16 1034 /dev/dsk/c1t0d0s7 a pc luo 1050 1034 /dev/dsk/c1t0d0s7 a pc luo 2084 1034 /dev/dsk/c1t0d0s7 a pc luo 16 1034 /dev/dsk/c1t1d0s7 a pc luo 1050 1034 /dev/dsk/c1t1d0s7 a pc luo 2084 1034 /dev/dsk/c1t1d0s7 cmapqlf01:root} metadb -a /dev/dsk/c2t1d0s7 cmapqlf01:root} metadb flags first blk block count a m pc luo 16 1034 /dev/dsk/c1t0d0s7 a pc luo 1050 1034 /dev/dsk/c1t0d0s7 a pc luo 2084 1034 /dev/dsk/c1t0d0s7 a pc luo 16 1034 /dev/dsk/c1t1d0s7 a pc luo 1050 1034 /dev/dsk/c1t1d0s7 a pc luo 2084 1034 /dev/dsk/c1t1d0s7 a u 16 1034 /dev/dsk/c2t1d0s7

reboot, donc....
Avec tous les miroirs sauf / (root), c'est OK.
Si on fait juste l'échange des # dans vfstab pour / (d40 au lieu de c1t0d0s0 ) =>
alors ça marche pas au boot (et il faut à nouveau booter cdrom pour inverser la vapeur
dans vfstab).

Après un nouveau reboot sur c1t0d0s0, on corrige :

metadetach d40 d42 metaclear d40

(d40 disparaît, reste les deux sous-miroirs)

metainit d40 -m d41 metaroot d40 lockfs -fa reboot

Après reboot (ok) : metattach d40 d42 (synchro)

Il faut refaire un essai de boot sur le miroir....

Tips & Tricks VxVm/Veritas

Olivier Duquesne aka DaffyDuke — 2006-01-17T12:55:53Z

Voir l'état actuel du cluster

 cfgadm -la vxdiskadm

Répondre aux questions :-)

– vérifier avec

 vxdisk list

– Capacité maximale du mirroir :

 vxassist -g oradg01 -b maxsize layout=mirrored,log

– création du mirroir

 vxassist -g oradg01 -b make oralocal 34725m layout=mirrored,log

– Liste des tâches, pour savoir quand il aura terminé son mirroir

 vxtask -l list

– Formatage

 mkfs -F vxfs -o largefiles /dev/vx/rdsk/oradg01/oralocal

– Etat du cluster

 hastatus -sum

– Visualiser les ressources associées au groupe clucufprd03

 hagrp -display clucufprd03

– Supprimer les ressources puis le groupe

 haconf -makerw hagrp -resources clucufprd03 hares -delete IP_lsnuf03 hares -delete UF03 hares -delete LISTENER_lsnuf03 hagrp -delete clucufprd03 haconf -dump -makero

– Contrôle des ressources

 hastatus -sum

RQ : le service est tj actif, aucune indispo !

Bascule VXVM

 vxvol -g PRODDG stop all vxdg deport PRODDG vxdisk

Enlever l'état failing

vxedit -g dg03 set failing=off c4t5d3_dg03

Veritas Mini-HOWTO

– Binaires VCS (Veritas Cluster Server) : dans /opt/VRTS* (notamment /opt/VRTSvcs/bin)
– Log : dans /var/VRTSvcs/log (surtout engine*.log)
– Conf : dans /etc/VRTSvcs/conf/config

Commandes de base

hastart : demarre un noeud (a faire sur les N noeuds si le cluster est arrete)
hastop [-all] : arrete un [tous les] noeud[s] -> hastop -all pour arreter completement le cluster et faire des manips sur les fichiers de config

– hagrp : manip sur un group
– hagrp -switch -to : bascule un groupe vers un noeud
– hagrp -online -sys : demarre un groupe sur un noeud (si il n est pas deja online ailleurs)
– hagrp -offline -sys

– hares : manip sur les ressources d'un groupe
– hares -clear -sys : enleve le flag FAULTED d'une ressource plantee, et la passe a OFFLINE

– halog -info : renvoie le path des logs et la taille max du fichier engine.log
– hacf -verify /etc/VRTSvcs/conf/config : verifie le fichier de config du noeud

– hastatus : montre l'etat de chaque noeud/group/ressource. Dans l'etat normal, chaque ressource/group est ONLINE sur un seul noeud, et OFFLINE sur les autres. Les etats anormaux sont : FAULTED, PARTIALLY_FAULTED, ADMIN_WAIT, STALE ...

chaque commande ha* possede plusieurs options ... RTFM :)

Manipulations de base

– Demarrer un cluster
hastart (sur chacun des noeuds)
– Arreter un cluster
hastop -all (sur un seul noeud)
– Basculer un groupe sur un noeud
tail -f /var/VRTSvcs/log/engine_A.log et hagrp -switch -to
surveiller le log pour verifier que les ressources sont bien arretes puis redemarres sur l'autre noeud

Ce qu'il ne faut pas faire

– Rebooter les noeuds en meme temps -> le cluster ne redemarrera pas
– Modifier un fichier de conf pendant que le cluster tourne sans avoir fait un haconf -makerw -> les modifs seront perdues

Tracer une requête java

Olivier Duquesne aka DaffyDuke — 2006-01-17T12:42:54Z

Sur Solaris

 truss -o /var/tmp/test -f -tsend,read,recv,write -rall -wall -p  > /var/tmp/test sshinstall tar jvmstat  puis jvmps -v jvmstat -gcapacity pid

Ajouter le parsage XML dans Java 1.4

 mkdir /usr/java/j2sdk1.4./jre/lib/endorsed cp depuis filer jaxp-api.jar -> /usr/local/classes/jar/jaxp/jaxp-api.jar xalan.jar -> /usr/local/classes/jar/xalan/xalan.jar xercesImpl.jar -> /usr/local/classes/jar/xerces/xercesImpl.jar xml-apis.jar -> /usr/local/classes/jar/xerces/xml-apis.jar restart service

Commandes sur l'OpenBIOS de SunOS

Olivier Duquesne aka DaffyDuke — 2006-01-17T12:40:48Z

Erreurs lors du boot de la machine

Si ce message survient :

{7} ok boot FATAL: system is not bootable, boot command is disabled

alors

{7} ok setenv auto-boot? false auto-boot? = false {7} ok reset-all Resetting ...

Ref : SunSolve

Créer un nouvel alias disk

quand dans un printenv on n'a pas le bon disk :
devalias pour voir les différents alias existants

 nvalias dis6 /pci@6,4000/scsi@4/disk@0,0 pour créer disk6 setenv boot-device disk6 pour forcer le boot sur disk6

Connaître le nombre de barrêtes de RAM sur une netra/Sunfire

Olivier Duquesne aka DaffyDuke — 2006-01-17T12:37:36Z

/usr/plateform/sun4u/sbin/prtdiag prtconf -pv memconf un script perl
(non supporté par Sun mais dispo chez SunFreeware)

- Au boulot / solaris

Tips & Tricks TCP/IP sous Solaris

Olivier Duquesne aka DaffyDuke — 2006-01-17T07:55:17Z

Echantillonnage TCP

pour avoir le debit IN/OUT en continu
/usr/local/etc/debit_lan
pour avoir le delta des valeurs du driver tcp entre 2 intervales de temps :
/usr/local/etc/delta_tcp

Config TCP

 ndd -get /dev/tcp tcp_keepalive_interval

Passer en 100 full duplex avec une carte Gigabit

The bge inferface (V210) can be forced to a certain speed and duplex via two methodes: ndd and bge.conf NDD Creating a script in /etc/rc2.d/S68net_tune #!/sbin/sh # /etc/rc2.d/S68net-tune PATH=/usr/bin:/usr/sbin # Force bge0 to 100fdx autoneg off ndd -set /dev/bge0 adv_1000fdx_cap 0 ndd -set /dev/bge0 adv_1000hdx_cap 0 ndd -set /dev/bge0 adv_100fdx_cap 1 ndd -set /dev/bge0 adv_100hdx_cap 0 ndd -set /dev/bge0 adv_10fdx_cap 0 ndd -set /dev/bge0 adv_10hdx_cap 0 ndd -set /dev/bge0 adv_autoneg_cap 0 bge.conf Adding the following line to the file /platform/sun4u/kernel/drv/bge.conf adv_autoneg_cap=0 adv_1000fdx_cap=0 adv_1000hdx_cap=0 \ adv_100fdx_cap=1 adv_100hdx_cap=0 adv_10fdx_cap=0 \ adv_10hdx_cap=0; However, using bge.conf will force all instances of bge to the speed/duplex specified in the file.

Connaître la f**king interface réseau

prtconf -Dv|grep net

Enlever la LED de panne matérielle d'une Netra/Sunfire

Olivier Duquesne aka DaffyDuke — 2006-01-17T07:51:05Z

Il s'agit d'un coup de chaud (ventilo, CPU, bref une forte charge). Une fois assuré que tout est ok, il est possible d'éteindre la LED via une console (en ssh ça ne marche pas) :

root@host>.# LOM>faultoff LOM>console root@host>ps -ef