顯示具有 Veritas 標籤的文章。 顯示所有文章
顯示具有 Veritas 標籤的文章。 顯示所有文章

VCS MySQL Agent Configuration

太久沒有碰到客戶用,又忘的差不多了,這次筆記下來吧


MySQL Agent Function
The operations or functions that the Symantec High Availability agent for MySQL
can perform are as follows:
online
$ BaseDir/bin/mysqld_safe --defaults-file=MyCnf --datadir=DataDir --user=MySQLUser
monitor
$ BaseDir/bin/mysqladmin --user=MySQLAdmin --password=MySQLAdminPasswd status
offline
$ BaseDir/bin/mysqladmin --user=MySQLAdmin --password=MySQLAdminPasswd shutdown
clean
$ BaseDir/bin/mysqladmin --user=MySQLAdmin --password=MySQLAdminPasswd shutdown


Create a MySQLAdmin user with shutdown privileages only:
# mysql -uroot -p{PASSWORD}
mysql> use mysql;
mysql> select user,host,password from user;
mysql> create user 'MySQLAdmin'@'localhost' identified by 'passw0rd' ;
mysql> create user 'MySQLAdmin'@'127.0.0.1' identified by 'passw0rd' ;
mysql> grant shutdown on *.* to 'MySQLAdmin'@'localhost' ;
mysql> grant shutdown on *.* to 'MySQLAdmin'@'l27.0.0.1' ;
mysql> select user,host,password from user;
mysql> flush privileges;

Test the user can shutdown the MySQL database
# $BaseDir/bin/mysqladmin --user=MySQLAdmin --password=passw0rd status
# $BaseDir/bin/mysqladmin --user=MySQLAdmin --password=passw0rd shutdown


Installation
# rpm -Uvh VRTSacclib-6.2.0.0-GENERIC.noarch.rpm
# rpm -Uvh VRTSmysql-6.2.0.0-GENERIC.noarch.rpm


Import MySQL resource type: 
/etc/VRTSagents/ha/conf/MySQL/MySQLTypes.cmd


Encrypt MySQLadmin password
# vcsencrypt -agent
Enter Password:
Enter Again:
GUGsHUjUJuNSvUIsK


VCS MySQL Resource Attribute
group MySQL (
        SystemList = { node1 = 0, node2 = 1 }
        )

        MySQL MySQLdb (
                Critical = 1
                MySQLAdmin = MySQLAdmin
                MySQLAdminPasswd = GUGsHUjUJuNSvUIsK   <=== encrypt password
                BaseDir = "/usr"
                DataDir = "/var/lib/mysql"
                MyCnf = "/etc/my.cnf"
                )


Running multiple instances of MySQL on a single node
VCS ENV file
#!/bin/ksh
MYSQL_UNIX_PORT=/tmp/mysql.sock; export MYSQL_UNIX_PORT
MYSQL_TCP_PORT=3307; export MYSQL_TCP_PORT


VxVM DCPA issue (Data Corruption Protection Activated)



http://www.symantec.com/docs/TECH128862
http://www.symantec.com/docs/TECH76355
http://www.symantec.com/docs/TECH167983
http://www.symantec.com/docs/HOWTO55903

VxVM Serial Split Brain - Detection & Resolution

Serial Split Brain - Detection & Resolution
http://www.symantec.com/docs/TECH33020

文件中有詳細說明前因後果與處理流程

第一次碰到這種 vxdg import fail 的狀況
過程是要 import HDS SI 的 disk 時無法 import
(怪,S-Vol 不是應該跟 P-Vol 完全一致嗎?)

VxVM vxdg ERROR V-5-1-10978 Disk group ctidbdg: import failed:
Serial Split Brain detected. Run vxsplitlines to import the diskgroup

發生的原因是 disk 存放的 dg config 不一致
所以 vxvm 不知道要用哪一份 dg config 來 import dg

那我們就指定他要用哪一顆硬碟的 dg config
就可以順利 import 了~

那我們怎麼知道哪顆硬碟的 dg config 是 ok 的呢?

文件中有詳細步驟 vxsplitlines 怎麼用
可是奇怪我跑卻好像卡住一樣,沒東西出來
我只好手動作業了

vxdisk list disk 找到一顆 config enable 的
再用 /etc/vx/diag.d/vxprivutil dumpconfig /dev/rdsk/cxtxd0s2
確認是否可以看到 dg config

ok 找到這顆硬碟 dg config 可用
vxdisk list disk 中有 diskid 資訊

# /usr/sbin/vxdg (-s) -o selectcp= import newdg

耶,成功 dg import 進來了~

.





Netbackup Email Notification


Netbackup 設定完 BLAT 後
測了好一陣子 email notify,備份失敗寄信 ok 沒問題
但是若連備份成功也要寄信通知的話,老是踹不出來
原來是每一台 clinet 都要個別設定 email,終於ok~


DOCUMENTATION: Email Notifications Settings and Their Behaviors
http://www.symantec.com/docs/TECH64984

節錄重點:

The Global Attributes section contains the Administrator's e-mail address field which will be the email NetBackup feeds to nbmail.cmd when a backup finishes with a nonzero status. Putting an email address in Global Attributes will cause NetBackup to send e-mail notifications for only non-zero backup statuses
這裡設定的 email,只會收到備份失敗的通知信

 


The Universal Settings section contains the Client administrator's e-mail field which will be the email address NetBackup feeds to nbmail.cmd when a backup finishes with any status. Putting the email address in Universal Settings will cause NetBackup to send e-mail notifications for all backup statuses
這裡設定的 email,不論成功失敗,所有的jobs完成都會發通知信
而且每一台 clinet 都要個別設定 email


最好都選擇 Server sends mail
才可以在 blat 中定義統一的 email subject



VEA can not start in RHEL 6.X


從 Storage Foundation 5.x 起, VEA 已不內含在套件中了,所以需要另外單獨下載安裝
RHEL 6.X 起,預設都是x64了,所以少裝了許多 32bit library
導致了 32bit 的程式 VEA 啟動失敗

原來在 VEA Readme File 裡面都有寫到,真是自己的疏忽
把缺少的 32bit library 補一補就 ok 啦

from Veritas Enterprise Administrator (VEA) Console
VRTSobgui 3.4.30.0 README file

PACKAGE INFORMATION
-----------------------------------
Product :    Veritas Enterprise Administrator (VEA) Console
Package :    VRTSobgui
Release :    3.4.30.0

SUPPORTED PLATFORMS
-----------------------------------
Operating Systems (OS):  Linux
OS Versions          :  RHEL(3.0,4.0,5.0,5.5,6.0,6.1), SLES(8.0,9.0,10.0,11)

Note: For launching VEA GUI in RHEL 6.0 onwards we need to install 32 bit versions of following packages:

1) libXau-1.0.5-1.el6.i686.rpm
2) libxcb-1.5-1.el6.i686.rpm
3) libX11-1.3-2.el6.i686.rpm
4) libXext-1.1-3.el6.i686.rpm
5) libXi-1.3-3.el6.i686.rpm
6) libXtst-1.0.99.2-3.el6.i686.rpm
7) libXrender-0.9.5-1.el6.i686.rpm

 .

VEA reports lun as failing, but "vxdisk list"does not


這狀況偶爾會碰到...
明明 vxdisk, vxprint 檢查都是 ok 沒問題的
VEA GUI 卻顯示 disk 有叉叉...可能是 VEA cache 的問題

 如何清除 VEA cache ?

VEA reports lun as failing, but "vxdisk list"does not
http://www.symantec.com/docs/TECH128994

* 關閉 VEA
* 清除 cache
# vxconfigd-k -x cleartempdir

* 重起 VEA
.

SCSI3 PGR operations on a VxDMP dmpnode result in dmp path disablement with RHEL5U8 and later kernels


RHEL 5.8 + SFCFS 一台重開另一台就 hang 住不動到 reboot ...

被這個搞死了,總算找到原因了
Linux Kernel 跑太快,竟然還加了個新的 scsi error type
VxVM 還不認識這個新 error type,導致使用 vxdmp 的 vxfen 出狀況



SCSI3 PGR operations on a VxDMP dmpnode result in dmp path disablement with RHEL5U8 and later kernels
http://www.symantec.com/docs/TECH192940

Problem
SCSI3 PGR (Persistent Group Registrations) operations on a VxDMP (VERITAS Dynamic Multi-Pathing) dmpnode result in VxDMP path disablement.

Side effects of the issue include the following:
• Reservation conflict immediately followed by VxDMP error V-5-0-112, whenever SCSI3 PGR operations are executed on a dmpnode.
         Operations that will issue SCSI3 PGR operation on a dmpnode include:
          - Stopping the cluster with hastop.
          - Issuing `/etc/init.d/vxfen start | stop`.  This command is automatically executed at server boot and shutdown.
          - Deporting a diskgroup that contain disk(s) with registrations or importing a diskgroup with groupreserve option.
• When a node is rebooted. The surviving node(s) may see diskgroups go into dgdisabled state and file system(s) get disabled. If VCS is managing resources you will see resource faults. This occurs because dmp paths and dmpnodes are being disabled as a result of multiple SCSI3 PGR operations.
• When a node is rebooted. The surviving node(s) may get paniced. The panic will be initiated by VxFEN as it is trying to avoid a split brain condition. This occurs because dmp paths and dmpnodes are being disabled as a result of multiple SCSI3 PGR operations, then reenabled by the VxDMP recovery daemon.

Error
kernel: sd 2:0:0:14: reservation conflict
kernel: VxVM vxdmp V-5-0-112 disabled path 66/0x0 belonging to the dmpnode 201/0xd0 due to path failure


Environment
RHEL5U8 running kernel 2.6.18-308.el5 and later
Storage Foundation 5.1 and later or Storage Foundation 6.0, 6.0RP1
VxFEN is configured and enabled with SCSI3 disk based fencing in either raw or dmp mode.
VxDMP is configured.


Cause
RHEL5U8 kernel SCSI layer error handling routine introduced a new error type : ID_NEXUS_FAILURE
This new error type is not handled properly by VxDMP, resulting in dmp paths getting disabled during SCSI3 PGR operations.


Solution
If you are planning to upgrade to RHEL5U8 or are currently running RHEL5U8 kernel 2.6.18-308.el5 or later kernels and are running VxVM 5.1 and later. Symantec recommends installing VxVM5.1SP1RP2P3HF5If you are planning to upgrade to RHEL5U8 or are currently running RHEL5U8 kernel 2.6.18-308.el5 or later kernels and are running VxVM 6.0 or 6.0RP1. Symantec recommends installing VxVM6.0RP1HF1

Workarounds:
Downgrade the kernel to pre RHEL5U8.
Configure vxfenmode in disabled mode.

Note: VERITAS Storage Foundation 6.0.1 will contain the fix and is slated for public release in early September. Rolling patch 5.1SP1RP3 will contain the fix and is slated for public release in early October. Rolling Patch 5.1SP1RP3 will also contain the vxfen patch noted in related articles.
.

How to Create a VxVM Snapshot from a mirror volume

VxVM 的 Volume Instance Snapshot 功能
Require: Storage Foundation Enterprise Version

有三種方式:
* Third-mirror break-off snapshots
* Full-sized snapshots
* Space-optimized snapshots

這兒介紹的就是第一種,範例如下

# vxrpint -th -g dg1
dg dg1          default      default  27000    1253797071.15.t2000

dm dg101        c1t2d0s2     auto     65536    143283520 -
dm dg103        c1t3d0s2     auto     65536    143283520 -

v  oracle_vol   -            ENABLED  ACTIVE   83886080 SELECT    -        fsgen
pl oracle_vol-01 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg101-03     oracle_vol-01 dg101   41943040 83886080 0         c1t2d0   ENA
pl oracle_vol-02 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg103-01     oracle_vol-02 dg103   0        83886080 0         c1t3d0   ENA


1. enable FastResync
# vxsnap -g dg1 prepare oracle_vol ndcomirs=1 alloc=dg101

# vxprint -th -g dg1
v  oracle_vol   -            ENABLED  ACTIVE   83886080 SELECT    -        fsgen
pl oracle_vol-01 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg101-03     oracle_vol-01 dg101   41943040 83886080 0         c1t2d0   ENA
pl oracle_vol-02 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg103-01     oracle_vol-02 dg103   0        83886080 0         c1t3d0   ENA
dc oracle_vol_dco oracle_vol oracle_vol_dcl
v  oracle_vol_dcl -          ENABLED  ACTIVE   6304     SELECT    -        gen
pl oracle_vol_dcl-01 oracle_vol_dcl ENABLED ACTIVE 6304 CONCAT    -        RW
sd dg101-01     oracle_vol_dcl-01 dg101 125829120 6304  0         c1t2d0   ENA

2. create a break-off snapshot volume
# vxsnap -g dg1 make source=oracle_vol/newvol=SNAP-oracle_vol/plex=oracle_vol-02

# vxprint -th g dg1
v  SNAP-oracle_vol -         ENABLED  ACTIVE   83886080 ROUND     -        fsgen
pl oracle_vol-02 SNAP-oracle_vol ENABLED ACTIVE 83886080 CONCAT   -        RW
sd dg103-01     oracle_vol-02 dg103   0        83886080 0         c1t3d0   ENA
dc SNAP-oracle_vol_dco SNAP-oracle_vol SNAP-oracle_vol_dcl
v  SNAP-oracle_vol_dcl -     ENABLED  ACTIVE   6304     SELECT    -        gen
pl SNAP-oracle_vol_dcl-01 SNAP-oracle_vol_dcl ENABLED ACTIVE 6304 CONCAT - RW
sd dg103-02     SNAP-oracle_vol_dcl-01 dg103 83886080 6304 0      c1t3d0   ENA
sp oracle_vol_snp SNAP-oracle_vol SNAP-oracle_vol_dco

v  oracle_vol   -            ENABLED  ACTIVE   83886080 SELECT    -        fsgen
pl oracle_vol-01 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg101-03     oracle_vol-01 dg101   41943040 83886080 0         c1t2d0   ENA
dc oracle_vol_dco oracle_vol oracle_vol_dcl
v  oracle_vol_dcl -          ENABLED  ACTIVE   6304     SELECT    -        gen
pl oracle_vol_dcl-01 oracle_vol_dcl ENABLED ACTIVE 6304 CONCAT    -        RW
sd dg101-01     oracle_vol_dcl-01 dg101 125829120 6304  0         c1t2d0   ENA
sp SNAP-oracle_vol_snp oracle_vol oracle_vol_dco

3. check snapshot status
# vxsnap -g dg1 -xv list
NAME          DG         OBJTYPE SNAPTYPE PARENT     PARENTDG   SNAPDATE         CHANGED_DATA SYNCED_DATA
oracle_vol    dg1        vol     -        -          -          - -              - -          40G (100%)
SNAP-oracle_vol dg1      vol     fullinst oracle_vol dg1        2011/07/31 02:57 64K (0.0%)   40G (100%)


4. split dg
# vxdg split dg1 dg2 SNAP-oracle_vol

# vxprint -th
dg dg1          default      default  27000    1253797071.15.t2000
dm dg101        c1t2d0s2     auto     65536    143283520 -

v  oracle_vol   -            ENABLED  ACTIVE   83886080 SELECT    -        fsgen
pl oracle_vol-01 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg101-03     oracle_vol-01 dg101   41943040 83886080 0         c1t2d0   ENA
dc oracle_vol_dco oracle_vol oracle_vol_dcl
v  oracle_vol_dcl -          ENABLED  ACTIVE   6304     SELECT    -        gen
pl oracle_vol_dcl-01 oracle_vol_dcl ENABLED ACTIVE 6304 CONCAT    -        RW
sd dg101-01     oracle_vol_dcl-01 dg101 125829120 6304  0         c1t2d0   ENA
sp SNAP-oracle_vol_snp oracle_vol oracle_vol_dco

dg dg2          default      default  7000     1312053225.56.t2000
dm dg103        c1t3d0s2     auto     65536    143283520 -

v  SNAP-oracle_vol -         ENABLED  ACTIVE   83886080 ROUND     -        fsgen
pl oracle_vol-02 SNAP-oracle_vol ENABLED ACTIVE 83886080 CONCAT   -        RW
sd dg103-01     oracle_vol-02 dg103   0        83886080 0         c1t3d0   ENA
dc SNAP-oracle_vol_dco SNAP-oracle_vol SNAP-oracle_vol_dcl
v  SNAP-oracle_vol_dcl -     ENABLED  ACTIVE   6304     SELECT    -        gen
pl SNAP-oracle_vol_dcl-01 SNAP-oracle_vol_dcl ENABLED ACTIVE 6304 CONCAT - RW
sd dg103-02     SNAP-oracle_vol_dcl-01 dg103 83886080 6304 0      c1t3d0   ENA
sp oracle_vol_snp SNAP-oracle_vol SNAP-oracle_vol_dco


5. join dg (snap vol refresh reattach must in the same dg)
# vxdg join dg2 dg1

6. Refresh snapshot (source vol, snapshit vol must in the same dg)
# vxsnap -g dg1 refresh SNAP-oracle_vol

7. Reattach, (source vol, snapshit vol must in the same dg)
# vxsnap -b -g dg1 reattach SNAP-oracle_vol source=oracle_vol

.

VxVM Cross-Platform filesystem, linux to sparc

http://www.symantec.com/docs/TECH147697

我的實際案例
是要把 Linux 的 data, 掛到 sparc 主機

1) Linux Production SFCFS P-Vol -> clone disk (S-Vol)

2) -> another Linux VxVM dg import S-Vol -> fscdsconv to sparc
# /opt/VRTS/bin/fscdsconv -e -t os_name=SunOS -f /var/tmp/recovery_vol01 /dev/vx/rdsk/oraracdg/oradata01-vol
# vxdg deport oraracdg

3) -> Solaris Sparc VxVM import S-Vol mount -> Backup
# vxdg -Cf import oraracdg
# vxvol -g oraracdg startall
# mount -F vxfs /oradata01 /dev/vx/rdsk/oraracdg/oradata01-vol

若沒有做 fscdsconv 的話
sparc 直接 import/mount 則會出現錯誤
#/opt/VRTS/bin/mount /dev/vx/dsk/oraracdg/oradata01-vol /oradata01
> UX:vxfs mount: ERROR: V-3-20012: not a valid vxfs file system
> UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version
.

[轉載] Recommended mount options for VxFS

http://www.mail-archive.com/veritas-vx@mailman.eng.auburn.edu/msg00289.html

節錄
DSS/HPC
==========================
VxFS mount options:
Log mode= delaylog (best performance and enables data integrity)
Logsize= medium (doesn't need to be very much larger than default or
keep default)
Mincache=direct (turn off in-kernel buffering)
Convosync=direct (delay inode updates for writes to files)

Tunefs:
Read_ahead=1 (traditional vxfs read ahead enabled)
Fcl_winterval=6000 (50 minute update interval for FCL)

VxVM kernel tuning (/etc/system)
Set vxio:vol_maxio=32768 (max IO size = 16MB)


OLTP
=======================
VxFS mount options:
Log mode= delaylog (best performance and enables data integrity)
Logsize= medium (doesn't need to be very much larger than default or
keep default)
Mincache=direct (turn off in-kernel buffering)
Convosync=direct (delay inode updates for writes to files)

Tunefs:
Read_ahead=0 (turn off read ahead)
Fcl_winterval=6000 (50 minute update interval for FCL)

VxVM kernel tuning (/etc/system)
Set vxio:vol_maxio=32768 (max IO size = 16MB)

續 - Solaris 8 Brand Zone with VCS in Share Storage

前幾天提到 Solaris 8 Brand Zone with VCS in Share Storage

昨天 Veritas 有 patch 出來了
VERITAS Cluster Server 5.0 MP1 and MP3 Hot Fix Zone Agent Patch for Solaris 10 SPARC

實際測試的結果....非常慢... :(
從 initinal onlie 到 online 花了約 150 sec
有點讓人無法接受....

因為只是是將手動的流程,轉由 zone agent online 來處理
把 switch over to other node 當作 migration to new host 來處理而已
每次的 switchover/failover 就是一次 detach/attach/migration to new host .... *_*
導致 zone online 要花上不少時間
除此之外,還有一些對 vcs permission 的檢查
不過那花不了一秒鍾....
每次 migration to new host 實在是太耗時了

顯然 Sun 的做法並不是這樣子
Patch 126020-03 for HA_Container
126020-03/SUNWsczone/reloc/SUNWsczone/sczbt/bin/functions
brand zone on share disk 可以用 override hostid file 的做法
也印證了不必每次切換都 s8_p2v migration to new host

若在 VCS zone agent 使用 Sun Cluster 的方式
只要十秒內 Zone 就 online 了
.

Workaround to access raw VxVM Volumes from Non-global zones

現在 Oracle 用 raw device 的不多了,大部分都是舊機器吧
在轉移到 Solaris 8 Container 的過程中,不可避免的也碰到了
需要在 local zone 中存取 raw device 的狀況

跟直接用 zonecfg 設定 raw device 給 zone 不太一樣

先確認 zone 執行中
global# zoneadm list -cv
ID    NAME                STATUS         PATH
0      global                running         /
1      myzone             running         /s8zone 

確認 raw volume 的 major and minor numbers
global# ls -l /dev/vx/rdsk/dg02
crw-------    1     root  root        370,  38001      Aug 14 18:39  vol01

在 local zone 中用 mknod 建立 volume
global# cd /s8zone/dev
global# mknod vol01 c 370 38001

因為是轉移舊系統,通常我把這兒路逕取的跟舊的一樣
global# mkdir -p /s8zone/dev/vx/rdsk/dg02
global# cd /s8zone/dev/vx/rdsk/dg02
global# mknod vol01 c 370 38001

登入 local zone 檢查一下
global# zlogin s8zone
[Connected to zone 's8zone' pts/2]
Last login: Mon Sep 29 02:07:42 on pts/2
Sun Microsystems Inc. SunOS 5.8 Generic Patch February 2004
Sourcing //.profile-EIS.....
root@s8zone # ls -l /dev/vx/rdsk/dg02
crw-------    1     root  root        370,  38001      Aug 14 18:39  vol01
OK~可以開始玩了 :)

參考文件︰
Document ID: 285063
Workaround to access raw Veritas Volume Manager volumes from Non-global zones

.

Solaris 8 Brand Zone with VCS in Share Storage

繼上次測試 Oracle in Solaris 8 Container with VCS 成功後
這次測試可否將 zone root 放在 share storage 上
文件的部份只有 solaris 10 native zone 寫說可以
不幸滴,測試 solaris 8 zone 的結果是失敗的
-------------------------------------------------------
zoneadm: zone 's8': This zone has been migrated to a new host.
zoneadm: zone 's8':
zoneadm: zone 's8': Run "/usr/lib/brand/solaris8/s8_p2v s8" before booting.
zoneadm: zone 's8':
zoneadm: zone 's8': exec /usr/lib/brand/solaris8/s8_boot s8 /zone/clarify failed
zoneadm: zone 's8': call to zoneadmd failed

--------------------------------------------------------
切換到另一個 node 後,認為轉移到了新的 host
需要跑個 migration 程序,s8_p2v
之後就可以順利將 s8 zone 由 vcs zone agent 帶起來了

可是 cluster failover 總不能這樣子啊,要可以自動帶起來才行
找找找,看有沒有法子 bypass 這個檢查步驟....

原來在 s8_boot 這程序中,會去檢查主機的 hostid
比對 zone root/.host.orig 這個檔案的 hostid
只要不一樣,就認為是轉移主機了
需要執行 s8_p2v 這個 migration 程序後,才可以 boot

那那那... Sun Cluster 怎麼處理這個問題呢?
嘿,給我找到了... Patch 126020-03 for HA_Containers
畢竟 S8/S9 Container 是後來出來的玩意兒,不過 Sun 手腳也很快
上個 Patch 就解決了這個問題
將 126020-03 解開看看裡面到底改了什麼玩意兒?
SUNWsczone/sczbt/bin/functions 裡面加了些東西
一些判斷 zone type 是 solaris8/solaris9/lx
重點來了,執行 hostid > $zonepath/root/.host.orig

嗯嗯,我如法炮製
去修改 VCS Zone agent 的 online script
測試一下,嘿嘿﹋﹋ it works!!

經詢問的結果,聽說這幾天 VCS patch 會針對此狀況做處理
到時再補個 patch 吧
.

VCS installation script 不認識 e1000g 網路卡

Discovering NICs on node1 .................................discovered e1000g0 e1000g1 e1000g2 e1000g3 e1000g4 e1000g5

Enter the NIC for the first private heartbeat link on node1: [b,?] e1000g1
e1000g1 is not a valid NIC name
Enter the NIC for the first private heartbeat link on node1: [b,?] e1000g1
e1000g1 is not a valid NIC name

好吧,只好安裝完在自己手動設定 heartbeat 了
修改 /etc/llttab 自己手動加上
link e1000g1 /dev/e1000g:1 - ether - -


2008.04.15 補
Veritas Cluster Server 5.0+e805061 fix for the e1000g NICs on Solaris
http://support.veritas.com/docs/301904


VCS with Solaris 8 Zone

畢竟 Solaris 8 zone in Solaris 10 (S8MA) 這玩意兒出來的 VCS Zone support 晚,所以目前 VCS 文件中寫到的 zone,並沒有特別說明是哪種 zone。
現在看來,當然指的都是 Solaris 10 native zone

由文件中看來,zone agent 對 local zone 的動作很單純,online 就是 zoneadm boot,offline 就是 zoneadm halt,對 Solaris 8 Zone 的 online/offline 應該沒什麼問題,但是其他要進去 local zone monitor 的 agent 呢?

在安裝 VCS 或建立 Solaris 10 native zone 時
有部份 VRTS 檔案是會自動從 global zone 複製到 native zone 的
就像 pkgadd or patchadd 時,若不加 -G 參數(Global only)
預設是會 apply 到所有的 running native zone
這兒我看來最重要的是那些 VCS agent 了
因為 global/local zone 都是 solaris 10 沒問題
但在 Solaris 8 zone 就有問題了...

check engin_A.log :
2008/01/13 18:56:16 VCS INFO V-16-2-13001 (node-2) Resource(ora8): Output of the completed operation (online) sh: /opt/VRTSvcs/bin/Oracle/online: not found
2008/01/13 19:33:35 VCS INFO V-16-2-13001 (node-2) Resource(ora8): Output of the completed operation (offline) sh: /opt/VRTSvcs/bin/Oracle/offline: not found

為什麼 not found ?原來是去用 local zone 中的 agent 了
因為不是 native zone,所以安裝時(pkgadd)不會複製這些檔案
導致 agent 無法正確的 monitor zone 中的 AP
我的偷吃步就是看有哪些 VRTS 檔案會被安裝到 native zone 中
就照樣複製這些檔案到 Solaris 8 zone 中

還有另一個問題
VCS WARNING V-16-1-52529 Login Incorrect, Invalid username/password
Agnet 在 global/local zone 中怎麼溝通?這兒需要設定一個 cluster user 讓他有 Group Administor 權限就ok了

在 native zone 中沒有這些問題,安裝時都會自動設好
但在 p2v zone 中,我們只好手動來把這些設定做完了

ok! It works !!

參考文件:
Veritas Cluster White Paper
Implementing Solaris™ Zones with Veritas™ Cluster Server
by Symantec
July 2006
Eric Hennessey
Group Technical Product Manager
Unix Clustering Solutions

VxVM DMP Tunning

All DMP 5.0 tuning can be done online as long as all tuning is performed using the vxdmpadm set-tune command. The set of tunables that can be configured online in DMP 5.0 MP1 are:

# vxdmpadm gettune all
Tunable Current Value Default Value
------------------------------ -------------
dmp_failed_io_threshold 57600 57600
dmp_retry_count 5 5
dmp_pathswitch_blks_shift 11 11
dmp_queue_depth 32 32
dmp_cache_open on on
dmp_daemon_count 10 10
dmp_scsi_timeout 30 30
dmp_delayq_interval 15 15
dmp_path_age 300 300
dmp_stat_interval 1 1
dmp_health_time 60 60
dmp_probe_idle_lun on on
dmp_log_level 1 1
dmp_retry_timeout 0 0
dmp_fast_recovery on on

參考文件:
Veritas Storage Foundation™ 5.0 Dynamic Multi-pathing
Optimizing Availability and Performance in Multi-Vendor Environments
May 2007

Verify the NBU 6.0 daemons / services are up and running

The bpps command in NetBackup 6.0 to see shared Veritas processes
# /usr/openv/netbackup/bin/bpps -x
On Netbackup Master Server:
http://support.veritas.com/docs/281789

The following is a listing of the services that need to be running on a NetBackup 6.0 master server:
  • Adaptive Server Anywhere - VERITAS_NB - ASA Database service (NB_dbsrv)
  • Netbackup Client Service (bpcd)
  • NetBackup Compatibility Service (bpcompatd)
  • NetBackup Database Manager (bpdbm)
  • NetBackup Device Manager (ltid)
  • Netbackup Enterprise Media Manager (nbemm)
  • NetBackup Job Manager (nbjm)
  • NetBackup Notification Service (nbnos)
  • Netbackup Policy Execution Manager (nbpem)
  • Netbackup Request Manager (bprd)
  • NetBackup Resource Broker (nbrb)
  • NetBackup Service Layer (nbsl)
  • NetBackup Service Monitor (nbsvcmon)
  • Netbackup Volume Manager (vmd)
  • Veritas Private Branch Exchange (pbx_exchange)

On Netbackup Media Server:

http://support.veritas.com/docs/282159

The following is a listing of the services / daemons which should be running by default on a NetBackup 6.0 media server:
  • Netbackup Client Service (bpcd)
  • NetBackup Compatibility Service (bpcompatd)
  • NetBackup Device Manager (ltid)
  • NetBackup Notification Service (nbnos)
  • NetBackup Service Layer (nbsl)
  • NetBackup Service Monitor (nbsvcmon)
  • Netbackup Volume Manager (vmd)
  • Veritas Private Branch Exchange (pbx_exchange)

On Netbackup Client:

http://support.veritas.com/docs/282162

There are no additional daemons or services that run on a NetBackup 6.0 client. Checking to see if the client software is running is similar to NetBackup 5.x and earlier versions. It is only necessary to check for the existence of the NetBackup Client Service (bpcd).

The NetBackup client software registers itself with inetd or xinetd on UNIX or Linux clients. The "netstat -a" command can be used to verify these daemons are in LISTEN status, indicating they are listening for incoming connections.

# netstat -a | grep bpcd
# netstat -a | grep bpjava-msvc
# netstat -a | grep vnetd
# netstat -a | grep vopied