This is an old revision of the document!
Table of Contents
HP-UX
- Verzeichnis der allgemeinen Cluster-Config: /etc/cmcluster.conf
- Verzeichnis der Pakete: /etc/cmcluster/
- Linux TOP → UNIX Glance
- kcusage - memory allocation nach tagen, monaten etc..
- Cluster Management
cmviewcl
cmrunpkg cmhaltpkg cmmodpkg -e cmcheckconf -P cmapplyconf -P
- Cluster-Pakete schwenken
tsm1: /root# cat env_tsm1
export DSMSERV_DIR=/opt/tivoli/tsm/server/bin export DSMSERV_CONFIG=/tsm1/server/dsmserv.opt cd /tsm1/server
tsm1: /root# cat mount_tsm1 #!/bin/sh vgchange -a e /dev/vgxy ... mount /dev/vgxy/lvoly /tsm1 mount /dev/vgxy/lvolx /tsm1/server mount -o largefiles /dev/vgxy/lvol1 /tsm1/db mount -o largefiles /dev/vgyz/lvol1 /tsm1/recoverylog mount -o largefiles /dev/vgab/lvol1 /tsm1/recoverylog2 mount -o largefiles /dev/vgcb/lvol1 /tsm1/disk
tsm1: /root# cat umount_tsm1 #!/bin/sh umount /tsm1/server umount /tsm1/db umount /tsm1/recoverylog umount /tsm1/recoverylog2 umount /tsm1/disk umount /tsm1 vgchange -a n /dev/vgxy vgchange -a n /dev/vgyz vgchange -a n /dev/vgav vgchange -a n /dev/vgcb
- Drive Status prüfen
ioscan -fnkC autoch
- tapeutil OHNE Parameter ausführen → “grafische” Darstellung in der Console
TSM-Server Software Upgrade
Beispielhafte Zusammenstellung verfügbarer Pakete
TIVsmS64.server PA-RISC 64 bit server TIVsmS64.license PA-RISC 64 bit license enablement TIVsmS64IA.server Itanium® 64 bit server TIVsmS64IA.license Itanium 64 bit license enablement TIVsmHsta64.storage_agent PA-RISC 64 bit storage agent TIVsmHstaIA.storage_agent Itanium 64 bit storage agent TIVsmDD64_PA11_23.tsmscsi Tivoli Storage Manager device driver for 64 bit 11.23 PA-RISC OS TIVsmDD64_IA11_23.tsmscsi Tivoli Storage Manager device driver for 64 bit 11.23 Itanium OS
Eine Liste aller installierten Tivoli Pakete
cbbtsm1: /root# swlist | grep TIV TIVsm64 5.5.0 IBM Tivoli Storage Manager Client TIVsmS64IA 5.4.0.0 IBM Tivoli Storage Manager Server TIVsmS64IA 5.4.5.1 IBM Tivoli Storage Manager Server
Datenbank und Konfiguration sichern
backup db type=full devclass=tape_device_class scratch=yes
Notieren welche Pakete wo laufen
cmviewcl
Pakete anhalten
cmhaltpkg $paketname
Entfernen der Server-Installation
swremove TIVsmS64,r=5.4.5.1 swremove TIVsmS64
Installieren der Neuen Version (je ein Befehl für 5.5.0.0, 5.5.4.0, 5.5.4.2)
swinstall -s /pfad/zur/datei/ -x ask=as_needed TIVsmS64
Vor jedem dsmsrv start müssen die Filesysteme gemoutet werden und die Umgebungswvariablen angepasst werden. Die nötigen Dateien liegen unter /var/hzd/admin/tsm/
/root/tsm/mount_tsmx /root/tsm/tsmx_env /root/tsm/umount_tsmx
Erstmaliges manuelles starten des Servers
./dsmserv -upgradedb
Bei Versionssprung:
register licence /opt/tivoli/tsm/server/bin/tsmee.lic
Nachdem alle Clusterknoten und alle Clusterpakete fertig sind können diese wieder per Clustermanager gestartet werden
cmrunpkg $paketname
Pakete auf autostart setzen
cmmodpkg -e $paketname
- ioscan
ioscan -fNC $class where class in lsdev For HDD
ioscan -nfC disk
For tape drive
ioscan -nfC tape
For LAN - Ethernet Card
ioscan -nfC LAN
For FC - Fiber Channel
ioscan -nfC FC
WWNs herausbekommen: unixha1:/root# ioscan -knfC fc Class I H/W Path Driver S/W State H/W Type Description
fc 0 0/2/1/0 fcd CLAIMED INTERFACE HP AB379-60001 4Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)
/dev/fcd0
fc 1 0/2/1/1 fcd CLAIMED INTERFACE HP AB379-60001 4Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 2)
/dev/fcd1
fc 2 0/3/2/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td2
fc 3 0/4/2/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td3
fc 4 0/5/1/0 fcd CLAIMED INTERFACE HP AB379-60001 4Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)
/dev/fcd4
fc 5 0/5/1/1 fcd CLAIMED INTERFACE HP AB379-60001 4Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 2)
/dev/fcd5
fcmsutil /dev/fcd1 (vpd)
- LVM
vgcreate -V 2.0 -S 1t -s 4m vg01
Additional Swap Space
01-19-2010 09:19 AM Hi Eric:
You don't need to extend primary swap — and as you have found, you can't easily do it. Generally you would re-ignite your server and choose a larger primary swap then.
Device swap space must be allocated contiguously. That is, without intervening disk extents used or free for another logical volume.
All this is moot. All you need to do is allocate secondary device swap somewhere. Whether or not it resides on vg00 is immaterial.
Secondary or primary device swap are equivalent. Simply add secondary device swap.
Do something like:
# lvcreate -C y -r n -L 32768 -n lvolN /dev/vgXX # swapon -p /dev/vgXX/lvolN
See the manpages for more information. You can do this without a reboot. Remember to add activation of the secondary device swap so built to '/etc/fstab':
/dev/vgXX/lvolN … swap pri=0 0 0
As you can see, the secondary device swap can be on any volume group you choose.
Regards!
…JRF…
