<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ZyHui &#187; Unix技术文章</title>
	<atom:link href="http://blog.onecheng.com/archives/category/unix%e6%8a%80%e6%9c%af%e6%96%87%e7%ab%a0/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.onecheng.com</link>
	<description>技术不是问题，关键是做人要厚道！</description>
	<lastBuildDate>Thu, 20 May 2010 05:30:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>vac license配置</title>
		<link>http://blog.onecheng.com/archives/461</link>
		<comments>http://blog.onecheng.com/archives/461#comments</comments>
		<pubDate>Sat, 28 Nov 2009 15:28:11 +0000</pubDate>
		<dc:creator>zyhui</dc:creator>
				<category><![CDATA[Unix技术文章]]></category>
		<category><![CDATA[AIX]]></category>
		<category><![CDATA[vac]]></category>
		<category><![CDATA[xlc]]></category>

		<guid isPermaLink="false">http://blog.onecheng.com/archives/461</guid>
		<description><![CDATA[<p>安装好vac之后，在编译的时候提示“1506-507 (W) No licenses available. Contact your program supplier to add additional users. Compilation will proceed shortly”，这是因为没有正确配置LUM（License Use Management）引起的 。</p>
<p>cd /usr/opt/ifor/ls/os/aix/bin</p>
<p>./i4config</p>
<p>From a License Management point of view,</p>
<p>you can choose to configure this system as:</p>
<p>1) Network License Client </p>
<p>2) Nodelock License Server (and/or Network License Client)</p>
<p>3) Network (and/or Nodelock) License Server</p>
<p>4) Central Registry (and/or Network and/or [...]]]></description>
			<content:encoded><![CDATA[<p>安装好vac之后，在编译的时候提示“1506-507 (W) No licenses available. Contact your program supplier to add additional users. Compilation will proceed shortly”，这是因为没有正确配置LUM（License Use Management）引起的 。</p>
<p>cd /usr/opt/ifor/ls/os/aix/bin</p>
<p>./i4config</p>
<p>From a License Management point of view,</p>
<p>you can choose to configure this system as:</p>
<p>1) Network License Client </p>
<p>2) Nodelock License Server (and/or Network License Client)</p>
<p>3) Network (and/or Nodelock) License Server</p>
<p>4) Central Registry (and/or Network and/or Nodelock) License Server (*)</p>
<p>(*) Remember that one and only one Central Registry License Server (i4gdb daemon) can be active</p>
<p>in a Licensing domain.</p>
<p> <span id="more-461"></span>
<p>Please indicate your choice [1,2,3,4]: 2</p>
<p>Do you want to disable remote administration of this Nodelock License</p>
<p>Server? [y,n]: y</p>
<p>You have to choose now which mechanism must be enabled</p>
<p>to locate this License Server:</p>
<p>1) NCS Namespace and Direct Binding (*)</p>
<p>2) Direct Binding only</p>
<p>(*) WARNING: Modifying NCS Namespace configuration may affect</p>
<p>any other application that use NCS on this system.</p>
<p>NCS Namespace is necessary to support old Netls, iFOR/LS Clients.</p>
<p>Please indicate your choice [1,2]: 2</p>
<p>Choose the desired Server(s) logging level</p>
<p>1) Default </p>
<p>2) All </p>
<p>3) Customized </p>
<p>Please indicate your choice [1,2,3]: 1</p>
<p>The default Log file(s) path is /var/ifor</p>
<p>Enter blank to accept default or specify a new path:直接回车</p>
<p>*******************************************************************************</p>
<p>Server configuration is complete.</p>
<p>Do you want to modify the list of remote Nodelock and/or Network License Servers</p>
<p>this system can connect to in direct binding mode (both for</p>
<p>Administration purposes and for working as Network License Client) ? [y,n]: n</p>
<p>Do you want the License Server(s) automatically start on this system</p>
<p>at boot time? [y,n]: y</p>
<p>*******************************************************************************</p>
<p>WARNING: Configuration is about to end.</p>
<p>This is your last chance to quit before your updates will be written.</p>
<p>Do you want to continue? [y,n]:y</p>
<p>*** Configuration file updated. ***    <br />Do you want the License Server(s) start now? [y,n]: y     <br />0513-059 The i4llmd Subsystem has been started. Subsystem PID is 18636.     <br />&#8216;Start Services&#8217; has completed successfully     <br />****************************************     <br />* Configuration completed successfully *     <br />****************************************</p>
<p>导入license</p>
<p>./i4blt -a -f /usr/vac/cforaix_cn.lic -R u -T 1000 </p>
<p>i4blt Version 4.6.8 AIX &#8212; LUM Basic License Tool</p>
<p>(c) Copyright 1995-2004, IBM Corporation, All Rights Reserved</p>
<p>US Government Users Restricted Rights &#8211; Use, duplication or disclosure</p>
<p>restricted by GSA ADP Schedule Contract with IBM Corp.</p>
<p>(c) Copyright 1991-1997 Gradient Technologies Inc., All Rights Reserved</p>
<p>(c) Copyright 1991,1992,1993, Hewlett-Packard Company, All Rights Reserved</p>
<p>ADM-10099: Product successfully enrolled</p>
<p>成功导入之后即可正常编译。</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.onecheng.com/archives/461/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IBM P5小型机连接使用DS8000遇到问题处理一例</title>
		<link>http://blog.onecheng.com/archives/459</link>
		<comments>http://blog.onecheng.com/archives/459#comments</comments>
		<pubDate>Fri, 21 Aug 2009 01:02:45 +0000</pubDate>
		<dc:creator>zyhui</dc:creator>
				<category><![CDATA[Unix技术文章]]></category>
		<category><![CDATA[存储技术]]></category>
		<category><![CDATA[DS8000]]></category>
		<category><![CDATA[hacmp]]></category>
		<category><![CDATA[vpath]]></category>

		<guid isPermaLink="false">http://blog.onecheng.com/archives/459</guid>
		<description><![CDATA[<p>之前有两台570做的HACMP，使用的DS4800，最近新购DS8000，就把DS4800上的数据迁移到了DS8000上，迁移完之后测试都正常，第二天查看日志出现如下错误：</p>
<p>72206E77&#160;&#160; 0819080009 P H vpath5&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED   72206E77&#160;&#160; 0819080009 P H vpath4&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    72206E77&#160;&#160; 0819080009 P H vpath3&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    72206E77&#160;&#160; 0819080009 P H vpath2&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    72206E77&#160;&#160; 0819080009 P H [...]]]></description>
			<content:encoded><![CDATA[<p>之前有两台570做的HACMP，使用的DS4800，最近新购DS8000，就把DS4800上的数据迁移到了DS8000上，迁移完之后测试都正常，第二天查看日志出现如下错误：</p>
<p>72206E77&#160;&#160; 0819080009 P H vpath5&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED   <br />72206E77&#160;&#160; 0819080009 P H vpath4&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0819080009 P H vpath3&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0819080009 P H vpath2&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0819080009 P H vpath1&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0819080009 P H vpath0&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0819000009 P H vpath5&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0819000009 P H vpath4&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0819000009 P H vpath3&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0819000009 P H vpath2&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0819000009 P H vpath1&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0819000009 P H vpath0&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED</p>
<p>详细日志信息：</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;   <br />LABEL:&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; VPATH_RESV_CFLICT    <br />IDENTIFIER:&#160;&#160;&#160;&#160; 72206E77 </p>
<p> <span id="more-459"></span>
<p>Date/Time:&#160;&#160;&#160;&#160;&#160;&#160; Wed Aug 19 08:00:08 BEIST 2009   <br />Sequence Number: 93250    <br />Machine Id:&#160;&#160;&#160;&#160;&#160; 00C8A1ED4C00    <br />Node Id:&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; abicserv5    <br />Class:&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; H    <br />Type:&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; PEND    <br />Resource Name:&#160;&#160; vpath0&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; <br />Resource Class:&#160; disk    <br />Resource Type:&#160;&#160; vpath    <br />Location:&#160;&#160;&#160;&#160;&#160;&#160;&#160; </p>
<p>Description   <br />REQUESTED OPERATION CANNOT BE PERFORMED </p>
<p>Probable Causes   <br />SOFTWARE PROGRAM </p>
<p>Failure Causes   <br />DEVICE LOCKED BY ANOTHER USER </p>
<p>&#160;&#160;&#160;&#160;&#160;&#160;&#160; Recommended Actions   <br />&#160;&#160;&#160;&#160;&#160;&#160;&#160; RELEASE DEVICE PERSISTENT RESERVATION </p>
<p>Detail Data   <br />SENSE DATA    <br />0000 0000 8000 0036 0000 0000 0000 0001 0000 0000 0000 0000 0000 0000     <br />&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;    <br />LABEL:&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; VPATH_RESV_CFLICT    <br />IDENTIFIER:&#160;&#160;&#160;&#160; 72206E77 </p>
<p>Date/Time:&#160;&#160;&#160;&#160;&#160;&#160; Wed Aug 19 00:00:19 BEIST 2009   <br />Sequence Number: 93249    <br />Machine Id:&#160;&#160;&#160;&#160;&#160; 00C8A1ED4C00    <br />Node Id:&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; abicserv5    <br />Class:&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; H    <br />Type:&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; PEND    <br />Resource Name:&#160;&#160; vpath5&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; <br />Resource Class:&#160; disk    <br />Resource Type:&#160;&#160; vpath    <br />Location:&#160;&#160;&#160;&#160;&#160;&#160;&#160; </p>
<p>Description   <br />REQUESTED OPERATION CANNOT BE PERFORMED </p>
<p>Probable Causes   <br />SOFTWARE PROGRAM </p>
<p>Failure Causes   <br />DEVICE LOCKED BY ANOTHER USER </p>
<p>&#160;&#160;&#160;&#160;&#160;&#160;&#160; Recommended Actions   <br />&#160;&#160;&#160;&#160;&#160;&#160;&#160; RELEASE DEVICE PERSISTENT RESERVATION </p>
<p>Detail Data   <br />SENSE DATA    <br />0000 0000 8000 0036 0000 0005 0000 0001 0000 0000 0000 0000 0000 0005 </p>
<p>于是网上搜索，发现IBM官方有该问题的处理方法：</p>
<p><a title="http://www-900.ibm.com/cn/support/viewdoc/detail?DocId=1811149A13000" href="http://www-900.ibm.com/cn/support/viewdoc/detail?DocId=1811149A13000">http://www-900.ibm.com/cn/support/viewdoc/detail?DocId=1811149A13000</a></p>
<p>详细信息如下：</p>
<h3>errpt中报“72206E77 P H vpath 不能执行请求的操作”错误的解决方法</h3>
<p>环境:(产品,平台,机型,软件版本,等)</p>
<p>产品: AIX 5L HACMP5.2 or 5.3</p>
<p>平台: p5，pSeries, JS BladeCenter, ESS Storage</p>
<p>问题描述: </p>
<p>客户从errpt中发现在每天凌晨 00:00 零点零分的时候系统报“72206E77 P H vpath 不能执行请求的操作”    <br />的错误，这些vpath是属于HACMP中配置的磁盘，并且这些磁盘上的vg在对端节点上正varyon着，但是存储    <br />vpath硬盘的访问一切正常。</p>
<p>解答:</p>
<p>errpt的具体信息如下:</p>
<p>#errpt   <br />&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;    <br />标识符 时间戳记 T C 资源名 描述    <br />72206E77 1101000005 P H vpath16 不能执行请求的操作    <br />72206E77 1101000005 P H vpath14 不能执行请求的操作    <br />72206E77 1101000005 P H vpath12 不能执行请求的操作    <br />72206E77 1101000005 P H vpath11 不能执行请求的操作    <br />72206E77 1101000005 P H vpath9 不能执行请求的操作    <br />72206E77 1101000005 P H vpath8 不能执行请求的操作    <br />72206E77 1101000005 P H vpath6 不能执行请求的操作    <br />72206E77 1101000005 P H vpath5 不能执行请求的操作    <br />72206E77 1101000005 P H vpath3 不能执行请求的操作    <br />72206E77 1101000005 P H vpath1 不能执行请求的操作    <br />72206E77 1031000005 P H vpath16 不能执行请求的操作    <br />72206E77 1031000005 P H vpath14 不能执行请求的操作    <br />72206E77 1031000005 P H vpath12 不能执行请求的操作    <br />72206E77 1031000005 P H vpath11 不能执行请求的操作    <br />72206E77 1031000005 P H vpath9 不能执行请求的操作    <br />72206E77 1031000005 P H vpath8 不能执行请求的操作    <br />72206E77 1031000005 P H vpath6 不能执行请求的操作    <br />72206E77 1031000005 P H vpath5 不能执行请求的操作    <br />72206E77 1031000005 P H vpath3 不能执行请求的操作    <br />72206E77 1031000005 P H vpath1 不能执行请求的操作    <br />&#8230;&#8230;</p>
<p>errpt -a   <br />标号： VPATH_RESV_CFLICT    <br />标识符： 72206E77</p>
<p>日期／时间： 公元2005年11月01日 星期   <br />序号： 5237    <br />机器标识： 00C662AF4C00    <br />节点标识： bmccdb    <br />类： H    <br />类型： PEND    <br />资源名： vpath16    <br />资源类： disk    <br />资源类型： vpath    <br />位置：</p>
<p>描述   <br />不能执行请求的操作</p>
<p>可能原因   <br />软件程序</p>
<p>失败原因   <br />设备被另一个用户锁定</p>
<p>推荐的操作   <br />F100</p>
<p>详细数据   <br />检测数据    <br />2FF3 9694 8000 002B 0000 0010 0000 0001 0000 0000 0000 0000 0000 0010    <br />&#8230;&#8230;</p>
<p>===========================================================================   <br />方法一: (临时解决方法)    <br />忽略这个报错信息，这不是一个真正的功能问题，但是错误每天依旧报告。</p>
<p>方法二: (临时解决方法)   <br /># smit hacmp    <br />=&gt; Problem Determination Tools     <br />=&gt; HACMP Verification    <br />=&gt; Automatic Cluster Configuration Monitoring    <br />Automatic Cluster Configuration Monitoring    <br />Type or select values in entry fields.    <br />Press Enter AFTER making all desired changes.    <br />[Entry Fields]    <br />* Automatic cluster configuration verification Disabled +    <br />Node name Default +    <br />* HOUR (00 &#8211; 23) [00] +#</p>
<p>将每天 00:00 零点零分 &quot; Automatic cluster configuration verificatio &quot; 的功能禁用，   <br />然后停止HACMP应用程序，再进行HACMP配置的验证和同步，使之生效后，错误从此不再报告。</p>
<p>方法三:(永久解决方法)   <br />访问下面网址下载并安装HACMP的补丁进行永久的解决。</p>
<p>IY70222 (HACMP5.2):    <br />VPATH_RESERVATION_CONFLICT OR DISK ERRORS LOGGED WHEN CLVERIFY RUNS    <br /><a href="http://www-1.ibm.com/support/docview.wss?uid=isg1IY70222">http://www-1.ibm.com/support/docview.wss?uid=isg1IY70222</a></p>
<p>IY77629 (HACMP5.3):    <br />VPATH_RESERVATION_CONFLICT OR DISK ERRORS LOGGED WHEN CLVERIFY RUNS    <br /><a href="http://www-01.ibm.com/support/docview.wss?uid=isg1IY77629">http://www-01.ibm.com/support/docview.wss?uid=isg1IY77629</a></p>
<p>安装HACMP的补丁并重新启动系统以后，错误从此不再报告。</p>
</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>由于我们使用的HACMP版本是5.3的，于是下载IY77629补丁进行安装，安装之后重启服务器，以为万事大吉，没想到第二天依然看到有如下错误：</p>
<p>72206E77&#160;&#160; 0820080009 P H vpath5&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED   <br />72206E77&#160;&#160; 0820080009 P H vpath4&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0820080009 P H vpath3&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0820080009 P H vpath2&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0820080009 P H vpath1&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED    <br />72206E77&#160;&#160; 0820080009 P H vpath0&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; REQUESTED OPERATION CANNOT BE PERFORMED</p>
<p>&#160;</p>
<p>于是众人大呼IBM的文档也不靠谱，正在无计可施的时候，忽然发现该错误的一个特点：</p>
<p>安装HACMP补丁之前凌晨0点和8点都有报错，安装HACMP补丁之后只有8点报错，感觉有些蹊跷，进一步检查：</p>
<p># crontab -l</p>
<p>发现其中每天0点和8点执行的命令如下，其中0点执行的是HACMP的，8点的不清楚是什么东西。</p>
<p>0 0 * * * /usr/es/sbin/cluster/utilities/clcycle 1&gt;/dev/null 2&gt;/dev/null # HACMP for AIX Logfile rotation</p>
<p>0 8 * * * /home/cron/checksys.sh 1&gt;&gt;/home/cron/checksys.log 2&gt;&gt;/home/cron/checksys.err</p>
<p>由此可以判断出HACMP的补丁已经生效了，现在的问题是checksys.sh 是什么东西。</p>
<p>看一下checksys.sh 的内容：</p>
<p>cd /abbin;   <br />/abbin/nmon64 -f -s 600 -c 144;    <br />date;    <br />find /var/tmp/testtmp/*.tmp -mtime +3 -print|xargs rm -f;    <br />find /var/tmp/*.tmp -mtime +3 -print|xargs rm -f;    <br />date;</p>
<p>原来是nmon，到/abbin下看了下，这个nmin64竟然是2006年的，现在问题已经确定了，就是这个2006年的nmon64的问题了，应该更新最新的nmon就OK了。</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.onecheng.com/archives/459/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>IBM小型机启动报0c31错误处理一例</title>
		<link>http://blog.onecheng.com/archives/456</link>
		<comments>http://blog.onecheng.com/archives/456#comments</comments>
		<pubDate>Mon, 29 Jun 2009 02:06:28 +0000</pubDate>
		<dc:creator>zyhui</dc:creator>
				<category><![CDATA[Unix技术文章]]></category>
		<category><![CDATA[0c31]]></category>
		<category><![CDATA[IBM小型机]]></category>
		<category><![CDATA[启动]]></category>

		<guid isPermaLink="false">http://blog.onecheng.com/archives/456</guid>
		<description><![CDATA[<p>一台P550重启之后无法正常启动，远程在HMC上看到一直停留在0c31，又重启一次问题一样，于是检查主机，发现主机内置磁带机中有一盘磁带，于是怀疑是从磁带启动了，把磁带取出来，重新启动正常，进入系统之后查看启动顺序，果然启动顺序磁带在前</p>
<p># bootlist -m normal –o</p>
<p> 
<p>cd0</p>
<p>rmt0</p>
<p>hdisk0 </p>
<p>ent0 speed=auto duplex=auto bserver=000.000.000.000 client=000.000.000.000 gateway=000.000.000.000 =5</p>
<p>&#160;</p>
<p>更夸张的是该机器的rootvg做了mirror，而启动向里面竟然没有hdisk1，由此感觉当时装系统的人真是粗心大意，随后调整了启动顺序</p>
<p># bootlist -m normal –o hdisk0 blv=hd5 hdisk1 blv=hd5</p>
<p>再查看一下</p>
<p># bootlist -m normal -o</p>
<p>hdisk0 blv=hd5</p>
<p>hdisk1 blv=hd5</p>
<p>由此自己也总结了下经验：重新启动服务器之前要注意查看一下启动顺序，特别是在远程操作，要不然又得跑趟机房了。</p>
]]></description>
			<content:encoded><![CDATA[<p>一台P550重启之后无法正常启动，远程在HMC上看到一直停留在0c31，又重启一次问题一样，于是检查主机，发现主机内置磁带机中有一盘磁带，于是怀疑是从磁带启动了，把磁带取出来，重新启动正常，进入系统之后查看启动顺序，果然启动顺序磁带在前</p>
<p># bootlist -m normal –o</p>
<p> <span id="more-456"></span>
<p>cd0</p>
<p>rmt0</p>
<p>hdisk0 </p>
<p>ent0 speed=auto duplex=auto bserver=000.000.000.000 client=000.000.000.000 gateway=000.000.000.000 =5</p>
<p>&#160;</p>
<p>更夸张的是该机器的rootvg做了mirror，而启动向里面竟然没有hdisk1，由此感觉当时装系统的人真是粗心大意，随后调整了启动顺序</p>
<p># bootlist -m normal –o hdisk0 blv=hd5 hdisk1 blv=hd5</p>
<p>再查看一下</p>
<p># bootlist -m normal -o</p>
<p>hdisk0 blv=hd5</p>
<p>hdisk1 blv=hd5</p>
<p>由此自己也总结了下经验：重新启动服务器之前要注意查看一下启动顺序，特别是在远程操作，要不然又得跑趟机房了。</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.onecheng.com/archives/456/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AIX下限制某个IP对服务器的访问</title>
		<link>http://blog.onecheng.com/archives/454</link>
		<comments>http://blog.onecheng.com/archives/454#comments</comments>
		<pubDate>Thu, 25 Jun 2009 09:37:24 +0000</pubDate>
		<dc:creator>zyhui</dc:creator>
				<category><![CDATA[Unix技术文章]]></category>
		<category><![CDATA[AIX]]></category>
		<category><![CDATA[限制IP]]></category>
		<category><![CDATA[限制访问]]></category>

		<guid isPermaLink="false">http://blog.onecheng.com/archives/454</guid>
		<description><![CDATA[<p>&#160;</p>
<p> </p>
<p> 
</p>
</p>
<p></p>
<p> </p>
<p> </p>
<p> </p>
</p>
</p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
</p>
<p> </p>
<p>如果策略有变化，需要刷新一下</p>
<p></p>
]]></description>
			<content:encoded><![CDATA[<p>&#160;</p>
<p><a href="http://blog.onecheng.com/wp-content/uploads/2009/06/image.png" rel="lightbox[454]"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.onecheng.com/wp-content/uploads/2009/06/image_thumb.png" width="583" height="255" /></a> </p>
<p> <span id="more-454"></span>
</p>
</p>
<p><a href="http://blog.onecheng.com/wp-content/uploads/2009/06/image1.png" rel="lightbox[454]"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.onecheng.com/wp-content/uploads/2009/06/image_thumb1.png" width="645" height="167" /></a></p>
<p><a href="http://blog.onecheng.com/wp-content/uploads/2009/06/image2.png" rel="lightbox[454]"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.onecheng.com/wp-content/uploads/2009/06/image_thumb2.png" width="670" height="257" /></a> </p>
<p><a href="http://blog.onecheng.com/wp-content/uploads/2009/06/image3.png" rel="lightbox[454]"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.onecheng.com/wp-content/uploads/2009/06/image_thumb3.png" width="669" height="219" /></a> </p>
<p><a href="http://blog.onecheng.com/wp-content/uploads/2009/06/image4.png" rel="lightbox[454]"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.onecheng.com/wp-content/uploads/2009/06/image_thumb4.png" width="653" height="478" /></a> </p>
</p>
</p>
<p><a href="http://blog.onecheng.com/wp-content/uploads/2009/06/image5.png" rel="lightbox[454]"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.onecheng.com/wp-content/uploads/2009/06/image_thumb5.png" width="591" height="136" /></a> </p>
<p><a href="http://blog.onecheng.com/wp-content/uploads/2009/06/image6.png" rel="lightbox[454]"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.onecheng.com/wp-content/uploads/2009/06/image_thumb6.png" width="645" height="131" /></a> </p>
<p><a href="http://blog.onecheng.com/wp-content/uploads/2009/06/image7.png" rel="lightbox[454]"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.onecheng.com/wp-content/uploads/2009/06/image_thumb7.png" width="623" height="107" /></a> </p>
<p><a href="http://blog.onecheng.com/wp-content/uploads/2009/06/image8.png" rel="lightbox[454]"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.onecheng.com/wp-content/uploads/2009/06/image_thumb8.png" width="613" height="150" /></a> </p>
</p>
<p><a href="http://blog.onecheng.com/wp-content/uploads/2009/06/image9.png" rel="lightbox[454]"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.onecheng.com/wp-content/uploads/2009/06/image_thumb9.png" width="597" height="163" /></a> </p>
<p>如果策略有变化，需要刷新一下</p>
<p><a href="http://blog.onecheng.com/wp-content/uploads/2009/06/image10.png" rel="lightbox[454]"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.onecheng.com/wp-content/uploads/2009/06/image_thumb10.png" width="677" height="245" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.onecheng.com/archives/454/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IBM主机上清除告警黄灯方法总结</title>
		<link>http://blog.onecheng.com/archives/431</link>
		<comments>http://blog.onecheng.com/archives/431#comments</comments>
		<pubDate>Mon, 16 Mar 2009 05:32:05 +0000</pubDate>
		<dc:creator>zyhui</dc:creator>
				<category><![CDATA[Unix技术文章]]></category>
		<category><![CDATA[AIX]]></category>
		<category><![CDATA[IBM]]></category>
		<category><![CDATA[小型机]]></category>
		<category><![CDATA[黄灯]]></category>

		<guid isPermaLink="false">http://blog.onecheng.com/archives/431</guid>
		<description><![CDATA[<p>机器亮黄灯告警一般是有硬件问题（单电源等可能有安全隐患的硬件配置也可能造成黄灯亮起），见到后首先进行下硬件诊断，方法如下：    诊断系统，</p>
判断是否硬件故障：
<p>1、Root用户执行diag；     2、回车后，进第2项，advanced diagnostics routines；     3、选system verification；     4、选all resources，回车；     5、按F7（或esc+7）进行执行检测；     6、看返回结果，是否存在故障。 如存在故障，记录故障及errpt –a，再做处理。     如无故障，或故障解决后黄灯依然不熄灭，清除警告灯。 </p>
<p>&#160;</p>
<p> 
<p></p>
方法一：
<p>1、Root用户执行diag；     2、回车后，进第3项，Task Selection (Diagnostics, Advanced Diagnostics, Service Aids, etc.)； [...]]]></description>
			<content:encoded><![CDATA[<p>机器亮黄灯告警一般是有硬件问题（单电源等可能有安全隐患的硬件配置也可能造成黄灯亮起），见到后首先进行下硬件诊断，方法如下：    <br />诊断系统，</p>
<h6>判断是否硬件故障：</h6>
<p>1、Root用户执行diag；     <br />2、回车后，进第2项，advanced diagnostics routines；     <br />3、选system verification；     <br />4、选all resources，回车；     <br />5、按F7（或esc+7）进行执行检测；     <br />6、看返回结果，是否存在故障。 如存在故障，记录故障及errpt –a，再做处理。     <br />如无故障，或故障解决后黄灯依然不熄灭，清除警告灯。 </p>
<p>&#160;</p>
<p> <span id="more-431"></span>
<p></p>
<h6>方法一：</h6>
<p>1、Root用户执行diag；     <br />2、回车后，进第3项，Task Selection (Diagnostics, Advanced Diagnostics, Service Aids, etc.)；     <br />3、选Identify and Attention Indicators；（很奇怪有些机器没有这个选项，比如H50）     <br />4、Set System Attention Indicator to Normal或Set ALL Identify Indicators to NORMAL，回车；     <br />5、按F7（或esc+7）进行执行。     <br />这招对大多数情况都有效。     </p>
<h6>方法二：</h6>
<p>执行命令     <br /># /usr/lpp/diagnostics/bin/usysfault -s normal     <br />这招貌似适用于所有情况，无论机器有无故障都能熄灭黄灯，不过真正有故障的机器执行此命令后黄灯熄灭只是临时性的，过不多久黄灯可能会再次亮起。</p>
<h6>方法三：</h6>
<p>在diag选项Task Selection (Diagnostics, Advanced Diagnostics, Service Aids, etc.)下有一个菜单：    <br />Log Repair Action     <br />进入之后，选中sys0和sysplanar0，并按下F7或ESC+7执行，这样黄灯就灭了！！！     </p>
<h6>还一个方法没实验过：</h6>
<p>有HMC控制台的，在HMC控制台上:     <br />选择左列的“Serivce Applications”     <br />-&gt;Serivce Focal Point     <br />右侧的LED Management中您可以看到LED State，右键可以把它从On状态变到Off状态。</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.onecheng.com/archives/431/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>在AIX中挂载ISO镜像</title>
		<link>http://blog.onecheng.com/archives/396</link>
		<comments>http://blog.onecheng.com/archives/396#comments</comments>
		<pubDate>Fri, 27 Feb 2009 10:12:13 +0000</pubDate>
		<dc:creator>zyhui</dc:creator>
				<category><![CDATA[Unix技术文章]]></category>
		<category><![CDATA[AIX]]></category>
		<category><![CDATA[ISO]]></category>

		<guid isPermaLink="false">http://blog.onecheng.com/archives/396</guid>
		<description><![CDATA[<p>1、在任意VG中创建一个LV，（cdlv），大小要等于或大于ISO的大小。</p>
<p>2、编辑/etc/filesystems</p>
<p>vi /etc/filesystems</p>
<p>在最后添加</p>
<p> 
<p>/cdlv:</p>
<p>dev = /dev/cdlv</p>
<p>vfs = cdrfs</p>
<p>mount = false</p>
<p>options = ro</p>
<p>account = false </p>
<p>3、创建一个目录作为挂载点 /cdrom</p>
<p>4、拷贝ISO文件到cdlv中</p>
<p>dd if=/home/LCD4_7544_08_5765G03_AIX_5L_V5300802.iso of=/dev/cdlv bs=2048k</p>
<p>5、挂载该ISO</p>
<p>mount -rv cdrfs /dev/cdlv /cdrom</p>
<p>然后cd /cdrom就可以看到ISO中的文件了</p>
]]></description>
			<content:encoded><![CDATA[<p><strong>1、在任意VG中创建一个LV，（cdlv），大小要等于或大于ISO的大小。</strong></p>
<p><strong>2、编辑/etc/filesystems</strong></p>
<p>vi /etc/filesystems</p>
<p>在最后添加</p>
<p> <span id="more-396"></span>
<p>/cdlv:</p>
<p>dev = /dev/cdlv</p>
<p>vfs = cdrfs</p>
<p>mount = false</p>
<p>options = ro</p>
<p>account = false </p>
<p><strong>3、创建一个目录作为挂载点 /cdrom</strong></p>
<p><strong>4、拷贝ISO文件到cdlv中</strong></p>
<p>dd if=/home/LCD4_7544_08_5765G03_AIX_5L_V5300802.iso of=/dev/cdlv bs=2048k</p>
<p><strong>5、挂载该ISO</strong></p>
<p>mount -rv cdrfs /dev/cdlv /cdrom</p>
<p>然后cd /cdrom就可以看到ISO中的文件了</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.onecheng.com/archives/396/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- www.000webhost.com Analytics Code -->
<script type="text/javascript" src="http://analytics.hosting24.com/count.php"></script>
<noscript><a href="http://www.hosting24.com/"><img src="http://analytics.hosting24.com/count.php" alt="web hosting" /></a></noscript>
<!-- End Of Analytics Code -->
