今日喝茶

老妖擾亂國政，衙上妖氣衝天，五犬亂堂。

可以確定必有奇禍。

無聊時的自言自語。

Solaris 11: name services change

Everything moves to SMF-based now:


root@solaris:~# grep nameserver /etc/resolv.conf
nameserver 8.8.8.8
nameserver 202.188.0.133
root@solaris:~#
root@solaris:~# svccfg
svc:> select client
Pattern 'client' matches multiple instances:
svc:/network/smb/client
svc:/network/nfs/client
svc:/network/nis/client
svc:/network/ldap/client
svc:/network/dns/client
svc:>
svc:> select dns/client
svc:/network/dns/client>
svc:/network/dns/client> listprop config
config application
config/value_authorization astring solaris.smf.value.name-service.dns.client
config/search astring "fms.com" "fujitsu.com" "oracle.com" "com"
config/searchss astring "fms.com" "fujitsu.com" "oracle.com" "com"
config/nameserver net_address 8.8.8.8 202.188.0.133
svc:/network/dns/client>
svc:/network/dns/client> setprop config/nameserver=astring:("8.8.8.8" "202.188.0.133" "192.168.1.1")
svc:/network/dns/client>
svc:/network/dns/client>
svc:/network/dns/client> listprop config
config application
config/value_authorization astring solaris.smf.value.name-service.dns.client
config/search astring "fms.com" "fujitsu.com" "oracle.com" "com"
config/searchss astring "fms.com" "fujitsu.com" "oracle.com" "com"
config/nameserver astring "8.8.8.8" "202.188.0.133" "192.168.1.1"
svc:/network/dns/client>
svc:/network/dns/client> refresh
Instance not selected.
svc:/network/dns/client> select dns/client:default
svc:/network/dns/client:default> refresh
svc:/network/dns/client:default> exit
root@solaris:~# grep nameserver /etc/resolv.conf
nameserver 8.8.8.8
nameserver 202.188.0.133
nameserver 192.168.1.1

Backup Battery for Storage Array

We have one case which we see how important it is for battery to function to maintain performance. Without backup battery, the storage controller will function in write through mode, this seriously impact the storage performance as can be seen in customer's system.

The performance is 3 times slower than write back mode. Though it is possible to still run in write back mode without backup battery, the system risk losing data in case of power outage.

All problem gone when we replaced the battery.

:)

Finally get it virtualized

This tough nut finally get cracked. The VM is up and running. , NT Backup, VMware Converter and Symantec BMR all failed to convert this machine. Finally using Acronis to solve it. Well this is another good experience to have.

This is really painfull

Good Deed

Doing good deed is sometimes a difficult thing. But a lot of good deed can be done without difficulty - be it physically or mentally. There's too many examples and here's some websites that's dedicated to good deed:

http://www.thegooddeedsorganisation.com
http://www.doagooddeed.com/

Yes, i know, it is not easy at all at certain time. For example, just imagine having to rescue someone from a burning house going to collapse at any time. Providing tuition at no cost to some poor children on long term basis can be both very taxing and time consuming.
I am thinking how to set up something that can promote good deeds, at least within a small community as a first step.

Problem with P2V

This is a tough nut. But it is not entirely my problem.
It's a old Compaq Proliant ML370 G3 server, running Windows 2000. The hardware raid controller is Smart Array 532. The P2V using VMware Converter failed at 97%, just about time i were ready to tell customer to celebrate. Backup using Symantec BMR also failed, it was unable to run discovery job. The error is status -1, the hardware controller's driver was unable to be determined.
Symantec advised me to re-install the driver, which customer is very uncomfortable to do so.
I still have to spend quite some effort it seems.