ent0, en0 和 et0的差異

ent0:

The notation ent0 is used to specify the hardware adapter. It has nothing to do with the TCP/IP address. The parameters associated with ent0 can be seen as below:

# lsattr -El ent0

It will show parameters related to card.

It shows adapter_names, alt_addr, auto_recovery, backup_adapter, hash_mode, mode, netaddr, noloss_failover, num_retries, retry_time, use_alt_addr, use_jumbo_frame.

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

en0:

en0 represents the interface associated with hardware adapter ent0. The notation en0 is used for Standard Ethernet(inet). The TCP/IP address is associated with this interface.

The parameters associated with en0 can be seen as below:

#lsattr -El en0

It shows all the parameters related with the interface en0 of the adapter ent0.

It shows alias4, alias6, arp, authority, broadcast=1500, mtu, netaddr, netaddr6, netmask, prefixlen, remmtu, rfc1323, security, state, tcp_mssdflt, tcp_nodelay, tcp_recvspace, tcp_sendspace.

Rest everything is same except mtu(Maximum Transfer Unit) value. Which is 1500 as per the standard ethernet protocol.

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

et0:

et0 represents the interface associated with hardware adapter ent0. The notation et0 is used for IEEE 802.3 Ethernet(inet). If you are using standard ethernet protocol then it will not have TCP/IP address.

The parameters associated with et0 can be seen as below:

#lsattr -El et0

It shows all the parameters related with the interface et0 of the adapter ent0.

It shows alias4, alias6, arp, authority, broadcast, mtu=1492, netaddr, netaddr6, netmask, prefixlen, remmtu, rfc1323, security, state, tcp_mssdflt, tcp_nodelay, tcp_recvspace, tcp_sendspace.

Note here as well that the MTU shown will be 1492 as per IEEE 802.3 standard. Rest all parameters will be same. Also, netaddr, netmask fields will be empty fr et0.

EXP510, DS4800, SAN, Switch, Power720接線圖和開、關機順序

1. 開機順序

          SAN Switch or Switch -> EXP510 -> DS4800(註1) -> HMC -> Power720

          註1：查詢DS4800的IP Address

1. 接妥console線, 查詢通用序列匯流排號碼
2. 開啟putty連結時透過 Ctrl + Break 按鍵進行正確字元的切換, 當出現正確的字元時, 再按 Esc 按鍵
3. login/password: shellUsr / w3oo&w4
4. 輸入 netCfgSet




1. 關機順序

   LPAR -> Power720 -> HMC -> DS4800 -> EXP510 -> SAN Switch or Switch

接線圖

vCenter Site Recovery Manager

• 以一個site為單位, 每一個site一定要有一個vCenter和一個SRM
• VR
• • 是透過網路的方式進行檔案複寫(file-level), 但其實傳輸的時候也是用block-level的方式進行傳送, RPO(採用非同步)=15min~24hr
  • 非同步的方式進行傳輸
  • 關於state的部分, 若guest os是windows os(Windows 2003版本以上), vmware tools會呼叫VSS的機制儲存, linux則無
  • plan migration會先將guest os先shutdown, 確保state可以寫回硬碟.
  • 只會拷貝開機狀態的Guest OS的檔案.
  • 若Protected端有做snapshot時, 複製到recovery端的時候會被合併
  • 被管理的IP要指向vCenter Server
  • 第一次會用完全的複寫方式到Recovery端, 複寫的過程不會做壓縮也不會做加密, 之後的複寫都是用ESXi內建的CBT(Change Block Tracking)的方式做複寫.
• Array-based
• • 會透過LUN(block-level)的方式進行複寫
  • 同步/非同步的方式傳輸(遠端的方式可能無法用同步的方式)
  • SRA的版本最好是要一樣, 且Storage也最好是相同的廠牌
• SRM5.1(只負責控制)到另一個site是可以透過Recovery plan(這個是可以自行定義的)自行定義啟動的優先順序
• • 不需要設定為Linked mode
  • SRM API是採用SOAP的方式, 也就是用XML語法的方式作為與其他平台做資料交換
  • 可以安裝在虛擬機器上
  • 需安裝在Windows 64bit的作業系統上
  • 若是走Storage Array的方式, 儲存設備廠商必須提供SRA(storage replication adapters)
  • support DB2、SQL Server、Oracle
  • 沒有support Storage vMotion和Storage DRS
• SRM5.5新功能
• • 支援Storage vMotion
  • 可保留VM的前24個複寫狀態
  • 支援Flash cache(SSD)
• Vmotion Latency need <= 5ms 的網路品質, 來源端和目的端的Port group需一樣
• Metro Vmotion Latency need <= 10ms 的網路品質
• placeholder：virtual machine的快照和設定
• VMkernel無法對應, 只能對應Port group
• Network Port group若更改名稱的話, 必須重新建立
• Protection Group：一群需要從Protection site端切換到Recovery site端的Guest OS
• • 建立完成之後會放在未來的Recovery Plan(自動化災難移轉)去做應用
• Recovery plan
• 是建立在Recovery Site的
• 還原時可以被定義是連接哪一個網路, 以避免與正式環境起衝突; 可透過一個dr-ip-customizer.exe小工具進行大量修改IP
• 可以修改開機順序, Power on之後馬上就會接下一個群組, 無法設定開機後delay多久才開啟第二個群組, 只能設定dependencies
• 每個Guest OS要確保都已安裝VMware Tools
• 只要Guest OS是Microsoft OS(windows2000, 2003, xp)的環境, 建議安裝User Profile Hive Cleanup Services以加速關機作業

DB2 user space 調整

Administrator
ITM@Admin


至DB2 GUI控制中心 -> 右鍵要增加容量的DB
管理儲存體 -> 新增自動儲存體 -> 增加位置 

db2 connect to database_name

db2 alter database add storage on 'd:\'

db2 connect reset

db2 connect to database_name 

db2 ALTER TABLESPACE tablespace_name REBALANCE

ITM CEC Base agent issue

ITM CEC Base agent重啟後，ITM無法顯示CEC的數據，解決步驟如下：

STEPS TO RECYCLE THE SHARED MEMORY:
1. Stop all the processes which use the SPMI shared library
(xmservd,filtd, xmperf, 3dmon, ptxrlog, harmd, topas, any PSSP process)
if they are currently running your AIX LPAR. 

2. Stop the ITM system P agents (PX, PK, PH) that you have running on
this system. 

3. To find if any zombie processes are running on your machine.
a. Run
# ps -ef | grep Provider
Kill each one of them "kill <pid> 

b. Run
ps -ef | grep kpkagent
ps -ef | grep kpxagent
ps -ef | grep kphagent
Kill each one of them "kill <pid>" 

c. Check if there are any defunct processes
"ps -ef | grep defunct" 

4. Kill the processes that are using the shared memory. 
genld -l | grep -p Spmi 

5. Run "ipcs -m" command and check for any segment "KEY" that begins
with '0x78', as listed below:
T ID KEY
m 0 0xc76283cc
m 1 0x78002323
If there are any such segments starting with 0x78, make sure the process
which uses those shared segments is stopped (or terminate it with kill
command) 

6. Then run: "ipcrm -m <ID #>" to clear the shared memory segments. 

7. Run "slibclean"

8. Restart system P agents - PH PX PK