Hudson's Blog

贴片电阻你会换吗？你会用温式尖头烙铁吗?

2011-11-17T13:45:00.001+10:30

贴片式元器件的拆卸、焊接宜选用200～280℃调温式尖头烙铁。

贴片式电阻器、电容器的基片大多采用陶瓷材料制作，这种材料受碰撞易破裂，因此在拆卸、焊接时应掌握控温、预热、轻触等技巧。控温是指焊接温度应控制在200～250℃左右。预热指将待焊接的元件先放在100℃左右的环境里预热1～2分钟，防止元件突然受热膨胀损坏。轻触是指操作时烙铁头应先对印制板的焊点或导带加热，尽量不要碰到元件。另外还要控制每次焊接时间在3秒钟左右，焊接完毕后让电路板在常温下自然冷却。以上方法和技巧同样适用于贴片式晶体二、三极管的焊接。

贴片式集成电路的引脚数量多、间距窄、硬度小，如果焊接温度不当，极易造成引脚焊锡短路、虚焊或印制线路铜箔脱离印制板等故障。拆卸贴片式集成电路时，可将调温烙铁温度调至260℃左右，用烙铁头配合吸锡器将集成电路引脚焊锡全部吸除后，用尖嘴镊子轻轻插入集成电路底部，一边用烙铁加热，一边用镊子逐个轻轻提起集成电路引脚，使集成电路引脚逐渐与印制板脱离。用镊子提起集成电路时一定要随烙铁加热的部位同步进行，防止操之过急将线路板损坏。

换入新集成电路前要将原集成电路留下的焊锡全部清除，保证焊盘的平整清洁。然后将待焊集成电路引脚用细砂纸打磨清洁，均匀搪锡，再将待焊集成电路脚位对准印制板相应焊点，焊接时用手轻压在集成电路表面，防止集成电路移动，另一只手操作电烙铁蘸适量焊锡将集成电路四角的引脚与线路板焊接固定后，再次检查确认集成电路型号与方向，正确后正式焊接，将烙铁温度调节在250℃左右，一只手持烙铁给集成电路引脚加热，另一只手将焊锡丝送往加热引脚焊接，直至全部引脚加热焊接完毕，最后仔细检查和排除引脚短路和虚焊，待焊点自然冷却后，用毛刷蘸无水酒精再次清洁线路板和焊点，防止遗留焊渣。

检修模块电路板故障前，宜先用毛刷蘸无水酒精清理印制板，清除板上灰尘、焊渣等杂物，并观察原电路板是否存在虚焊或焊渣短路等现象，以及早发现故障点，节省检修时间。

如何替换场效应管

注意事项：
结型场效应管的栅源电压不能接反，可以在开路状态下保存，而绝缘栅型场效应管在不使用时，由于它的输入电阻非常高，须将各电极短路，以免外电场作用而使管子损坏。

焊接时，电烙铁外壳必须装有外接地线，以防止由于电烙铁带电而损坏管子。对于少量焊接，也可以将电烙铁烧热后拔下插头或切断电源后焊接。特别在焊接绝缘栅场效应管时，要按源极－漏极－栅极的先后顺序焊接，并且要断电焊接。

用 25W 电烙铁焊接时应迅速，若用 45～75W 电烙铁焊接，应用镊子夹住管脚根部以帮助散热。
结型场效应管可用表电阻档定性地检查管子的质量（检查各 PN 结的正反向电阻及漏源之间的电阻值），而绝缘栅场效管不能用万用表检查，必须用测试仪，而且要在接入测试仪后才能去掉各电极短路线。取下时，则应先短路再取下，关键在于避免栅极悬空。

在要求输入阻抗较高的场合使用时，必须采取防潮措施，以免由于温度影响使场效应管的输入电阻降低。
如果用四引线的场效应管，其衬底引线应接地。

Windows 2008 MPIO commands

2011-11-10T15:10:00.003+10:30

#List the disks that are currently claimed by MPIO

C:\Windows\system32>mpclaim -s -d

For more information about a particular disk, use 'mpclaim -s -d #' where # is
he MPIO disk number.

MPIO Disk System Disk LB Policy DSM Name
-------------------------------------------------------------------------------
MPIO Disk21 Disk 22 RR Microsoft DSM
MPIO Disk20 Disk 21 RR Microsoft DSM
MPIO Disk19 Disk 20 RR Microsoft DSM
MPIO Disk18 Disk 19 RR Microsoft DSM
MPIO Disk17 Disk 18 RR Microsoft DSM
MPIO Disk16 Disk 17 RR Microsoft DSM
MPIO Disk15 Disk 16 RR Microsoft DSM
MPIO Disk14 Disk 15 RR Microsoft DSM
MPIO Disk13 Disk 14 RR Microsoft DSM
MPIO Disk12 Disk 13 RR Microsoft DSM
MPIO Disk11 Disk 12 RR Microsoft DSM
MPIO Disk10 Disk 11 RR Microsoft DSM
MPIO Disk9 Disk 10 RR Microsoft DSM
MPIO Disk8 Disk 9 RR Microsoft DSM
MPIO Disk7 Disk 8 RR Microsoft DSM
MPIO Disk6 Disk 7 RR Microsoft DSM
MPIO Disk5 Disk 6 RR Microsoft DSM
MPIO Disk4 Disk 5 RR Microsoft DSM
MPIO Disk3 Disk 4 RR Microsoft DSM
MPIO Disk2 Disk 3 RR Microsoft DSM
MPIO Disk1 Disk 2 RR Microsoft DSM
MPIO Disk0 Disk 1 RR Microsoft DSM

#More information about a particular disk

C:\Windows\system32>mpclaim -s -d 21

MPIO Disk21: 02 Paths, Round Robin, ALUA Not Supported
Controlling DSM: Microsoft DSM
SN: 6064800290102093533031343830
Supported Load Balance Policies: FOO RR RRWS LQD WP LB

Path ID State SCSI Address Weight
---------------------------------------------------------------------------
0000000077030000 Active/Optimized 003|000|000|017 0
0000000077050000 Active/Optimized 005|000|000|017 0

rename files under DOS and Windows

2011-09-18T21:32:00.001+09:30

for /f %i in (sub.bat) do @echo ren "%i" "[xxxx].{original name}.bat

## del the Windows moutn point manually.

mountvol | find "VS6" > 1.list

for /f %i in (1.list) do @echo mountvol %i /d >> 1.bat

iMac G3 issues

2011-09-16T10:31:00.004+09:30

Some valuable recommandation from the internet,

http://68kmla.org/forums/viewtopic.php?f=13&t=16106

#
1.) Check the P-RAM battery. Voltage must be at 3.67V up to 3.8V at maximum. If not, replace the battery and don't forget to press the PMU reset button once for about a second.

2.) One thing to keep in mind is that all models of iMac G3s across the board will suffer (or have suffered) the death of their P.A.V. (Power Analog Video) Board. When this happens, successful power up or normal startup is one-in-a-million to nill. In your case, the symptoms you describe warrant the need to check if it's bad. In more severe cases, you will hear a single zap or click, followed by the power button turning either orange or lighting up for a second and shutting off. You'll need to match part for part, when it comes to PAV Boards. Apple had 2 different part numbers for this part: one with a toggle switch and one without. This was due to Apple using 2 different companies making CRTs: LG and CPT.

3.) Check the Down Convertor board, attached to the logic board. Sometimes these go bad and throw off the rest of the iMac.

Here is a link for where to get the service manual and tear-down procedures. They should cover Rev. A through Rev. C and D (iMac G3 Summer 2001). You can also go to http://www.ifixit.com and they post take apart steps for these iMacs as well, but may not go as far as access to the PAV Board and CRT.

So, go grab a multimeter and start narrowing down where your trouble is. Use the Troubleshooting section within the service manuals in the first link to help navigate what to test and where. Let us know what you find. We'll be here to help.

#

With G3 imac series, the main failure is with the PAV board (often the Flyback transformer is the culprit)

If the two units are of the same type (ie tray or slot loading) you can try swaping logic boards.

The message is a kernel panic, can be hard or soft issue.

try swaping ram, i had a lot of issues with sticks on G3 Imacs.(you will probably get an unusual chime, but this is not always the case)

Concerning the P-RAM battery, you can have a try without, and press the reset (only once)anyway.

Never had any issue with Down Convertor Board, but swaping boards is a logical path, and the easy one... the PAV board is hard to reach.

#
A couple of things I forgot to mention regarding logic boards. If you have a Rev. A through Rev. D G3 iMac logic board, theoretically you can mix and match the boards. For example, a Rev. D board could be installed in a Rev. A model, boosting the speed by 50 to 100 Mhz. Somebody correct me if that is accurate. The slot loading G3 iMacs (350 to 700 Mhz) I'm 100 percent sure they can be mix and matched. But make sure the models you are swapping logic boards out of use the same P.A.V. board.

https://discussions.apple.com/thread/887247?start=0&tstart=0

Well I've worked on about 50 of these iMacs, trays and slots, and have only seen 1 bad logic board and no bad down converters. It's most often the PAV board that goes bad and most often the flyback transformer. If it's a newer model that has the VGA output (under the elongated oval perforated grill that you can snap out) you can plug an external monitor into that to see if you have video out off the logic board.

For conversion to ATX see:
http://www.hardmac.com/articles/39/page3
http://www.cryogenius.com/hardware/imac/
http://www.ct-scan.com/iMacATX/
I like this one LCD and all in the original iMac case.
http://www.macmod.com/content/view/414/193/

TFTP软件升级ADSL Modem

2011-07-14T15:18:00.000+09:30

使用TFTP软件升级

　　一般ADSL Modem厂商都会随产品将Firmware升级软件一起搭售，该工具程序可让你采用局域网络接ADSL路由器的方式，在远端下载Firmware软件程序的最新版本。但是，不同的厂商会有不同的升级软件。我们这个TD-2001 ADSL Modem采用的是一个tftputil.exe的工具程序，专用于升级ADSL Modem的Firmware，它在ADSL路由器软盘中。可以直接在软盘上执行tftputil.exe，或将其拷贝到微机的硬盘中执行。而 Firmware的最新版本，则可以在该公司的网站上下载。

　　在准备好tftputil.exe和最新的ADSL Modem的Firmware，并保证ADSL Modem和计算机正常连接后，我们就可以进行升级工作了，其步骤是：

　　1.在Windows界面运行tftputil.exe，如图1所示。按照提示，输入Password(原厂密码默认为12345)、ADSL路由器的LAN IP address (局域网络IP地址，原厂默认为192.168.1.1，MASK 255.255.0.0)。

　　2.在“FIRMWARE UPGRADE”中，选中“Image/Pack File(图形/压缩文件)”，通过浏览按钮，把最新的Firmware文件选上。

　　3.再点“Download(下载)”，系统就会自动把新的Firmware写入ADSL Modem中。如果顺利的话，会出现如图2所示的信息。

图1升级应用程序

　　等到Modem重新启动之后，你就可以更稳定、更快速地上网了。

　　从损毁的Firmware文件中恢复

　　如果在升级TFTP软件时断电的话，可能会使Firmware损毁。我们还可以使用ADSL路由器提供的损毁恢复功能，以复原损毁的Firmware。

　　首先，将ADSL Modem的RS-232端口接入个人计算机上的串口上，在终端仿真程序中(如Windows自带的超级终端)将串口通讯参数设定如下：

　　VT100终端仿真

　　波特率：9600

　　校验位：None

　　数据位：8

　　停止位：1

　　流量控制：None

　　然后，进入超级终端的CONSOLE模式。此时CONSOLE会出现一些讯息。

　　我们现在就可以按照下面的步骤来恢复Firmware了。

　　1.输入指令启动xmodem。

　　　] xmodem fast

　　2.将串口的波特率设定为38400。选择“file/properties”(文件/属性)→“Configure”(设定)，然后将“bit per second”(每秒比特)更改为38400。

图2顺利升级

　　3.点选“Transfer/Send File”(传输/发送文件)，输入“FIRMWARE”的路径和文件名，然后选择“Xmodem”，再点选“Send”(发送)，如图3所示。

　　4.依照步骤2，将波特率改回默认值9600。

　　5.输入“quit”(退出)指令，关闭主控屏幕。

　　6.在提示符号后，输入“flashfs”和“update”。

　　7.将电源变压器拔开之后再插上，重新启动ADSL路由器。

图3恢复Firmware

　　8.按下Enter键，此时CONSOLE会要求你输入Password(密码)。输入Password后，Firmware已经全部恢复，就可以退出超级终端了。

http://www.chinadsl.net/thread-16841-1-1.html

AWK tips

2011-03-29T16:00:00.001+10:30

if (condition) then-body [else else-body]

Eg,
awk '{ if (x % 2 == 0) print "x is even"; else
       print "x is odd" }'

http://people.cs.uu.nl/piet/docs/nawk/nawk_71.html

Alcatel SpeedTouch ST716v5

2011-03-27T14:11:00.001+10:30

Firmware:
http://www.technicolorgateways.nl/software.html

http://download.modem-help.co.uk/mfcs-A/Alcatel/Modems/SpeedTouch-716/v5/Firmware/

Use the apt-cache

2010-12-10T11:29:00.001+10:30

# If the package hasn't being installed.

apt-cache show ov51x-jpeg-source
Package: ov51x-jpeg-source
Priority: extra
Section: universe/graphics
Installed-Size: 120
Maintainer: Ubuntu MOTU Developers
Original-Maintainer: Romain Beauxis
Architecture: all
Source: ov51x-jpeg
Version: 1.5.9-1
Depends: module-assistant, debhelper (>= 5), make, bzip2
Filename: pool/universe/o/ov51x-jpeg/ov51x-jpeg-source_1.5.9-1_all.deb
Size: 82236
MD5sum: 609444e136080a606e424413b6d4a41d
SHA1: f6eeceacb3d9510093fdb85fc842a94e05412cb7
SHA256: 1769e5a185d12acb6e0273cd52687af632a05fab977baa6ec7d66cac79926865
Description: Source for the ov51x-jpeg driver
This package provides the source code for the ov51x-jpeg kernel modules.
.
This driver works with webcams that use an ov511, ov518 and ov519 chip.
This includes the Eye Toy, the Hercules Webcam Classic, some SpaceCam 320
and many others. Contrary to the original driver, this driver has in place
JPEG decompression which make the ov519 cameras work as required.
.
This package allows you to compile your own modules for this driver.
Homepage: http://www.rastageeks.org/ov51x-jpeg/
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu

Issues with my proxy settings in Ubuntu

2010-12-10T11:19:00.001+10:30

to set up Synaptic:
http://ubuntuforums.org/archive/index.php/t-1575.html
fill the fields with something like
user name:passw@host
(no http:// in front, no :8080 at the end)
then fill the port field with the correct prot number (8080, in my case)

to set up apt-get:
http://ubuntuforums.org/showpost.php...postcount=1006

sudo gedit /etc/apt/apt.conf

add the following:

ACQUIRE {
http::proxy "http://user name:passw@host:port/"
}

## for Windows Domain user, user domain\username, you don't need \\ between the domain and user.

to set up wget:
sudo gedit /etc/wgetrc

uncomment the line with the http_proxy like this:

# You can set the default proxies for Wget to use for http and ftp.
# They will override the value in the environment.
http_proxy = http://proxy.yoyodyne.com:18023/
#ftp_proxy = http://proxy.yoyodyne.com:18023/
# If you do not want to use proxy at all, set this to off.
use_proxy = on

NetApp ONTAP Simulator and ESX Server

2010-12-02T14:53:00.002+10:30

http://blog.scottlowe.org/2006/06/27/netapp-ontap-simulator-and-esx-server/

I found the document from above Blog, the guy enabled the promiscuous mode via command,

echo PromiscuousAllowed yes > /proc/vmware/net/vmnic0/config

Replace “vmnic0″ in this command with whatever virtual switch or NIC team the virtual machine in question is using.

But, I was using the ESXi server, so you need go to the VMware network configuration and change the VM switch accept the promiscuous mode.

固体电容代换电解电容的原则

2010-11-15T10:37:00.003+10:30

目前大多数影音及计算机产品中配置以下几组电压12V、5V、3.3V、2.5V、 1.8V、及1.8V以下.首先我们强调一下5V电源在板卡的数字电路系统中主要负责各类输入输出接口的供电，其分布范围是比较少，电容的损坏率也相当低．所以,在正常情况下电脑板卡和以数字逻辑电路为主的电路板中,在小批量维修替换时10V的电解电容完全可以使用6.3V的电容替代.

耐压的选择:由于铝电解电容的误差较大,在耐压选取方面设计时会留有很大的余量例如:12V电源部分常用16V铝电解电容,5V电源常用 10V ，3.3V选用6.3V,3.3V以下选用6.3V或者4V(这种很少见)这是厂商选择的一般规律,我们在板卡上也会见到用在12V电源上的 25V铝电解电容,甚至在CPU 1.45V的滤波部分看到10V的电解电容.所以原铝电解电容耐压只做为参考,选用电容耐压的唯一的标准是电路的电压, 如果选用固体电容,只要电路电压低于固体电容耐压即可,不需要考虑余量(事实上电容设计者已经根据常用电源电压留好了余量)

容量的选择,电容容量的选择是根据电路中的电流(即功耗)来确定的,如CPU是主板中的耗电之王,在其周边我们就见到了密密麻麻的电解电容和高频瓷片电容,在显卡的GPU附近亦是如此.同样由于电解电容的误差大和老化后容量减小较大,在容量选择上也会留有很大的余量.固体电容容量几乎不会减小,不用考虑老化后容量减小的问题,再者ESR值明显优于铝电解电容,所以在容量选择上固体电容有很大的空间,根据经验一般可选择为铝电解容量的四分之一或者更大,当然这个值不是绝对的,略有偏差,无关要紧.

大家对电解电容比较熟悉,对于电容的认识往往只记得容量及耐压值,没错，但忘却了关于电容品质的决定性因素[电容的材质]，当替换选择电解电容时，在体积允许的情况下,按照与原使用型号的容量耐压贴近的，高压替换低压，高容量替换低容量，都是正确的认识,但在固体电容的选择上，是不能按照这样传统的替换概念的，由于材料及工艺不同,在同等耐压及容量情况下,电解电容和固体电容对比,固体电容的体积要大出电解电容一倍以上.由于固体电容材料价格较铝电解电容的材料价格贵出很多,越大的越贵,固体已经很贵啦,没有必要做得那么大.更重要的是由于固体电容优秀的性能决定了小容量即可胜任更恶劣工作环境,

纯固态材料决定了其寿命更长,误差更小,其出厂时的参数在连续工作数万小时后,仍可维持不变.但铝电解电容在工作两千小时后,电解液将慢慢出现干涸现象, 容量变小,随着时间推移,电路系统将变得不稳定,如运行变慢死机等等固体电容强调的是低ESR，高温时性能不变.所以更换固体电容，大家不要老觉得容量够不够啦，电压会不会太低啊这些概念性的错误.

下面给家例举一些比拟常用的电解换固体的比例值：

1.CPU供电类电容，此位置普通原来均是6.3V-10的电解（用到10V的电解普通都是些耐压不达标，容量不合格的劣质产品来替代6.3V的，这些就不用太在意耐压了，普通都是用6.3V的电解，改换固体，我们就能够依据CPU的实践电压来改换，就这个道理，估量至今没哪个兄弟的CPU电压曾经超频到了4V以上的，所以2.5V的固体电容曾经完整够了，更何况2.5V的固体实践耐压到达了3.5普遍的，这就是高耐压的表现）

2200UF/6.3V-3300UF/6.3V 电解交换固体电容 1200UF/4V 1500UF/2.5V 固体
1500UF/6.3V 电解交换固体电容 820UF/6.3V/4V/2.5V

2.CPU滤波类

1500UF/16V-2200UF/16V 电解交换固体电容 16V330UF （此处大家常常被原来电解的高容量所迷惑，问的最多的是容量够不够，呵呵，其实大可放心，之前说过，固体的材质是半导体，不是电解类的东西，容量比值大致参照下1：3－3.5之间就能够了）

3.最常用的1000UF/6.3，普遍散布与内存插槽，AGP插槽，PCI插槽，此类电解换固体：560UF/4V 470UF/6V

4.另外一些常用的，470UF/16V 电解换固体 180UF/16v 220uf/10v电解换固体180UF/16V

以上就根本掩盖了比拟常用的主板电解类的换固体的计划，主要目的是通知大家，固体改换电解一定要修正的概念，第1：要留意实践电容位置的电压，第2：不要过火的强调容量来交换电解

当然在以上的交换准绳之中还要优先选择批次比拟好的型号，就是电容的分类啦，呵呵，给大家个规律～

*******************

(1)用于滤波电路的电解电容，一般来讲只要耐压、耐温相同，稍大容量的电容可代稍小的，但有些电路电容值差不可太悬殊。比如交流市电整流滤波电容，原机为21英寸时，采用100UF/400V电解电容滤波，不宜用470UF/400V代用，因为电容容量太大时会造成开机瞬间对整流桥堆等件的冲击电流过大，造成元件损坏。

(2)起定时作用的电容要尽量用原值代用。若容量小，就采用并联方法解决，容量大时，串联解决。

(3)代用电容在耐压，温度系数方面不能低于原电容。

(4)应急维修时可用质量可靠的有极性电解电容等值替代钽电容。

(5)不能用有极性电解电容取代无极性电解电容。当无极性电解电容较小时，可用其他无极性电容代换。

(6)行逆程电容若损坏，可在容量方面灵活掌握，只要保证代换后逆程电容的总容量与原总容量等值就行。

自己动手拯救电源!滤波电容更换实战!

2010-11-11T20:31:00.010+10:30

http://diy.pconline.com.cn/other/study_others/0504/601752.html

爱机这些天频繁重启，经过替换检查确定是电源问题。看来，在岗位上坚持了大半年的电源终于“寿终正寝”了。拆开电源外壳，发现内部灰尘弥漫，故障多半由此发生。先用皮老虎和毛刷将灰尘清掉，露出了灰尘掩盖下的电子元件。

　　　故障分析

　　为了便于检修，我又拆掉了固定线路板的螺丝钉，将电源输出插头从线路板上拔掉后小心将线路板取出（如图1）。仔细检查每一个电子元件之后，发现其中一个高压滤波电容已经爆浆了。查阅资料得知，高压滤波电容是构成开关电源高压滤波电路的主要部件，其功能是交流电转直流电时过滤纹波。滤波电容的大小是和开关电源输出功率有着直接关系的，通常情况下优质电源多采用470μF滤波电容，而优质大功率电源采用的则可高达680μF。电源的功率越大，采用的滤波电容也越大。查看这个损坏的高压滤波电容，发现其电容容量仅为330μF，除了耐压值与容量之外没有任何厂商标识，显然这个电源中所采用的是滤波电容是劣质产品（如图2）！这个电源拿到维修部修复得花三十块钱维修费，实际上做的工作仅仅是更换电容，检测一下有无其他故障。为了节约资金，我决定亲自动手来更换电容，拯救电源。

图1 裸露的线路板

图2 损坏的滤波电容

　　更换电容实战

　　首先到电子商店买两个高压滤波电容，滤波电容的耐压值与容量应参考原有滤波电容（电脑开关电源中高压电容耐压值多为200V），当然为了保险起见，选择耐压值为250V的电容也无妨。高压电容还有一个耐温参数，开关电源中常用的多是85℃产品，一般购买85℃电容足够了，如果有105℃的电容更好。为了避免再次因电容容量过小不堪重负而造成损坏，我买了两个“200V 470μF”的85℃电容（如图3）。

图3 新购买的电容

　　接下来开始替换线路板上损坏的电容。将线路板翻转到背面，找到损坏电容对应的焊脚，将电烙铁加热后放到电容焊脚上，等待焊锡熔化。在拆卸电容时难度较大，加热左引脚时，将电容向右掰；加热右引脚时，将电容向左掰。反复数次，即可将电容从焊盆上取下。取下坏电容后用吸锡器清理一下空出的两个小洞（没有吸锡器可用注射器代替）。

　　取下坏电容后，将购买的电容按原有电容的极性位置安装到小洞中（电容短引脚为负极），翻到线路板的背面给电容的两个引脚上锡。焊接时也应注意电容的极性，千万不要焊错，否则一通电电容即会被击坏。焊好后的电容明显比边上的330μF电容高出一截（如图4）。接着依样画葫芦，将另一个电容也更换为470μF的电容。需要提醒各位的是更换电容时电容体积也是需要考虑的问题，在电子元件密集的线路板上电容体积过大将影响到安装。

图4 更换后的电容

　　替换电容之后，按开关电源工作的先后顺序依次检查了整流二极管、EMI滤波电路、开关三极管等元件，没有发现其他问题。检查保险管时发现保险丝熔断，更换后对电源进行空载加电测试，用万用表测量时证实其已经恢复正常。重新将其组装起来，一个濒临死亡的电源重又恢复了活力。

http://www.buynow.com.cn/portal.php?mod=view&aid=1292

二、电容器损坏后，原则上应使用与其类型相同、主要参数相同、外形尺寸相近的电容器来更换。但若找不到同类型电容器，也可用其它类型的电容器代换。纸介电容器损坏后，可用与其主要参数相同但性能更优的有机薄膜电容器或低频瓷介电容器代换。玻璃釉电容器或云母电容器损坏后，也可用与其主要参数相同的瓷介电容器代换。用于信号耦合、旁路的铝电解电容器损坏后，也可用与其主要参数相同但性能更优的钽电解电容器代换。电源滤波电容器和退耦电容器损坏后，可以用较其容量略大、耐压值与其相同（或高于原电容器耐压值）的同类型电容器更换。可以用耐压值较高的电容器代换容量相同，但耐压值低的电容器。

三、再来说说更换固体电容，大家不要老觉得容量够不够啦，电压会不会太低啊这些概念性的错误，说了一大堆,实战应用举例：

1. CPU供电类电容,此位置一般原来均是6.3V-10的电解电容,根据CPU的实际电压来更换，近五年生产的CPU核心电压已经没有高于2.5V的了,都在1.8V以下，用在CPU外围的6.3V 1500uF-6.3V 3300uF电解替换可使用固体电容 4V 1200uF, 4V 1500uF, 2.5V 1500uF, 4V 820uF及2.5V 820uF亦可胜任。

2. 6.3V1500uF-2200uF(直径8MM)电解用于3.3V或者3.3V以下电源部分,可用固体电容容量330-820uF耐压4V以上即可.如常见的4V560uF。

3. 12V电源16V1000uF--16V3300uF电解可用固体电容16V270uF 16V330uF（12V电源作为高电压不直接供给大电流的电路部分,故此处可选用之容量较小）。

4. 最常用的1000uF/6.3，广泛分布与内存插槽，AGP插槽，PCI插槽，此类电解换固体：耐压高于4V容量大于270uF即可,如: 4V 560uF, 4V 470uF。

5. 另外一些常用的，470uF/16V电解可用固体180uF/16v。

6. 更换10V耐压的电解电容请注意先确认电路电压,主板中存在5V电压,如为5V电压,请使用6.3V耐压固体代用。

以上就基本覆盖了比较常用的主板电解类的换固体的方案，主要目的是告诉大家，固体更换电解一定要修正的概念，
第1：要注意实际电容位置的电压，
第2: 替换时不要过份强调容量,固体优越的性能足以胜。

没有标志的贴片电容的更换
http://www.bokee.net/company/weblog_viewEntry/4844699.html
1.根据检修统计来看这类电容损坏的机率很小，以前本人在设计一款电源板时因为板子有点特殊，电容太靠近稳压管的散热部位，有过此类电容短路的现象。如果此类电容仅仅是些许漏电，用电容表量一下容量也不会相差到哪里去，找个相同容量和耐压（或耐压更高一点）的电容代上去好了。

2.如果电容实在是坏得一蹋糊涂，比如短路或开路，则可以分析一下该电容在电路中的作用来判别一下，如果是滤波（通常数字电路中每一个芯片旁都有一个这样的滤波电容，从 1000pF到10000pF的都有），在代换的时候，从1000pF到10000pF选取都没有关系的，甚至去掉不用也没有问题。

3.如果电容是做为震荡电路的一部分，比如应用在开关电源中的此类电容，通常这个电容是配合其它电阻决定一个振荡频率的，还少不了一个芯片，则我们可以下载这个芯片的 DATASHEET，DATASHEET中通常会给出外围元件参数的实例，参照这个实例代换电容也不会偏差到哪里去。

贴片电阻，一般都是下面是白色的上面是黑色的还标有102,104.223等数字的。

电感一般上面都标R22或R多少的。
电容吗。是什么上面都都没有的东西。
二极管一般都是圆柱型的。

怎么焊接贴片电容？

有镊子就好办啊，先清空焊盘，在一个焊盘上留点锡，烫化了，把电容推到位置，一头就OK了
没镊子你还是用胶水吧, 一般专门电装的人员直接用电烙铁沾起电容,放到焊盘上就OK了,熟练得很.


贴片式电容的作用

其作用主要是清除由芯片自身产生的各种高频信号对其他芯片的串扰，从而让各个芯片模块能够不受干扰的正常工作。
在高频电子振荡线路中，贴片式电容与晶体振荡器等元件一起组成振荡电路，给各种电路提供所需的时钟频率。

贴片式电容有贴片式陶瓷电容、贴片式钽电容、贴片式铝电解电容。

贴片式陶瓷电容无极性（如图3），容量也很小
（PF级），一般可以耐很高的温度和电压，常用于高频滤波。陶瓷电容看起来有点像贴片电阻（因此有时候我们也称
之为“贴片电容”），但贴片电容上没有代表容量大小的数字。

贴片式钽电容的特点是寿命长（如图4）、耐高温、准确度高、滤高频改波性能极好，不过容量较小、价格也比
铝电容贵，而且耐电压及电流能力相对较弱。它被应用于小容量的低频滤波电路中。

贴片钽电容与陶瓷电容相比，其表面均有电容容量和耐压标识，其表面颜色通常有黄色和黑色两种。譬如100-16即
表示容量100μF，耐压16V。

贴片式铝电解电容拥有比贴片式钽电容更大的容量，其多见于显卡上，容量在300μF~1500μF之间，其主要是满足
电流低频的滤波和稳压作用。

#直立电容和贴片电容的区别

无论是插件还是贴片式的安装工艺，电容本身都是直立于PCB的，根本的区别方式是贴片工艺安装的电容，有黑色的
橡胶底座。贴片式的好处主要在于生产方面，其自动化程度高，精度也高，在运输途中不像插件式那样容易受损。
但是贴片工艺安装需要波峰焊工艺处理，电容经过高温之后可能会影响性能，尤其是阴极采用电解液的电容，经过
高温后电解液可能会干枯。插件工艺的安装成本低，因此在同样成本下，电容本身的性能可以更好一些。

在性能方面，直立式电容对频率的适应性差一些，不过不到500MHz以上的频率是很难体现出差异的。
使用插件式安装的电容中也有很好的产品，例如CHEMICON的PS系列有一部分就是使用插件式的。

##
电容并联后等效容量值为各电容容量之和，耐压为最低那个的耐压值；

电容串联后等效容量值为各电容容量倒数之和的倒数，比如两个3Ω的电容串联后为1.5Ω，耐压为几个的耐压值相加。

它的计算方法：用欧姆定律计算电阻电路时，如果不用电阻单位而采用电导作单位，那么这时的方法就与计算电容电路相类似。

解决HP TC1100运行XP TABLET慢

2010-11-08T14:37:00.002+10:30

我用过也换过不少笔记本，总体感觉HP TC1100是很实在的，质量、屏幕、声音（这玩意的喇叭真是不错）。。。

现在用的是CELERON 800的TC1100，刚开始觉得卡，后来在http://www.tabletpcbuzz.com/forum/询问高人，终于明白了TC1100运行XP TABLET 2005慢和卡的原因在于那个在开始菜单旁边的TABLET TIP，把那个隐藏就可以了。。。

其实在http://www.tabletpcbuzz.com/forum/上面有许多人用TC1100试装VISTA，而且他们也找到了MX440实现玻璃效果的驱动，他们的评测TC1100运行VISTA并不比XP TABLET慢。。。

BM X31 + Brodcom 4318 Wireless on Debian Etch

2010-11-05T11:34:00.000+10:30

http://www.phpfans.net/ask/fansa1/4954708006.html

前几天在X31上加了一块无线网卡，本来以为很简单的事情，结果搞了好几天，这里做一个总结，希望对遇到同样问题的朋友有所帮助。

1.我的无线网卡不是IBM原装的，而是Dell DW1370,芯片是BCM4318,所以在插入机器的minipci接口前要先运行1802解除程序，网上很多，在dos下面运行一遍，然后插入minipci接口就行了。

2.安装BCM4318的fireware。
1)apt-get install bcm43xx-fwcutter
2)bcm43xx-fwcutter -w /lib/fireware bcmwl5.sys
3)mkdir -p /lib/hotplug/firmware
cp /lib/fireware/* /lib/hotplug/firmware/

说明：
1.其实Debian Etch已经带有BCM43xx的驱动，但是没有fireware的支持，所以要从bcmwl5.sys里面提取fireware文件。运气好的话，在第一步会自动从网上下载bcmwl5.sys，后面就自动完成。

2.如果第一步无法自动下载，那么就要自己寻找。其实这个就是从windows/system32/drivers/下面拷贝过来，使用bcm43xx-fwcutter -l以查看支持的驱动版本，但是我的机器上目前bcm43xx-fwcutter不能支持v4.以上的版本，只能支持v3.版本。如果系统不能支持，在运行bcm43xx-fwcutte的时候会有提示，但是还是会提取出fireware。

3.第三步是以防万一，有些系统会查找这个目录。

4.其实整个过程不过十多分钟，我花了几天，主要是bcm43xx-fwcutter没有自动下载到bcmwl5.sys,而后又费了很多时间找V3的bcmwl5.sys。

5.如果有什么问题，建议大家用一些基础命令查看一下，比如ifconfig,lspci|grep bcm,dmesg|bcm,more /var/log/syslog什么的，当然也离不开神奇的google。
顺便说一下，debian把我的无线网卡叫做eth2。

IBM 隐藏分区 FAQ

2010-11-04T15:45:00.001+10:30

IBM 隐藏分区 FAQ

1. 什么是隐藏分区 IBM没有提供随机的恢复光盘或者操作系统安装光盘，操作系统、随机软件、设备驱动都存放在隐藏分区里面，隐藏分区的大小约为5G。配合IBM的软件，可以实现一键恢复（蓝色的Access IBM键）。
2. 隐藏分区有什么优缺点？

优点：恢复系统方便，只要按一个键就自动可以完成，中间不需要有人值守
缺点：占用硬盘空间大，恢复过程比较慢，通常需要一个小时以上，远远没有GHOST恢复有效率。
综上所述，如果您是一个入门用户，独立安装操作系统以及设备驱动有困难，建议最好还是保留隐藏分区；如果您已经是有一定经验的用户，可以轻松完成操作系统以及硬件驱动、软件的安装，那么隐藏分区对您来说可以算是一个可有可无的东西了，完全可以删除掉来节约硬盘空间

3. 如果我想删掉隐藏分区，要做好那些备份工作？

最重要的一点，备份好随机的驱动程序。C:\IBMTOOLS 和C:\DRIVERS两个目录需要单独copy出来；至于I386 VALUEADD SUPPORT这些目录，都是windows安装光盘里面会出现的重要目录，里面含有操作系统的安装文件，考虑到中国的特殊国情，备份这些文件夹不是特别必要注：如果您拿到机器以后C盘下没有IBMTOOLS和DRIVERS文件夹，请立即使用一键恢复重新安装系统，这样C盘下就会出现这两个文件夹

4. IBMTOOLS文件夹太大了，我想对它减肥一下刻成CD，有哪些东西可以删除？C:\IBMTOOLS\APPS下面是IBM的随机软件。个人建议可以删除的软件：Adobe Acrobat Reader（满世界都有的免费软件）、Norton Antivirus（只含有3个月的免费升级，鸡肋，而且没有防火墙）、Record Now（IBM随机的刻录软件）、DLA（可以让CDRW当作移动硬盘使用的软件），Record Now和DLA的功能都可以用Nero Burning Rom代替，而且体积小很多
IBM_JRE是Java Runtime Environment；THEMES是IBM的桌面主题；AIBMMsgCtr是IBM Message Center，提供IBM网站的更新信息；OSFIXES是微软的操作系统补丁。是不是需要删除请根据个人情况而定,其他的软件和驱动，建议都不要动，以免在需要使用时产生不必要的麻烦。

5. 该怎么删除隐藏分区？
开机按F1进BIOS，光标移动到Security—Predesktop Area，设置成Disable。保存设置后重新启动，进入桌面用常用的分区软件（比如Partition Magic 8.0）就可以对隐藏分区进行操作了。

6. 如果我想在保留隐藏分区功能的前提下重新分区，该怎么操作？
因为T42使用的隐藏分区机制不同于以往，所以分区步骤也比较繁琐，不能用PQ 8.0或者WINDOWS的安装光盘直接分区，否则很可能导致隐藏分区失效。IBM官方推荐的步骤为用winme的安装光盘引导到DOS下面，用fdisk进行分区。当然这也意味着硬盘上的数据将会全部丢失，所以请备份好您的数据。分区完毕以后用Access IBM恢复系统即可。

7. 我手上有T42的恢复光盘，该怎么来重做隐藏分区？
首先，确保硬盘上没有任何分区（即分区状况和新买回来的硬盘没有区别），其次，确认BIOS里面Security—Predesktop Area的设置为Enable，首选启动设备设置为光驱，开机的时候将第一张光盘放入光驱，按照提示即可操作。

8. 恢复光盘有什么用？
在硬盘没有任何分区的情况下可以重做隐藏分区如果硬盘已经有了分区，恢复盘可以向C盘里面写入IBMTOOLS、DRIVERS、I386等文件夹并进行自动安装，功效等同于用Access IBM进行恢复，不同的是，中间需要更换光盘，不能做到无人值守。

用Ghost强力打造一键恢复功能

2010-11-04T15:21:00.004+10:30

自2001年下半年开始，IBM就在部分机型取消了原先随机的系统和驱动恢复光碟，进而在硬盘上划出一个数百
MB到几G多的隐藏分区存放恢复数据，系统启动过程中用户按F11（如今的新机型是按ACCESS IBM）进行恢复操作，目前所有的XTRA四大机型均全部采用这样的方式。这样做有利有弊，不方便的地方就是占用了一定的硬盘空间，而且一旦本本里面的硬盘损坏要恢复系统就麻烦大了；另一方面，对于IBM来说这样可以节省2－3张光碟的成本，而用户出门的时候也可以不携带光驱和光碟，系统一旦出现问题可以随时按F11或ACCESS IBM来恢复系统，正常工作。不过比较不爽的就是，这个一键恢复的是出厂时候的系统状态，没有常用软件，还要一一安装，恢复过程要近一个小时，T42更是需要80～100分钟，那么有没有办法把自己做好的系统放到自己制作隐藏分区里面，然后需要的时候按自己定义的一键恢复呢？（自己做系统？自己做隐藏分区？自定义一键恢复？

没听错吧？呵呵，我对隐藏分区研究已经有一段时间了，在技术板块可以找到不少我写的关于隐藏分区的帖子
，经过无数次的摸索和时间，基本掌握了IBM隐藏分区的一键恢复机制，且听我慢慢道来，倒杯咖啡先）

目前大多数的用户均喜欢用ghost来备份系统，通常是分区到文件的备份，这是一个非常快速的备份/恢复工具
，支持压缩功能，自带相当丰富的参数，通过今晚的试验，我终于结合ghost把备份的系统放进了隐藏分区，
这样开机的时候一按F11（这个键值可位于F1~F12之间，暂定F11）就会自动运行ghost把系统恢复到C盘，速度快捷，几分钟内就完成。

此次试验成功还得感谢一个T30的用户，没有隐藏分区，没有F11一键恢复，操作系统装得是D版XP，且无法在
internet上进行update，于是来找我，希望我帮他做一个隐藏分区，装一个IBM OEM版的winxp pro。这可难为
了我，我可没有T30的恢复光盘和恢复程序呀，冥思苦想，猛然想起我在做X22隐藏分区的时候，曾清楚地看到
过XP的安装界面......说到这里，肯定会有人有疑问了：不是吧？难不成你想用X22的恢复程序恢复T30？显卡
、主板芯片等都不一样啊。嘿嘿，正是！假设安装XP只是恢复过程的一个步骤，那么我只需要这一步骤就够了
，驱动程序可以等装完XP后再装，事后试验成功的事实证明，我的假设是正确的。

于是先做出T30的隐藏分区，调入X22的恢复程序，一键恢复成功（这一过程不再赘述，详见http://www.8buy.net/8buy/dispbbs.asp?boardID=4&ID=4348&page=1）
和我预想的一样，很多驱动都没有打上，windows xp还不带sp1和sp2，上IBM官方网站down最新的驱动安装即可（下载驱动的技巧参见http://www.8buy.net/8buy/dispbbs.asp?boardid=2&id=5680），
再安装事先下载好的sp2升级包，为windows打上sp补丁，接着安装常用软件（根据个人需要来安装），一切完毕，为操作系统瘦身，删除C盘根目录下面的一些如I386、DRIVERS、IBMTOOLS等文件夹，关闭系统还原，关闭休眠功能（可选），用ghost制作出一个备份的gho文件，存放到C盘以外的逻辑分区，如E、F盘等，文件系统为FAT32的，用PQMAGIC将隐藏分区设为非隐藏，清空里面所有文件（没有隐藏分区的略去这一步，直接划分一个FAT32的卷标为IBM_SERVICE的分区即可），把备份好的GHO文件和GHOST.EXE程序拷贝到隐藏分区（此时是非隐藏状态）。

接着用DOS启动盘（把IBM的F11的恢复程序也做进去，下载URL：http://www-900.ibm.com/cn/support/viewdoc/detail?DocId=JWUU-4ZNC86）启动到DOS下，将himem.sys拷贝到
IBM_SERVICE分区，运行sys g:(假设G就是IBM_SERVICE所在的盘符)，就把一个基本的DOS传过去了，这样
IBM_SERVICE分区就可以启动起来了，并用edit命令建立config.sys和autoexec.bat这两个文件，内容如下：

config.sys:
device=c:\\himem.sys

autoexec.bat:
ghost -clone,mode=pload,src=c:\\winxp.gho :1,dst=1:1-rb

这里简单地说一下DOS知识和GHOST参数，CONFIG.SYS和AUTOEXEC.BAT这两个文件是用来配置系统运行环境和自动执行一些命令，它们对电脑的运行性能以及许多设备的驱动起到了至关重要的作用，DOS系统启动时，要先从启动盘中读取两个系统文件IO.SYS、MSDOS.SYS，然后在启动盘的根目录下寻找并执行 CONFIG.SYS、COMMAND.COM、AUTOEXEC.BAT三个文件，autoexec.bat是自动批处理文件，它是批处理文件的一种，因为DOS启动时会自动运行它。解释一下为什么src=c:\\.....，因为启动时IBM_SERVICE所在的盘符就是C，为验证autoexec.bat文件的正确性，我们可以先将盘符C改为G（假设G就是IBM_SERVICE所在的盘符），然后在dos下直接键入 autoexec.bat，如顺利启动ghost，说明语句编写无误，再把G改为C。

简单说一下GHOST参数：
-rb
本次Ghost操作结束退出时自动重启。这样，在复制系统时就可以放心离开了。
-sure
对所有要求确认的提示或警告一律回答“Yes”。此参数有一定危险性，只建议高级用户使用。
-clone
　这是实现Ghost无人备份/恢复的核心参数。使用语法为：

-clone,MODE=（operation),SRC=（source),DST=（destination),[SZE（size),SZE（size)......]

此参数行较为复杂，且各参数之间不能含有空格。 　其中operation意为操作类型，值可取：copy：磁盘到磁
盘；load：文件到磁盘；dump：磁盘到文件；pcopy：分区到分区；pload：文件到分区；pdump：分区到文件。
　Source意为操作源，值可取：驱动器号，从1开始；或者为文件名，需要写绝对路径。
   Destination意为目标位置，值可取：驱动器号，从1开始；或者为文件名，需要写绝对路径。

因此ghost -clone,mode=pload,src=c:\\winxp.gho :1,dst=1:1-rb，这一命令所完成的操作就是自动运行本
地硬盘上的映象文件（src=c:\\winxp.gho :1），目标是本地硬盘上的第1个分区（dst=1:1），操作结束自动
重启。

网上有文章说在-rb后面加上-sure，个人认为风险较大，因为假如开机的时候不小心按到F11，没确认
就自动恢复系统了，哭都来不及啊，呵呵。

接着运行启动盘上的BMGR命令，否则F11不会显示出来，命令为：
bmgr.exe /Fboot.bin /MBMGRUS.BA1

注意两个斜杠前面有空格。

OK，重新启动，在IBM LOGO出现之后，就会出现To Start the Product Recovery program, press F11的提示
（重新启动一次时就会看到F1、F11、F12一起出现），按下F11，就会出现GHOST的界面，系统提示：Proceed with partition load?Destination partition will be permanently overwritten.YesorNo?

选择Yes，系统就开始恢复了，从开始恢复到重启启动到windows下，我看了一下表，只用了4分钟时间，当然
，这取决于你做的gho文件的大小。

至此，自制IBM一键恢复宣告完成，如F11不显示出来，看看bios选项里面有没有打开，这个F11可以自己定义
为F1~F12任意一键（不包括F1和F12），参见http://www.8buy.net/8buy/dispbbs.asp?boardID=4&ID=4348&page=1

启动完毕，卷标为IBM_SEVICE应该会自动隐藏，在windows下看不到，假如看得到，用PQ工具将其隐藏以达到保护之目的。

补充说明：

1、F11只会清除C盘的资料，对其它分区没有影响，但仍然建议注意备份资料
2、隐藏分区是一个系统分区，如从扩展分区/逻辑分区划出的空间来建立，是不具有启动功能的
3、autoexec.bat是DOS的自动批处理文件，启动时自动运行
4、一个硬盘可以有最多三个系统分区，但只能其中一个激活，而Fdisk只能建立一个系统分区，所以只有借助
第三方软件，如PQMAGIC。
5、F11功能可以在任何一台IBM兼容PC上使用，前提是你要用PQmagic划分出一个FAT32的Primary分区卷标是IBM_SERVICE，而且，提示信息可以自己随意写，一键恢复的按键也可以自己定义

******************************************************
IBM的笔记本具有F11键恢复机器的功能，但如果我们使用的是一般的台式机，是不是也可以把恢复功能集成到机器中，不用任何恢复盘，就可以随时恢复呢？答案是肯定的！

第一步：必备工具

Windows 9x/2000/XP安装盘，Ghost，Windows 98启动盘。

第二步：安装98记录

先把硬盘分为几个区，C区不用太大，3G，D盘分3G，用来存放C盘系统。然后用Windows 98启动盘启动电脑，在纯DOS下输入format c: /s ，格式化C盘，并传输系统。

第三步：编写config.bat

用edit工具打开C:config.sys文件，在其中输入如下内容（如图1）：


[menu]
menuitem=Clone,Backup your system.
menuitem=RestoreHD,Restore from HD.
menuitem=NormalBoot,Boot your machine.
menudefault=NormalBoot，18
menucolor=7,0
[Clone]
device=himem.sys /testmem:off
[RestoreHD]
device=himem.sys /testmem:off
[NormalBoot]
device=himem.sys /testmem:off
device=device=oakcdrom.sys /D:oemcd001
[COMMON]
files=60
buffers=20
dos=high,umb
stacks=9,256
lastdrive=z


接着把Windows 98启动软盘上的himem.sys拷贝到C:目录中（此步骤不是必须的）。
第四步：编写autoexec.bat

用edit工具打开C:autoexec.bat文件，在其中输入如下内容（如图2）：


@ECHO OFF
set EXPAND=YES
SET DIRCMD=/O:N
cls
set temp=d:
set tmp=d:
path=a:
IF "%config%"=="Clone" goto Clone
IF "%config%"=="RestoreHD" goto RestoreHD
IF "%config%"=="NormalBoot" goto NorBoot
:Clone
d:ghost -sure -clone,mode=pdump,src=1:1,dst=d:system.gho
GOTO QUIT
:RestoreHD
d:ghost -sure -rb -clone,mode=pload,src=d:system.gho:1,dst=1:1
GOTO QUIT
:NorBoot
LH MSCDEX.EXE /D:oemcd001 /L:Z
:QUIT


第四步：拷贝必须文件

格式化D盘，然后把ghost.exe文件拷贝到D盘根目录下。

第五步：安装Windows 2000/XP

接下来，把Windows 2000/XP光盘放入光驱，并把Windows 2000/XP安装到C盘上，同时装好硬件驱动，设置好自身的参数。

第六步：备份系统

重新启动电脑，当出现启动菜单时，选择“Microsoft Windows 98”，再在出现的屏幕中选择Clone,Backup your system.。这样，Ghost会把系统备份到D:system.gho文件中。

第七步：恢复系统

以后机器坏了，可以随时重新启动电脑，当出现启动菜单时，选择“Microsoft Windows 98”，再在出现的屏幕中选择RestoreHD,Restore from HD.。这样，Ghost会把D:system.gho克隆到C盘，从而快速恢复系统。


当然，如果你对系统作了重新设置或调整，也可以随时重新启动电脑，当出现启动菜单时，选择“Microsoft Windows 98”，再选择Clone,Backup your system.随时更新d:system.gho文件，这样以后恢复时将会使用最新的设置。

Don't Chang IMEI Number

2010-08-31T11:05:00.001+09:30

"Your" phone connects to the GSM/DCS/PCS network and gives it its specific IMEI number. Then the network checks it against a EIR (Equiptment something Register) and does one of four things.

1. If it's not on there, it drops the connection.
2. If it matches one they can put it on the the blacklist, which disables it from EVER connecting to a GSM/DCS/PCS network.
3. If it matches one it can put it on the greylist, which makes it usable BUT, traces who the phone is registered to in the SIM info and that person can get into a butload of trouble.
4. If it matches one they can give full service.

I don't mean to make it sound hopeless, but it probably isn't going to happen for you. Anyway, here's my next advice:

Before you do anything to the phone, dial *#06# to get it to display the IMEI number. Then go to

http://www.numberingplans.com/index.php?goto=imei

and check if it's blacklisted or greylisted or useable (If it doesn't work now, it will be black or greylisted).

If it's greylisted you may not want to turn it on until you crack it (or return it)--you could get the person it's registered to in alot of trouble.

If it's blacklisted you HAVE to set the IMEI number to one on an EXISTING phone (preferably not greylisted). This is the difficult step. I suggest giving up at this point and sticking to a phone you bought. If you want to continue then there is one option that I know of: buying an IMEI number.

This may sound weird, but there is a trojan for phones with Symbian OS (http://www.linuxsecurity.com/content/view/116782/65/) that disables everything on the phone but it's functionality. This allows a hacker to steal it's IMEI number at the expence of robbing someone of their phone. I'm not sure where you can find such an IMEI number, but google around and see what you can find.

I suggest returning the phone.

How to release Configuration lock

2010-08-06T15:58:00.001+09:30

1. symcfg -sid xxx list -lock -lockn all

Lock Lock Lock Time
SymmID Attachment Status Number Usage Held (Sec)

XXX Local Locked 15 Config Change 1917

2. can check with symaudit and search for symconfigure actions running elsewhere...
symaudit list -sid xxx -start_date 08/01/10

3. symcfg -sid XXX -lockn 15 release -force

Useful SAN Storage command and OS system commands

2010-08-04T19:43:00.000+09:30

Useful SAN Storage command and OS system commands.

Created to:
http://www.sanduel.com/SAN-Storage-Commands/Useful-SAN-Commands.html

Symdev Commands

symdev List ~ List all devices on symm

symdev -sa -p List ~ List devices maped to that one FA

symdev List -bcv or -rdf1 ~ List all bcv or rdf1 volumes

symdev List -noport ~ List devices not mapped to any FE ports

symdev List -clariion

symdev show 0123 -v ~ vebose Listing of one device

symdev List -RANGE 0001:0123 -v ~ vebose Listing of a rage of devices

symdev List pd ~ List devices this host can see

Symcfg Commands

symcfg discover ~ discover the storage environment

symcfg List ~ List local and remote symmetrixes

symcfg List -clariion ~ List clariions

symcfg List -v ~ Lists whether the Symmetrix director has device masking turned on

symcfg List -FA all List ~ Lists all fibre directors in a Symmetrix system

symcfg List -dir all -address -sid 1924 ~ identify the address information for devices

symcfg List -dir all -address -available ~ sid 1924 ~ returns the next available LUN address

symcfg List -lockn all ~ List of visible Symm exclusive locks

symcfg -sid 098712321337 -lockn 15 release ~ release a lock on a Symmetrix array.

Symconfigure Commands

symconfigure -sid -f preview ~ checks file to make sure it is ok to exe

symconfigure -sid -f commit ~ makes the changes from file

symconfigure -sid -f prepare

Symmaskdb Commands

symmaskdb List devs ~ Lists all devices accessible to an HBA on a specified Symmetrix system

symmaskdb remove ~ removes the meta member devices

symmaskdb restore ~ restores a database from a specified file

symmaskdb backup ~ backs up a database to a specified file

symmaskdb init ~ deletes and creates a new VCMDB

symmaskdb List assignment ~Lists deives already assigned

symmaskdb List no_assignment ~Lists deives not yet assigned

Symmask Commands

symmask add devs ~ adds a device to the List of devices that a WWN can access in the database

symmask remove devs ~ removes a device from the List of devices that a WWN can access in the database

symmask delete ~ deletes all access rights for a WWN in the database

symmask replace ~ allows one HBA to replace another

symmask refresh ~ refresh vcmdb to all FA ports

symmask login ~ Lists for each Fibre director which hosts and HBA’s are logged in to a Symmetrix system

symmask List HBA’s ~ Lists the WWN of the Fibre HBAs on this host

symmask -sid 381 -wwn 50060D000034F7F6 -dir 16C -p 1 set heterogeneous on HP_UX

symmask -sid SymmID set lunoffset on offset base \ -awwn awwn -dir # -p # ~ offset high lun numbers

Other SYMCLI Commands

symsan ~List ports and LUN WWNs seen from a specific Symmetrix director and port

symdg ~ creates/deletes/renames device groups

symld ~ addes & removes devices to a deivce group

symbcv ~ associates/disassociate BCV with device groups

symmir ~ performs (split/establish/restore) BCV mirror commands against device groups

symclone ~ performs (split/establish/restore/activate/terminate/recreate)

symsnap ~ performs (restore/activate/terminate/recreate)

symrdf ~ performs (split/establish/restore/failover/update/failback/suspend/resume) against RDF device groups

symcg ~ Performs operations on a Symmetrix RDF composite group

symrslv ~ Displays logical-to-physical mapping information about a logical object that is stored on a disk.

symstat ~ Displays statistics information about a Symmetrix, any or all directors, a device group, a disk, or a device.

symioctl ~ sends I/O control commands to application

SYMCLI BASE Commands

symapierr - Used to translate SYMAPI error code numbers into SYMAPI error messages.
symaudit - List records from a symmetrix audit log file.
symbcv - Perform BCV support operations on Symmetrix BCV devices.
symcfg - Discover or display Symmetrix configuration information. Refresh the host's Symmetrix database file or remove Symmetrix info from the file. Can also be used to view or release a 'hanging' Symmetrix exclusive lock.
symchg - Monitor changes to Symmetrix devices or to logical objects stored on Symmetrix devices.
symcli - Provides the version number and a brief description of the commands included in the Symmetrix Command Line
symdev - Perform operations on a device given the device's Symmetrix name. Can also be used to view Symmetrix device locks.
symdg - Perform operations on a device group (dg).
symdisk - Display information about the disks within a Symmetrix.
symdrv - List DRV devices on a Symmetrix.
symevent - Monitor or inspect the history of events within a Symmetri
symgate - Perform operations on a gatekeeper device.
symhost - Display host configuration information and performance statistics.
syminq - Issues a SCSI Inquiry command on one or all devices. Interface.
symlabel - Perform label support operations on a Symmetrix device.
symld - Perform operations on a device in a device group (dg).
symlmf - Registers SYMAPI license keys.
sympd - Perform operations on a device given the device's physical name.
symstat - Display statistics information about a Symmetrix, a Director, a device group, or a device.
symreturn - Used for supplying return codes in pre-action and post-action script files.

SYMCLI CONTROL Commands
symacl - Administer symmetrix access control information.
symauth - Administer symmetrix user authorization information.
symcg - Perform operations on an composite group (cg).
symchksum - Administer checksum checks when an Oracle database writes data files on Symmetrix devices.
symclone - Perform Clone control operations on a device group or on a device within the device group.
symconfigure - Perform modifications on the Symmetrix configuration.
symconnect - Setup or Modify Symmetrix Connection Security functionalit
symmask - Setup or Modify Symmetrix Device Masking functionality.
symmaskdb - Backup, Restore, Initialize or Show the contents of the device masking database.
symmir - Perform BCV control operations on a device group or on a device within the device group.
symoptmz - Perform Symmetrix Optimizer control operations.
symqos - Perform Quality of Service operations on Symmetrix Devices
symrdf - Perform RDF control operations on a device group or on a device within the device group.
symreplicate - Perform automated, consistent replication of data given a pre-configured SRDF/Timefinder setup.
symsnap - Perform Symmetrix Snap control operations on a device group or on devices in a device file.
symstar - Perform SRDF STAR management operations.
symrcopy - Perform Symmetrix Rcopy control operations on devices in a device file.

SYMCLI SRM(Mapping) Commands
symhostfs - Display information about a host File, Directory, or host File System.
symioctl - Send IO control commands to a specified application.
symlv - Display information about a volume in Logical Volume Group (vg).
sympart - Display partition information about a host device.
symrdb - Display information about a third-party Relational Database.
symrslv - Display detailed Logical to Physical mapping information about a logical object stored on Symmetrix devices.
symvg - Display information about a Logical Volume Group (vg).

NAVICLI COMMANDS

navicli -h getsp ~ verify connectivity

navicli -h register ~registers host with Clariion and tests agent install

navicli -h storagegroup ~ List all info about existing groups

navicli -h getrg -lunList ~ List all existing raid groups and LUNS

navicli -h getdisk ~ shows numbers of disks in storage array

navicli -h getrg ~ shows the number of raid groups

navicli -h get lun ~ Lists all the disks

navicli -h storagegroup -List ~ displays storage groups

navicli -h getcache ~ shows the cache

navicli -h storagegroup -create -gname ~ creates a new storage group

navicli -h storagegroup -addhlu -gname -hlu <#> -alu <#> ~ assigns LUNs to storage group

navicli -h storagegroup -connecthost -host -gname ~ assigns host to storage group

POWERPATH COMMANDS

powermt ~ manage powerpath environment

powercf ~ configure powerpath devices

emcpreg ~ manage powerpath license registration

emcpupgrade ~ convert powerpath configuration files

INQ

INQ

Inq -h ~ List options and syntax

Inq -hba ~ List hba wwn

Inq -btl ~ display Bus Target and Lun

Inq -show_vol ~ display Symmetrix Volume Number.

Inq -winvol ~ show Windows filesystems

Inq -dev ## -page0 ~ Raw unformatted data on a single device

Inq -clariion ~ display CLARiiON device information

MDS-SERIES (CISCO) COMMANDS

MDS-SERIES Switch Commands

ip address 191.168.123.222 255.255.255.0

View = ~ show running-config

show environment ~ shows status of all installed hardware components

show flogi database ~ shows database List of all FLOGI events

show fcns database ~ shows database List of all N-ports logged in

show vsan membership ~ shows List of VSAN members

show interface brief ~ Lists the interfaces and status

MDS-SERIES Zoning Commands

config terminal ~Enters configuration terminal

zone name TestZone1 vsan 4 ~ creates a zone

member pwwn 10:01:10:01:10:ab:cd:ef ~ adds node to the zone above

no member pwwn ~deletes member from zone

zoneset name Zoneset1 vsan 4 ~ creates a zoneset

member ~adds zone to the ZoneSet above

no zone name vsan ~ Deletes a zone

zoneset activate name Zoneset1 vsan 4

zone copy active-zoneset full-Zoneset1 vsan 4

copy running-config start-up config ~ copy from source to startup configuration

vsan database ~ go into vsan configuration mode

vsan 4 interface fc3/21 ~move port 21 on module 3 to vsan 4

show zoneset ~ shows all zonesets that are active

show zone vsan <#> ~ shows all zones active in vsan

show zoneset active ~ displays the active zoneset

show vsan ~ shows the vsans on the switch

show zoneset active vsan ~ Shows active zoneset

B-SERIES (BROCADE) COMMANDS

B-SERIES Switch Commands

switchDisable ~ offline

ipAddrSet ~set the IP address of a Brocade switch

switchShow ~ display switch info

supportShow ~ full detailed switch info

portShow # ~ display port info

nsShow ~ Name server contents

nsAllShow ~ NS for full fabric

fabricShow ~ fabric information

ad --create ~create a new Admin Domain.

ad -apply ~enforce the new Admin Domain configuration.

B-SERIES Zoning Commands

aliCreate “Alias”, “20:00:00:e0:23:40:07:08”

zoneCreate “ZoneName”, “20:00:00:e0:69:40:07:08; 50:06:04:64:b6:91:c1:1d”

cfgCreate “Test_cfg”, “Zone1; Zone2”

cfgSave ~ saves zoning information across reboots

cfgEnable “Test_cfg”

zoneShow or cfgShow ~ shows defined and effective zones and configurations

zoneAdd ~ adds a member to a zone

zoneRemove ~ removes a member from a zone

zoneDelete ~ deletes a zone

cfgAdd ~ adds a zone to a zone configuration

cfgRemove ~ removes a zone from a zone configuration

cfgDelete ~ deletes a zone from a zone configuration

cfgClear ~ clears all zoning information/ must disable the effective configuration

M-SERIES (McDATA) COMMANDS

M-SERIES Switch Commands

View= ~ config ip show

Config> ip ~ (new IP and Subnet mask)

Show> switch

Show> switch

Show > system

Show> nameserver

Show> loginServer

Show> nameServer

Show.Fabric> nodes

Maint > system > setOnlineState

M-SERIES Zoning Commands

Config.Zoning> addWwnMem:

Config.Zoning> addZone ~ add a new zone to the working area

Config.Zoning> activateZoneset ~ activation of changes

Config.Zoning> showactive ~ shows actively connected running zoneset

Config.Zoning> clearZone ~ clear WWNs in a zone

Config.Zoning> deletezone ~ remove zone from the running config

Config.Zoning> showPending ~ show pending zones

Config.Zoning> renameZone:

Config.Zoning> deleteWwnMem ~

Config.Zoning> renameZoneSet ~

Veritas VM HOST COMMANDS

Veritas VM Device Commands

vxdisk List ~ List all disks under volume manager control and give there status.

vxdiskadd c1t2d3 ~ add or bring a disk under volume manager control

vxdiskadmin ~ Interactive front end to the vxdisk program

Veritas VM Filesystem commands

vxdisk init ~ Initialize Physical Volume

vxdg init mydg mydg-01=c1t11d0 ~ Create Disk Group

vxassist -g mydg make myvol ~ Create Logical Volume

mkfs -F vxfs /dev/vx/rdsk/mydg/myvol ~ create file system

vxvol -g mydg stopall ~ stop a volume

vxdg deport mydg ~ deport disk group

vxdg import mydg ~ import disk group

vxvol -g mydg startall ~ starting a imported volume

VMware ESX HOST COMMANDS

VMware ESX Device Commands

esxcfg-rescan ~scan for new disks

esxcfg-swiscsi -e ~enable iSCSI initiator

more /proc/scsi/lpfc/X ~ wwn of HBA

esxcfg-vswitch ~

VMware ESX Filesystem Commands

vmkfstools ~

Windows HOST COMMANDS

Windows 2003 server SP1 Device Commands

SystemInfo ~ Displays detailed configuration information about a computer and its operating system

Shutdown /r /f ~ forced reboot

Netstat ~ Displays active TCP connections, ports on which the computer is Listening

mstsc /v: 255.255.255.255 /console ~ launches a Remote desktop Connection

net use \\ComputerName\ShareName\volume ~ Connects a computer to a computer shared resource

FC ~ compares two files and displays the differences

ChkDsk ~ check and repair disk problems

Recover ~ Recover a damaged file from a defective disk.

fcinfo /details ~ if fcinfo is installed ,this will List the HBA’s wwns

Windows 2003 server SP1 LVM Commands

Diskpart rescan ~ Locates new disks that may have been added to the computer

Diskpart List disk ~ Displays a List of disks and information about them,

Diskpart select disk ~ Selects the specified disk and shifts the focus to it.

Diskpart detail disk ~ Displays the properties of the selected disk and the volumes on that disk.

MountVol ~ Creates, deletes, or Lists a volume mount point.

Diskpart assign ~ Assigns a drive letter or mount point to the volume with focus.

Diskpart extend ~ Extends the volume with focus into next contiguous unallocated space

Diskpart import ~ Imports a foreign disk group into the local computer's disk group

Format /FS:filesystem ~ Specifies the type of the file system (FAT, FAT32, or NTFS).

FSutil volume dismount

VI COMMANDS

Cursor movements

h ~ left one character

l ~ right one character

j ~ down one line

k ~ up one line

w ~ right one word

b ~ back one word

Deleting, Yanking, and Pasting

d ~ delete

x ~ delete character cursor is on

r ~ replace one character

y ~ yank (copy into temporary buffer)

Y ~ yank line cursor is on

p ~ paste below cursor line (deleted or copied text)

Saving and Exiting

u ~ undo last editing command

ZZ ~ save and exit (hold down shift and press "z" twice)

:wq! ~ write and quit even if it is read-only

FTP COMMANDS

open ~ undo last editing command

close ~ save and exit (hold down shift and press "z" twice)

bin ~set to transfer for binary and text files

hash ~display progress during get

mget ~mutiple get - download files in to current directory

mput ~multiple pu - upload files from current directory

AIX/IBM HOST COMMANDS

AIX Software Installation

/usr/lpp ~ Software Directory

lslpp -L all ~ List installed software

lslpp -f fileset ~ List all files

instfix -i ~ List installed patches

cp *.lpp /usr/sys/inst.images ~ copy lpp software to the install directory

smit installp ~ Install a software package

rmdev ~ Remove a device

AIX Device Commands

lscfg ~ Lists all comfigured components

smit or smitty ~ system management utility

lscfg -v l ~ Lists all attributes (WWN’s) for a device

emc_cfgmgr ~ configures symmetrix devices

mkbcv ~ makes BCV visable to AIX to avoid locking during boot

(1) chdev -l fcsX -a init_link=pt2pt -P ~ “To change INIT Link flags parameter”

(2) chdev -l fscsiX -a fc_err_recov=fast_fail -P ~ “Fabric Event Error RECOVERY Policy”

(3) cfgmgr -v ~ cofigures devices and optionally installs device software

AIX NFS Commands

exportfs ~Lists all exported filesystems

exportfs -a ~Exports all fs's in /etc/exports file

exportfs -u (filesystem) ~Un-exports a filesystem

mknfs ~Configures and starts NFS services

rmnfs ~Stops and un-configures NFS services

mknfsexp -d /directory ~Creates an NFS export directory

mknfsmnt ~Creates an NFS mount directory

mount hostname:/filesystem /mount-point ~Mount an NFS filesystem

nfso -a ~Display NFS Options

AIX iSCSI Commands

smit iscsi

AIX Filesystem Commands

lsdev -Cc disk ~ Device Listing and status

mkdev ~ configures a disk device masking sue it is available as a physical volume

chdev -l hdisk# -a pv=yes ~ Initialize Physical Volume

lspv -l hdisk# ~ Disk Label

mkvg -y myvg -s 16 hdisk2 ~ groups one or more physical devices into a volume group

mirrorvg ~Creates mirror volumes for all volumes in a volume group.

extendvg myvg hdisk3 hdisk4 ~ Extend Volume Goup

lsvg -l vgname ~ displays volumes, with a specified volume group

mklv -y mylv myvg 16 ~ Make logical volume

mklvcopy hd1 2 hdisk1 ~(2) makes a copy of lv should be followed up by syncvg command

lslv ~ List Logical Volume

crfs -v jfs -d mylv -m /myfs

mount ~ mounts a filesystem

varyoffvg myvg ~ Deactivate Volume Group

exportvg myvg ~ Export Volume Group

importvg -y myvg -f /dev/hdisk9 ~ Import Volume Group

varyonvg myvg ~ Activate Volume Group

HP/UX HOST COMMANDS

HP/UX Software Installation

sysdef ~ analyzes current running system

swList -l bundle ~ displays version and type of HP-UX

swList -l patch ~ List installed patches

swreg -l depot /full/path/to/your/depot_file ~ Register a depot package for install

swinstall ~ Install the Software depot

HP/UX Device Commands

insf -e ~ install special device files

ioscan -fnC disk ~ scans system hardware

sam ~ System administration tool

dd if=/dev/rdsk/c34t15d0 of=/dev/zero count=1 ~ makes HP register with a Clariion thru LUNZ device

navicli -h register ~registers host with Clariion and tests agent install

lsdev -C disk ~ List device drivers in the system

mknod ~ makes a directory, special, or ordinary file

/stand/system ~ system configuration file

HP SAN Commands

fcmsutil /dev/fcd0 ~ List HBA wwn

tdutil /dev/td0 ~ List HBA wwn

HP NFS Commands

/etc/exports ~file controls which file systems are exported to remote hosts and specify options

/exported/directory example.emc.com ~Exports directory to host example.emc.com (found in /etc/exports)

exportfs -a ~command to read /etc/export and export filesystem

mount shadowman.emc.com:/misc/export /misc/local ~mount an NFS export from shadowman.emc.com to the dir /misc/local

HP/UX Filesystem commands

pvcreate /dev/rdsk/c1t0d2 ~ creates a physical volume within a LVM volume group

pvdisplay ~ display info about physical volumes within an LVM volume group

ls -l /dev/*/group ~List the minor number of each vg in 6th field (all not Listed are available)

mkdir /dev/myvg ~Create directory entry in /dev for Volume Group

mknod /dev/myvg/group c 64 0x010000 ~ Create a file for Volume Group

vgcreate -s 16 /dev/myvg /dev/dsk/c1t0d0 ~ creates a LVM volume group

vgextend /dev/myvg /dev/dsk/c1t0d1 ~ add disk to VG

vgchange -a y myvg ~ Avtivate VG

vgscan ~ scan physical volumes for LVM volume groups

vgdisplay ~ displays info about LVM volume groups

lvcreate -l 16 -n mylv /dev/myvg ~ creates LVM logical volumes

lvcreate -m mylv /dev/myvg ~ creates mirrored logical volumes

lvdisplay ~ displays LVM logical volumes

newfs /dev/myvg/rmylv ~ Create file system

mount /dev/myvg/mylv /myfs ~ Mount file system

vgchange -a n myvg ~ Deactivate Volume Group

vgexport myvg ~ Export Volume Group

vgimport /dev/myvg /dev/dsk/c1t0d0 ~ Import Volume Group

PROCEDURES

zone hp server to symm

symmask List hba -v ~to List your servers paths to the symm

symmask -wwn -dir -p add dev ~(use wwn, dir, p values from above command) run command for each hba to FA zone

symmask -wwn -dir -p set heterogeneous on HP_UX ~use wwn from the (symmask List hba -v )

symmask refresh

ioscan -fnC disk

insf -e

symcfg dis

sympd List

To get HPUX to register with Clariion if using NaviAgent

Install NaviAgent

Edit agent.config file

ioscan -fnC disk

insf -e

/sbin/init.d/agent stop
rm /etc/log/HostIdFile.txt
/sbin/init.d/agent start

dd if=/dev/rdsk/c34t15d0 of=/dev/zero count=1 ~ makes HP register with a Clariion thru LUNZ device

navicli -h register ~registers host with Clariion and tests agent install

# rmsf path ( The paths are showing NO_HW or not sensing).

# ioscan -fnc disk (check)

# insf -e

# symcfg discover

# powermt display ( check for any dead path)

# powermt check (checks and corrects dead path).

# powermt config

# powermt save

Linux HOST COMMANDS

Linux Software Installation

rpm -hiv

Linux Device Commands

modprobe -l *lpfc* `List Emulex modules

modprobe -r ~ discover new disk

/sys/class/scsi_host/host1/issue_lip ~ discover new disk

/sys/class/scsi_host/host1/scan ~ discover new disk

/usr/sbin/lpfc lun_scan all

Linux FC SAN Commands

more /proc/scsi/lpfc/X ~ wwn on RHEL3

more /sys/class/scsi_host/hostX/port_name ~ wwn on RHEL4

more /sys/class/fc_host/hostX/port_name ~ wwn on RHEL5

(X is the instance number of the HBA)

Linux iSCSI Commands

yum install iscsi-initiator-utils ~install iSCSI soft initiator

rpm -q srvadmin-deng iscsi-initiator-utils ~install iSCSI soft initiator

rpm -ql iscsi-initiator-utils ~confiure iSCSI soft initiator

iscsiadm -m discovery -t -p 192.168.1.100 ~discover iSCSI target

iscsiadm --mode node --targetname iqn ~

Linux NFS Commands

/etc/exports ~file controls which file systems are exported to remote hosts and specify options

/exported/directory example.emc.com ~Exports directory to host example.emc.com (found in /etc/exports)

exportfs -a ~command to read /etc/export and export filesystem

mount shadowman.example.com:/misc/export /misc/local ~mount an NFS export

redhat-config-nfs ~RedHat NFS tool

Linux Filesystem commands

pvcreate /dev/emcpowerX ~ initializes PhysicalVolume for later use by the Logical Volume Manager

vgcreate VG_Name /dev/emcpowerX ~ creates a new volume group

lvcreate --size 2000m --name LV_Name /dev/VG_Name ~creates 2000MB logical volume mkfs -t ext2 /dev/VG_Name/LV_Name ~ Make a file system on a logical volume

mount -t ext2 /dev/VG_Name/LV_Name /mnt/FS_MountPoint ~ mount File system

df -a ~display filesystems

Fdisk /dev/sda ~ partition table manipulation

pvdisplay ~ allows you to see the attributes of one or more physical volumes

pvscan ~ scans all supported LVM block devices in the system for physical volumes

vgdisplay ~display attributes of volume groups

vgextend ~ allows you to add one or more initialized physical volumes

vgscan ~ scan physical volumes for LVM volume groups

vgexport ~make volume groups unknown to the system

vgimport ~make volume groups known to the system

lvdisplay ~display attributes of a logical volume

lvextend ~ Extend logigal volume

e2fsadm ~ resizing of a logical volume

fsck ~Command used to check and repair a Linux filesystem

SUN/SOLARIS HOST COMMANDS

SOLARIS Software Installation

ptree -a ~ Shows all running processes in a tree format

showrev -p ~ Displays currently installed Solaris patches

prtconf ~ prints system configurations

pkginfo ~ Lists installed software packages

pkgadd ~ install software packages

pkgrm ~ removes installed software packages

Solaris Device Commands

cfgadm -a ~ List all

cfgadm -c configure c4 ~ configure StorEdge Leadville driver.(Search for new devices)

devfsadm -vC ~ searches for devices and also cleans up old

update_drv -f sd -d -I ~ searches for devices

devinfo ~ print device specific information about disk devices

drvconfig ~ generates special device files

reboot -- -r ~ reboots system to discover configuration changes, and rebuild special files

/etc/system ~ system files

/kernel/drv/sd.conf ~ Lists of available target ids and luns

/kernel/drc/lpfc.conf ~ used for persistent binding on Emulex (qla22xx.conf for Qlogic)

/var/adm/messages ~ system messages

Solaris iSCSI Commands

iscsiadm add static-config iqn.1999-08.com.array:sn.01234567,192.168.1.3:3260 ~map target

iscsiadm add discovery-address 192.168.1.13:3260

iscsiadm modify discovery --isns enable

iscsiadm List target -vS Target: iqn.1986-03.com

devfsadm -Cv -i iscsi

Solaris FC SAN Commands

fcinfo hba-port ~ Lists information and WWNs

fcinfo remote-port -p 10000000c937694f -ls ~ Lists the remote-port information

Solaris NFS Commands

share -F nfs -d "Cartman dir" / share2

mount -F nfs cartman:/share2 /cartman

share -F nfs -o ro=sun.ucs.indiana.edu,rw=teak.uwsg.indiana.edu /reports ~ export (share) /reports à read only to sun.ucs.indiana.edu, read,write to teak.uwsg.indiana.edu

/etc/dfs/dfstab ~ file to edit to make a share permanent

shareall -F nfs ~ command to excute that will read /etc/dfs/dfstab and share to the network

SOLARIS Filesystem Commands

*** Format and lable all devices before using zpool ***

zpool create spoon c3t6d9 ~create & mounts storage pool named spoon and mounts it at /spoon (no slice #)

zpool create spoon mirror emcpower3c emcpower4c ~create a RAID1 storage pool mounted at /spoon

zpool destroy -f spoon ~destroy a zpool

zfs create spoon/fs ~creates ZFS file system spoon/fs, automatically mounted at /spoon/fs.

zpool List ~List pools

format ~ Disk partitioning and maintenance program

sysdef ~ Device Listing

prtvtoc ~ Disk Label

metadevadm ~ Checks device ID configuration.

metainit ~ Configures volumes.

metastat ~ Displays the status of volumes or hot spare pools.

metaset ~ Administers disk sets.

newfs -v ~ makes a UFS filesystem on disk drive or partition within a diskdrive

SOLUTIONS ENABLER COMMANDS

Commands to see devices

syminq ~ List all devides seen by host OS

syminq -cids ~ List Clariion devices

syminq hba -fibre ~ List HBA

syminq -pdevfile ~List the location of devices

sympd List ~ Lists the Symmetrix devices that the host OS can see

sympd List -vcm ~ Lists all the physical device name in the device masking database

symdev List pd ~ Lists the Symmetrix devices that the host OS can see

Some most useful Symcli Commands

2010-07-02T21:17:00.000+09:30

You may find useful the Symcli Script maker utilities listed below the menu bar , to create the symcli scripts for various operations like Mapping,Masking,Meta Creation etc.. in EMC Symmetrix boxes.

symcfg

symcfg list : A brief description of the all connected Symmetrix boxes.
symcfg -sid 1234 list -lockn all : Lists all the external locks held in Symmetrix array 1234.
symcfg -sid 1234 -lockn 15 release -force : Release the lock 15 held on array 1234 .
symcfg -sid 1234 list -v : Displays detailed information about the Symmetrix Array 1234.
symcfg -sid 1234 -dir 4a -p 0 list -addr -avail : Lists the LUN information / availability of lun ids on port 4a:0 in array 1234 .
symcfg -sid 1234 list -rdfg all : List details about all the rdf groups in array.
symcfg -sid 1234 list -rdfg 3 : List details about rdf group 3 .
symcfg -sid 1234 list -rdfg all -dynamic : List details about all the dynamic rdf groups in array .
symcfg -sid 1234 list -rdfg all -static : List details about all the static rdf groups in array .
symcfg -sid 1234 list -ra all : List all RA ports with details like rdfg number , remote array sid and online status.
symcfg discover : Scans all the devices in hosts looking for new symmetrix devices and rebuilds the symmetrix configuration database .

symdev

symdev -sid 1234 list : Lists all devices in symmetrix 1234.
symdev -sid 1234 list -noport : Lists the devices which are not mapped to any ports.
symdev -sid 1234 list -noport -meta : Lists all unmapped meta devices .
symdev -sid 1234 list -dynamic : Lists all devices whose dyn_rdf attribute set .
symdev -sid 1234 list -hotspare : Checks whether hotspare invoked in the array .
symdev -sid 1234 show ABC : show the detailed information about the devioce ABC.
symdev -sid 1234 write_disable ABC -SA all : Write disable the device ABC from through all directors.
symdev -sid 1234 not_ready ABC -SA all : Not ready the device ABC from through all directors.

symmaskdb

symmaskdb -sid 1234 -dev ABC list assign : List the masking details of the dev ABC .
symmaskdb -sid 1234 -wwn xxxxxxx list devs : List the devices masked to the given wwn number .

symmask

symmask list hba : List the HBA details of the host.
symmask -sid 1234 -dir 4a -p 0 list logins : List out wwn s logged through port 4a:0 .
symmask -sid 1234 refresh : Refresh the VCM Data Base after a masking and unmasking operation.
symmask -sid 1234 -wwn xxxx -dir 4a -p 0 add devs ABC,ABD : Mask the devices ABC and ABD to the given wwn in 1234 arrray .
symmask -sid 1234 -wwn xxxx -dir 4a -p 0 remove devs ABC,ABD : Unmask the devices ABC and ABD from the given wwn in 1234 arrray .

symdg

symdg -sid 1234 list : List the device groups which include the devices from array 1234.
symdg create mydg -type rdf1 : Create device group mydg of rdf1 type .
symdg show mydg : Shows the members/details of mydg.
symdg rename mydg yourdg : Renames the mydg to yourdg.
symdg delete mydg -force : Delete device group mydg.

symld

symld -g mydg -sid 1234 add dev ABC DEV006 : Add the RDF device ABC to device group mydg as DEV006
symld -g mydg remove DEV006 : Remove DEV006 form device group mydg.

symrdf

symrdf -sid 1234 -rdfg 3 -type rdf1 -file rdf.txt -g mydg createpair -establish : Establish the SRDF relation between the devices given in the file rdf.txt from array 1234(R1) and remote box according to the rdf group . This command start sync between R1 and R2, and also add these devices after creating the device group mydg.
symrdf -sid 1234 -rdfg 3 -file rdf.txt query : Query the Devices by using the device pair file.
symrdf -g mydg set mode acp_disk : Set syncing mode to Adaptive Copy.
symrdf -g mydg query : Query the device group.
symrdf -g mydg split : Split the dynamic srdf pair.
symrdf -sid 1234 -rdfg 3 -file rdf.txt deletepair.txt -force : Delete the srdf pairing between R1/R2 and return them to normal.

symdisk

symdisk -sid 1234 list -hotspare : Lists the Hotpsraes configured in the array.
symdisk -sid 1234 list -by_diskgroup : Dispalys all the disks in the array by grouping by disk groups.
symdisk -sid 1234 list -diskg_roup 1 : Dispalys all the disks in disk group 1.

Mainframe 之间的文件传输

2010-06-04T14:31:00.000+09:30

Mainframe之间的文件传输
Hunter Zhou

概述

Mainframe主机系统之间的文件传输方式很多。下面的方法适应于 MVS, OS/390和Z/OS系统。
最常见的有以下几种情况：
1、两个系统在同一个Sysplex中。
2、两个系统共享磁盘。
3、两个系统相互独立。

下面分别就每种方式的文件传输加以介绍。

两个系统在同一个Sysplex中

这两个系统共享同一个Catalog，所有文件都是共享的，所以不存在文件传输的问题。

两个OS/390系统共享磁盘

方法一

假如两个系统是彼此独立，但是共享磁盘，而且各自有不同的磁盘卷 (VOLSER)和Catalog name。

这种情况下可以使用Import Catalog的方法来拷贝文件：
1、将目的系统的Ｃａｔａｌｏｇ卷Ｏｎｌｉｎｅ
２、ＩＭＰＯＲＴ目的系统的Ｃａｔａｌｏｇ
３、利用ＤＳＳ拷贝文件
４、ＥＸＰＯＲＴ目的系统的Ｃａｔａｌｏｇ
５、将目的系统的Ｃａｔａｌｏｇ卷Ｏｆｆｌｉｎｅ

下面的例子将生产系统的IODF文件(VSAM)拷贝到测试系统。IODF文件存在于Master Catalog中。
该作业在生产系统上执行。

//*********************************************************************
//* VARY THE MASTER CATALOG VOLUME OF TEST SYSTEM ONLINE              
//*********************************************************************
//ONLINE  EXEC PGM=IKJEFT01,PARM='VARY 2102,ONLINE'                   
//SYSEXEC  DD DISP=SHR,DSN=SYS1.USER.CMDPROC                          
//SYSTSPRT DD SYSOUT=*                                                
//SYSTSIN  DD DUMMY                                                   
//*********************************************************************
//* IMPORT TEST SYSTEM MASTER CATALOG TO PRODUCTION SYSTEM.           
//*********************************************************************
//IMPTMCAT EXEC PGM=IDCAMS                                            
//SYSPRINT DD SYSOUT=*                                                
//SYSIN    DD *                                                       
 IMPORT CONNECT OBJECTS((SYS1.TEST.MASTCAT  -                        
        VOLUMES(TSTMCT) DEVICETYPE(3390)))                          
/*                                                                    
//*********************************************************************
//* COPY THE PRODUCTION IODF DATASET FROM PRODUCTION TO TEST SYSTEM.  
//*********************************************************************
//COPYIODF EXEC PGM=ADRDSSU                                           
//SYSPRINT DD  SYSOUT=*                                               
//SYSIN    DD  *                                                      
 COPY DATASET(INCLUDE(SYS1.IODF00.CLUSTER)) -                        
      INDYNAM(SYSMCT) OUTDYNAM(TSTMCT) -                             
      RECAT(SYS1.TEST.MASTCAT) TOL(ENQF) REPLACE                     
/*                                                                    
//*********************************************************************
//* EXPORT TEST SYSTEM MASTER CATALOG FROM PRODUCTION SYSTEM.         
//*********************************************************************
//EXPTMCAT EXEC PGM=IDCAMS                                            
//SYSPRINT DD SYSOUT=*                                                
//SYSIN    DD *                                                       
   EXPORT SYS1.TEST.MASTCAT DISCONNECT                               
/*                                                                    
//*********************************************************************
//* VARY TARGET MASTER CATALOG VOLUME OFFLINE                         
//*********************************************************************
//OFFLINE  EXEC PGM=IKJEFT01,PARM='VARY 2102,OFFLINE'                 
//SYSEXEC  DD DISP=SHR,DSN=SYS1.USER.CMDPROC                          
//SYSTSPRT DD SYSOUT=*                                                
//SYSTSIN  DD DUMMY

方法二

对于不需要Ｃａｔａｌｏｇ的文件，例如Sequential, PDS等类型文件，也可以使用共享卷来拷贝。
不共享Ｃａｔａｌｏｇ的系统可以使用一个共享卷，该卷在两个系统同时Ｏｎｌｉｎｅ．

下面的拷贝的步骤：
１、在第一个系统，将文件先拷到共享卷上。
２、在第二个系统，将文件从共享卷拷走。
３、在第一个系统，将共享卷上的文件删除。

两个相互独立的OS/390系统

下面主要介绍当两个系统不共享磁盘，例如两个单位的不同主机系统的情况下的文件传输。
这里是大概的步骤：
第一，将要拷的文件用DSS打包到一个文件中，有点像WinZIP。
第二，用TSO XMIT命令将该文件转换成可以传输的格式。
第三，将该文件传到另外一个ＯＳ/390系统上。
第四，用TSO RECEIVE命令将该文件还原为DSS格式。
第五，用DSS将文件还原。

这里是作业的实例：

首先，将要拷的文件用DSS打包到一个文件中

用DSS的好处是同时可以拷多个不同格式的文件，而且使用压缩来节省磁盘。
下面的例子将文件打包到文件SP2487.FILE.DUMP中。

//DELETE  EXEC PGM=IDCAMS                                  
//SYSPRINT DD SYSOUT=*                                     
//SYSIN    DD *                                            
 DELETE SP2487.FILE.DUMP                                  
 IF LASTCC<=8 THEN SET MAXCC=0                            
//*                                                        
//BACKUP  EXEC PGM=ADRDSSU,COND=(0,NE)                     
//SYSPRINT DD SYSOUT=*                                     
//DUMPDS   DD DISP=(NEW,CATLG),
//         UNIT=SYSDA,RECFM=U,LRECL=32760,
//         SPACE=(CYL,(100,100),RLSE),        <--- CHANGE
//         VOL=SER=SYSWRK,                    <--- CHANGE
//         DSN=SP2487.FILE.DUMP               <--- CHANGE
//SYSIN    DD *                               <--- CHANGE
 DUMP DATASET(INCLUDE( -                                  
      SYS1.IPLPARM                           -            
      SYS1.PARMLIB                           -            
      SYS1.TCPPARMS                          -            
      SYS1.USER.**                           -            
      SP2487.ZHOUGH.JCL                      -            
      SP2487.ZHOUGH.REXX                     -            
      SP2487.ASM.**                          -            
      )) -                                                
      OUTDDNAME(DUMPDS) -                                 
      TOLERATE(ENQF) -                                    
      COMPRESS                                            
/*

第二，用TSO XMIT命令将该文件转换成可以传输的格式

使用ＴＳＯ的ＴＲＡＮＳＭＩＴ命令将该ＤＳＳ　ＤＵＭＰ文件转换成ＸＭＩＴ格式。
１、在ＩＳＰＦ中，使用=6命令到ＴＳＯ命令提示中。
２、使用下面命令:
xmit jes2node.userid dataset('source.dataset') outdsn('xmitout.dataset')

下面是该命令的注释:

参数	参数描述
jes2node	这是你当前系统的ＪＥＳ２　ＮＯＤＥ　Ｎａｍｅ．　通过下面的方法得到你的ＪＥＳ２　ＮＯＤＥ　Ｎａｍｅ：到ＳＤＳＦ中，使用ｎｏｄｅ命令，(例如=S;NODE)，或者使用ＭＶＳ命令$D NODE Ｓｔａｔｕｓ属于ＯＷＮＮＯＤＥ的NodeName就是你当前系统的ＪＥＳ２　Ｎｏｄｅｎａｍｅ. 例如PRODSYS1 SDSF NODE的输出示例： `------------------------------------------------------------------------------- SDSF NODE DISPLAY SYS9 OSHAWA1 N1 LINE 1-5 (5) COMMAND INPUT ===> SCROLL ===> CSR NP NUMBER NodeName Status Authority Trans Recv Hold N1 PRODSYS1 OWNNODE (D=Y,J=Y,N=N,S=Y) BOTH BOTH NONE N2 TESTSYS1 UNCONNECTED (D=Y,J=Y,N=N,S=Y) BOTH BOTH NONE N3 N3 UNCONNECTED (D=Y,J=Y,N=N,S=Y) BOTH BOTH NONE N4 N4 UNCONNECTED (D=Y,J=Y,N=N,S=Y) BOTH BOTH NONE N5 N5 UNCONNECTED (D=Y,J=Y,N=N,S=Y) BOTH BOTH NONE` JES2 命令'$D　NODE'的输出示例： Display Filter View Print Options Help ------------------------------------------------------------------------------- SDSF SYSLOG 4317.101 OFD1 OFD1 04/25/2005 0W 29334 COLUMNS 1 80 COMMAND INPUT ===> /$D NODE SCROLL ===> CSR $HASP826 NODE(1) 886 $HASP826 NODE(1) NAME=PRODSYS1,STATUS=(OWNNODE), $HASP826 AUTH=(DEVICE=YES,JOB=YES,NET=NO,SYSTEM=YES), $HASP826 TRANSMIT=BOTH,RECEIVE=BOTH,HOLD=NONE, $HASP826 PENCRYPT=NO,ENDNODE=NO,REST=0,SENTREST=ACCEPT, $HASP826 COMPACT=0,LINE=0,LOGMODE=,LOGON=0, $HASP826 PASSWORD=(VERIFY=(SET),SEND=(FROM_OWNNODE)), $HASP826 PATHMGR=YES,PRIVATE=NO,SUBNET=,TRACE=YES
ｕｓｅｒｉｄ	这是你当前使用的TSO用户名，例如SP2487。
source.dataset	这是你要转换的源文件名, 例如SP2487.FILE.DUMP。
xmitout.dataset	这是经XMIT转换以后的文件名称, 例如SP2487.FILE.XMIT。

例子：
xmit prodsys1.sp2487 dataset('sp2487.file.dump') outdsn('sp2487.file.xmit')

注意XMIT生成的文件的属性是： RECFM=FB,LRECL=80,BLKSIZE=3120 。在另一个系统上的XMIT文件一定要有与此相同的文件属性。

第三、将该文件传到另外一个ＯＳ/390系统上

两个系统在同一个网络中

当两个系统在同一个网络中时，最常用的方法是利用FTP。
下面是从源系统执行FTP命令的例子：
=6到ISPF的TSO命令行，执行下面FTP命令：

ftp os390s2.company.com
tso tsouser
password
put 'sp2487.file.xmit' 'hunter.file.xmit'
quit

这个FTP命令会把源文件的属性传给目标文件。

两个系统在不再同一个网络中
1、用FTP将该文件从OS/390上传到你的PC上，刻一个CD或软盘。
此时注意要使用BINARY的方式下载源文件：

ftp os390s1.company.com
tso tsouser
password
binary
get 'sp2487.file.xmit' c: empdssdump.xmi
quit

2、将该CD或者软盘上的文件上传到另一个OS/390上。
使用下面的FTP命令将PC上的文件传到主机上：
ftp os390s2.company.com
tso tsouser
password
binary
quote site RECFM=FB LRECL=80 BLKSIZE=3120
quote site CYLINDERS PRIMARY=100 SECONDARY=100
put c: empdssdump.xmi 'hunter.file.xmit'
quit

第四，用TSO RECEIVE命令将该文件还原为DSS格式

在目的系统上，使用下面的命令将XMIT文件还原为DSS 的DUMP文件:

receive indsn('hunter.file.xmit')

dataset('hunter.file.dump')

这样，DSS文件就恢复到了目的系统上。

第五，用DSS将文件还原

在目的系统上，你可以使用下面的作业将DUMP文件中的所有文件恢复到目的系统上。

//**************************************************
//RESTORE EXEC PGM=ADRDSSU                         
//SYSPRINT DD SYSOUT=*                             
//DUMPFILE DD DISP=SHR,DSN=HUNTER.FILE.DUMP        
//DASD     DD DISP=OLD,UNIT=SYSDA,VOL=SER=TSTMCT   
//SYSIN    DD *                                    
 RESTORE DATASET(INCLUDE(**)) -                   
      INDDNAME(DUMPFILE) -                        
      OUTDDNAME(DASD) -                           
      CATALOG                                     
/*

很多时候由于两个系统的HLQ(Higher Level Qualifier, 第一级文件名) 定义不一致。这时需要将一些文件的HLQ改名，可以使用下面的作业：

//**************************************************
//RESTORE EXEC PGM=ADRDSSU                         
//SYSPRINT DD SYSOUT=*                             
//DUMPFILE DD DISP=SHR,DSN=HUNTER.FILE.DUMP        
//DASD     DD DISP=OLD,UNIT=SYSDA,VOL=SER=TSTMCT   
//SYSIN    DD *                                    
 RESTORE DATASET(INCLUDE(SP2487.**)) -            
      RENAMEU(HUNTER)  -                          
      INDDNAME(DUMPFILE) -                        
      OUTDDNAME(DASD) -                           
      CATALOG                                     
/*

在此例子中，作业将所有以SP2487开头的文件(或者HLQ为SP2487)的文件恢复，并将他们的HLQ改为HUNTER。

总结
以上总结了在不同情况下，在两个Mainframe系统之间进行文件传递的方法。

Hercules vs ADCD and DEMOpkg

2010-06-04T13:55:00.000+09:30

谈及Hercules，一般就会谈及ADCD（http://www-304.ibm.com/jct01005c/isv/zseries/adcd.html）和DEMOpkg。。他们都是什么呢，其实顾名思义，ADCD是Application Developer的CD，而DEMOpkg是IBM给客户做DEMO用的pkg

区分你手里的Hercules是基于ADCD还是DEMOpkg的最好办法是看卷名，这是ADCD的系统卷典型卷名（粗体）
zares1 RES Volume 1 – Required for IPL
zares2 RES Volume 2 – Required for IPL
zasys1 System volume 1 – Required for IPL
zauss1 UNIX Services Volume 1 – Required for IPL
zaprd1 Product target Libraries – Required to run selected products
zaprd2 Product target Libraries – Required to run selected products

而DEMOpkg的如下

# System Volumes
device 0100 3390 3990 /zdemopkg/zOS/DMTRES
device 0101 3390 3990 /zdemopkg/zOS/DMTCAT
device 0102 3390 3990 /zdemopkg/zOS/DMTOS1
device 0103 3390 3990 /zdemopkg/zOS/DMTOS2
device 0104 3390 3990 /zdemopkg/zOS/DMTOS3
device 0105 3390 3990 /zdemopkg/zOS/DMTOS4

仅从容量上来看，2008 2Q的DEMOpkg 1.9就8个DVD了，而ADCD最新的2008 Winter 1.10的只有5个DVD，二者都带了zos的主流产品，包括DB2，WAS等，貌似DEMOpkg带的内容要多，主要是Rational，Tivoli和IM tools，我前段时间的项目和Rational的产品有不少关系，这是我选择DEMOpkg的主要原因，而ADCD看起来更精选些，或许更适合大家。此外，ADCD的网站有各种配置等介绍，也要方便不少。当然我要的就是一个大而全而已……至于如何获得ADCD或者DEMOpkg，请参照ADCD网站

现在新版的ADCD和DEMOpkg的卷都是基于3390-3的……关于卷的大小，可以参看IBM Mainframe Disk Capacity Table（http://sdisw.com/vm/dasd_capacity.html），简单来说，每个3390-n的卷，就是n个GB……感谢现在个人电脑硬盘容量的飞速发展，和大型机的差距毕竟缩小了很多。。所以如果你的PC有3G以上的 RAM（貌似Hercules IPL卷有多大，就要占多大RAM），以及250G以上的剩余硬盘空间（相信2011年来看吧这篇文章的时候大家都没啥问题），你所需要做的事情只是将这几张DVD里面的卷文件全部解压到一个目录下就可以了（2011年的朋友，现在蓝光标配了么？）

否则，只能牺牲下你台式机的CPU，将这些解压后再次转换为CCKD（以zip或者bzip进行压缩），旧版的Hercules带的 DASDCONV的程序可能无法支持3390-3的大卷文件，3.06的肯定没问题，不过新版的Hercules改用DASDCOPY进行复制和转换了，用法很简单，命令行或者HercGUI里操作都很傻瓜，就不详细介绍了

如何在自己的PC上建立的IBM主机系统

2010-05-29T22:14:00.008+09:30

http://www.efglobe.com/modules.php?name=News&file=article&sid=19

http://fandezhi.efglobe.com/modules.php?name=Forums&file=viewtopic&t=2385&sid=dc4e27bd341c20e5dbd4a66368aac299

http://www.dzxr.com/2009/03/demopkg-z-os-19-on-hercules-4-customize-their-zos

IBM主机系统可以借助仿真软件Hercules 在你的PC上面运行。在安装主机系统之前，你必须遵循IBM对于主机软件的有关规定。

有些操作系统是可以免费在Hercules上运行的。请参照有关在PC上运行主机操作系统的说明：
http://www.conmicro.cx/hercules/hercfaq.html#2.02

现在假设你是IBM Employee或者代理, 你手头有OS/390或者Z/OS的Demopkg的软件。下面介绍如何在PC上安装OS/390 DemoPkg.

第一步，下载Hercules 软件，到下面网站下载：
http://www.conmicro.cx/hercules/

第二步，下载Cygwin软件，到下面网站下载∶
http://www.cygwin.com/

第三步,下载TCP/IP支持软件，
Hercules CTCI-W32
WinPCap
FishPack-1.3.0.323-dll.zip
TunTap32-2.0.3.379-dll.zip
tt32info-1.0.2.133-exe.zip
到下面网站去下载：
http://www.softdevlabs.com/Hercules/ctci-w32-index.html

第四步，解压缩Demopkg光盘中的所有3390卷。用Unzip或者Winzip搞定。
假若你想省磁盘空间，用Hercules的cckd2ckd或者dasdcopy命令压缩成CCKD格式。

第五步，配置Hercules.cnf, 参照下面网站:
http://www.conmicro.cx/hercules/hercconf.html

第六步，安装3270仿真软件。看看下面得志的网站所列可下载的软件：
http://fandezhi.homedns.org/modules.php?name=Downloads&d_op=viewdownload&cid=1

当你安装和配置好以上软件后，你就可以起你的主机了。

下面只执行的步骤：
1、执行Hercules。
Hercules 相当于主机CPU。你可以在PC上建立下面的批处理文件HERCONS.CMD来运行它:

例如：Windows 下HERCONS.CMD:
@echo off
C:
chdir C:cygwin in
bash --login -i "/usr/local/bin/hercules -f /cygdrive/c/OS390/hercules.cnf"

2、运行3270仿真软件, 配置成TN3270, Local host, port 3270.
一般运行至少有3个terminal，两个为MVS console, 一个为3270terminal.

3、IPL
在Hercules命令行执行ipl 1c0

4、回答IPL Message

5、登陆TSO. User SYSPRG1/SYSPRG1

下面是Hercules配置文件HERCULES.CNF范本：

# Sample configuration file for Hercules ESA/390 emulator
CPUSERIAL 01C5D1 # CPU serial number
CPUMODEL 2064 # CPU model number
MAINSIZE 256 # Main storage size in megabytes
CODEPAGE default # CodePage conversion table
XPNDSIZE 0 # Expanded storage size in megabytes
CNSLPORT 3270 # TCP port number to which consoles connect
HTTPPORT 8088 noauth userid password # HTTP server port
HTTPROOT C:/CYGWIN/usr/local/share/hercules/ # base directory for built-in web server
NUMCPU 1 # Number of CPUs
LOADPARM 01C1DP.1 # IPL parameter LOADDP FOR BASE SYSTEM
OSTAILOR OS/390 # OS tailoring
TZOFFSET +0000 # TOD clock offset
PANRATE SLOW # Panel refresh rate
PGMPRDOS LICENSED # LICENSED OS/390 V2R9
ARCHMODE ESA/390 # Architecture mode S/370, ESA/390 or ESAME
CCKD CACHE=24 # CCKD CACHE SIZE IN MB

# .-----------------------Device number
# | .-----------------Device type
# | | .---------File name and parameters
# | | |
# V V V
#--- ---- --------------------
01c0 3390 C:OS390VOLUMESdmtres.1c0
01c1 3390 C:OS390VOLUMESdmtcat.1c1
01c2 3390 C:OS390VOLUMESdmtos2.1c2
01c3 3390 C:OS390VOLUMESdmtos1.1c3
01c4 3390 C:OS390VOLUMESdmtd01.1c4
01c5 3390 C:OS390VOLUMESdmtd02.1c5
01c6 3390 C:OS390VOLUMESdmtd03.1c6
01c7 3390 C:OS390VOLUMESdmtp01.1c7
01c8 3390 C:OS390VOLUMESdmtp02.1c8
01c9 3390 C:OS390VOLUMESdmtp03.1c9
01ca 3390 C:OS390VOLUMESdmtos3.1ca
01cb 3390 C:OS390VOLUMESdmtd04.1cb
#Master Console Address must be 0463
0461 3270
0463 3270
#LOCAL 3270 TERMINAL
0470 3270

# TCP/IP CTCI Ports, emulate 3 network adapters.
# OS/390 IP PC's IP
0530-0531 3088 CTCI 172.15.1.144 172.15.1.143
0532-0533 3088 CTCI 192.168.1.68 192.168.1.66
0534-0535 3088 CTCI -n 00-06-5B-E2-D9-4C 169.254.1.68 0.0.0.0

系统怎么正常关闭

先使用下面的命令停掉一般的任务：

S SHUTDOWN

使用D A,L确认仍然在运行的任务，不记得是不是VTAM是否会自动停掉，如果没有，使用下面的命令：

Z NET,QUICK

最后使用下面的命令停掉JES2：

$P JES2,TERM

之后在Hercules上输入STOP停止模拟机。

之后,可以使用下面的几个命令：
1、输入EXIT退出Hercules, 可能要等一会儿。
2、输入LOADPARM 来改变IPL 参数，以便以不同的配置重新起动系统。
例如:

LOADPARM 0A82ACM1

3、使用命令IPL A80来重新启动系统。
你的3270仿真软件(MVS Console)应该不需要重新连接。

# A VMware Virtual appliance to enable Mainframe Server Virtualisation on an x86 Platform
http://www.vmware.com/appliances/directory/369

使用了Hercules -f zos.cfg之后在最后你如果你看到21:13:32 ** tt32_loaddll: LoadLibraryEx("TunTap32.dll") failed; rc=14001: 由于应用程序配置不正确，应用程序未能启动。重新安装应用程序可能会纠正这个问题。 21:13:32 ** tt32_loaddll: LoadLibraryEx("TunTap32.dll") failed; rc=14001: 由于应用程序配置不正确，应用程序未能启动。重新安装应用程序可能会纠正这个问题。 21:13:32 HHCTU002E Error opening TUN/TAP device: 00-00-5E-80-00-00: No error 21:13:32 HHCCF044E Initialization failed for device 0E21

相信很多朋友配置CTCI的时候都遇到这个问题。我也为这个问题郁闷了很久了……
就我而言，用的CTCI-W32_3.2.1.160 、hercules-3.05、wincap3.1 和或者4.0，老是加载不上TUNTAP32.DLL。后来ELVIS找到了这个问题的解决方法，就是下载安装vcredist_x86.exe 这个VS2005的SP1补丁就OK……这里再次感谢Elvis……

FreeNAS, Openfiler

2010-05-21T07:34:00.001+09:30

FreeNas
http://www.verycd.com/topics/2814320/

http://linuxce.spaces.live.com/blog/cns!46EAC5B4D6FF6B5D!598.entry)

Chameleon USB-Stick information for EFI based BIOS

2010-05-06T14:28:00.006+09:30

There are 3 different bootloaders: PC-EFI v10.5, Chameleon v2.0 RC4, RC3 or Chameleon v1.0.12
PC-EFI:
http://netkas.org/

Chameleon project: 变色龙
http://chameleon.osx86.hu/

都有EFI欺骗功能，（fake EFI）

1.device-properties string 更灵活（支持换行、tab、空格）
2.不管是MBR还是GUID的分区，使用统一的 boot0/boot1h，而PC_EFI针对MBR和GUID则有着分别对应的代码，这使得DVD的制作和用户的使用变得麻烦。（太酷了！）
3.boot0甚至可以引导未激活的HFS+主分区，而PC_EFI做不到。
4.cdboot也已经可用，完美工作于连接在JMicron芯片上的IDE DVD。而PC_EFI没有???（原文：you can’t get cdboot with PC_EFI.）(不对吧？那我们之前用的这些破解的DVD的boot代码都是谁的？) DVD的制作者将会happy，它使我们 life easy!(的确！这是实话！)
5.支持操作系统级别的Soft RAID，PC_EFI不行。
6.不再需要用startupfiletool来将stage2的boot嵌入你的分区（即论坛里所谓的“可见的第二引导”）；取而代之的仅仅是将 ‘boot’这个文件copy 到你要引导的分区的根目录；且boot1h将仍然兼容startupfile的loading的方法。

安装步骤不需要翻了吧！
* Installation takes only 3 steps:
Suppose that your installation is on /dev/disk0s2
1. Install boot0 to the MBR:
fdisk -f boot0 -u -y /dev/rdisk0
2. Install boot1h to the partition’s bootsector:
dd if=boot1h of=/dev/rdisk0s2 bs=512 count=2
3. Install boot to the partition’s root directory:
cp boot /

忘了说，变色龙有DMG版本的，可以直接使用……不用这么麻烦……
下载见此贴 http://bbs.pcbeta.com/viewthread.php?tid=307592&extra=&page=1

安装变色龙到EFI分区

当初安装变色龙的时候就是不知道如何装到EFI分区里边去，我把EFI分区mount进来以后，在选择安装分区时还是看不到EFI分区，搞得我不得不手动安装efi_boot_v5_1这个东东，后来仔细看变色龙的每一步安装，终于找到了那个选项，其实都怪我没对EFI分区理解好，

http://aserebln.blogspot.com/2009/10/6-106-prepare-chameleon-usb-stick.html

rebel_efi:
http://store.psystar.com/rebel_efi

Reverse Project: --- interesting.
http://refit.sourceforge.net/

Modify BIOS for Multi-cores support:
http://www.insanelymac.com/forum/lofiversion/index.php/t90505.html

Avamar useful commands

2010-04-30T15:19:00.008+09:30

1. Show services status:
mccli server show-services
mccli server show-prop

2. Check if GC runs,

grep "Elapsed time\|Total bytes" /usr/local/avamar/var/cron/gc.log | tail -30

3. Restore from command line
A.) using avtar ....
1.) to list all backups
avtar --backups --id= --path= --hfsaddr= --after=YYYY-MM-DD --quiet
1.1) To list detail
avtar --verbose --list --id= --path=

2.) avtar --extract --label=<"Label_Name"> --id= --path= --target=<"DESTINATION_TARGET_NAME"> <"FILE_YOU_WANT_TO_RESTORE">

B.) or involving "mccli"
1.) list all the backups on the Avamar server, of the mccli doesn't work, use avtar.
# mccli backup show --name=/XXXDomain/ClientName

2.) to restore the backup from specific client with specific LabelNum to the destination target name
# mccli backup restore --labelNum= --plugin= --name=// --dest-dir=<"DESTINATION_TARGET_NAME">

Live Upgrade - luactivate and OBP

2010-03-05T20:43:00.005+10:30

LiveUpgrade from Solaris 9 to Solaris 10

Here's how to leverage LiveUpgrade to safely upgrade from Solaris 9 to Solaris 10 using a spare disk. No data is ever deleted, and to roll back to Solaris 9, all you need is one command and a reboot.

Let's continue on from the example in Unmirroring a RAID 1 Root Volume on Solaris - we have two disks, c1t0d0 and c1t1d0. c1t0d0 is our Solaris 9 disk, c1t1d0 is our spare.
Phase One: Prepare the Solaris 9 environment

First, we need to prepare the Solaris 9 environment with some packages and patches. First, check out Sun's InfoDoc 206844 and make sure you have all of the patches required installed.

Next, for LiveUpgrade to work properly, you need to install the LiveUpgrade packages from your Solaris 10 install media to your Solaris 9 box. First, remove the existing packages:

pkgrm SUNWlucfg SUNWluu SUNWlur

Then, install the new packages from your Solaris 10 media (if you're using CD's, it's on disc 2):

cd $SOLARIS10MEDIA/Solaris_10/Tools/Installers
./liveupgrade20

Next, let's copy the disk label from c1t0d0 over to c1t1d0 giving us the exact same disk layout on the new disk as the old disk:

prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2

We now have all the prep work done for getting ready for our LiveUpgrade. Now, we need to create our boot environment.
Phase Two: Create the New Boot Environment

First, let's make some assumptions. Since we're upgrading from Solaris 9 to Solaris 10, we'll be upgrading from UFS to UFS file systems. Also, since we are upgrading from one disk to another, we will copy all filesystems from c1t0d0 to c1t1d0 - no filesystems will be shared.

In order to create our new boot environment, we will use the 'lucreate' command. Let's define some variables:
Flag Description
-c Sets the current boot environment name to this name. In this example, we use Solaris9
-n Sets the newly created environment's name to this name. In this example, we use Solaris10
-m The -m option is the most critical part of the lucreate command. It specifies the filesystems in the new environment. To create more than one filesystem, you use the -m flag more than once. By using different variations on the -m flag, you can reorganize, resize, and merge filesystems, but that's beyond the scope of this article. The value to the -m flag is: mountpoint:device:fs_options. From the previous example in Unmirroring a RAID 1 Root Volume on Solaris, we have 5 filesystems: /, /usr/local/, /apps, /export/home/, and swap.

Using the above options for our scenario, we end up with:

lucreate -c Solaris9 -n Solaris10 -m /:/dev/dsk/c1t1d0s0:ufs -m -:/dev/dsk/c1t1d0s1:swap \
-m /usr/local:/dev/dsk/c1t1d0s3:ufs -m /export/home:/dev/dsk/c1t1d0s4:ufs \
-m /apps:/dev/dsk/c1t1d0s5:ufs

Depending on the number and size of files in your source boot environment, this may take awhile. The lucreate process gives you output for each step, letting you know what it's doing.
Phase Three: Upgrade the New Boot Environment to Solaris 10

Now that phase two is done, we have a bootable copy of our current Solaris 9 environment. Now, we need to apply the upgrade to Solaris 10 to our new boot environment. For simplicity, I have an exported Solaris 10 install DVD extracted on another server that I use the automounter to access.

Now, we'll run the 'luupgrade' command and tell it to install the upgrade to the new boot environment we just created:

luupgrade -u -n Solaris10 -s /net/install.mydomain.com/export/jumpstart/install/sparc_10

Again, this will take some time, and the process will give you output as it clicks along.
Phase Four: Mark the New Boot Environment as Active and Boot Into It

Now, our Solaris 10 boot environment actually has a copy of our Solaris 9 environment with the upgrade to Solaris 10 within it. To boot into that environment, we need to mark it as active, and reboot. These instructions cover SPARC machines, for x86/x64, see the Sun documents referred in the summary of this article - there are a couple of differences.

To make our new boot environment active, we'll use the 'luactivate' command:

luactivate Solaris10
init 6

Should something not go completely right during the upgrade, you can roll back to your previous boot environment simply by specifying 'Solaris9' for 'Solaris10' in the above 'luactivate' command. If something really went wrong with the upgrade, and you didn't boot successfully, don't worry. The 'luactivate' command above should have given you some output that you should copy/paste someplace. Here's an example:

In case of a failure while booting to the target BE, the following process
needs to be followed to fallback to the currently working boot environment:

1. Enter the PROM monitor (ok prompt).

2. Change the boot device back to the original boot environment by typing:

setenv boot-device disk:a

3. Boot to the original boot environment by typing:

boot

If that doesn't do it, see the Sun docs in the summary of this article, they will coach you through booting off the CD/DVD and reactivating the old environment.
Summary

As an admin coming from Linux, the LiveUpgrade suite is a breath of fresh air for giving you an easy upgrade path that's just as easy to undo as it is to do. We've only begun to scratch the surface of what you can do with LiveUpgrade. You can use it to migrate from a UFS root to a ZFS root, use it to install and test patches, install Flash Archives with it, reconfigure and resize partitions, and on and on. For a much more comprehensive look into what all LiveUpgrade can do, check out the Solaris Live Upgrade and Upgrade Planning guide on http://docs.sun.com - the current release is for Solaris 5/09.

***************************************
Issues and the fixes,

Useful commands:
lustate
lufslist "BE Name"

1. If luactivate not works on init 6.

The solution to this rather strange problem:
It was not booting due to an OBP setting on the server.

The diag-switch must be set to false, otherwise the system will not boot on the new environment.

eeprom diag-switch?


diag-switch?=false

2.

If reports the packages that failed to install, especially the "SUNWcsr".

--- mount the BE to a mount points
--- mount the CDROM, the binaries can be found under /cdrom/Solaris_10/Product/ folder.
--- Using pkgadd -R (install to alternative Root_path) to re-install the failed packages
--- You may need copy some version 10 binaries to verson 9 folders to fix some pkgadd errors, such as : /usr/sbin/svccfg

Property information.

2010-01-29T10:59:00.000+10:30

Report:

http://onthehouse.yahoo.com.au/buy/property/30209709

PDF证书加密破解

2010-01-18T16:23:00.002+10:30

软件准备（一定要是比这些版本高级的最新版本）：
1.Adobe Acrobat 9 Pro 完美中文绿色版
2.Foxit PDF Editor 2.1build0119 汉化版
3.FoxitPDF Reader Pro 3.0 汉化版

首先，本文只以大家网（www.topsage.com）为例，其他的相信大家可以举一反三的，
一般下载的压缩包里面有加密的PDF、使用说明.doc和topsage.pfx三种文件。
1、解压安装topsage证书。双击安装topsage证书，一直点击下一步，并且提示输入已知的请键入身份证
口令(口令是：www.topsage.com)，一般在使用说明doc文件里面提供了，直到完成(这时候应该能看这
pdf，但不能修改和打印)；
2、下载解压安装foxit pdf editor 2.1 build0119，并且打开pdf文件，（其实在foxit pdf editor
2.1打开的pdf是已经能够打印修改保存了的，但是水印还在）；
3、使用foxit pdf editor 2.1打开加密的pdf文件，在菜单栏中选择“文档”-----“导出页面”-----
选择“输出目录”和导出页面的页码范围，例如“1-800”-----点击“确定”；
4、用Adobe Acrobat 9 Pro打开刚才导出的PDF文件，在菜单栏中选择“文档”-----“页眉和页脚”/“
背景”/“水印”，选择其中一个需要的----点击“删除”，即可清除logo和水印了。（其实在foxit
pdf editor 2.1也可以逐个删除，不过太麻烦，机器人重复的劳动，我也曾经试过用“按键精灵”来自
动点击这种重复劳动，哈哈~~~）
5. ok，大功告成！Enjoy 这个绿色完美的PDF文档吧~~~~证明了一句话，最原始才是最美的

_____________________________________
PDF证书加密级文件如何解密？

问题：我需要打印PDF文件，但是这些文件都经过加密，无法打印。而且加密方式是证书形式，不是普通的密码。常用的那些破解软件对于证书级加密全部无效。
解答：破解分两个步骤（实际上根据需要只要做第一步就基本可以了），当然，破解的前提是你已经可以用adobe reader打开PDF文件了，也就是说你已经有了证书了，只是除了查看之外其他功能都被禁用了，如果你连你的这个pdf文档从哪里下载来的以及怎么打开怎么使用证书之类的都不知道的话，那我就彻底无语了。。。。。。
1.用Foxit PDF Editor (PDF文件编辑，可以上百度搜索下载) 打开需要破解的PDF文件,然后选择“文档”--“导出页面”导出所要的页面（我一般是将所有页面都导出来，如这个PDF文件有100页，就填写 1-100）这样导出来的文件就基本上已经被破解，解除了打印啊等等其他限制了。
2.然后用Arcobat（建议用8.0以上版本，注意是 arcabat哦，不是adobe reader，至于两者的区别大家可以百度一下，多了解，基本上Arcobat的功能涵盖了adobe reader的功能，要强大很多）打开导出的PDF，用PDF打印机打印，这样就完全解除证书限制。
Foxit PDF Editor 的下载可以百度搜索最新的版本，一般可以到www.crsky.com这个站点去下载

关于pdf文件识词
pdf阅读：建议使用adobe acrobat 7.0Professional简体中文版（只有专业版本才有ocr功能，而reader版本没有ocr，而且同以前版本比较打开速度快，无专利认证那套东东，文件大小209M吧。以下简称“Acrobat 7.0 pro”）

注意：在安装acrobat 7.0 pro的时候要选择完全安装或者自定义安装选择安装上
“亚洲语言支持”，因为在“典型”安装时是不安装“亚洲语言支持”的，这在看中文的时候可能有影响。
针对电子词典：金山词霸2003医学版（以下简称“金山”）
新医药大词典（以下简称“新医药”）
1.所有的pdf文件都不能识词
或者在“金山”和“新医药”都安装的情况下，用其中一个可以识词，另外一个不能识词，
可以肯定是插件问题。
对于金山
AcrobatReader 7.0取词：将金山词霸的安装目录下(*:\Program Files\Kingsoft\Powerword2003\PlugIn *代表你所安装到的盘符，以下同)的Xdict32.API复制到Adobe Reader7.0的安装目录*:\Program Files \Adobe\Acrobat 6.0Reader\plug_ins 文件夹下即可。
Acrobat 7.0取词：将金山词霸的安装目录下的Xdict32.API复制到Adobe 7.0的安装目录*:\Program Files\Adobe\Acrobat 7.0\Acrobat\plug_ins文件夹下即可。
如果上述办法仍然无法加入词霸的插件（Acrobat工具栏没有出现词霸的图标），则请到在中文版acrobat 7.0pro中设置如下：选择"编辑"菜单中的"首选项"，在弹出的界面的左侧列表中选中"启动"一项，然后在"启动"面板中将"仅认证增效工具"前的选项去掉，再将右下角的浏览方式设为单页,最后重启Acrobat reader即可。（好像acrobat 7.0pro默认的就是去掉的估计这项用不着，Acrobat Reader 7.0我没装不知道）
6.0版把7.0换成6.0即可。

对于新医药
一般情况下，《新编全医药学大词典》在安装时会将自己的一个插件自动添加到acrobatreader中去,用户安装词典后即可在pdf文件中使用词典,但是正确添加插件的前提是acrobatreader是正常安装的,即注册表中有acrobat reader的安装路径。不能取词，可能是注册表中没有acrobatreader的安装路径,需要手工添加词典的插件到acrobat reader中
解决办法：
第一步：首先找到词典的安装路径,例如默认安装路径,*\program files\kingyee\meddic\ 找到meddic文件夹中的plugin文件夹打开,里面有三个文件：RwAcrob4c.api,RwAcrob5c.api,RwAcrob6c.api;
如果是acrobat reader4.0就拷贝RwAcrob4c.api;
如果是acrobat reader5.0就拷贝RwAcrob5c.api;
如果是acrobat reader6.0就拷贝RwAcrob6c.api; （4，5，6没人用了吧）
如果是acrobat reader7.0也拷贝RwAcrob6c.api;
第二步：找到acrobat reader的安装路径,打开plug_ins文件夹,然后将拷贝的文件粘贴进来。然后重新启动acrobat reader软件。
第三步：此时一般就可以翻译pdf文件了。如果还是不行,就是acrobat reader还需要设置一下。
设置方法：
在中文版acrobat 7.0pro中设置如下：选择"编辑"菜单中的"首选项"，在弹出的界面的左侧列表中选中"启动"一项，然后在"启动"面板中将"仅认证增效工具"前的选项去掉，再将右下角的浏览方式设为单页,最后重启Acrobat reader即可（好像acrobat 7.0pro默认的就是去掉的估计这项用不着，Acrobat Reader 7.0我没装不知道）。

部分pdf文件可以识词，部分不可以。
把握一个原则：pdf文档内容只要可以复制就可以识词。
分以下两种情况：
A：有密码保护：有些虽有密码保护只是不准更改文档，可以复制，内容只要可以复制，就可以识词，就不用理什么密码了。
对不允许复制的就要用软件去出密码。
注意有些时候文件名比较长或有特殊字符或是中文，可能无法打开，此时将文件名改成数字的，如“1.pdf”（pdf为扩展名），处理完后再改回原来的文件名就可以了。
B：pdf文件是扫描图片做的，虽无任何限制，但无法复制文档内容。
这就要用到Adobe Acrobat Pro 7.0的ocr功能，图片格式的PDF可以直接转换成文字PDF，版面形式不变，转完后直接保存即可。
选择“文档”－－“使用OCR识别文本”
另外针对前面提到的密码保护的图片格式pdf文件，先去除密码后再ocr。（未去除密码前，ocr功能是灰色的不能用）。

另外有些从网站下载来的文献，会在页眉和页脚加上“Copyright”等字样，此时直接运用ocr时，会出现提示“acrobat无法在本页执行识别，因为：本页包含可渲染的文本”
针对以上情况，摸索出了一个方法：
先从“高级”－－“导出所用图像”（文中的插图也会按一张图片导出），然后再用

Choice of building materials

2010-01-09T13:01:00.001+10:30

Your choice of building materials can make a significant difference to the performance and comfort of your home. Dense materials such as brick, stone, concrete and rammed earth heat up and cool down slowly - they have what is called a high 'thermal mass'. Lightweight materials such as weatherboard and fibre cement allow the home to heat up and cool down quickly. These materials have a low thermal mass.

Thermal mass is simply the ability of a material to store heat. A 200 square metre home in the south west with good solar access to the north needs about 20 cubic metres of concrete and 20 to 30 cubic metres of internal brick or equivalent depending on your location (20 cubic metres for Geraldton and 30 cubic metres for Perth to Albany) to adequately store winter daytime warmth and gradually release it at night.

Thermal mass is most beneficial in homes which have good solar access to north facing windows. If solar access is limited, large amounts of thermal mass can increase your home's heating requirements during winter.

In summer, thermal mass can also help keep your home cooler during the day, provided you properly ventilate your home overnight. The aim is to allow the night air to cool down the mass inside your home, resulting in more comfortable conditions the next day.

Brick walls
Double brick walls heat up slowly and stay warm for long periods. This is an advantage during short periods of hot weather, but can make your home uncomfortable over extended hot spells. Insulating double brick walls will add to initial costs, but will help to prevent heat transfer to the interior of the home during summer and help to retain heat during winter.

Brick veneer walls consist of a single external layer of brickwork, with a lined stud frame inside. These walls have less thermal mass than double brick walls and therefore respond more quickly to temperature changes. Homes with brick veneer walls are better at cooling down during extended periods of hot weather - making conditions more comfortable at night during summer. Brick veneer walls are also easier to insulate.

Reverse brick veneer walls have the brickwork inside and lightweight frame and cladding outside. This has the advantage of providing the thermal mass on the inside of your home.

With both double brick and brick veneer walls (or any type of wall for that matter), it is important to ventilate your home in summer once the temperature outside becomes cooler than the temperature inside. This will help cool your home down and make conditions more comfortable. Retained night time coolness achieved through ventilation can also keep your home cooler during the day.

Lightweight walls
Weatherboard, fibre cement and other lightweight walls get hot quickly in the sun, but also cool down quickly once shaded and after sunset. During winter, they lose heat far more quickly than brick walls. The thermal performance of lightweight walls will improve significantly with insulation, which is cheaper and easier to install at the building stage.

Floors
Concrete floors store heat from the sun shining through northern windows in winter and return some of that heat during the evening. Laying dark tiles where the low angle winter sun hits the floor will maximise the absorption of heat to be re-radiated. It is important that this thermal mass is not exposed to direct solar energy during summer, as this can lead to uncomfortably warm internal conditions.

Timber floors do not have the high thermal mass of concrete floors. This means that a home with a timber floor will lose far more heat than one with a concrete floor. For homes on stumps which are open at the sides, it is recommended that insulation be installed to the underside of all exposed floorboards. Another solution is to fully enclose the area between the ground and the floor with a solid material like brick, but this will not be as effective as using insulation. An enclosed space under the floor will also require some permanent ventilation to control subfloor dampness.

Colour of external building materials
As a general rule, light colours tend to reflect the sun's heat while darker colours absorb it. You can take advantage of this fact when selecting the colour of your roof and wall materials. In summer, lighter coloured materials will help to keep your home cooler by reflecting heat from the sun. However if your home is properly insulated, which is a much more effective method of controlling heat transfer, the effect of external building colour on your comfort will be greatly reduced.

http://www.sedo.wa.gov.au/pages/building.asp

Brick veneer house construction

2010-01-09T12:54:00.000+10:30

1928
prestige without the price

If you have lived in a brick house in Australia there’s a high chance it was made using the brick veneer construction technique – a wood or metal frame to hold up the roof, panelling on the inside walls and a skin of bricks on the outside.

Compared to the traditional double brick house, a brick veneer house is cheaper and faster to build without sacrificing the status of a solid brick house.

The first identifiable brick veneer house was built in Geelong in Victoria 1903, but it was not until about 1930 that the method was considered reliable enough for a bank to approve a building loan.

By 1936 it was recognised as a standard method of house construction. Leading architects designed large and prestigious houses in Melbourne that were built using the technique. By 1950 brick veneer had almost replaced double brick construction in Victoria. The success of the ‘project home’ in Australia had begun.

In 1993-1994, 67% of new dwellings were built using brick veneer, which was most common in the Australian Capital Territory, South Australia and Victoria. At the end of the century brick veneer was the most popular form of house construction. It had changed the face of Australia’s urban and rural environments.

Who Did It?
Key Organisations
Unknown
Key People
Unknown

Further Reading
The history and design of the Australian house, Robert Irving, Oxford University Press, Melbourne, 1985.

http://www.powerhousemuseum.com/australia_innovates/?behaviour=view_article&Section_id=1040&article_id=10102

FCoE

2010-01-07T11:40:00.002+10:30

http://en.wikipedia.org/wiki/Fibre_Channel_over_Ethernet

FCoE Target
http://open-fcoe.org/openfc/wiki/index.php/FCoE_SW_Target_Quickstart

FCoE Initiator
http://open-fcoe.org/openfc/wiki/index.php/FCoE_Initiator

Support From Vendors:
http://www.ntapgeek.com/2009/02/netapp-fcoe-san-details.html

Exchange rate with Money Transfer.

2009-12-20T13:33:00.011+10:30

汇联:
www.everforex.com

KVB昆仑国际：(悉尼)
www.kvbkunlun.com
A1:昆仑国际??是在QVB对面的吗? 如果是,倒是换过CASH,汇率是一般银行没得比的,最优惠!
A2:kvb汇率不是最好的，在townhall的那个citibank building的18楼kvb旁边的那家换汇公司是我见过汇率最好的，基本是按照现时汇率换的

联通速汇
http://www.supay.com/rateListAction.do?method=website

Travelex Online at Travelex:
http://www.travelex.com.au/

Paypal:
https://www.paypal.com/au/cgi-bin/webscr?cmd=_display-fees-outside
This exchange rate includes a 2.5% spread above the wholesale exchange rate at which PayPal obtains foreign currency, and the spread is retained by PayPal.

Wizard Credit Card:
In the user guide, Page 3: No Cash Advance fees or foreign exchange fees

PennyTransfer
http://www.pennytel.com.au/International-Money-Transfer/Overview.aspx.aspx
http://www.pennytel.com.au/International-Money-Transfer/Exchange-Rates.aspx

costs just $8 every time you send money, no matter what the size of the transfer or where you are sending funds to.

Simply use your debit or credit card and PennyTransfer. It’s fast, convenient and secure.

What’s more, transferring funds will also get you PennyTel minutes for making calls to the same country you have sent money to. So if you wire money to your mother in China, you also get free minutes to call and let her know the funds are coming!

?? http://www.ozforex.com.au/cgi-bin/interbank-spot-rates.asp

Strata report

2009-11-05T08:42:00.001+10:30

看SINKING FUND有没有钱.
澳洲华人论坛|中文论坛|移民|交友|美食|生活- ]1 y# M+ p- q2 b# m$ p: h" h% U
Strata Fees 怎样开销的, breakdown; 有没有special levy

有没有upcoming major repairs, e.g. new painting

每年交的情况，看起来近几年没涨过。另外你要看special levy的历史，要看保险状况，最主要的还有会议记录，看看有没有没解决的遗留问题，这么多年修过什么东西，有没有大笔支出。

用 cbrom 修改 Award BIOS (new)

2009-11-04T17:03:00.001+10:30

CBROM是专门修改Award BIOS文件的一款工具，它能够从主板的BIOS(后缀名为bin)文件里提取、删除或加入某些文件。CBROM主要是通过分析BIOS文件来显示主板 BIOS的组成情况，它还可以将EPA、BMP、VGA BIOS等功能模块添加到BIOS文件中。因此，在使用CBROM之前，你必须首选获取主板的BIOS文件，这可以通过Awdflash.exe刷新程序获取，或者到主板厂商的网站上下载最新的BIOS文件。

1.显示BIOS文件内容

CBROM208.EXE bios.bin /D

显示的内容包括BIOS程序主文件(System BIOS)、EPA图像文件(EPA Logo)、BIOS内置刷新程序(Flash ROM)等。

2.提取BIOS文件中的相应模块文件

CBROM208.EXE*.bin/模块名 EXTRACT

例如提取磐英8KTA3主板的 BIOS文件(ekta.bin)中的ISA总线控制模块，当在DOS命令提示符后键入“CBROM208.EXE ekta.bin /ISA extract”时，系统首先会告诉你ISA ROM模块的文件名为stde.dat，直接回车后，则stde.dat将释放在当前目录下，并可看到“[ISA-1] ROM is extracted to stde.dat”的提示，这说明ISA模块文件stde.dat已经提取成功。

3.添加ISA总线控制模块

　　CBROM208.EXE*.BIN/ISA*.*

如果要将刚刚提取的stde.dat文件添加到上面提到的 8kt31411.bin文件中，只要键入“CBROM208.EXE kt31411.bin/ISA stde.dat”命令即可。当然，前提是8kt31411.bin文件中的剩余空间(“Remain compress code space =”后的数字)大于stde.dat文件的大小

现在，我们可以再次使用“CBROM208.EXE 8kt31411.bin/D”命令来检查，就会发现stde.dat模块已经被添加到8kt31411.bin文件中去了！

除了以上三个使用命令外，CBROM还有许多命令参数呢，只要键入

CBROM208.EXE /?

就可查看到(CBROM的命令参数详见表，这里笔者只介绍几个比较实用的使用参数供朋友们参考。

4.删除BIOS文件中的无用内容

　　CBROM208.EXE*.BIN/模块名 RELEASE

例如键入“CBROM208.EXE 8kt31411.bin/ISA RELEASE”命令就可以将刚才移植到BIOS中的stde.dat文件删除。有时，如果你为了向BIOS中添加某些特殊模块，却发现剩余空间比较紧张，就可以使用这个命令将一些无用的模块请出去以腾出足够的空间，例如图1中的“Flash ROM[0]”因为并无多大实用价值，就可以清除出去。

5.让主板具有内置刷新BIOS的功能

CBROM 208.EXE *.BIN/Awdflash Awdflash.exe

因为一般情况下，我们都是先用一张干净的启动盘启动系统到纯DOS模式下，然后再使用Awdflash.exe来刷新BIOS，而现在的许多新式主板内置了刷新BIOS的功能，只要在开机时按下“Alt+F2”键就可以自动刷新，这样一来，刷新BIOS的危险性自然大大减少。我们可以为自己的老主板添加内置刷新BIOS的功能，先按照上述命令格式将Awdflash.exe添加到BIOS文件中，然后再用这个BIN文件刷新主板BIOS，以后就可以可以轻轻松松升级BIOS啦。

6.修改自己的EPA LOGO和开机LOGO

CBROM208.EXE *.BIN /EPA *.bmp

我们每次开机后都会在屏幕右上角看到一个“能源之星”LOGO(图案)，你是否想到过将它更换为一幅自己所钟爱的图片呢？

这当然可以做到，不过在操作之前，你需要检查一下BIOS文件中有无足够的剩余空间，然后再键入

CBROM208.EXE 8kt31411.bin/EPA *.bmp

这里的“*.bmp”是指你自己制作的EPA图片。但笔者要说明一下，这个bmp文件必须是16色、136×126像素，至于内容就随你啦，不过最后的刷新BIOS这一步是免不掉的；假如在图1窗口中看到的“EPA LOGO”模块文件扩展名是epa(epa格式仅见于一些老式主板上，现在绝大多数皆为bmp格式)，那么还必须利用一个名为BMPTOEPA的软件先将其转换为epa格式，当然最后写入BIOS文件时也必须使用“CBROM208.EXE 8kt31411.bin /EPA *.epa”命令。

按照同样的思路，我们还可以像品牌机那样，DIY自己的开机LOGO，例如将自己的照片放在开机LOGO上，这样是不是看起来特别酷？制作开机 LOGO有一些特别的要求，图像文件为640×480像素或者更小，但必须是16色的BMP文件格式，而且文件大小必须控制在150KB以内，否则会无法启动。做好图片后只须用CBROM写入BIOS文件即可，如“CBROM208.EXE 8kt31411.bin /LOGO *.bmp”，最后刷新BIOS。成功后就会在“能源之星”图案出现之前显示出来，同时屏幕最下方还会有一行信息“Press [TAB] to Show POST screen,[DEL] to enter SETUP”，此时按下TAB键进入原来EPA画面，按DEL键进入BIOS Setup设置程序。

7.添加多个OEM模块

CBROM208.EXE *.BIN /OEM(0-7) *.*

我们经常可以看到某些品牌的主板会附加许多特殊的功能，如RAID、恢复精灵、数据保险柜等。因此，如果你想同时添加多个模块，那就必须使用

CBROM208.EXE 8kt31411.bin /OEM(0-7) *.*

注意这里的“OEM(0-7)”在使用时必须写成“OEM 2/OEM 3”的形式，即第一次用1，第二次用2，依此类推。

CBROM的功能十分强大，除了上面提到的功能外，它还可以将显卡的BIOS添加到主板BIOS文件中，从而实现主板、显卡BIOS一体化，即把显卡BIOS写入Boot Block引导块，从而在黑屏时实现显卡启动(不一定非要找到ISA显卡)；添加专用指令控制包等。

Windows Installer

2009-11-04T11:22:00.000+10:30

Uninstall Windows Installer:

Eg: Windows Installer 3.1,

Name:	Windows Installer 3.1 (KB893803)
Description:	Add or Remove Programs entry for Windows Installer 3.1 (KB893803). Update to the Microsoft Windows Installer that was originally packaged with Windows 2003 but them became available for other Windows versions.
Uninstallation Command:	C:\WINDOWS\$MSI31Uninstall_KB893803v2$\spuninst\spuninst.exe

Deduplication

2009-10-21T21:17:00.004+10:30

http://gotitsolutions.org/

Open Source Backup and Deduplication

While researching on the data de-duplication technology, I ran across an article in GotITSolutions.org which shows an open source solution for backup and data de-duplication. The project is called BackupPC Virtual Appliance. It's worth a look, given that products like Avamar, DataDomain, PureDisk, Asigra could chunk a considerable share in your IT budget.

http://gotitsolutions.org/files

Avamar vs DataDomain vs PureDisk

http://onlinedatastorage.blogspot.com/2009/08/avanar-vs-datadomain-vs-puredisk.html

http://onlinedatastorage.blogspot.com/2009/09/avamar-vs-datadomain-vs-puredisk-part-2.html

In the past 2 months, I've been in the R&D and had the chance to do my own evaluation on some of the major players in the data deduplication industry -- EMC's Avamar, EMC's new acquisition DataDomain and Symantec's NetBackup PureDisk. These products have been in the market for sometime and have proven their strengths in data deduplication in their very own rights.

Our major problem is the short backup window and the ever increasing data that needs to be backed up. To shorten our backup time we tried several solutions -- from deploying more Netbackup Media servers, to using 1GB backup network, to dumping data to SATA disks then scraping them later to tape. With the maturity of deduplication technology and the competitive price that each product has to offer, I start to look into this side of data management.

.... to be continued

The term de-duplication basically means elimination of redundant data. In the de-duplication process duplicate data are deleted, leaving only one copy of the data to be stored. However indexing of all data is still retained just in case the data is still required. For example, a typical email system might contain 100 instances of the same one megabyte (MB) file attachment. If the email platform is backed up or archived, all 100 instances are saved, requiring 100 MB storage space. With data de-duplication, only one instance of the attachment is actually stored; each subsequent instance is just referenced back to the one saved copy. In this example, a 100 MB storage demand could be reduced to only 1 MB.

Avamar is a backup and recovery solution of EMC, which utilizes data deduplication technology to identify redundant data at the source, minimizing backup data before it gets transported via LAN/WAN.

Data Domain deduplication storage systems reduce the amount of disk storage needed to retain and protect enterprise data. By identifying redundant files and data as they are being stored, the product can dramatically reduce the storage footprint of the original data.

Veritas NetBackup PureDisk uses data deduplication and integration with NetBackup to enable efficient, storage-optimized, data protection for data center, remote office, and virtual environments. The deduplication engine can be deployed within NetBackup or independently using a PureDisk client. The modular architecture and integrated replication features simplify scalability and disaster recovery.

.... to be continued

How do I enable weak authentication in gssftp?

2009-10-15T18:56:00.002+10:30

If gssftp is enabled and there are errors while logging in, the client may not be using secure authentication. To tell gssftp to allow weak authentication:

1. Edit /etc/xinit.d/gssftp. Change:

    server_args = -l -a

to

    server_args = -l

2. Then restart xinetd:

 #service xinetd restart

AIX Sendmail issue

2009-10-03T01:41:00.005+09:30

1. the name service:
/etc/netsvc.conf = nsswitch

2. Sendmail configuration
/etc/sendmail.cf

3. Mail log location
get from /etc/syslog.conf

4. if enabled the sender address verification
Use mailx -r options.

File System

2009-09-26T18:07:00.001+09:30

WAFL from NetApp and ZFS from Solaris (which are quite similar actually - so similar there's a class action law suit between them about the FS)

The next version of MACOSX is apparently going to be ZFS. But we'll wait and see!

http://www.sadikhov.com/forum/index.php?showtopic=60207&view=&hl=Netapp&fromsearch=1

http://www.sadikhov.com/forum/index.php?showtopic=60207&hl=Netapp&st=20

Online Dictionary

2009-09-08T18:04:00.004+09:30

http://www.iciba.com/revamp/

Rototech Forum:
http://forum.snowzhang.com/forumdisplay.php?fid=15&page=3

http://www.tfg2.com/thread.php?fid-50.html

SLIC and OS

2009-09-05T18:03:00.007+09:30

A69T BIOS:
http://www.bios.net.cn/BBS/forum-162-1.html

Guide for VMware Fusion 2 SLIC Hack (MacOS)

http://forums.mydigitallife.info/showthread.php?t=3376

http://www.insanelymac.com/forum/index.php?showtopic=172474

1. VT-x is enabled in the BIOS
2. Change you VMX file and make sure you have these settings:

guestos = "darwin-64"
monitor.virtual_exec = "hardware"
monitor.virtual_mmu = "software"

Install OS X on Your Hackintosh PC, No Hacking Required - Leopard ...

http://lifehacker.com/348653/install-os-x-on-your-hackintosh-pc-no-hacking-required

威廉第三的MAC系列教程（一） ——使用ACPI Patcher制作DSDT补丁
http://bbs.pcbeta.com/thread-484842-1-1.html

IBM make really good Laptops. Sometimes they just need hacking...
http://www.paul.sladen.org/thinkpad-r31/wifi-card-pci-ids.html

BIOS内部模块功能详解

2009-08-18T12:22:00.003+09:30

不论是AMI的BIOS还是AWARD的BIOS，整个程序代码都是由一系列模块组成的，这对于OEM厂商来说，修改BIOS添加自己的信息提供了方便，下面我们来看一下两种BIOS中各模块代表的具体功能。

一、Award-BIOS内部模块相关说明：
用CBROM打开Award-BIOS文件后，可看到各模块：
二、AMI-BIOS内部模块相关说明：
用amibcp打开AMI-BIOS文件，可看到各模块：

BIOS中，不同的模块具有不同的功能。象SYSTEM BIOS项和扩展BIOS程序项等模块，是BIOS中的核心模块，不能做任何改动；有些模块，如开机画面、能源之星图标等，可有可无，如果该模块删除，开机后就不显示图案，如果更换此模块所代表的图案，开机后便能显示不同的画面。如果不知某个模块的功能，最好不要随意修改它。

模块名称	ID 号码	模块用途
INIT		从Reset跳入点开始的Boot Block程序代码
NVRAM／ESCD		FlashEPROM的GPNV区域，存储系统组态数据
POST	00h	POST程序代码
Setup Server	01h	AMIBIOS设置服务器端
Runtime	02h	BIOS功能函数／常驻的程序代码
DIM	03h	Device Initialize Manager（装置初始化）
Setup Client	04h	提供AMIBIOS设置画面的接口程序
Remote Server	05h	搭配远程遥控除错系统
DMI Data	06h	数据区
Green PC	07h	符合APM规范的节电管理程序
Interface	08h	BIOS模块压缩／解压子程序模块
MPS	09h	多重处理器起始模块
Int-10	0Bh	BIOS文字／绘图等显示处理模块
ROM-ID	0Ch	记录ROM ID与相关信息的模块
Int-13	0Dh	BIOS软盘／硬盘／光驱读写形式
ACPI Table	0Fh	ACPI规范控制表格区
ACPI AML	10h	ACPI的AML句柄存放区域
P6 Micro Code	11h	Intel P6处理器微码修补模块
Configuration	12h	系统组态显示模块
DMI Code	13h	DMI控制程序码模块
PCI AddOn ROM	20h	PCI适配器ROM程序代码模块
Multilanguage	21h	多重语言控制模块
Font DataBase	30h	中文（双位语系）字形数据模块
EPA / OEM Logo	31h	屏幕右上方OEM商标画面模块
Image Dsiplay Code	32h	Silent Boot，OEM全屏幕画面处理程序
Full Screen Logo	33h	Silent Boot，OEM全屏幕图形文件数据模块
Virus	36h	TCAV杀毒模块

以上每一个模块，事实上是由好几个甚至几十个编译过的＊.ASM、＊.OBJ等文件所连结而成，至于每个模块会参考到那些＊.ASM、＊.OBJ或其它文件，这由是由AMI当初设计的一连串编译维护批处理文件，如MAKEBIOS.BAT，MAKEALL.BAT，以及位于芯片层的几个＊.MAK维护文件，依照不同的芯片组特性，以及IO.BAK OEM.AMK等文件中字段／标识位的控制来决定，模块内会牵扯到＊.ASM、＊.OBJ等文件内容是随时有变动的。

　　BIOS模块中，INIT、NVRAM／ESCD、POST以及INTERFACCE这四个模块是属于开机最初被执行的模块，也是所有 BIOS模块中，唯一以非压缩的程序代码形式（Un-copmressed code）存储于ROM中，也就是说BootBlock的程序代码跟存储在FlashROM的程序代码完全相同的，而其它模块在编译／连结完成后，要做模块总联接成一块BIOS　ROM之前，事实上都是先经过压缩处理，然后才写回BIOS　ROM文件中。

Award BIOS内部模块

模块名称	在BIOS中的文件名	模块用途
SYSTEMBIOS	original.tmp	系统中最基本的部分，所有的BIOS都有这一部分

模块名称	在BIOS中的文件名	模块用途
XGROUPCODE	awardext.rom	扩展BIOS程序，是各个厂商自己定制的不同于标准AwardBIOS的功能，实际上几乎所有的厂商都会增加这一部分内容
CPUmicrocode	cpucode.bin	CPU微代码，是用来兼容各型号CPU的
ACPItable	acpitbl.bin	支持ACPI的ACPI列表。只有支持ACPI的BIOS，才能真正实现ACPI功能
Other EPApattern	awdflash.exe awardepa.epa	BIOS中内置的刷新程序 EPA格式的能源之星图形文件
EPApattern	awardepa.bmp	BMP格式的能源之星图形文件
LOGOROM	dbios.bmp	技嘉主板中的双BIOS图标
OEMROM VRSROM	v.rom anti_vir.bin	主板厂家在BIOS中内置的程序模块 BIOS中内置的防病毒代码
LOGOBitMap	lcjao.bmp	BMP格式的全屏开机画面文件

注：以上模块的序号及文件名称，在不同的BIOS中并不相同，某些模块，在某些BIOS中并不存在。

AMI BIOS内部模块

AMIBIOS内部模块的相关说明如表2所示。

表2 AMIBIOS内部模块

模块名称	ID 号码	模块用途
INIT		从Reset跳入点开始的BootBlock程序代码
NVRAM／EscD		FlashEPROM的GPNV区域，存储系统组态数据
POST	00h	POST程序代码
SetupServer	01h	AMIBIOS设置服务器端
Runtime	02h	BIOS功能函数／常驻的程序代码
DIM	03h	DeviceInitializeManager（装置初始化）
SetupClient	04h	提供AMIBIOS设置画面的接口程序
RemoteServer	05h	搭配远程遥控除错系统
DMIData	06h	数据区
GreenPC	07h	符合APM规范的节电管理程序
Interface	08h	BIOS模块压缩／解压子程序模块
MPS	09h	多重处理器起始模块
Int-10	0Bh	BIOS文字／绘图等显示处理模块

模块名称	ID 号码	模块用途
ROM-ID	0Ch	记录ROMID与相关信息的模块
Int-13	0Dh	BIOS软盘／硬盘／光驱读写形式
ACPITable	0Fh	ACPI规范控制表格区
ACPIAML	10h	ACPI的AML句柄存放区域
P6MicroCode	11h	IntelP6处理器微码修补模块
Configuration	12h	系统组态显示模块
DMICode	13h	DMI控制程序码模块
PCIAddOnROM	20h	PCI适配器ROM程序代码模块
Multilanguage	21h	多重语言控制模块
FontDataBase	30h	中文（双位语系）字形数据模块
OEMLogoData	31h	屏幕右上方OEM商标画面模块
GraphicLogoCode	32h	SilentBoot，OEM全屏幕画面处理程序
GraphicLogoData	33h	SilentBoot，OEM全屏幕图形文件数据模块
Virus	36h	TCAV杀毒模块

http://blog.zol.com.cn/243/article_242788.html

AWARD BIOS刷PXE启动

2009-08-18T07:06:00.000+09:30

步骤：
1. 查看 BIOS 信息
命令格式：
cbrom nf5.bin /d ( 参数 d 为查看 BIOS 信息 )

下面是 NF5 BIOS 里的信息

这里大家可以看到这款主板自带了 RAID ，网卡和网卡的 PXE 启动 LOM （即 PCI ROM 里的内容，这里有 A BC 三个）由于这款主板是集成 NV 的网卡目前不支持 MZD 无盘启动（ MZDLIVE 除外），所以我们要把这些都去掉。

2 ．删除 PCI ROM 的信息
命令格式：
cbrom nf5.bin /pci release

enter a choice ：这里现在 A
依次删除其他 PCI ROM 信息
这里是删除后的情况如下图：

3. 添加 8169PXE 启动代码（ 8169153.lom ）
命令格式： cbrom nf4.bin /pci 8169153.lom

4 ．查看添加 8169PXE 启动代码后的 BIOS 信息
命令格式： cbrom nf5.bin /d

这时我们可以看到 BIOS 里 PCI ROM [A] 项的内容里就有我们添加的 8169153.lom
说明我们已经把 8169PXE 启动代码刷入了 BIOS

1
5 . 将修改后的 BIOS 刷入主板
命令格式：
awd865 nf5.bin /py /sn /r

注意：刷新 BIOS 的时候不能断电，否则 BIOS 将会损坏
刷新后插入 8169 网卡开机后如果可以看到 MZ99 并出现 DHCP 画面那么可以恭喜你已经成功的刷新了修改好的 BIOS

修改BIOS大法(AWARD BIOS为例)

2009-08-18T07:01:00.003+09:30

首先，我们需要几个能对BIOS进行“手术”的软件——AWARD 公司的BIOS刷新工具AWDFLASH和AWARD BIOS的修改软件CBROM（请对应自己AWARD BIOS的版本进行选择，这里不再赘述）。接下来我们要使用AWDFLASH提取到自己主板BIOS文件，这个只有256k的文件就是我们启动的时候主板所需要读取的，这里面究竟放了一些什么东西呢？

将CBROM和我们的BIOS文件放到C盘根目录下，然后进入纯DOS模式，在C盘根目录下运行 cbrom i845.bin /d 其中：SYSTEM BIOS是AWARD BIOS主程序；CPU micro code是对应的CPU微码，我们的主板能识别各种CPU就*它了；ACPI是主板实现ACPI功能的基础；XGROUP是主板厂商根据自己的需要对 BIOS文件进行的补充，其他的几个项目如EPA 、VRS分别是开机启动的时候能源之星的标志和防病毒固件，这个VRS其实就是早年486时代的防病毒卡的翻版，因此对我们来说除了妨碍启动速度一点用处也没有。

如果说上面几个BIOS内部文件还是必不可少的话，那么下面这个两个PCI ROM对我们来说就是BIOS文件中的垃圾了，由于厂商在生产主板的时候往往会搭配一些特价的板卡，出于对OEM的厂商保护的原因，因此这些板卡往往不带 BIOS芯片，直接使用整合在主板BIOS文件中的板卡设备BIOS文件，这就使得这些板卡只能使用在特殊的主板上，玩电脑稍微有点年头的朋友一定还记得早年GIGA的系列板卡都能搭配MAROX对GIGA专供的G400，其实就是这种情况，我们通过对文件名称的判断，可以了解到，该MSI主板 BIOS 中的两个PCI ROM分别是MSI的IDE RAID卡和网卡的BIOS文件，对于我们来说一点用处也没有，所以，出于加快启动速度考虑，我们可以把它安全的删除。

在C盘跟目录下输入 cbrom I845.bin /pci rom release 这个时候出现了一个选择项目，让我们选择A、B两个rom文件，到底需要删除哪个。输入a之后回车，PCI ROM[A]就被删除了，同样，运行cbrom I845.bin /vrs release和cbrom w619mj27.bin /epa release。

最后，重新使用CBROM 的/D命令查看下我们的卫生扫除工作完成了没有，然后在按部就班的把我们改好的BIOS 文件刷到主板上。

日前各主板厂商都在为自己的主板增加新功能(如捷波恢复精灵)。有此功能也能应用于其它主板，这就使广大DIY们频繁改动自己的BIOS。目前应用最多的就是CBROM，使用这个功能强大的软件，可以分离、加入、删除BIOS中的内容。以下为CBROM各参数的应用。
提示：在你修改自己的BIOS前，一定要做好备份，以防万一。此软件只限于AWARD BIOS。
加入某项内容： (以下 ***.BIN 为BIOS文件)

CBROM ***.BIN /EPA ***.EPA 更新能源之星图标（用于只支持EPA格式的4.5X）
CBROM ***.BIN /EPA ***.BMP 更新能源之星图标（用于只支持BMP格式的4.6X-6.X）
CBROM ***.BIN /EPA1-7 ***.BMP 部分主板支持多个更换能源之星图标功能
CBROM ***.BIN /LOGO ***.BMP 更新全屏画面用法（用于只支持BMP格式的6.X和部分4.5X）
CBROM ***.BIN /LOGO1-7 ***.BMP 部分主板支持多个更换全屏画面功能

CBROM ***.BIN /ISA STDE.BIN 使你的主板拥有和捷波恢复精灵一样的功能
CBROM ***.BIN /ISA BIOS-10.BIN 使你的主板拥有承启主板的GHOST功能
CBROM ***.BIN /PCI PXE.LOM 下载网卡BOOTROM 启动芯片 PXE 代码，写进主板的BIOS将PXE启动代码写到 BIOS 中去，用做无盘启动工作站
CBROM ***.BIN /VSA ***.BIN 更新防毒模块
CBROM ***.BIN /AWDFLASH AWDFLASH.EXE "FLASH ROM"使你的主板拥有自刷新工能（启动时按ALT+F2）
CBROM ***.BIN /MIB ***.TXT 在支持MENU IN BIOS的主板加入文本信息(加入后，在BIOS SETUP里按F5或F9）
CBROM ***.BIN /YGROUP AWARDEYT.ROM 更换 YGROUP组
CBROM ***.BIN /XGROUP AWARDEXT.ROM 更换 XGROUP组
CBROM ***.BIN /GROUP _EN_CODE.BIN 写入英文显示代码
CBROM ***.BIN /GROUP _GR_CODE.BIN 写入繁体中文代码
CBROM ***.BIN /GROUP _B5_CODE.BIN 写入德语代码
CBROM ***.BIN /FNT1 FONT1.AWD 写入字库

system bios, this is what the bios modder sometimes called original.tmp, since when the bios file decompressed by modbin (an award bios "limited" editor program) or another bios file decompressor, it will result in a file named original.tmp. This is the main bios file which does the initialization of the board during boot and services bios interrupts. The initialization of the system that is accomplished by this program, inlcluding calling of additional bios file sometimes called option rom. Option rom will be explained later.

XGROUP CODE and YGROUP CODE. These are extensions to the system BIOS (original.tmp). They are executed when original.tmp executed, after it's decmpressed to system RAM by bootblock. The reason they are separated is a bit obscure, but possibly since the "decompressed address space" already exhausted, that's why they have to be treated differently. I mean original.tmp need 128 KB of addres-space while the real initialization routine need more than that, that's why they are separated from original.tmp. I have to point out here that they are an INTEGRAL PART of system BIOS.

Explanation of Expansion/Option ROM

Expansion rom actually is a firmware similar to the mainboard bios, but their purpose is to initialize the card in which they are soldered/socketed. Sometimes they are mounted into an old ISA card (in which we call them ISA option/expansion ROM) or to a PCI card (in which we call them PCI option/expansion ROM). There are also things called BIOS32 services, but this is quite seldom implemented, and I don't know too much about it. Eventhough in most cases, PCI or ISA expansion ROM are implanted in a eprom/eeprom/flashrom chip in a PCI or ISA card, there also certain cases which they are implemented as the mainboard bios component, sometimes due to the mainboard design which incorporate some add on PCI chip in their mainboard, such as RAID controller, SCSI controller or serial ATA controller like the one you saw in the DFI865PE bios example above. Note that an expansion ROM implemented as a mainboard bios component is no different with expansion rom implemented in a PCI/ISA expansion card.

Advanced Configuration and Power Interface (ACPI)

移出某项内容：
在以上各参数的基础上（CBROM ***.BIN /ISA）加入EXTRACT参数，则为移出BIOS中的新功能。各参数、BIOS文件不同，移出的内容也不相同。
注意：移出的文件最好用BIOS文件中的原文件名。否则可能移植到BIOS中，可能无法使用。

删除某项内容：
如你不想用BIOS中的某个文件，可以在以上参数的基础上（CBROM ***.BIN /ISA）加入RELESAE参数，则为删除对应的项目。

警告：修改BIOS可能造成机器不能启动的严重后果，在没有安全保证的情况下，请慎重使用！！！

Refer to: http://www.geocities.com/mamanzip/Articles/Bios_Structure.html

修改新主板BIOS的几种方法

2009-08-17T23:04:00.002+09:30

修改AWARD BIOS

打造自己的个性BIOS，是每个电脑爱好者的愿望。随着Phoenix公司与AWARD公司的合并，BIOS生产商现在只剩下AWARD和AMI两个公司了。AWARD和AMI各具特色，并且，借助于特定的工具，都可以方便地修改BIOS的相关内容，DIY出具有自己特色的电脑。下面就分别介绍一下 Award和AMI BIOS的修改方法。

一、所需要的工具：要全面地修改BIOS，需要一些专用工具：

修改AWARD BIOS所需要的软件有：

AWDFLASH.EXE：我们早已熟悉的Award BIOS刷新程序。当BIOS进行修改之后，需要它将修改结果写入BIOS。
CTBIOS.EXE：识别BIOS版本的程序。某些用户不知道自己的BIOS版本，那么就可使用它来识别。
CBROM.EXE：可显示、导入、导出、修改BIOS模块的程序，常用的版本为V2.15，目前最新的版本是V6.06。
MODBIN.EXE：可修改BIOS设置画面内容以及自检时所显示的部分内容。
BMPTOEPA.EXE：可实现BMP和EPA图片的相互转换。
EPAFlash．EXE：制作会动的EPA图标工具。

修改AMI公司的BIOS所用的工具：

AMIFLASH.EXE：AMI BIOS刷新程序。
AMIBCP.EXE：一个类似于MODBIN.EXE的工具软件，主要是用来显示和修改AMI BIOS文件的内容。
AMImbid.EXE：用来识别AMI BIOS相关信息的软件
AMILOG.EXE：用来制作AMI BIOS能源之星图案的软件。
另外，还要有相应的操作界面文件、显示模块文件等。

相应主板的BIOS文件（在此假设文件名为bios.bin），可以从主板厂家网站下载或备份自己主板上的BIOS；如果自己制作开机LOGO、能源之星等图案，还需要使用图形处理软件，一般用Windows95/98中的画图即可，也可以使用如Phtotshop、Photo Impact等图形处理软件，如要进行更全面的文字修改，还需要WinHex等十六进制编辑软件。以上软件，大家可以到BIOS专页（http://www.rebios.net）中的程序下载区下载，下载后，放在C盘下的BIOS目录中。

下载本文所需的部分文件：AMI BIOS文件,从中你可以分离出Graphic Logo Code。
sunset.jpg
hiflex.bin、simple.bin、winsetup.bin、easy.bin

二、注意事项：

修改BIOS具有一定的危险性，一旦操作不慎，会损坏BIOS程序码的完整性，造成严重的后果。Award公司并不鼓励使用者自行修改BIOS程序码，当然也不提供任何技术支持，一切后果都由使用者自行承担。国内的联想公司，对使用者自行修改BIOS导致的主板损坏也不提供保修服务。在这里我们特别强调，我们修改的只是BIOS中的图案或开机时显示的文本信息，对于BIOS中的程序码，一旦改变了其完整性，就会导致开机时没有显示；
修改好的BIOS文件要刷新到BIOS芯片中才能正常显示，因此整个操作过程还要涉及到BIOS升级，具有一定的危险性。
向 BIOS中添加内容时，要注意BIOS的容量。1M、2M、4M BIOS对应的文件大小分别为：128K、256K、 512K。BIOS芯片的容量越大，那么能够加入的内容就会更多；相反，如果BIOS芯片的容量较小，可能有些内容就不能加入到BIOS中（如开机 LOGO、AWDFLASH.EXE刷新程序等较大的文件）。
并不是所有的主板BIOS都可以成功地完成开机画面的替换过程。有些品牌主板不允许替换操作的进行；有些主板在替换EPA图标后，开机并不能正确地显示；还有的机器干脆根本就不能正常启动。因此，在替换开机画面前要有一定的思想准备，最好看看你的系统启动屏幕，如果发现缺省的EPA图标是厂商所特有的，最好三思而后行。

Windows 2008之Hyper-V硬件需求

2009-08-17T22:58:00.002+09:30

http://hi.baidu.com/jaimy_jie/blog/item/8b3932452e6d3420cefca3ad.html

Hyper-V是微软伴随Windows Server 2008推出的重量级虚拟化工具平台，很多网友都在问，为什么安装了Windows Server 2008之后找不到这个功能？或者即时重新安装了这个组件，Hyper-V虚拟化也不能使用呢？

　　其实，要完全实现正常安装并使用Hyper-V，除了需要软件条件，还需要硬件条件才行。

　　安装 "Hyper-V"虚拟化的先决条件：

　　Windows Server 虚拟化需要特定的CPU：

　　－基于 x64： Windows Server 虚拟化功能只在 x64 版本的 Windows Server 2008 标准版、企业版和数据中心版中提供。

　　－硬件辅助虚拟化：需要具有虚拟化选项的特定CPU，即包含 Intel VT(Vanderpool Technology)或 AMD Virtualization (AMD-V，代号 "Pacifica")功能的CPU。

　　－硬件数据执行保护(DEP)，而且被开启(如果CPU支持 Server 2008 默认开启)。

　　下面提供两种快速检测方法：

　　（一）使用 EVEREST Ultimate Edition 软件（下载），可以方便的辨别你的CPU是否符合要求：

　　在"主板"下的"CPUID"一项中，查看是否支持以下三种特性：

　　1、指令集：64位x86扩展

　　2、 CPUID特征：对于AMD处理器：Secure Virtual Machine Extensions (Pacifica) ;对于Intel处理器：Virtual Machine Extensions (Vanderpool)

　　3、安全特征：数据执行保护(DEP) (DEP, NX, EDB)（图1）

　　（二）在这里，给大家介绍另外一个简单便捷的小工具－securable（下载）。（图2）

　　如果机器显示如上图，代表不支持Hyper-V，因为三个条件均不满足，呵呵（记住，只要有一项不满足就不支持！）。如果你的系统显示的与下面的图相同，那么恭喜你，可以体验Hyper-V的无穷魅力了！（三个条件均支持）（图3）

当你的系统完全能够满足上述条件后，即可开始安装Hyper-V平台.

http://home.ixpub.net/space.php?uid=272339&do=blog&id=405258

让主板自己刷新BIOS功能

2009-08-17T22:57:00.001+09:30

首先您需要上网下载BIOS通用编辑工具AWARD(Cbrom.exe)、AMI(Amibcp.exe)，以及刷新工具AWARD(Awdflash.exe)、AMI(Amiflash.exe)和自己主板的BIOS文件(本文简称这个文件为mb.bin)~

　　AWARD类BIOS使用方法

　　将已经下载的cbrom.exe、awdflash.exe、mb.binBIOS文件拷贝到同一个目录，在纯DOS状态下使用cbrom mb.bin /d查询主板BIOS文件是否有10K-40K的空间写入BIOS文件中。(如图)还剩余50.72K的空间绝对足够了。不过，不可能每款主板都有足够的剩余空间，这时您可以适当删除一些非必要的设备文件腾出空间。(如图)的第7项PCI设备的NCR SCSI BIOS，许多品牌的主板BIOS都集成有NCR SCSI BIOS，由于太老很早就没人使用，朋友们完全可以将其删除，这里使用释放命令(cbrom mb.bin /pci release)删除。还有一些主板集成有其它外接的设备BIOS，你也可以在确认未使用的情况下将它们删除，命令形式都是(CBROM主板BIOS /设备类型release)。不过得提醒您：错误删除重要的BIOS文件极有可能导致系统不能启动甚至损坏主板，所以最好先使用cbrom /？熟悉一下具体的操作方好行事。

　整理完空间后这时就可以添加选择好的awdflash.exe文件了，键入(cbrom mb.bin /awdflash awdflash.exe )。完成后使用(cbrom mb.bin /d)命令确认一下操作是否正确，如无错误下面就应该将修改完的系统BIOS像正常升级一样刷新到主板中。(方法不用说了吧，大家都应该会)

　　AMI类BIOS使用方法

　　由于AMI的所有工具都使用的是图形界面，功能都十分强大使用也非常方便，照说明操作就行了。将Amibcp、Amiflash、mb.binBIOS 文件拷贝到同一个目录，键入(amibcp mb.bin)进入主界面，选择第三项(编辑BIOS模式)回车。进来后同样先查看BIOS剩余的空间情况(如图)这里有82272(单位byte)换算成千字节就是80.3K足够添加了。(不够的话，也可以删除一些无效的设备BIOS，这里方法就简单多了选好该文件按DEL确认就可以了)~

　然后，依照图示按一下中键盘的Insert键(添加设备BIOS)，弹出一个要求输入文件的对话框，输入选择好的Amiflash文件回车即完成修改。确认无误后，重启系统进入纯DOS模式，键入(Amiflash mb.bin)移动光标到第一项Go ahead(刷新确认)，等待几秒钟进度条到100%时就完成了系统BIOS的更新工作。

　　完成以上所有的操作后，朋友们就可以在每次开机的时候，在第一屏显示的画面下方发现PRESS(ALT+F2)FLASH BIOS,自动刷新BIOS的提示了，这样朋友们以后刷新BIOS就不会觉得很麻烦了，完全可以轻松搞定刷新BIOS~

建议：首先您需要确定自己的主板具体型号以及当前BIOS版本~相关BIOS可到http://www.mydrivers.com/cgi-bin/bios/796,1.htm进行查找~由于升级BIOS具有一定的危险性~如无十分把握建议不要更新为好~！！！

实战修改bios安装vista

2009-08-17T21:57:00.004+09:30

以前用ｘｐ的时候只要改一下DMI信息就可以激活　而ｖｉｓｔａ采取了新的ＳＬＰ２．０技术来打击盗版　　现在破解的方法已经很多了　随便　 google 一下就出来了　　　所有方法中我感觉最完美的是改bios 了，在ｂｉｏｓ中添加SLIC表来通过验证　　不过风险也是最大的　但还是再一次冒险成为小白鼠　吼吼～

我的主板是ＭＳＩ的　K8N NEO4, 决定改成ＭＳＩ笔电的

首先需要下载主板的ｂｉｏｓ　以及ｂｉｏｓ编辑工具modbin6和cbrom，把它们放到同一个文件夹中，并且把bios文件的扩展名改为bin。运行modbin6,打开ｂｉｏｓ文件，之后暂时先不要关闭程序。

这时用UltraEdit打开ｂｉｏｓ所在文件夹中新增加的ORIGINAL.BIN文件　点击搜索－〉查找

输入RSDT 以ASCII的形式查找　会找到一个较长的字符串

将找到的字符串中的ＳＲＡＴ替换为ＳＬＩＣ　在ｂｉｏｓ中增加ＳＬＩＣ表

切换到modbin6 保存打开的ｂｉｏｓ退出

然后在DOS环境下运行CBROM w7125nms.bin /acpitbl extract (w7125.bin为主板的BIOS文件名)

用Ultraedit32打开分离出的ACPITBL.BIN文件，修改RSDT表的OEMID和OEMTableID为SLP标志的对应字串。OEMID固定为6字节MSI_NB，OEMTableID 固定为8字节MEGABOOK。

改完之后

然后追加SLIC表数据到ACPI数据区尾部。

SLIC表大小为374字节

在WINXP命令行下运行命令：copy acpitbl.bin/b + acpislic.bin/b　acpitbl.bin。　这里的acpislic.bin对应的是ＭＳＩ笔电的　注意一定不要忘记在文件后面加/ｂ参数　否则不是以二进制合并的　我曾因为这个导致无法开机　　惨痛教训啊～

合并完成后，使用CBROM将acpitbl.bin添加到BIOS文件中，在DOS命令行下输入CBROM w7125nms.bin /acpitbl acpitbl.bin

bios修改完成　刷进机器就行了　

重启之后用Ｅｖｅｒｅｓｔ查看ｓｌｉｃ表　　如果修改成功应该是这样的

可以装ｖｉｓｔａ了　然后导入ＭＳＩ的证书就激活喽～

问题：一块 D6VAA 双 CPU PIII 主板在 FB 5.3 下无法正常通过 ACPI 关机（shutdown -p now），造成老板（我）很生气！！！

BIOS 信息：AWARD BIOS 6.0PG

OS：FreeBSD 5.4

主要 BIOS 修改工具：cbrom ，个人推荐版本：2.19
推荐 BIOS 刷新工具：uniflash 1.40

思路：
　　由于板子是同一型号，又经比较，发现 PCB 1.1 板子的 ACPI table 与 PCB 1.0 略有不同。由此引发我修改的想法。

总结（只供参考）：
　　如果你的机器在 FB 下无法通过 ACPI 关机，那么可以试试此方法。替换、修改的原则一般是：
1、必须是同一南北桥芯片组的主板；
2、尽量是同一厂家同一系列的主板；
3、必须同一品牌的 BIOS；
4、AMI BIOS 也可以通过类似的方法使用 AMIBCP 来修改。

不修改Bios完成OEM版Vista系统免激活
http://hapeacock.blog.51cto.com/193534/57020

Award BIOS

2009-08-16T21:28:00.010+09:30

For Award BIOS:
You can list/add/remove them by cbrom.exe program. You can also extract all modules in one time with awarddec.exe.

For AMI BIOSes
There are similar tools called amibcp.exe for DOS & Windows and mmtool.exe for Windows.

Porjects:
http://rayer.ic.cz/romos/romose.htm#DOWNLOAD

HowTo:
http://www.nforcershq.com/forum/ga-7n400-how-to-update-flash-the-bios-of-silicon-sata-contro-t67101.html

Tools:
http://www.wimsbios.com/awardnumbers.jsp

BIOS tool
http://www.rom.by/

The Cbrom
http://www.pcqifei.com/bbs/read.php?tid-77.html

bios.net.cn昂达技术部
http://www.bios.net.cn/bbs/forumdisplay.php?fid=162

VMware ESX

2009-08-05T21:07:00.003+09:30

VMware ESX and ESXi Scripts & Resources

http://www.engr.ucsb.edu/~duonglt/vmware/

http://blog.colovirt.com/2009/03/31/linuxnetworkingsecurity-tftp-deamon-setup-and-cisco-configuration-backup/

UNIX CDP Configuration

2009-07-15T09:56:00.002+09:30

Copied from URL below:

http://etutorials.org/Networking/Integrated+cisco+and+unix+network+architectures/Chapter+6.+The+Analyzer+Toolbox+DHCP+and+CDP/Lab+6-2+UNIX+CDP+Configuration/

Sometimes it is convenient to use the Cisco Discovery Protocol (CDP) to get an overview over a Cisco topology, especially when familiarizing yourself with an unknown network. CDP is also helpful when dealing with integration of UNIX gateways into an existing Cisco Works network management infrastructure. Cisco Works, for example, heavily relies on CDP. UNIX workstations can send CDP packets to Cisco neighbors.

Depending on the tool, these packets are either CDPv1 or CDPv2. Four UNIX CDP implementations pretty much achieve the same:

* cdpd
* cdpr
* scdp
* lcdpd (Linux kernel patch)

Because UNIX workstations usually do not care about CDP neighbors, they transmit only CDP packets; they do not digest received protocol information. Example 6-18 shows the CDP configurations of the lab gateways. The callisto scdp crontab entry is activated every 60 seconds to match the Cisco default timers.

Example 6-18. CDP Configuration

Castor: /usr/local/libexec/cdpd ?a

Callisto crontab entry: * * * * * /usr/local/bin/scdp -i eth0 -v2

Scar: Cisco CDP can be enabled per-interface via the cdp enable command

The result of this setup is shown in Example 6-19, and Example 6-20 shows a sniffer trace of the CDP protocol traffic.

Example 6-19. CDP Lab Operation

scar# show cdp neighbors

Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge

                 S - Switch, H - Host, I - IGMP, r - Repeater



Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID

callisto         Eth 1              124          H        Linux     eth0

castor           Eth 0              147          H        i386      ed0



scar# show cdp neighbors detail

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

Device ID: callisto

Entry address(es):

 IP address: 192.168.14.1

Platform: Linux,  Capabilities: Host

Interface: Ethernet1,  Port ID (outgoing port): eth0

Holdtime : 178 sec

Version : 2

advertisement version: 1

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

Device ID: castor

Entry address(es):

 IP address: 192.168.7.7

Platform: i386,  Capabilities: Host

Interface: Ethernet0,  Port ID (outgoing port): ed0

Holdtime : 142 sec

Version :

FreeBSD 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Tue Nov

advertisement version: 1

Example 6-20. CDP Protocol Behavior?Sniffer Output

[root@callisto:~#] tcpdump -i eth0 ether dst 01:00:0c:cc:cc:cc

tcpdump: listening on eth0

14:41:00.784334 CDP v1, ttl=180s

        DevID 'callisto'

        Addr (1): IPv4 192.168.14.1

        PortID 'eth0'

        CAP 0x10

        Version: (suppressed)

        Platform: 'Linux'

14:41:04.922217 CDP v2, ttl=180s

        DevID 'scar'

        Addr (1): IPv4 192.168.14.254

        PortID 'Ethernet1'

        CAP 0x01

       [!cdp]

14:41:04.923162 CDP v1, ttl=180s

        DevID 'scar'

        Addr (1): IPv4 192.168.14.254

        PortID 'Ethernet1'

        CAP 0x01

       [!cdp]



[root@castor~#] tcpdump -i ed0 ether dst 01:00:0c:cc:cc:cc

tcpdump: listening on ed0

14:09:04.837219 CDP v2, ttl=180s

        DevID 'scar'

        Addr (1): IPv4 192.168.7.254

        PortID 'Ethernet0'

        CAP 0x01

       [!cdp]

14:09:04.838186 CDP v1, ttl=180s

        DevID 'scar'

        Addr (1): IPv4 192.168.7.254

        PortID 'Ethernet0'

        CAP 0x01

       [!cdp]

14:11:24.686029 CDP v1, ttl=180s

        DevID 'castor'

        Addr (1): IPv4 192.168.7.7

        PortID 'ed0'

        CAP 0x10

       [!cdp]

CDP on Linux

2009-07-15T09:49:00.000+09:30

The CDP protocol:

The Cisco Discovery Protocol (CDP) is a proprietary layer 2 network protocol developed by Cisco Systems.
It runs on Cisco and some HP equipment devices.

It is useful for two reasons:

- Getting information about the directly connected CDP devices such as the operating system version and IP address.
- Checking that the OSI layer 2 connectivity is okay in case of IP (OSI layer 3) connectivity problems

The CDP announcements are sent to the multicast destination address 01-00-0c-cc-cc-cc.

CDP on Linux:

Linux does not natively support the CDP protocol, so we have to use a tool called “cdp-tools” to activate it.

Enabling CDP on Linux systems can be interesting on routers like Quagga and Vyatta in a Cisco environment.

Download CDP-tools in the /root directory.
If you want to download “cdp-tools” directly from the Linux CLI, proceed as follows:

#wget http://gpl.internetconnection.net/files/cdp-tools.tar.gz

Extract “cdp-tools”:

#tar -xvf cdp-tools.tar

This will create the “cdp-tools” directory.

Download and install the “build-essential” meta-package containing the tools to compile programs.

#apt-get install build-essential

Download and install libnet0-dev:
Libnet0 is a generic networking API that provides access to several protocols.

#apt-get install libnet0-dev

The libpcap library (in our example libpcap0.8-dev) is installed at the same time.

Compile “cdp-tools”:

#make

cc -D_BSD_SOURCE -D__BSD_SOURCE -D__FAVOR_BSD -DHAVE_NET_ETHERNET_H -DLIBNET_LIL_ENDIAN -c -o cdp-listen.o cdp-listen.c
cc cdp-listen.o /usr/lib/libpcap.so -o cdp-listen
cc -D_BSD_SOURCE -D__BSD_SOURCE -D__FAVOR_BSD -DHAVE_NET_ETHERNET_H -DLIBNET_LIL_ENDIAN -c -o cdp-send.o cdp-send.c
cdp-send.c:70: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[6]‘
cdp-send.c:71: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[6]‘
cdp-send.c:74: warning: ‘packed’ attribute ignored for field of type ‘u_int8_t’
cdp-send.c:75: warning: ‘packed’ attribute ignored for field of type ‘u_int8_t’
cdp-send.c:77: warning: ‘packed’ attribute ignored for field of type ‘u_int8_t’
cdp-send.c:78: warning: ‘packed’ attribute ignored for field of type ‘u_int8_t[3]‘
cc cdp-send.o /usr/lib/libnet.so -o cdp-send

If everything goes as planned, you should have two new files called “cdp-send” and “cdp-listen” which are used to respectively send or receive traffic.

1. cdp-send

Launch cd-send

cdp-send is used to send CDP traffic to directly connected devices.

Let’s launch cdp-send with the minimal setting:

Syntax: cdp-send [options] interfaces… &

/root/cdp-tools/cdp-send eth0

“eth0″ is the interface through which we are sending CDP traffic.
“/root/cdp-tools/cdp-send eth1 eth2″ would send CDP traffic trough the eth1 and eth2 interfaces.

Check how a directly connected Cisco device sees our Linux machine:

Cisco_device>show cdp neighbours

Capability Codes:	R - Router, T - Trans Bridge, B - Source Route Bridge
	S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone

Device ID	Local Intrfce	Holdtme	Capability	Platform	Port ID
ubuntu	Fas 1/0/5	176	H	i686	eth0

The Linux system is seen as a layer 3 host “H”, on interface “eth0″, with a hostname “ubuntu” and a platform “i386″.

Cisco_device>show cdp neighbours details

Device ID: ubuntu
Entry address(es):
IP address: 10.1.1.1
Platform: i686, Capabilities: Host
Interface: FastEthernet1/0/5, Port ID (outgoing port): eth0
Holdtime : 120 sec

Version :
Linux 2.6.22-10-generic

advertisement version: 2
Management address(es):

Configure “cdp-tools” to start automatically on startup:

#crontab -u root -e

@reboot /root/cdp-send eth0

cd-send advanced settings:

To see the advanced settings:

#/root/cdp-send

Usage: cdp-send [options] interfaces… &
	-a	addr	use specified address instead of that on interface
	-c	caps	enable capabilities (try -c list)
	-d	enable	debugging output
	-D	dom	specify VTP management domain (octal escapes ok)
	-L	vlan	specify native VLAN (vlanid)
	-V	vlan	specify voice VLAN (voiceid)
	-m	mach	specify machine/platform to advertise (e.g. “i686″)
	-n	name	specify a hostname
	-p	name	override port name (default: interface)
	-P	duplex	specify port duplex (full/half)
	-o	enable	oneshot mode
	-s	vers	specify software/version to advertise (e.g. “Linux 2.6.22-10-generic”)
	-S	subnet	specify ip prefix/subnet (need for routers, etc)
	-t	secs	set wait-time (default: 60 seconds)

Let’s see an example, where our test ubuntu machine pretends to be a Cisco device.

#/root/cdp-send eth0 -n “7206 Core” -m 7206VXR -p “Fas 0/0″ -P half -c l3r -s 7206VXR -a 10.1.1.1 -V 123 -s “Cisco Internetwork Operating System Software S ™ 7200 Software (C7200-IK9S-M), Version 12.2(23a), RELEASE SOFTWARE (fc2) Copyright (c) 1986-2004 by cisco Systems, Inc. Compiled Tue 30-Mar-04 12:26 by kellmill”

Check how the directly connected Cisco device sees our Linux machine:

Capability Codes:	R - Router, T - Trans Bridge, B - Source Route Bridge
	S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone

Device ID	Local Intrfce	Holdtme	Capability	Platform	Port ID
7206 Core	Fas 1/0/5	176	R	7206VXR	Fas 0/0

The Linux system is seen as a layer 3 router “R”, on interface “Fas 0/0″, with a hostname “7206 Core” and a platform “7206VXR”.

Cisco_device>show cdp neighbours details

Device ID: 7206 Core
Entry address(es):
IP address: 10.1.1.1
Platform: 7206VXR, Capabilities: Router
Interface: FastEthernet1/0/5, Port ID (outgoing port): Fas 0/0
Holdtime : 164 secVersion :
Cisco Internetwork Operating System Software S ™ 7200 Software (C7200-IK9S-M), Version 12.2(23a), RELEASE SOFTWARE (fc2) Copyright (c) 1986-2004 by cisco Systems, Inc. Compiled Tue 30-Mar-04 12:26 by kellmilladvertisement version: 2
Management address(es):

cd-send packet analysis:

The debugging (-d) option shows the CDP Ethernet frame.

#/root/cdp-send eth0 -d -n “7206 Core” -m 7206VXR -p “Fas 0/0″ -P half -c l3r -s 7206VXR -a 10.1.1.1 -V 123 -s “Cisco Internetwork Operating System Software S ™ 7200 Software (C7200-IK9S-M), Version 12.2(23a), RELEASE SOFTWARE (fc2) Copyright (c) 1986-2004 by cisco Systems, Inc. Compiled Tue 30-Mar-04 12:26 by kellmill”

Sent over: eth0, total length: 306
0000 01 00 0c cc cc cc 00 1c 23 11 22 33 01 24 aa aa	……..#….$..
0001 03 00 00 0c 20 00 02 b4 d4 3d 00 01 00 0d 37 32	…. ….=….72
0002 30 36 20 43 6f 72 65 00 02 00 11 00 00 00 01 01	06 Core………
0003 01 cc 00 04 0a 01 01 01 00 03 00 0b 46 61 73 20	…………Fas
0004 30 2f 30 00 04 00 08 00 00 00 01 00 05 00 d7 43	0/0…………C
0005 69 73 63 6f 20 49 6e 74 65 72 6e 65 74 77 6f 72	isco Internetwor
0006 6b 20 4f 70 65 72 61 74 69 6e 67 20 53 79 73 74	k Operating Syst
0007 65 6d 20 53 6f 66 74 77 61 72 65 20 53 20 28 74	em Software S (t
0008 6d 29 20 37 32 30 30 20 53 6f 66 74 77 61 72 65	m) 7200 Software
0009 20 28 43 37 32 30 30 2d 49 4b 39 53 2d 4d 29 2c	(C7200-IK9S-M),
000a 20 56 65 72 73 69 6f 6e 20 31 32 2e 32 28 32 33	Version 12.2(23
000b 61 29 2c 20 52 45 4c 45 41 53 45 20 53 4f 46 54	a), RELEASE SOFT
000c 57 41 52 45 20 28 66 63 32 29 20 43 6f 70 79 72	WARE (fc2) Copyr
000d 69 67 68 74 20 28 63 29 20 31 39 38 36 2d 32 30	ight (c) 1986-20
000e 30 34 20 62 79 20 63 69 73 63 6f 20 53 79 73 74	04 by cisco Syst
000f 65 6d 73 2c 20 49 6e 63 2e 20 43 6f 6d 70 69	6c ems, Inc. Compil
0010 65 64 20 54 75 65 20 33 30 2d 4d 61 72 2d 30 34	ed Tue 30-Mar-04
0011 20 31 32 3a 32 36 20 62 79 20 6b 65 6c 6c 6d 69	12:26 by kellmi
0012 6c 6c 00 06 00 0b 37 32 30 36 56 58 52 00 0b 00	ll….7206VXR…
0013 05 00	…

The same Ethernet frame analyzed with tshark, the CLI Wireshark version.

Frame 4 (306 bytes on wire, 306 bytes captured)
	Arrival Time: Nov 11, 2007 14:37:11.128038000
	[Time delta from previous captured frame: 0.614262000 seconds]
	[Time delta from previous displayed frame: 0.614262000 seconds]
	[Time since reference or first frame: 1194615431.128038000 seconds]
	Frame Number: 4
	Frame Length: 306 bytes
	Capture Length: 306 bytes
	[Frame is marked: False]
	[Protocols in frame: eth:llc:cdp:data]
IEEE 802.3 Ethernet
	Destination: CDP/VTP/DTP/PAgP/UDLD (01:00:0c:cc:cc:cc)
		Address: CDP/VTP/DTP/PAgP/UDLD (01:00:0c:cc:cc:cc)
		…. …1 …. …. …. …. = IG bit: Group address (multicast/broadcast)
		…. ..0. …. …. …. …. = LG bit: Globally unique address (factory default)
	Source: Dell_11:22:33 (00:1c:23:11:22:33)
		Address: Dell_11:22:33 (00:1c:23:11:22:33)
		…. …0 …. …. …. …. = IG bit: Individual address (unicast)
		…. ..0. …. …. …. …. = LG bit: Globally unique address (factory default)
	Length: 292
Logical-Link Control
	DSAP: SNAP (0xaa)
	IG Bit: Individual
	SSAP: SNAP (0xaa)
	CR Bit: Command
	Control field: U, func=UI (0×03)
		000. 00.. = Command: Unnumbered Information (0×00)
		…. ..11 = Frame type: Unnumbered frame (0×03)
	Organization Code: Cisco (0×00000c)
	PID: CDP (0×2000)
Cisco Discovery Protocol
	Version: 2
	TTL: 180 seconds
	Checksum: 0xd43d [correct]
		[Good: True]
		[Bad : False]
	Device ID: 7206 Core
		Type: Device ID (0×0001)
		Length: 13
		Device ID: 7206 Core
	Addresses
		Type: Addresses (0×0002)
		Length: 17
		Number of addresses: 1
		IP address: 10.1.1.1
			Protocol type: NLPID
			Protocol length: 1
			Protocol: IP
			Address length: 4
			IP address: 10.1.1.1
	Port ID: Fas 0/0
		Type: Port ID (0×0003)
		Length: 11
		Sent through Interface: Fas 0/0
	Capabilities
		Type: Capabilities (0×0004)
		Length: 8
		Capabilities: 0×00000001
			…. …. …. …. …. …. …. …1 = Is a Router
			…. …. …. …. …. …. …. ..0. = Not a Transparent Bridge
			…. …. …. …. …. …. …. .0.. = Not a Source Route Bridge
			…. …. …. …. …. …. …. 0… = Not a Switch
			…. …. …. …. …. …. …0 …. = Not a Host
			…. …. …. …. …. …. ..0. …. = Not IGMP capable
			…. …. …. …. …. …. .0.. …. = Not a Repeater
	Software Version
		Type: Software version (0×0005)
		Length: 215
		Software Version: Cisco Internetwork Operating System Software S ™ 7200 Software (C7200-IK9S-M), Version 12.2(23a), RELEASE SOFTWARE (fc2) Copyright (c) 1986-2004 by cisco Systems, Inc. Compiled Tue 30-Mar-04 12:26 by kellmill
	Platform: 7206VXR
		Type: Platform (0×0006)
		Length: 11
		Platform: 7206VXR
	Duplex: Half
		Type: Duplex (0×000b)
		Length: 5
		Duplex: Half

The example above, where a device pretends to be another by sending false CDP information, could be used by dishonest people.
Furthermore, if a hacker copies your usual network device banner, you could think the Linux system is one of your Cisco devices and try to log into this device with your credentials which would be captured by the hacker.

2. cdp-listen

cdp-listen is used to receive CDP packets.
Let’s see how our test Linux sees the Cisco device directly connected to its eth0 interface.

#/root/cdp-listen eth0

# Interface:	eth0
# Hostname:	Cisco-hall4.katesgantung.com
# Address:	10.117.1.234
#
# TimeToLive:	180
# Capabilities:	L3R(router) L2SW(switch) IGRP
#
# Networks:

Configure “cdp-tools” to start automatically at startup:

#crontab -u root -e

@reboot /root/cdp-listen eth0

Share and Enjoy:

Finding the Optimal MTU Size

2009-07-10T20:09:00.001+09:30

To find the optimal size of MTU (Maximum Transmission Unit) for your computer to connect to a network / broadband router, perform the test here.

In addition to the information on the test page, it is necessary to change the router MTU size, which is usually done by logging into the web interface and changing the MTU size field on one of the set-up screens.

Default sizes in the UK are:
ADSL = 1458
ADSL2 = 1500 or 1478 if 1500 causes problems

********************************************

MTU Ping Test

A series of ping tests using the command, ping www.expedient.net -f -l xxxx, where xxxx is the packet size, can be used to determine the optimal MTU for your connection.

Go to Start and select Run.
Type in cmd (Windows 2000/XP) or command (Windows 98/ME) into the Open: field. Hit the enter key or click OK. The DOS prompt should open.
At the DOS prompt, type in ping www.expedient.net -f -l 1492 and hit the Enter key.
Note the results above indicate that the packet needs to be fragmented. Lower the size the packet in increments of +/-10 (e.g. 1472, 1462, 1440, 1400) until you have a packet size that does not fragment.
Begin increasing the packet size from this number in small increments until you find the largest size that does not fragment. Add 28 to that number (IP/ICMP headers) to get the optimal MTU setting. For example, if the largest packet size from ping tests is 1462, add 28 to 1462 to get a total of 1490 which is the optimal MTU setting.
Change the MTU using DrTCP or editing the registry. See MTU Settings for further information.

FTP firewall issues in Passive mode

2009-07-09T15:06:00.001+09:30

In Linux, the default FTP mode is "Passive" where it is "Active" in Windows. The Passive mode FTP causes client to connect to high portÂ in server. This high port is unpredictable and can range from 1024 to 65535 (high ports). Different client connections use different ports and it is difficult to identify the port which needs to be opened in server side to establish data connection from client in Passive mode. Normally if you use a firewall (say iptables) and block all the ports except 21 (FTP control port), the data transfer between client and server will be blocked in Passive mode.

Here is a simple solution using iptables to overcome this situation by allowing all high ports in server. (configuration will be saved in /etc/sysconfig/iptables)

-A INPUT -p tcp -m tcp -s 0/0 -d 0/0 --dport 21 -j ACCEPT
-A INPUT -p tcp -m tcp -s 0/0 -d 0/0 --dport 1024: -j ACCEPT

The INPUT chain will accept all incoming connections on any high port in server. But it is less secure and not recommended to leave your server ports open to everyone.

So here is a better solution implemented using the connection tracking mechanismfor FTP in iptables. This is achieved in iptables by loading an additional module called "ip_conntrack_ftp". This module will keep track of your established control connections and will find out the required data connections to be opened by analysing PORTcommand sent over the control channel. ip_conntrack_ftp module will open those required high ports only in server and allow data transfer.

You can enable this module in two ways. For loading the module on demand, execute

/sbin/modprobe ip_conntrack_ftp

And for loading it when iptable starts, modify the iptables configuration file "/etc/sysconfig/iptables-config" as given below

IPTABLES_MODULES="ip_conntrack_netbios_ns ip_conntrack_ftp"

Addition modules can be loaded by placingÂ their names separated by space.

So the new iptables entry will be like this

-A INPUT -p tcp -m tcp -s 0/0 -d 0/0 --dport 21 -j ACCEPT

Here you are specifying only the control connection in iptables and data connection will be opened on demand by ip_conntrack_ftp module.

Voice encryption

2009-07-02T09:53:00.001+09:30

http://www.broadbandreports.com/forum/remark,13657675~start=20

I currently have no way of telling how good the encryption built into the Sipura adapters is (so it may be easier to "crack" then people believe). And furthermore, the only place I've found to get the encryption keys is the Voxilla.com web site (and no matter how secure a web site is, it is still a "3rd party" that has access to your keys, and from a security/encryption standpoint that is "a bad thing"). And finally, encryption will only work with other sites/adapters that support encryption, which most of them don't (so most of your calls will still probably behave the same as if you didn't have encryption enabled).

So all things considered, I wouldn't trust Sipura "secure calls" (encryption) to keep people from "listening in" on your calls. However, it might "slow them down" some, and IMHO you have nothing to lose by enabling this feature. After all, if the encryption works, you may have prevented some "eves-dropper" from intercepting you call. But even if the encryption fails, you are no worse off then before (because the "normal case" is to send your voice "in the clear"). With that in mind, here is how I just enabled voice encryption on my Sipura adapters (tested by calling between my SPA-3000, and my older SPA-2000).

1) Sign up with a free account at »www.voxilla.com. This is necessary, as the only place I am currently aware of that allows you to get the encryption keys is the voxilla web site, and they require you to be a "member" to run their "wizards".

2) Go to the Voxilla Sipura encryption Wizard. You can either find the link (on the left hand panel) at the main voxilla web site, or the current "direct link" is at this URL: »voxilla.com/certrequest.php

3) On the above web page, completely fill out the form. Apparently the form will fail unless ALL of the field (including the "Your name or alias" field) are filled in. In the case of the "Your name or alias" field entry, if you don't want to fill it in, do what I did, and just use a single space character as your "name". This Wizard will allow you to push a set of keys (public and private) to your Sipura. Don't forget that this Wizard needs to be run once for each "Line" that the Sipura has (for example, my SPA-2000 has two "lines", and each line needs a different "key").

4) Check to make sure that the Voxilla encryption wizard pushed encryption keys to your adapter. You can verify this by looking at the (admin login, advanced) "Line x" tab fields: "Mini Certificate:" and "SRTP Private Key:". If these fields are still empty/blank (the default for Sipura adapters) than the Wizard didn't do its job. However, if the "Mini Certificate:" has a bunch of characters in it, and the "SRTP Private Key:" shows "*************" (indicating that something hidden is in that field), than the public/private keys were entered into your Sipura (which is what you want to have happen).

5) The Voxilla wizard suggests you enter "*18" to do a "secure" call. However, why would you want to bother with that? Wouldn't you want the Sipura to just "default" to "secure" mode when it can? To make "secure"/"encrypted" calls the default (while still allowing other calls when encryption isn't available), go over to the (admin login, advanced) user tab for the line, and change "Secure Call Setting:" to "yes".

6) At this point, the Sipura should work the same as it did before, EXCEPT when you call DIRECTLY (not via a 3rd party) some location that supports encrypted calls (for example, another Sipura with this feature enabled). When encryption is supported (by both sides), the Sipura appears to take an extra second or so to initially connect, and then beeps at you three times (to let you know that the call is "secure"). I also noticed a little extra (maybe 1/3 second?) latency/lag in the call, but the sound was otherwise "clear" when I tried this on my LAN between my SPA-2000 and SPA-3000.

NOTE: I have not yet had an opportunity to test encryption with "Free World Dialup" (so YMMV). But according to posts I've seen in the past, FWD does support (pass though) Sipura voice encryption when all of the following are the case: 1) Both parties (the caller and the called party) in the call have Sipura adapters with encryption keys installed (and remember they are NOT installed by default, you have to use the Voxilla wizard to get them). 2) Both parties are on FWD directly, not via some "peering partner". 3) Both parties are using "fwd.pulver.com" as their proxy (i.e. neither party is using the alternate "fwdnat.pulver.com"). and 4) the party making the call has told their adapter to make a "secure call" (for example by having "Secure Call Setting: yes").

A list of Sipura "tricks", and pap2, multiple providers

2009-07-02T09:33:00.004+09:30

Since I started this thread, I thought I would post a few "tricks". All of the "tricks" in this note work by adding things to the "Dial Plan" for the line in your SPA. If you have an "unlocked" SPA you can use these tricks. However, if you have a "locked" SPA, the provider may prevent you from editing the "Dial Plan" (and thus prevent you from using these "tricks").

NOTE: Per the Sipura SPA-xxxx manual, all dial plan patterns need to be separated from each other by a "|" (vertical bar) character. So when I say to add a pattern to your dial plan, don't forget to separate it from the rest of the dial plan by a "|" character!

BTW: In my case, I have tested these tricks on "line 2" of my SPA-2000 (which is currently setup with the $11.99/month DialPad.com outbound VoIP service). Since these tricks do work on my SPA-2000, and they appear to follow the syntax that is common to the Sipura adapters, they should work with pretty much any SPA model. However, I have only tested them on my SPA-2000, so YMMV.

Trick 1: Do your own "911" support.
This can be useful if/when using a provider that doesn't provide 911 (for example dialpad.com). This does NOT give you E911 (just normal "speed dialing"), but it is better than nothing. You first decide which number you would like to "speed dial" when 911 is entered on a phone connected to that SPA-xxxx line. IMHO the "best way" to get the number, is to call the non-emergency number for your area (usually listed in the front a phone book), and ask them what number to call in an emergency when using a phone that can't directly dial 911. You can then make an automatic "translation" in the dial plan, so that 911 is turned into your own custom "speed dial". For example, if your emergency number is 319-555-2222 (no that's not a real emergency number, use the real number for your area), than the following added to your "Dial Plan" will enable custom 911 services:

<911:13195552222>S0

NOTE: Replace the dummy number after the : (above), with your real emergency "speed dial" number (before adding this code to your SPA's "Dial Plan")!

Trick 2: Calling Free World Dialup from a line provisioned to another provider.
The Sipura has a little understood "IP dialing" feature, that can be usefully combined with the FWD SIP gateway (and no you do NOT have to turn on "IP dialing" in the Sipura to use this trick). When you have a line provisioned to another provider (for example my "line 2" is setup for DialPad.com), you can still make outbound FWD calls (including calling the FWD "Service numbers", and calling "FWD partners") from that line for only 3 extra keystrokes. Once the following code is added to your line's "Dial Plan", FWD calls are as simple as pressing: #3 fwd_number # (for example, the FWD time number would be reached by calling #3612#).

<#3:>[x*].<#:>S0 <:@fwd.pulver.com>

Trick 3: Transparently use FWD for USA "Toll Free" numbers, instead of using your provider:
This is a variation of trick 2 (above). Some "pay as you go" VoIP providers not only charge for normal LD calls, but also charge for "toll free" calls. And other providers (such as DialPad.com), don't officially "support" calling toll free number via their service. In such cases, it could be useful to have toll free numbers automatically go via FWD, instead of dialing through your VoIP provider. You can easily force 1 (800/888/877/866) xxx-xxxx numbers to use FWD, by putting the following (long string) in your "Dial Plan" BEFORE (to the left of) the pattern that would normally dial LD numbers:

<:*>1800xxxxxxxS0 <:@fwd.pulver.com> | <:*>1888xxxxxxxS0 <:@fwd.pulver.com> |
<:*>1877xxxxxxxS0 <:@fwd.pulver.com> | <:*>1866xxxxxxxS0 <:@fwd.pulver.com>

**********************************************************************************

said by tlpintpe :

I think it was me trying to just cut and paste from your entries (dialing toll free numbers via FWD) that was the culprit. There is a carrage return in there, and when I edited the dial plan in a text editor, and removed the carrage return, then reentered the dial plan, all worked as it should.

Yep. A "dial plan" for a Sipura should all be on one line. Please ignore any extra "line breaks" in the examples. They are simply because BBR doesn't support 2K long text lines (without wrapping), whereas the Sipura dial plan does...

While we are on the subject of "dial plans", here are a couple of cute ones. Since SIPphone.com accepts inbound "peering", you can directly call any SIPphone.com account (which all have numbers in the form: 1 747 xxx-xxxx) by adding the following to your Dial Plan (before your normal LD pattern):

1 747 xxx xxxx <:@proxy01.sipphone.com>

And potentially even more interesting, is that you can use the "phone conferencing" ability of SIPphone (even if you don't have a SIPphone account), by adding the following to your Dial Plan (again before your normal LD pattern):

1 222 xxx xxxx <:@proxy01.sipphone.com>

Do I need to use two separate phones?

2009-07-01T15:39:00.000+09:30

Copied from http://scratchpad.wikia.com/wiki/Linksys_pap2:Home

I have not been able to get this to work.. yet I am using www.dyndns.com instead of no-ip.com Why? Because you can use www.dyndns.com in your WRT for DDNS. No WRT? Go buy one.

DracoFelis writes... Call one line of the SPA from the other line: This is not especially useful (more of a "parlor trick"), but it was a good "learning experience" in trying to get "forwarding" to work. Believe it or not, the SPA-2000 can directly call one line from the other (by using the internal "loop back" IP address)! Here's how:

First make sure that each "Line" on the SPA is setup with a unique SIP port, and a unique userid (i.e. make the settings for these two values different for each line). You will also need to set "Make call without reg: Yes" on the calling line, and "Ans Call Without Reg: Yes" on the line receiving. And you will also have to make sure that the lines have at least one CODEC in common (it might as well be "G711u", since the "call" is "internal" to the SPA). Finally, you will have to setup a "dial plan" to call the other line, at "userid@127.0.0.1:sip_port".

For example, if the other line is on SIP port 5063, and is userid "testing", than you can call that line (from the other one) by pressing #1 if you have the following as part of your "dial plan":

<#1:> S0 <:testing@127.0.0.1:5063>

And now (drum roll), how to forward all inbound calls to the OTHER line: This is VERY USEFUL, because it either lets you have a TWO VoIP accounts that both "ring" the same phone, OR lets you use one account for all incoming, and a 2nd account for all outgoing (by putting the "phone" on the line with the outgoing VoIP service, and then forwarding all incoming calls on that other VoIP line to that one)!

NOTE: This theory was tested earlier this evening, by forwarding my SPA-2000's "Line 1" (setup for FWD) to "Line 2" (setup for DialPad.com), and then calling my FWD number from Packet8. After I finally got all the pieces in place, my "Line 2" was happy to "ring", and when I picked up that phone 2-way talking worked fine! So this appears to work (at least for me). But naturally YMMV.

Here are the needed pieces:

1) As in the previous "trick", you need unique SIP ports and unique userids for the two lines. NOTE: It's quite OK to use whatever "userid" the provider on that line supplied (for logging into their SIP proxy). You don't need the UserId set to any specific value, just something unique!

2) Again, the line you are forwarding from will need "Make call without reg: Yes", and the line you want to forward to will need "Ans Call Without Reg: Yes".

3) If you are behind a router (I am), you will need to forward the SIP port of the line you want to ring (the line you are forwarding to) to the SPA. This is probably much easier if you program the SPA for a "static LAN IP" (instead of using DHCP).

4) Your external address will need to either be "static", _OR_ you will need to use a dynamic DNS service (btw: I'm happy with the free dynamic DNS service from »www.no-ip.com ). This is necessary, as you will need to always know the internet address of your SPA-2000 (not the LAN address, the "external address") for forwarding to work.

5) Turn on "Cfwd All Serv: yes" on the line you are forwarding "from" (i.e. if you want calls to the VoIP on "Line 1" to ring "Line 2", than you set this on "Line 1").

6) Go over to the "user" tab for the line you are forwarding from, and setup the "Cfwd All Dest:" field as "userid@external_address:sip_port". For example, if your dynamic DNS entry is "dummy.no-ip.com", your target line's userid is "testing", and the target line's SIP port is 5063, than you would want to "Cfwd All Dest:" to "testing@dummy.no-ip.com:5063".

NOTE: I was NOT successful in getting the loopback address (127.0.0.1) working for call forwarding (even though it worked for calling one line from the other, above). I had to use the "external address" for the SPA, to get forwarding to work (even between one line and the other on the same Sipura adapter)!

7) Test the setup. The easiest way is to get a friend to call the VoIP number you are forwarding from, and see if the forwarded to line "rings". In my case, I verified the setup by using my Packet8 account (and the Packet8 to FWD gateway) to call my FWD line (line 1 of my SPA-2000), and have the DialPad.com line (Line 2) ring! I then picked up the phones, and verified that two-way talking was working. Success!!!

Netapp introduction

2009-05-26T20:34:00.008+09:30

NETAPP技术学习全程记录

http://bbs.doit.com.cn/thread-59137-1-1.html

netapp的snapshot和emc的比较

NETAPP的snapshot采用的是“0”拷贝模式，而EMC用的却是“copy out"的方式，我想在时间上和在对系统性能的影响上NETAPP在这方面的优势是明显的，其实EMC的优势也只有那些比较大的吞吐量上了，当然，谨限于 SAN上，而且，尽管EMC的吞吐量比较大，但它的响应时间是很糟糕的，这点在SPEC上也有评测，大家可以去看看，不过上面只有跑NFS的性能，至少也能说明在NAS方面，NETAPP还是无人可比的，而且NETAPP现在是真正意义上的统一存储，EMC做NAS还要加网关这也是众所周知的~~~呵呵~~！！

NETAPP的0拷贝和它的WALF文件系统有关的。当你做SNAPSHORT的时候，新的数据不回覆盖以前老的数据块而是放在新的空磁盘空间，然后将 INODE指针指向新的位置，而SNAPSHORT里只保留INODE指针。也就是对NETAPP来是，SNAPSHORT实际上是指针的变化。所谓零拷贝是对数据来说的。其实指针是要拷贝的。

EMC的CLARIION里SNAPSHORT的原理不一样，它是建立一个reserv lun ,这个LUN的作用是将源LUN中数据发生变化的老数据拷贝出来,举个例子,对某个源LUN做个SNAPSHORT,那么当往这个LUN写数据的时候,首先,将老的数据拷贝到RESERV LUN,然后将新的数据覆盖老的数据块上.这时候才给写返回一个成功的信息.这里面和NETAPP的SNAPSHORT相比较会发现多了个数据COPY OUT的动作.如果激活了EMC的SNAPSHORT,这个SNAPSHORT是一个虚拟LUN实际上是由源LUN和RESERV LUN虚拟成一个LUN.这个LUN就是个快照.
那么是否认为EMC的块照没有NETAPP的块照好呢?我认为他们的设计理念不一样.谈不上谁好谁坏.举个例子,EMC的SNAPSHORT对SECOND SERVER是可写的.而NETAPP的SNAPSHORT只读的.这个本质上是由他们设计的不同原理来决定的.
个人认为.他们各有各的优势,具体还要看应用了.

Netapp产品线分为三大类：FAS系列主存储、近线存储、以及cache。
FAS系列有：fas200系列（fas250，fas270、fas270c）※FAS900系列（fas920、fas920c、fas940、 fas940c、fas960、fas960c、fas980、fas980c）。需要指出的是：fas270以上的主存储都是同时支持san、 iscsi、nas。

1.中端统一存储FAS920/FAS920C
2.DataOntap 7.0版本
DataOntap7.0开始支持缩小VOL了，以前是只能增大的。
7.0中的raid组可以跨VOL了
3.Spinserver 实现集群下的负载均衡

关于block的共享，现在实现的方法是只能在主机端安装软件吧，比如adic snms，sanergy，imagesan等，单凭ficon的存储设备本身就能实现blcok级的共享？我觉得不太可能，因为基于block，就意味着ip san或者fc san的访问，那样的话都是一对一的，所以必须在主机端安装相应的软件才能实现共享。

http://www.netapp.com/tech_library/3251.html

一篇ISCSI性能优化的文章，看看对你有没有帮助~~呵呵！

What are the main features that WAFL can provide?

WAFL is a UNIX compatible file system optimized for network file access. In many ways WAFL is similar to other UNIX file systems such as the B ...

NetApp 为此在公司成立之初就设计了一个高可用性、具有专利的文件系统WAFL，结合有电池保护的NVRAM（非挥发性内存）来担任WAFL的日志 (journal)，并藉由consistency points提供文件系统一致性 (consistent) 的保证，在不正常断电及关机时，重新开机后可在2分钟内开始提供服务，不需要执行文件系统检查，也不用担心文件系统会损毁。NetApp于1995年5月提出专利申请，在1998年10月获得专利（专利号码：5,819,292），题目为「Method For Maintaining Consistent States of A File System and For Creating User-Accessible Read-Only Copies of A File System」，前半部分就是WAFL，后半部分就是快照 (Snapshot)。另一项专利于1995年6月申请，在1998年9月获得专利（专利号码：5,948,110），题目为「Method For Providing Parity In a RAID Subsystem Using Non-Volatile Memory」，这就是如何利用NVRAM来加速RAID，并保护RAID数据的一致性。WAFL结合NVRAM、RAID、Snapshot的设计难度极高，故从1992年至今仍未有其它厂商可以做到。

希望楼主能解释一下NetApp独特的快照技术（无需存储空间）和RAID组扩展不需要同步，一分钟即可完成；还有卷大小和LUN的大小的区别；以及系统缓存有两个，分别使用的环境；还有就是需要杀毒软件，杀毒软件安装在什么地方？

1.NetApp独特的快照技术（无需存储空间）

有数据变化的时候一样需要空间,只是照的那下不用,只是复制root inode,所以很快,不影响系统性能,这也是WAFL的独到之处,别的文件系统做不到.

2.RAID组扩展不需要同步

NETAPP是raid4+,往RAID GROUP中加盘后,数据会先写你新加的盘,直到容量和RAID GROUP中的其他盘一样(由于是条带化,所有盘的使用容量一样)以后,再做所有盘的条带化,也就是在所有盘上写,所以一般扩展RG的时候都建议多加几块,否则比如只加一块盘的话,在容量到达和其他盘一样之前,这块盘提供的IOPS毕竟有限.还有不是1分钟完成,是瞬间完成.

3.还有卷大小和LUN的大小的区别

LUN是VOLUME的文件系统下的一个特殊文件.LUN属于VOLUME,占用VOLUME的空间.

前两个滋先生已经回答了
后两个我来答一下。

两个缓存
nvram＝操作日志保存的地方
ram＝实际数据page存放的地方。
nvram就好比数据库系统的日志文件，只不过数据库把日志放到磁盘上，而filer把日志放到nvram里。

杀毒。
vscan server与filer之间使用rpc通讯，通过设置各种策略，读的时候可以设置先查杀后给客户端。将来的版本中会增加其它选项。

Import expired images

2009-05-21T14:29:00.005+09:30

#1. Use the `bpimport` but first you have to move the tapes from the scratch pool into a valid data pool.
#2. If there is unexpired image on the tape, you don't have to expire the tape first, just do the phase 1 import, the expired image recard will be generated in database.

Phase1
/usr/openv/netbackup/bin/admincmd/bpimport -create_db_info -id -server nbmaster -L /tmp/bpimport.phase1 &

# /tmp/bpimport.phase1 is the log file.

Generate image list on that media:
/usr/openv/netbackup/bin/admincmd/bpimport -PM -s 07/15/08 12:30:00 -e 08/01/08 23:59:59 -id | awk '{print $5}' > /tmp/import_list

Phase2
/usr/openv/netbackup/bin/admincmd/bpimport -Bidfile /tmp/import_list -L /tmp/bpimport.phase2 &

Refer to:
http://seer.entsupport.symantec.com/docs/278948.htm
http://seer.entsupport.symantec.com/docs/259827.htm
Error when importing.
http://seer.entsupport.symantec.com/docs/284494.htm

VSS Provider and Netbackup

2009-03-15T04:51:00.009+10:30

VSS Provider:
http://technet.microsoft.com/en-us/library/cc785914.aspx

Veritas NetBackup (tm) 6.x Snapshot Client (Advanced Client) OS, Arrays and Database Agent Compatibility:
http://seer.entsupport.symantec.com/docs/279042.htm

Some common VSS error:
http://seer.entsupport.symantec.com/docs/308084.htm
http://seer.entsupport.symantec.com/docs/304279.htm
http://seer.entsupport.symantec.com/docs/281781.htm
http://seer.entsupport.symantec.com/docs/297223.htm

DOCUMENTATION: How to configure backup for maximum throughput when a volume or folder contains millions of small files.
http://support.veritas.com/docs/275912

DOCUMENTATION: Why are file system restores are running very slow with large number of small files?
http://support.veritas.com/docs/279061

White paper:
http://dell.altiris.com/portals/3/off-host_nbu_exchange_emc_clariion.pdf
http://eval.symantec.com/mktginfo/enterprise/white_papers/ent-whitepaper_vsfw_5.0_best_practices_for_storage_mgmt_02-2007.en-us.pdf
http://eval.symantec.com/mktginfo/enterprise/white_papers/ent-whitepaper_veritas_netBackup_6.5_vmware_nov2007.pdf
http://eval.symantec.com/mktginfo/enterprise/white_papers/ent-whitepaper_netbackup_for_ms_exchange_best_practices_guide_2005.en-us.pdf

robtest and caps

2009-03-14T16:41:00.002+10:30

assuming you are referring to the access cap.

1st option:
to move tape from slot 10 to access cap 1:
m s10 p1

to move tape from access cap 1 to slot 10:
m p1 s10

OR
2nd Option:

m s10 i1
move a media on slot 10(library slot number) to media access port 1(CAP on some libararies)

mpathadm luxadm fcinfo usage info

2009-02-09T21:52:00.000+10:30

Solaris 10 i386
Sun Microsystems Sun Fire X4100 M2
QLE2462

Which library support mpath
# mpathadm list mpath-support
mpath-support: libmpscsi_vhci.so

mpathadm list initiator-port (also you can get these wwn via fcinfo hba-port)
Initiator Port: iqn.1986-03.com.sun:01:ba98a3efffff.47286525,4000002a00ff
Initiator Port: 2100001b32025dc6
Initiator Port: 2101001b32225dc6
Initiator Port: 2101001b32224f93
Initiator Port: 2100001b32024f93

# mpathadm list lu
/dev/rdsk/c8t60060E800429D200000029D20000003Fd0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c8t60060E800429D200000029D200000800d0s2
Total Path Count: 2
Operational Path Count: 2

Check if your SAN is supported.
# mpathadm show mpath-support libmpscsi_vhci.so
Vendor: HITACHI
Product: OPEN
Revision:
Supported Load Balance Types:
round-robin

# mpathadm show initiator-port 2101001b32224f93
Initiator Port: 2101001b32224f93
Transport Type: Fibre Channel
OS Device File: /devices/pci@0,0/pci10de,5d@d/pci1077,143@0,1/fp@0,0

Get information about disk
# mpathadm show lu /dev/rdsk/c8t60060E800429D200000029D20000003Fd0s2
Logical Unit: /dev/rdsk/c8t60060E800429D200000029D20000003Fd0s2
mpath-support: libmpscsi_vhci.so
Vendor: HITACHI
Product: OPEN-V -SUN
Revision: 5007
Name Type: unknown type
Name: 60060e800429d200000029d20000003f
Asymmetric: no
Current Load Balance: none
Logical Unit Group ID: NA
Auto Failback: off
Auto Probing: NA

Paths:
Initiator Port Name: 2101001b32224f93
Target Port Name: 50060e800429d274
Override Path: NA
Path State: OK
Disabled: no

Initiator Port Name: 2100001b32024f93
Target Port Name: 50060e800429d264
Override Path: NA
Path State: OK
Disabled: no

Target Ports:
Name: 50060e800429d274
Relative ID: 0

Name: 50060e800429d264
Relative ID: 0

# This is another way to see disk information.
luxadm disp /dev/rdsk/c8t60060E800429D200000029D20000003Fd0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c8t60060E800429D200000029D20000003Fd0s2
Vendor: HITACHI
Product ID: OPEN-V -SUN
Revision: 5007
Serial Num: 50 029D2003F
Unformatted capacity: 46088.000 MBytes
Write Cache: Enabled
Read Cache: Enabled
Minimum prefetch: 0x0
Maximum prefetch: 0x0
Device Type: Disk device
Path(s):

/dev/rdsk/c8t60060E800429D200000029D20000003Fd0s2
/devices/scsi_vhci/disk@g60060e800429d200000029d20000003f:c,raw
Controller /dev/cfg/c4
Device Address 50060e800429d264,2
Host controller port WWN 2100001b32024f93
Class primary
State ONLINE
Controller /dev/cfg/c5
Device Address 50060e800429d274,2
Host controller port WWN 2101001b32224f93
Class primary
State ONLINE

# You can get hba info
fcinfo hba-port
HBA Port WWN: 2100001b32025dc6
OS Device Name: /dev/cfg/c6
Manufacturer: QLogic Corp.
Model: QLE2462
Firmware Version: 4.0.27
FCode/BIOS Version: N/A
Type: unknown
State: offline
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: not established
Node WWN: 2000001b32025dc6
HBA Port WWN: 2101001b32225dc6
OS Device Name: /dev/cfg/c7
Manufacturer: QLogic Corp.
Model: QLE2462
Firmware Version: 4.0.27
FCode/BIOS Version: N/A
Type: unknown
State: offline
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: not established
Node WWN: 2001001b32225dc6
HBA Port WWN: 2100001b32024f93
OS Device Name: /dev/cfg/c4
Manufacturer: QLogic Corp.
Model: QLE2462
Firmware Version: 4.0.27
FCode/BIOS Version: N/A
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 2Gb
Node WWN: 2000001b32024f93
HBA Port WWN: 2101001b32224f93
OS Device Name: /dev/cfg/c5
Manufacturer: QLogic Corp.
Model: QLE2462
Firmware Version: 4.0.27
FCode/BIOS Version: N/A
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 2Gb
Node WWN: 2001001b32224f93

# Get remote information over hba
fcinfo remote-port -l -s -p 2101001b32224f93
Remote Port WWN: 50060e800429d274
Active FC4 Types: SCSI
SCSI Target: yes
Node WWN: 50060e800429d274
Link Error Statistics:
Link Failure Count: 0
Loss of Sync Count: 0
Loss of Signal Count: 0
Primitive Seq Protocol Error Count: 0
Invalid Tx Word Count: 0
Invalid CRC Count: 0
LUN: 1
Vendor: HITACHI
Product: OPEN-V*5 -SUN
OS Device Name: /dev/rdsk/c8t60060E800429D200000029D200000800d0s2
LUN: 2
Vendor: HITACHI
Product: OPEN-V -SUN
OS Device Name: /dev/rdsk/c8t60060E800429D200000029D20000003Fd0s2

luxadm and SAN disks

2009-02-09T21:46:00.002+10:30

There are always a bunch of strange commands to connect a server to SAN disks. In my case, I’m running Solaris 9, using QLogic Fibre Channel cards, and connecting to an IBM DS4300.

1) Connect the Solaris server SAN disks. After I made the connection, the GUI that allows me to zone the SAN recognized the QLogic connections, and I zoned the LUNs.

If you need more detailed instructions, here are some potentially useful posts: How to Zone a Brocade SAN Switch and How to Zone IBM DS4000 SAN Disks.

2) Scan your disks, and it should show up as a new disk when you run “format”.

Solaris# devfsadm
Solaris# format

My result: No new disks. Sigh.

3) Run a bunch of cryptic but useful diagnostic commands:

To see your HBA ports and whether you’re connected:

Solaris# luxadm -e port
Found path to 3 HBA ports
/devices/pci@8,700000/SUNW,qlc@2/fp@0,0:devctl CONNECTED
/devices/pci@8,700000/SUNW,qlc@2,1/fp@0,0:devctl CONNECTED
/devices/pci@8,600000/SUNW,qlc@4/fp@0,0:devctl CONNECTED

To see your disks:

Solaris# luxadm probe

Or luxadm -e dump_map

To see your HBA ports (type fc-private, below) and their connected disks (type disk):

Solaris# cfgadm -al

Ap_Id Type Receptacle Occupant Condition
c8 fc-private connected configured unknown
c8::200800a0b8199b3b disk connected configured unknown
c9 fc-private connected configured unknown
c9::200900a0b8199b3b disk connected configured unknown

4) Force Fibre Channel SAN disk rescan, since everything looks connected and okay. Use your device path from “luxadm -e port” output.

Solaris# luxadm -e forcelip /devices/pci@8,700000/SUNW,qlc@2/fp@0,0:devctl
Solaris# luxadm -e forcelip /devices/pci@8,700000/SUNW,qlc@2,1/fp@0,0:devctl
Solaris# luxadm -e forcelip /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:devctl

5) Rerun format command.

Solaris # format

AVAILABLE DISK SELECTIONS:
0. c1t0d0
/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w500000e0107111e1,0
1. c1t1d0 t2
/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w500000e01070d761,0
2. c7t600A0B801019B1B2002032A5489C60F3d0
/scsi_vhci/ssd@g600a0b801019b1b2002032a5489c60f3

Voila! There it is, disk #2.

****************************

Here are some of the commands I use, also attached stuff for old ssa.

FCAL Disks
luxadm probe (discovers fcal)
luxadm display Enclosure (displays information on fcal box)
luxadm reserve /dev/rdsk/c#t#d#s# (reserves device so it can’t be accessed)
luxadm -e offline /dev/rdsk/c#t#d#s# (takes a device offline)
luxadm -e bus_quiesce /dev/rdsk/c#t#d#s# (quiesce the bus)
luxadm -e bus_unquiesce /dev/rdsk/c#t#d#s# (unquiesce the bus)
luxadm -e online /dev/rdsk/c#t#d#s# (bring the disk device back online)
luxadm release /dev/rdsk/c#t#d#s# (unreserved the device for use)
luxadm remove_device BAD,f2 (removes a device from slot f2 on enclosure BAD)
luxadm insert_device BAD,f2 (hot plug a new device to slot f2 on enclosure BAD)

SSAADM (for old ssa drawers)
ssaadm display c# (displays ssa on controller)
ssaadm display /dev/rdsk/c#t#d#s# (display drive information)
ssaadm start /dev/rdsk/c#t#d#s# (spin up a specific drive)
ssaadm stop /dev/rdsk/c#t#d#s# (spin down a specific drive)
ssaadm start –t 3 c# (spin up all drives in tray 3 on controller )
ssaadm stop –t 3 c# (spin down all drives in tray 3 on controller)
ssaadm start c# (spin up all drives in array)
ssaadm stop c# (stop all drives in array)

bpsetconfig

2009-01-30T15:58:00.000+10:30

bpsetconfig -H
NetBackup 6.5 -- Update Configuration

Usage: bpsetconfig [-h "host"] [-u "user"] ["file" ...] [-i|-e "file" [-c "class" [-s "schedule"]]]
bpsetconfig -H

Options:
-h Specifies the host name ("host") of the server or client
whose configuration will be updated.
-u Specifies the user ("user") whose configuration will be updated.
"file" Specified the file or files where the updates are listed.
If not specified, standard input is read.

-i Specifies the include file ("file") that will be set on the host.
-e Specifies the exclude file ("file") that will be set on the host.
-c Specifies the class for which the include or exclude file will be set.
-s Specifies the schedule for which the include or exclude file will be set.
-H Displays the help screen.

Finding Nemo, about trunking on Solaris 10

2009-01-28T13:55:00.001+10:30

From URL:
http://vegdave.wordpress.com/2006/12/02/finding-nemo-a-learning-journey-about-trunking-on-solaris-10/

Recently, I was looking for information on what Ethernet cards will work with Nemo drivers for link aggregation/trunking. It was a long search and took me a while to figure out what is supported and what product/technologies should be used on what hardware. So, here are my notes for configuring trunking on various Solaris 10 systems.

The first thing you should do before even begin working on trunking on a Solaris 10 machine is to make sure it has latest patches.

Next, check what kind of Ethernet driver do you have. There are several ways you can find out. Here is one way:

dladm show-link

Look for the first word for each line. If you see any of the following driver types, then you can use Nemo drivers: bge, e1000g, xge, nge, rge, ixgb

If you have qfe, ge, or ce, then you should use Sun Trunking 1.3. See also support matrix.

Let’s say that you have Nemo supported drivers, then here are the steps to setup link aggregation:

1. Identify which ports you want to aggregate. dladm show-link should give you an idea what are available. I’ll assume you want to aggregate bge0 and bge1.
2. Run the following command to create an aggregation interface:

dladm create-aggr -d bge0 -d bge1 1

If you get an error, it is most likly you either attempting to use Nemo drivers on a not supported Ethernet driver or you do not have the latest patches for Solaris 10.
3. Plumb the interface. See example below:

ifconfig aggr1 plub 192.168.1.200 up

4. Check the configuration:

dladm show-aggr
ifconfig -a

If you decided that Sun Trunking 1.3 is what you need, then follow the steps below:

1. Download the binary.
2. Read the Installation Guide
3. After unzip the binary from step #1, follow the installation steps stated in page 46 (printed on the left corner on the page or page 56 according to your Acrobat reader) in the Installation guide.
4. Install the appripriate patches for the driver you use. See page 44 (printed on the page or 54 according to Acrobat reader) in the Installation Guide.
5. Set local-mac-address as root on the command-line:

eeprom local-mac-address?=true

6.Reboot
7. Make sure the interfacs that you want aggregate isn’t plumb. If not, use the following command to unplumb:

ifconfig ce0 unplumb

8 Create an aggregated interface

/etc/opt/SUNWconn/bin/nettr -setup 0 device ce  members=0,1

This should create an aggregated interface for use with switches (MAC based policy) If you want to use Round Robin for back to back connection, use the following command instead:

/etc/opt/SUNWconn/bin/nettr -setup 0 device ce members=0,1 policy=2

See Page 29 and 32 for further information about other policies.
9. Plumb the interface.

ifconfig ce0 plumb 192.168.1.200 up

10. Check config:

/etc/opt/SUNWconn/bin/nettr -conf

Life will be easier once you get clearview with Solaris.

http://www.sun.com/products/networking/ethernet/suntrunking/

Mac OS X BBS

2009-01-26T23:00:00.004+10:30

PPC Mac and the VGA Mac Rom,
http://themacelite.wikidot.com/9250-trick
http://www.cubeowner.com/forums//index.php?showtopic=8806
http://strangedogs.proboards.com/index.cgi?board=experiments&action=display&thread=549

MacWind:
http://macos.it168.com = www.macwind.com

Yuanjing:
http://bbs.pcbeta.com

OSX86 Project:
http://wiki.osx86project.org/wiki/index.php/Main_Page

OS on USB

2009-01-22T21:26:00.001+10:30

Mac OS X on USB:
http://blog.bradbergeron.com/2006/11/howto-install-and-boot-os-x-on-a-flash-drive/

Linux on USB:
http://www.pendrivelinux.com/live-ubuntu-810-usb-persistent-install-windows/

250GB hosting
http://www.filedropper.com/

Operating System Configurations and resource controls

2009-01-20T22:31:00.000+10:30

http://docs.sun.com/app/docs/doc/819-4445/6n6jk8vb2?a=view

Operating System Configurations

To install and run the provisioning system, you must configure your systems as described in the following sections.

Solaris System Configuration Requirements

A Solaris system that is running the Master Server requires the following /etc/system settings.

Note –

If you are using the Solaris 9 or Solaris 10 OS, you cannot change the values for shmsys:shminfo_shmmin and shmsys:shminfo_shmseg. If you are using the Solaris 10 OS, you cannot change the values for shmsys:shminfo_shmmax, shmsys:shminfo_shmmni, semsys:seminfo_semmns, and semsys:seminfo_semvmx.

The default values for these settings are acceptable.

Table 2–2 Solaris /etc/system Settings


Variable	Minimum Value
`shmsys:shminfo_shmmax`	0x20000000 [536870912 in decimal (512Mb), but this number must be specified in hex for the Solaris 8 Operating System.]
`shmsys:shminfo_shmmin`	1
`shmsys:shminfo_shmmni`	2
`shmsys:shminfo_shmseg`	1
`semsys:seminfo_semmni`	32
`semsys:seminfo_semmns`	512
`semsys:seminfo_semmsl`	17
`semsys:seminfo_semvmx`	537

For more instructions to change the /etc/system settings, see Solaris Tunable Parameters Reference Manual.

Solaris 10 Configuration Requirements

In the Solaris 10 environment, the /etc/system settings are replaced by resource controls in the context of the user who owns the installation. The following table defines the minimum values:

Table 2–3 Solaris 10 Resource Controls Settings


Variable	Minimum Value
`project.max-shm-memory`	512
`project.max-sem-ids`	32
`process.max-sem-nsems`	17

To Determine If the Resource Controls Need to be Reset

Steps

Determine the project ID.
$ id -p

Verify the current values of project.max-shm-memory, project.max-sem-ids, and process.max-sem-nsems assuming a project ID value of 1.

# prctl -P -n project.max-shm-memory -i project 1
# prctl -P -n project.max-sem-ids -i project 1
# prctl -P -n process.max-sem-nsems -i process $$

Set resource controls.

If the current values do not meet the minimum settings required, you can use either the prctl command or the projmod command. Changes made with the prctl command are good only until system reboot. The projmod command should be used to make changes that persist across reboot.

Using the prctl command:

# prctl -n project.max-shm-memory -v 536870912 -r -i project 1
# prctl -n project.max-sem-ids -v 32 -r -i project 1
# prctl -n process.max-sem-nsems -v 17 -r -i process $$

Using the projmod command:

# projmod -a -K "project.max-shm-memory=(priv,512mb,deny)" default
# projmod -a -K "project.max-sem-ids=(priv,32,deny)" default
# projmod -a -K "process.max-sem-nsems=(priv,17,deny)" default

Comparing Price From Internet

2008-12-19T05:02:00.003+10:30

Books:
http://www.booko.com.au/

IT:
http://www.shopbot.com.au

http://staticice.com.au

Online auction:
http://www.graysonline.com.au/