无法删除文件系统
环境 产品：RS6000
平台：RS
软件版本：AIX 4.3
问题 可以mount或unmount一个文件系统，但却无法删除该文件系统，在删除时，系统报错：0516-306：get lvodm: unable to find in the device confgiguration data.
解答 发生此错误的原因可能是ODM数据库中的定义与实际不一致。可以用命令 lsvg -l rootvg 检查该文件系统的类型，若类型显示为？？？，则用命令 synclvodm -P rootvg 和 syncvg -v rootvg 进行同步，之后再用命令 lsvg -l rootvg 显示出正确的文件类型。此时可以成ι境?梦募?低场?
如何限制某些用户无法ftp至RS/6000服务器
环境 产品：RS6000
平台：RS
软件版本：AIX 4.3
问题 RS/6000的系统管理员想要限制某些用户无法ftp至RS/6000服务器, 如何做？
解答 可通过以下两种方法进行限制：
1. 直接编辑 /etc/ftpusers 文件，将被禁止进行ftp至本RS/6000服务器操作的用户名列在该文件中，每个用户名列一行。
2. 通过SMIT菜单设置：
smit ---> Communications Applications and Services ---> TCP/IP ---> Further Configuration ---> Server Network Services ---> Remote Access ---> Restrict File Transfer Program Users (/etc/ftpusers) ---> Add a Restricted User
如何扩大文件系统的空间
环境 平台：RS/6000
软件版本：AIX V4
问题 遇到文件系统空间已满的情况时，可用下述方法将其空间扩大。
解答 1. 运行命令
smit chfs
---> Change/Show Characteristics of a Journaled File System
将光标移至需要修改的文件系统，并按下回车键，屏幕显示如下（下表中各字段值为示例）：
*******************************************************
Change / Show Characteristics of a Journaled File System
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
File system name /
NEW mount point [/]
SIZE of file system (in 512-byte blocks) [98304]
Mount GROUP [bootfs]
Mount AUTOMATICALLY at system restart? yes +
PERMISSIONS read/write +
Mount OPTIONS [/] +
Start Disk Accounting? no +
Fragment Size (bytes) 4096
Number of bytes per inode 2048
Compression algorithm no
Large File Enabled false
Allocation Group Size (MBytes) 8
**************************************************************
2. 将光标直接定位于“SIZE of file system (in 512-byte blocks) [98304]”，把此文件系统当前定义的总空间值（例中为98304）改为需要的大小（注意：这里填写的数值以512字节为单位），按下回车键，命令运行结束后修改后的文件系统空间值立即生效。此操作不需重启系统。
3. 使用命令
df -k
可以查看修改后的文件系统空间值。
PCI 两口多协议卡（2-Port Multiprotocol PCI Adapter 9-L)的配置方法
环境 平台: RS/6000;
软件版本: AIX 3.2.5 -- AIX 4.3.3
问题 两口多协议卡(2-port PCI multiprotocol adapter)常被用于基于SNA协议的广域网的连接接口，本文介绍如何在AIX系统中配置此卡。
解答 1. 安装驱动程序
使用smit命令从AIX系统盘找出并安装下列驱动程序：
devices.pci.331121b9.com IBM PCI 2-Port Multiprotocol
devices.pci.331121b9.diag IBM PCI 2-Port Multiprotocol
Adapter (331121b9) Diagnostics
devices.pci.331121b9.rte IBM PCI 2-Port Multiprotocol
2. 运行命令
# lsdev -Cs pci | grep 331121b9
查看该卡的状态信息，命令输出如下：
dpmpa0 Available 04-05 IBM 2-Port Multiprotocol Adapter
3. 运行命令
# lsdev -Cs 331121b9
查看卡上端口的状态信息，命令输出如下：
hdlc0 Available 04-05-00 IBM HDLC Network Device Driver
hdlc1 Available 04-05-01 IBM HDLC Network Device Driver
4. SDLC仿真端口的配置
如果该卡用于SNA网络接口，需要安装软件包
devices.common.IBM.hdlc.sdlc
此软件包提供与MPQP驱动程序兼容的应用程序接口的支持。用户需要对每个hdlc端口配置SDLC COMIO 设备驱动程序的仿真设备。这可以通过smit 菜单完成。具体方法如下：
在命令行输入：
smitty sciesdlc_dd
显示菜单如下:
*****************************************************
Manage SDLC COMIO Device Driver Emulator
Move cursor to desired item and press Enter.
Add a Device Driver
Change/Show Characteristics of an SDLC Device Driver
Remove a Device Driver
Configure a Defined Device Driver
F1=Help F2=Refresh F3=Cancel F8=Image
F9=Shell F10=Exit Enter=Do
*****************************************************
选择“Add a Device Driver”将创建设备文件 “/dev/mpcX”（如/dev/mpc0, /dev/mpc1）。
使用命令行:
mkdev -c driver -s sdlc -t scie -a nddname=hdlc0
mkdev -c driver -s sdlc -t scie -a nddname=hdlc1' command
同样可以创建该设备文件mpc0 和mpc1。
上述步骤完成后，系统对两口多协议卡的配置工作已经完成。用户可以针对所使用的网络协议做进一步配置。
用户转换错误
环境 产品：RS6000
平台：RS
软件版本：AIX 4.3
问题 一个普通用户执行su命令切换到root或其他普通用户时，系统报错说权限被禁止(Authentication Denied).
解答 产生该错误的原因是/usr/bin/su文件的权限不正确。请用如下命令检查该文件的权限：
ls -l /usr/bin/su
正确的权限应为：-r-sr-xr-x root security /usr/bin/su
若权限不正确，用如下命令修改：
cd /usr/bin
chmod 4555 su
杀进程的shell程序
环境 AIX V4
问题 用来杀掉由用户"user1"产生的进程的shell命令。
解答 # kill -9 `ps -ef|grep user1|grep -v grep|awk '{print $2}'`
怎样在AIX中Mount Redhat Linux上的nfs文件系统？
环境 任何机型,操作系统 AIX 4.3.3，Redhat 6.2
问题 当在R6上mount redhat linux的nfs时，系统报错：
1831-008: Operation not permitted
解答 当在R6上mount redhat linux的nfs时，系统报错：
1831-008: Operation not permitted
用nfso命令修改参数nfs_use_reserved_ports,如下:
#nfso -o nfs_use_reserved_ports=1
缺省时AIX的参数nfs_use_reserved_ports是0，而linux
在响应客户的mount请求时，需要使用reserved_ports。
修改参数后，故障排除。
如何限制用户改变密码
环境 RS6000，AIX V4
问题 如何限制用户改变密码?
解答 可以用命令pwdadm -f ADMIN username来实现，如果想让用户恢复更改密码的权利，运行pwdadm -f ADMCHG username 来重置.
如何自动启动和关闭软件的运行
环境 产品: AIX
平台: RS
问题 本文档讨论了如何定制系统, 以使用户定义的应用在系统引导过程中自动启动, 并在系统关闭时自动停止.
解答 1. 自动启动定制的软件
在系统引导时, init进程顺序检测/etc/inittab文件, 决定在引导过程中进行什么样的操作.如果应用, 进程或其它的用户操作需要在系统引导过程中进行, 则要在/etc/inittab文件中加入相应的条目.通常的做法是创建一个名为rc.local的脚本文件, 将所有要在系统引导过程中启动的用户应用写入该脚本文件中. 该脚本文件可以在/etc/inittab文件中被调用, 通常是在所有系统应用和服务启动后, 在用户登录被允许之前被调用. 位置通常是在主控登录的条目前.
下面是一个例子:
rc.local:2:wait:/etc/rc.local > /dev/console 2>&1
在上面的条目中, init将在执行余下的条目之前等待该脚本程序的完成.如果进程, 应用或命令需要通过特定的用户运行, 则可在运行的命令中加入su命令.
如: su myuser "-c /usr/bin/myapp"
建议在脚本程序中加入应用开始启动和完成启动的输出提示.
如:
#!/bin/ksh
echo "Starting User Applications...."
echo "Starting Application XYZ"
su myuser "-c /usr/bin/myapp"
echo "Startup of User Applications completed"
2. 自动停止定制的软件
shutdown命令用于关闭AIX系统. 在此操作中会关闭所有AIX子系统及文件系统.如果名为/etc/rc.shutdown的脚本程序存在, 系统会首先执行该脚本程序中的命令. 在该脚本程序中可以加入关闭用户应用的命令. 建议在脚本程序中加入应用停止运行和完成停止运行的输出提示.
如:
#!/bin/ksh
echo "Stopping User Applications...."
echo "Stopping Application XYZ"
[ commands to stop application ]
echo "Shutdown of User Applications completed"
AIX4.3 的维护包(Maintenance Level) 及推荐维护包(Recommended Maintenance)
内容
提要 说明
适用操作系统
AIX 4.3 维护策略
维护包(Maintenance Levels)
推荐维护包(Recommended Maintenance)
说明 本文描述了AIX4.3的维护策略以及作为一个对AIX 4.3维护包升级的通知。本文档在有新的升级维护包时将会被更新。
最新的 AIX 4.3 维护包(Maintenance Level) 是: 4.3.3
最新的 AIX 4.3.3 推荐维护包(Recommended Maintenance) 是: 4330-06
最新的 AIX 4.3 Update CD is: 0011
Maintenance Levels 和 Recommended Maintenance 可从FixDist中的 Base Maintenance Levels 得到。要得到更多的有关FixDist的信息, 请发邮件到 aixserv@austin.ibm.com 并以FixDist作为标题。
Update CD包含了对严重问题的修正补丁，预防性的维护包，软件功能的增强，以及对新硬件的支持驱动程序。
正文 适用操作系统
AIX 4.3
AIX 4.3 维护策略
=============
文件集(Filesets)
----------------
AIX 4.3 分为文件集, 文件集中又包含了一组逻辑相关的文件。每个文件集可以被独立地分为安装的和升级的。
对文件集的修订通过version, release, modification, and fix (VRMF) 来管理. 每次当文件集被升级后，fix的版本就会被调整。
每次当maintenance level被升级后，modification level 的版本就会被调整，而fix的版本就会被置为0。
维护包(Maintenance Levels)
======================
维护包(简称ML) 由从AIX 4.3 的base level文件集更新后的一系列文件集组成。
每个文件集的更新都是累计的，即它包含了AIX 4.3发布以来的所有那个文件集的补丁，并替换了所有以前的更新。
维护包(ML)的命名规则是4位的 VRMF.
V-version
R-release
M-modification
F-fix
AIX 4.3有3 个维护包(ML)：
* ML 4310, 也叫做 AIX 4.3.1
* ML 4320, 也叫做 AIX 4.3.2
* ML 4330, 也叫做 AIX 4.3.3
可以用oslevel来判定当前系统中的维护包版本。
推荐维护包(Recommended Maintenance)
=================================
推荐维护包(简称RM)是由一系列适用于最新的ML的文件集组成的软件包，它由一系列经过实际测试过的更新的文件集组成，
它提供了一种在两个完全ML之间来交付预防性的维护包的机制。
推荐维护包(RM)的命名规则是4位的 VRMF,在加两位数字后缀：
V-version
R-release
M-modification
F-fix
对于 ML 4330 有6个推荐维护包(RM)：
* 4330-01
* 4330-02
* 4330-03
* 4330-04
* 4330-05
* 4330-06
可以用以下的命令来判定是否4330-06已经安装在你的系统里，oslevel将仍然显示4.3.3.0,表示系统的ML仍是4330：
instfix -ik 4330-02_AIX_ML
AIX4.3.2下安装显卡GXT130P
环境 产品：RS6000
平台：AIX
版本：AIX 4.3.2
问题 AIX4.3.2下安装显卡GXT130P
解答 AIX4.3.2下安装显卡GXT130P
这个版本不支持该显卡,需要去从UPDATE光盘(JUNE 1999 or later)上安装驱动程序,包括:
devices.pci.2b102005.X11 4.3.2.0
devices.pci.2b102005.rte 4.3.2.1
devices.pci.2b101a05.X11 4.3.2.4
devices.pci.2b101a05.rte 4.3.2.4
/var/adm/wtmp文件保存所有用户登录的信息,随着时间会增长到很大,有时需要清理或编辑它,要清理它,
运行cp /dev/null /var/adm/wtmp. 要部分清理,用fwtmp命令先将文件wtmp变成ASCII格式的文件
dummy.file:/usr/sbin/acct/fwtmp < /var/adm/wtmp > dummy.file,编辑之后用
/usr/sbin/acct/fwtmp -ic < dummy.file > /var/adm/wtmp再将ASCII文件转变成二进制文件. 显示设置启动引导顺序
环境:(产品,平台,机型,软件版本,等)
问题描述:
解答:bootlist -m normal -o显示引导顺序,如hdisk0 cd0
bootlist -m normal cd0 hdisk0更改引导顺序为cd0 hdisk0
安装MAN
环境 产品：RS6000
平台：AIX
问题 安装MAN
解答 AIX上的帮助MAN需从文档盘上安装,所需要安装的文件集为:
bos.html.en_US.cmds.cmds1 4.3.0.1 AIX Commands Reference 1 - U.
bos.html.en_US.cmds.cmds2 4.3.0.1 AIX Commands Reference 2 -
bos.html.en_US.cmds.cmds3 4.3.0.1 AIX Commands Reference 3 -
bos.html.en_US.cmds.cmds4 4.3.0.1 AIX Commands Reference 4 -
bos.html.en_US.cmds.cmds5 4.3.0.1 AIX Commands Reference 5 - U.S
bos.html.en_US.cmds.cmds6 4.3.0.1 AIX Commands Reference 6 -
bos.html.en_US.nav 4.3.0.1 Online Navigation - U. S.
bos.html.en_US.topnav.navigate
改变主机IP地址解析顺序
环境 产品：RS6000
平台：AIX
问题 改变主机IP地址解析顺序
解答 一般主机IP地址的解析顺序是DNS,NIS,本机host文件,改变这个顺序,需创建一个/ect/netsvc.conf文件,并在这个文件中加一行hosts=local,bind,nis,这样主机IP地址就先从本地文件开始搜索,其次再去DNS server,最后是NIS server,也可通过运行export NSORDER=bind,nis,local改变环境变量来改变顺序
telnet提示"所有的网络端口已用"
环境 产品：RS6000
问题 telnet提示"所有的网络端口已用"
解答 1.检查pty0是否可用:lsdev -Cl pty0
2.检查telnet守护进程是否启动:lssrc -t telnet
3.检查/etc/security/login.cfg中maxlogins是否不够大
4.smitty pty检查最大可用终端是否够用
5.no -a|grep thewall检查网络缓冲是否够用
LED 223-229故障的解决
环境 产品: AIX
平台: RS
机型: RS6000
软件版本: V4
问题 统无法正常启动，液晶面板LED显示223-229.
解答 LED 223-229通常由非法引导列表顺序引起.应启动机器进入维护服务模式(对于较旧的微通道式机器,应将钥匙拧至维护模式后启动系统),更改引导列表顺序后,关机并重新启动系统.
LED 553故障的解决
环境 产品: AIX
平台: RS
机型: RS6000
软件版本: V4
问题 系统无法正常启动，液晶面板LED显示553.
解答 LED 553通常是由于/etc/inittab文件系统被破坏引起的.应检查并修正这些遭到破坏的文件系统.
具体步骤:
1.启动,进入维护模式;
2.用df命令检查根目录下,/var目录下和/tmp目录下的剩余空间;
3.检查/etc/inittab文件,并修正inittab文件的错误;
4.检查执行错误;
/etc/environment
/bin/bsh
/bin/fsck
5.重新启动系统.
AIX版本号释疑
环境 产品: AIX
平台: RS
机型: RS6000
软件版本: V4
问题 AIX的版本号代表什么意思?
解答 AIX的版本号的格式通常为AIX x.x.x.x.例如: AIX 4.3.3.1.其代表意义分别为:
操作系统版本号(version).发行版号(release).改进版号(modification).修正版号(fix)
/etc/preserve.list文件有什么用?
环境 产品: AIX
平台: RS
机型: RS6000
软件版本: V4
问题 /etc/preserve.list文件有什么用?
解答 /etc/preserve.list文件里包括有一个系统在BOS保留安装(preservation BOS installation)期间,所复制和保存的系统文件列表.
LED 201故障的解决
环境 产品: AIX
平台: RS
机型: RS6000
软件版本: V4
问题 系统无法正常启动，液晶面板LED显示201.
解答 LED 201通常由引导镜像损坏引起.应检查 /and/tmp 文件系统.
解决LED 201的具体步骤:
1.键入: lslv -m hd5 来确定引导盘;
2.键入: bostboot -a -d /dev/hdiskn 来重建引导镜像;
3.关机并重新启动系统.
LED 551,555和557故障的解决
环境 产品: AIX
平台: RS
机型: RS6000
软件版本: V4
问题 系统无法正常启动，液晶面板LED显示551,555或557.
解答 LED 551,555,557通常由文件系统被破坏或JFS日志被破坏引起.应检查并修正这些遭到破坏的文件系统.
具体步骤:
1.检查文件系统;
fsck -y /dev/hd1
fsck -y /dev/hd2
fsck -y /dev/hd3
fsck -y /dev/hd4
fsck -y /dev/hd9var
2.重建JFS日志;
/usr/sbin/logform /dev/hd8
3.键入 lslv -m hd5 来确定引导盘;
4.重建引导镜像bosboot -a -d /dev/hdiskn;
5.重新启动系统.
LED 552,554和556故障的解决
环境 产品: AIX
平台: RS
机型: RS6000
软件版本: V4
问题 系统无法正常启动，液晶面板LED显示552,554或556
解答 LED 552,554,556通常由超级块(Super Block)被破坏或定制的ODM数据库被破坏引起.应检查并修正这些遭到破坏的文件系统.
具体步骤:
1.用备份的超级块(Super Block)替换被破坏超级块(Super Block),重建文件系统;
dd count=1 bs=4k skip=31 seek=1 if=/dev/hdn of=/dev/hdn
/usr/sbin/logform /dev/hd8
2.加载(Mount)根文件系统和用户文件系统;
mount /dev/hd4 /mnt
mount /usr
3.将系统配置拷贝到备份目录;
mkdir /mnt/etc/objrepors/backup
cp /mnt/etc/objrepors/Cu* /mnt/etc/objrepos
4.从RAM文件系统复制出系统配置;
cp /etc/objrepos/Cu* /mnt/etc/objrepos
5.卸载(Unmount)所有的文件系统;
6.确定引导盘;
lslv -m hd5 command.
7.保存新的ODM到根逻辑卷;
savebase -d/dev/hdiskn
8.重新启动系统.
如果系统仍无法正常启动,亦可重装BOS.
如何替换损坏的镜像卷组硬盘?
环境 产品: AIX
平台: RS
机型: RS6000
软件版本: V4
问题 如何替换损坏的镜像卷组硬盘?
解答 要替换损坏的镜像卷组硬盘,应运行以下命令:
# unmirrorvg workvg hdisk7
# reducevg workvg hdisk7
# rmdev -l hdisk7 -d
# extendvg workvg hdisk7
# mirrorvg workvg
RS/6000液晶显示屏上显示代码(LED)的含义
环境 平台：RS/6000
版本：AIX 4.3
问题 本文介绍RS/6000启动过程中机器上的液晶显示屏代码的含义。本文代码不针对具体机型。
解答 ---------- Dump Progress Indicator ----------
0c0 The dump completed successfully
0c1 The dump failed due to an I/O error.
0c2 A user-requested dump has started. You requested a dump using the SYSDUMPSTART command, a dump key sequence, or the Reset button.
0c3 The dump is inhibit
0c4 The dump did not complete. A partial dump was written to the dump device. There is not enough space on the dump deviceto contain the entire dump. To prevent this problem from occuring again, you must increase the size of your dumpmedia.
0c5 The dump failed to start. An unecpected error occured while the system was attempting to write to the dump media.
0c6 A dump to the secondary dump device was requested. Make the secondary dump device ready, then press CTRL-ALT-NUMPAD2.
0c7 Reserved.
0c8 The dump function is disabled. No primary dump device is configured.
0c9 A dump is in progress.
0cc Unknown dump failure
---------- Diagnostics Load Progress Indicators -----------
c00 AIX Install/Maintenance loaded successfully.
c01 Insert the first diagnostic diskette.
c02 Diskettes inserted out of sequence.
c03 The wrong diskette is in the drive.
c04 The loading stopped with an irrecoverable error.
c05 A diskette error occurred.
c08 RAM filesystem started incorrectly.
c07 Insert the next diagnostic diskette.
c09 The diskette drive is reading or writing a diskette.
c20 An unexpected halt occured, and the system is configured to enter the kernel debug program instead of entering asystem dump.
c21 The 'ifconfig' command was unable to configure the network for the client network host.
c22 The 'tftp' command was unable to read client's ClientHostName.info file during a client network boot.
c24 Unable to read client's ClientHostName.info file during a client network boot.
c25 Client did not mount remote miniroot during network install.
c26 Client did not mount the /usr filesystem during the network boot.
c29 System was unable to configure the network device.
c31 Select the console display for the diagnostics. To select "No console display", set the key mode switch to normal thento Service. The diagnostic program will then load and run the diagnostics automatically.
c32 A direct-attached display (HFT) was selected.
c33 a TTY terminal attached to serial ports S1 or S2 was selected.
c34 A file was selected. The console messages store in a file
c40 Configuration files are been restored.
c41 Could not determine the boot type or device.
c42 Extracting data files from diskette.
c43 Diagboot cannot be accessed.
c44 Initialyzing installation database with target disk information.
c45 Cannot configure the console.
c46 Normal installation processing.
c47 Could not create a physical volume identifier (PVID) on disk.
c48 Prompting you for input.
c49 Could not create or form the JFS log.
c50 Creating rootvg volume group on target disk
c51 No paging space were found.
c52 Changing from RAM environment to disk environment.
c53 Not enough space in the /tmp directory to do a preservation installation.
c54 Installing either BOS or additionnal packages.
c55 Could not remove the specified logical volume in a preservation installation.
c56 Running user-defined customization.
c57 Failure to restore BOS.
c58 Display message to turn the key.
c59 Could not copy either device special files, device ODM, or volume group information from RAM to disk.
c61 Failed to create the boot image.
c70 Problem Mounting diagnostics CDROM disc.
c99 Diagnostics have completed. This code is only used when there is no console.
--------Debugger Progress Indicators ----------
c20 Kernel debug program activated. An unexpected system halt has occured, and you have configured the system
to enter the kernel debug program instead of performing a dump.
---------Built-In Self Test (Bist) Indicators---------
100 BIST completed successfully. Control was passed to IPL ROS.
101 BIST started following RESET
102 BIST started following Power-on Reset
103 BIST could not determine the system model number.
104 Equipment conflict. BIST could not find the CBA.
105 BIST could not read the OCS EPROM.
106 BIST detected a module error.
111 OCS stopped. BIST detected a module error.
112 A checkstop occured during BIST.
113 BIST checkstop count is greater than 1.
120 BIST starting a CRC check on the 8752 EPROM.
121 BIST detected a bad CRC in the first 32K of the OCS EPROM.
122 BIST started a CRC check on the first 32K of the OCS EPROM.
123 BIST detected a bad CRC on the OCS area of NVRAM.
124 BIST started a CRC check on the OCS area of NVRAM.
125 BIST detected a bad CRC on the time-of-day area of NVRAM.
126 BIST started a CRC check on the time-of-day area of the NVRAM.
127 BIST detected a bad CRC on the 8752 EPROM.
130 BIST presence test started.
140 BIST failed: procedure error
142 BIST failed: procedure error
143 Invalid memory configuration.
144 BIST failed; procedure error.
151 BIST started AIPGM test code.
152 BIST started DCLST test code.
153 BIST started ACLST test code.
154 BIST started AST test code.
160 Bad EPOW Signal/Power status signal
161 BIST being conducted on BUMP I/O
162 BIST being conducted on JTAG
163 BIST being conducted on Direct I/O
164 BIST being conducted on CPU
165 BIST being conducted on DCB and Memory
166 BIST being conducted on interrupts
170 BIST being conducted on 'Multi-Processor
180 BIST logout failed.
182 BIST COP bus not responding
185 A checkstop condition occured during the BIST
186 System logic-generated checkstop (Model 250 only)
187 Graphics-generated checkstop (Model 250)
195 BIST logout completed.
888 BIST did not start
------- Power-On Self Test -------
200 IPL attempted with keylock in the SECURE position.
201 IPL ROM test failed or checkstop occured (irrecoverable)
202 IPL ROM test failed or checkstop occured (irrecoverable)
203 Unexpected data storage interrupt.
204 Unexpected instruction storage interrupt.
205 Unexpected external interrupt.
206 Unexpected alignment interrupt.
207 Unexpected program interrupt.
208 Unexpected floating point unavailable interrupt.
209 Unexpected SVC interrupt.
20c L2 cache POST error. (The display shows a solid 20c for 5 seconds
210 Unexpected SVC interrupt.
211 IPL ROM CRC comparison error (irrecoverable).
212 RAM POST memory configuration error or no memory found (irrecoverable).
213 RAM POST failure (irrecoverable).
214 Power status register failed (irrecoverable).
215 A low voltage condition is present (irrecoverable).
216 IPL ROM code being uncompressed into memory.
217 End of bootlist encountered.
218 RAM POST is looking for 1M bytes of good memory.
219 RAM POST bit map is being generated.
21c L2 cache is not detected. (The display shows a solid 21c for 5 sec)
220 IPL control block is being initialized.
221 NVRAM CRC comparison error during AIX.
IPL(Key Mode Switch in Normal mode).
Reset NVRAM by reaccomplishing IPL in Service mode. For systems with an internal, direct-bus-attached(DBA)disk,IPL
ROM attempted to perform an IPL from that disk before halting with this three-digit display value.
222 Attempting a Normal mode IPL from Standard I/O planar attached devices specified in NVRAM IPL Devices List.
223 Attempting a Normal mode IPL from SCSI attached devices specified in NVRAM IPL Devices List.
Note: May be caused by incorrect jumper setting for external SCSI devices or by incorrect SCSI terminator.
REFER FFC B88
224 Attempting a Normal mode restart from 9333 subsystem device specified in NVRAM device list.
225 Attempting a Normal mode IPL from IBM 7012 DBA disk attached devices specified in NVRAM IPL Devices List.
226 Attempting a Normal mode restart from Ethernet specified in NVRAM device list.
227 Attempting a Normal mode restart from Token Ring specified in NVRAM device list.
228 Attempting a Normal mode IPL from NVRAM expansion code.
229 Attempting a Normal mode IPL from NVRAM IPL Devices List; cannot IPL from any of the listed devices, or there are
no valid entry in the Devices List.
22c Attempting a normal mode IPL from FDDI specified in NVRAM IPL device list.
230 Attempting a Normal mode restart from adapter feature ROM specified in IPL ROM devices list.
231 Attempting a Normal mode restart from Ethernet specified in IPL ROM devices list.
232 Attempting a Normal mode IPL from Standard I/O planar attached devices specified in Rom Default Device List.
233 Attempting a Normal mode IPL from SCSI attached devices specified in IPL ROM Default Device List.
234 Attempting a Normal mode restart from 9333 subsystem device specified in IPL ROM device list.
235 Attempting a Normal mode IPL from IBM 7012 DBA disk attached devices specified in IPL ROM Default Device List.
236 Attempting a Normal mode restart from Ethernet specified in IPL ROM default devices list.
237 Attempting a Normal mode restart from Token Ring specified in IPL ROM default device list.
238 Attempting a Normal mode restart from Token Ring specified by the operator.
239 System failed to restart from the device chosen by the operator.
23c Attempting a normal mode IPL from FDDI specified in IPL ROM device list.
240 Attempting a Service mode restart from adapter feature ROM.
241 Attempting a Normal mode IPL from devices specified in the NVRAM IPL Devices List.
242 Attempting a Service mode IPL from Standard I/O planar attached devices specified in NVRAM IPL Devices List.
243 Attempting a Service mode IPL from SCSI attached devices specified in NVRAM IPL Devices List.
244 Attempting a Service mode restart from 9333 subsystem device specified in NVRAM device list.
245 Attempting a Service mode IPL from IBM 7012 DBA disk attached devices specified in NVRAM IPL Devices List.
246 Attempting a Service mode restart from Ethernet specified in NVRAM device list.
247 Attempting a Service mode restart from Token Ring specified in NVRAM device list.
248 Attempting a Service mode IPL from NVRAM expansion code.
249 Attempting a Service mode IPL from NVRAM IPL Devices List; cannot IPL from any of the listed devices, or there areno valid entries in the Devices List.
24c Attempting a service mode IPL from FDDI specified in NVRAM IPL device list.
250 Attempting a Service mode restart from adapter feature ROM specified in IPL ROM device list.
251 Attempting a Service mode restart from Ethernet specified in IPL ROM device list.
252 Attempting a Service mode IPL from standard I/O planar attached devicesspecified in ROM Default Device List.
253 Attempting a Service mode IPL from SCSI attached devices specified in IPL ROM Default Device List.
254 Attempting a Service mode restart from 9333 subsystem device specified in IPL ROM device list.
255 Attempting a Service mode IPL from IBM 7012 DBA disk'attached devices specified in IPL ROM Default Devices List.
256 Attempting a Service mode restart from Ethernet specified in IPL ROM default device list.
257 Attempting a Service mode restart from Token Ring specified in IPL ROM default device list.
258 Attempting a Service mode restart from Token Ring specified by the operator.
259 Attempting a Service mode restart from FDDI specified by the operator.
25c Attempting a normal mode IPL from FDDI specified in IPL ROM device list.
260 Information is being displayed on the display console.
261 Information will be displayed on the tty terminal when the "1" key is pressed on the tty terminal keyboard.
262 A keyboard was not detected as being connected to the system's
NOTE: Check for blown planar fuses or for a corrupted boot on disk drive
263 Attempting a Normal mode restart from adapter feature ROM specified in NVRAM device list.
269 Stalled state - the system is unable to IPL
271 Mouse port POST.
272 Tablet port POST.
277 Auto Token-Ring LANstreamer MC 32 Adapter
278 Video ROM Scan POST.
279 FDDI adapter POST.
280 3COM Ethernet POST.
281 Keyboard POST executing.
282 Parallel port POST executing
283 Serial port POST executing
284 POWER Gt1 graphadapte POST executing
285 POWER Gt3 graphadapte POST executing
286 Token Ring adapter POST executing.
287 Ethernet adapter POST executing.
288 Adapter card slots being queried.
289 GTO POST.
290 IOCC POST error (irrecoverable).
291 Standard I/O POST running.
292 SCSI POST running.
293 IBM 7012 DBA disk POST running.
294 IOCC bad TCW SIMM in slot location J being tested.
295 Graphics Display adapter POST, color or grayscale.
296 ROM scan POST.
297 System model number does not compare between OCS and ROS
(irrecoverable). Attempting a software IPL.
298 Attempting a software IPL (warm boot).
299 IPL ROM passed control to the loaded program code.
301 Flash Utility ROM failed or checkstop occured (irrecoverable)
302 Flash Utility ROM failed or checkstop occured (irrecoverable)
302 Flash Utility ROM: User prompt, move the key to the service in order to perform an optional Flash Update. LED
will only appear if the key switch is in the SECURE position. This signals the user that a Flash Update may be
initiated by moving the key switch to the SERVICE position. If the key is moved to the SERVICE position,
LED 303 will be displayed. This signals the user to press the reset button and select optional Flash Update.
303 Flash Utility ROM: User prompt, press the reset button in order to perform an optional Flash Update. LED
only appear if the key switch is in the SECURE position. This signals the user that a Flash Update may be initiated
by moving the key switch to the SERVICE position. If the key is moved to the SERVICE position, LED 303 will be
displayed. This signals the user to press the reset button and select optional Flash Update.
304 Flash Utility ROM IOCC POST error (irrecoverable)
305 Flash Utility ROM standard I/O POST running.
306 Flash Utility ROM is attempting IPL from Flash Update Boot Image.
307 Flash Utility ROM system model number does not compare between OCS and ROM (irrecoverable).
308 Flash Utility ROM: IOCC TCW memory is being tested.
309 Flash Utility ROM passed control to a Flash Update Boot Image.
311 Flash Utility ROM CRC comparison error (irrecoverable).
312 Flash Utility ROM RAM POST memory configuration error or no memory found ( iirecoverable).
313 Flash Utility ROM RAM POST failure( irrecoverable).
314 Flash Utility ROM Power status register failed (irrecoverable).
315 Flash Utility ROM detected a low voltage condition.
318 Flash Utility ROM RAM POST is looking for good memory.
319 Flash Utility ROM RAM POST bit map is being generated.
322 CRC error on media Flash Image. No Flash Update performed.
323 Current Flash Image is being erased.
324 CRC error on new Flash Image after Update was performed. (Flash Image is corrupted).
325 Flash Image successful and complete.
500 Querying Native I/O slot.
501 Querying card in Slot 1
502 Querying card in Slot 2
503 Querying card in Slot 3
504 Querying card in Slot 4
505 Querying card in Slot 5
506 Querying card in Slot 6
507 Querying card in Slot 7
508 Querying card in Slot 8
510 Starting device configuration.
511 Device configuration completed.
512 Restoring device configuration files from media.
513 Restoring basic operating system installation files from media.
516 Contacting server during network boot
517 Mounting client remote file system during network IPL.
518 Remote mount of the root and /usr filesystems failed during network boot.
520 Bus configuration running.
521 /etc/init invoked cfgmgr with invalid options; /etc/init has been corrupted or incorrectly modified
(irrecoverable error).
522 The configuration manager has been invoked with conflicting options (irrecoverable error).
523 The configuration manager is unable to access the ODM database (irrecoverable error).
524 The configuration manager is unable to access the config rules object in the ODM database (irrecoverable error).
525 The configuration manager is unable to get data from a customized device object in the ODM database
(irrecoverable error).
526 The configuration manager is unable to get data from a customized device driver objet in the ODM database
(irrecoverable error).
527 The configuration manager was invoked with the phase 1 flag; running phase 1 flag; running phase 1 at this point
is not permitted (irrecoverable error).
528 The configuration manager cannot find sequence rule, or no program was specified in the ODM database
(irrecoverable error).
529 The configuration manager is unable to update ODM data
(irrecoverable error).
530 The program "savebase" returned an error.
531 The configuration manager is unable to access PdAt object class
(irrecoverable eroor)
532 There is not enough memory to continue (malloc failure);
irrecoverable error.
533 The configuration manager could not find a configure method for a device.
534 The configuration manager is unable to aquire database lock. irrecoverable error.
536 The configuration manager encountered more than one sequence rule specified in the same phase. (irrecoverable error).
537 The configuration manager encountered an error when invoking the program in the sequence rule.
538 The configuration manager is going to invoke a configuration
539 The configuration method has terminated, and control has returned to the configuration manager.
551 IPL Varyon is running
552 IPL Varyon failed.
553 IPL phase 1 is complete.
554 Unable to define NFS swap device during network boot
555 Unable to define NFS swap device during network boot
556 Logical Volume Manager encountered error during IPL varyon.
557 The root filesystem will not mount.
558 There is not enough memory to continue the IPL.
559 Less than 2MB of good memory are available to load the AIX kernel.
570 Virtual SCSI devices being configured.
571 HIPPI common function device driver being configured.
572 HIPPI IPI-3 master transport driver being configured.
573 HIPPI IPI-3 slave transport driver being configured.
574 HIPPI IPI-3 transport services user interface device driver being configured.
576 Generic async device driver being configured.
577 Generic SCSI device driver being configured.
578 Generic commo device driver being configured.
579 Device driver being configured for a generic device.
580 HIPPI TCPIP network interface driver being configured.
581 Configuring TCP/IP.
582 Configuring token ring data link control.
583 Configuring an Ethernet data link control.
584 Configuring an IEEE ethernet data link control.
585 Configuring an SDLC MPQP data link control.
586 Configuring a QLLC X.25 data link control.
587 Configuring NETBIOS.
588 Configuring a Bisync Read-Write (BSCRW).
589 SCSI target mode device being configured.
590 Diskless remote paging device being configured.
591 Configuring an LVM device driver
592 Configuring an HFT device driver
593 Configuring SNA device drivers.
594 Asynchronous I/O being defined or configured.
595 X.31 pseudo device being configured.
596 SNA DLC/LAPE pseudo device being configured.
597 OCS software being configured.
598 OCS hosts being configured during system reboot.
599 Configuring FDDI data link control.
5c0 Streams-based hardware drive being configured.
5c1 Streams-based X.25 protocol being configured.
5c2 Streams-based X.25 COMIO emulator driver being configured.
5c3 Streams-based X.25 TCP/IP interface driver being configured.
5c4 FCS adapter device driver being configured.
5c5 SCB network device driver for FCS is being configured.
5c6 AIX SNA channel being configured.
600 Starting network boot portion of /sbin/rs.boot
602 Configuring network parent devices.
603 /usr/lib/methods/defsys
/usr/lib/methods/cggsys, or
/usr/lib/methods/cggbus failed.
604 Configuring physical network boot device.
605 Configuring physical network boot device failed.
606 Running /usr/sbin/ifconfig on logical network boot device.
607 /usr/sbin/ifconfig failed.
608 Attempting to retrieve the client.info file with tftp. Note that a flashing 608 indicates multiple attempts
to retrieve the client_info file are occuring.
609 The client.info file does not exist or it is zero length.
610 Attempting remote mount of NFS file system
611 Remote mount of the NFS filesystem failed.
612 Accessing remote files; unconfiguring network boot device.
614 Configuring local paging devices.
615 Configuring of a local paging device failed.
616 Converting from diskette to dataless configuration.
617 Diskless to dataless configuration failed.
618 Configuring remote (NFS) paging devices.
619 Configuration of a remote (NFS) paging device failed.
620 Updating special device files and ODM in permanent filesystem with data from boot RAM filesystem.
622 Boot process configuring for operating system installation.
650 IBM SCSD disk drive drive being configured
700 Progress indicator. A 1.1GB 8-bit SCSI disk drive being identified or configured.
701 Progress indicator. A 1.1GB 16-bit SCSI SE disk drive being identified or configured.
702 Progress indicator. A 1.1GB 16-bit SCSI differential disk drive being identified or configured.
703 Progress indicator. A 2.2GB 8-bit SCSI disk drive being identified or configured.
704 Progress indicator. A 2.2GB 16-bit SCSI SE disk drive being identified or configured.
705 The configuration method for the 2.2GB 16-bit differential SCSI disk drive is being run. If a irrecoverableerror occurs, the system halts. identified or configured.
706 Progress indicator. A 4.5GB 16-bit SE SCSI disk drive is being identified or configured.
707 Progress indicator. A 4.5GB 16-bit differential SCSI drive is being identified or configured.
708 Progress indicator: A L2 cache is being identified or configured.
710 POWER GXT150M graphics adapterbeing ientifyied or configured.
711 Unknown adapter being identified or configured.
712 Graphics slot bus configuration is executing.
713 The IBM ARTIC960 device is being configured.
714 A video capture adapter is being configured.
715 The Ultimedia Services audio adapter is being configured. This LED displays briefly on the panel.
720 Unknown read/write optical drive type being configured.
721 Unknown disk or SCSI device being identified or configured.
722 Unknown disk being identified or configured.
723 Unknown CDROM being identified or configured.
724 Unknown tape drive being identified or configured.
725 Unknown display being identified or configured.
726 Unknown input device being idenor configured
727 Unknown adync device being idenor configured
| | |
