AIX System Administration
aixadm3r系统管理工具
本章主要介绍学完本章早期的系统管理方式操作系统中要缺点是没有统一的界面来实施系统管理的任务这一类的系统管理方式主要是采用以下技术统前端理任务每种方式之间并不一致例如熟练使用系统编辑器AIX V.4SMITÄܹ»ÔÚÒ»¸öͳһµÄ»·¾³ÏÂÍê³É´ó¶àÊýϵͳ¹ÜÀí¹¦ÄÜËüÖ»ÊÇÒ»¸öÓû§½çÃæÓû§Ò²¿ÉÒÔÖ±½Ó¼üÈëÃüÁîÀ´Ö´ÐÐͬÑùµÄÈÎÎñ程序高级命令通过运行多个低级命令或中级命令来执行系统管理功能接运行这些命令组件这些命令极少被用户执行不能覆盖所有可能的系统管理任务高Ｄｉｓｔｒｉｂｕｔｅｄ Ｓｙｓｔｅｍ Ｍａｎａｇｅｍｅｎｔ Ｉｎｔｅｒｆａｃｅ ＴｏｏｌHP-UX9.0VSM是一个系统管理的图形界面系统管理工具对象数据管理中存储的信息包括数据库因此用户进入菜单的路径不同都会使得用户看到的菜单略有不同3.1.2 SMIT提供一个可变的用户环境供的功能是相同的有一个层次菜单一些子菜单可以显示在多层次适当的位置有许多可能的参数值需要你列出命令而且可以在命令完成后查看SMIT主菜单ＳＭＩＴ的主菜单可供用户选择要执行的管理功能 在ＡＳＣＩＩ模式下选择菜单项使亮条在菜单项上移动 在这一阶段也可以使用其它的功能键主菜单对话窗口供用户输入执行操作的参数般而言选择窗口是对话窗口的一种特例命令将要操作该对象将亮条移动到要修改的值上标明以表明显示区域的左右两端还有数据ring´°²¢Ö´ÐÐÃüÁî一示可以用弹出表或环环是一种特殊的表形式键能循环列出各选项用鼠标点击列表可以列出弹出表以供选择SMIT的热键在菜单和对话窗口下可使用以下热键只能在ASCII 界面使用的用标记MF1帮助棗显示联机帮助信息F2刷新棗刷新窗口取消棗退回到上一级窗口Ｆ３ 列表棗给出可能取值的弹出表Ｆ４ 复位棗恢复参数域的初值Ｆ５ F6命令棗显示要执行的AIX命令F7编辑棗弹出框的修改一个区域的值或从多重选择弹出表中选择F8图象棗将当前屏幕存储到某个文件并且显示当前的快速路径启动shell (Shell)——启动一个子shellＦ９ F9 复位所有域Ｆ１０ 退出棗立即退出SMITF10 转入命令行退出棗立即退出SMITＦ１２ Ctrl-1 列表棗给出可能取值的弹出表下翻一页ＰｇＤｎ（Ｃｔｒｌ－ｖ） PgUp上翻一页Home (ESC-<) 跳到页的顶部End (ESC-<) 跳到页的底部Enter 执行当前的命令或者从选单表中选择/text 在输出窗口中查找文本textn 查找text的下一次出现记录所有访问过的菜单和对话窗口会话期的错误记录时如果文件已经存在这两个文件随着时间的推移而逐渐增大所以用户必须注意维护并在适当时清空这两个文件对话框命令和命令的输出结果文件件后面执行的日期和时间加在前面程序多次执行• smit 命令的语法用ｓｍｉｔ 命令进入ＳＭＩＴ菜单则启动ＡＳＣＩＩ ＳＭＩＴ如果不带选项用户也可以指定一个快速路径直接进入ＳＭＩＴ的某个子菜单 用户也可以给出ｓｍｉｔ命令的命令行选项并且控制日志文件中保存的信息数量对系统安全无害 Ｓｍｉｔ命令的选项如下ＳＭＩＴ的ｓｈｅｌｌ程序文件记录由ｓｍｉｔ运行的中间命令和最终命令 －Ｄ 设置调试模式 －Ｘ 不运行任何高级命令• DSMIT类似布到其他客户端例如快速路径和日志记录文件是需要额外订购的授许可证的软件产品可视化系统管理是图形界面的系统管理工具是标准包的一部分的设计主要着眼于提供直观的图形界面大部分任务可以通过拖放单个图标来完成在模板区提供了创建不同对象的缺省模板的所有应用程序在使用时都有相同的风格支持应用程序SMIT devls chÓÃÓÚÁÐʾɾ³ýϵͳÎï¼þʹÓøö¿ÉÒÔ¼ÇÒäµÄ¹æÂÉ之间的主要区别是什么。
AIX初级系统管理员培训教程
●建立AIX目录结构
●从安装介质复制BOS、本地化文件和文件集
●从已加电设备或网络设备上安装必要的软件 BOS安装完成后： ●设置终端类型（如果是字符终端） ●显示安装辅助菜单
开始安装（基于PCI的RS/6000）
Installing Base Operating System Turn the system key to the NORMAL position any time before the installation ends. Please wait. Approximate Elapsed time %task completed (in minutes) 16 1
UNIX的哲学
• 简单、通用的命令 • 用管道连接不同的命令 • 通用、可选择的接口风格 • 无文件类型
AIX操作系统简介
●AIX = ADVANCED INTERACTIVE EXECUTIVE ●高级的交互式执行系统。
●applications ●shell
●AIX系统的结构 ●AIX SYSTEM STRUCTURE
Normal Secure Service
安装过程（基于PCI的RS/6000）
步骤1：
● 将操作系统CD插入CD-ROM驱动器 ● 外部设备加电
● 系统加电
系统将从启动设备列表中的第一项设备开始读取启动介质并 启动，一般情况下，这个设备是磁带机或CD-ROM驱动器
控制台和语言定义
步骤2：பைடு நூலகம்
****** Please define the System Console. ****** Type a 2 at the terminal and press <Enter> if you want this display to be the System Console.
AIX系统管理
金证科技
SHENZHEN KINGDOM TECHNOLOGY CO.LTD.
AIX存储管理命令
Varyonvg , varyoffvg , lsvg , lsvg –o Exportvg , importvg Lspv Lslv,mklv Crfs smit命令（是执行其它命令的一个工具，将其 它命令的命令名作为smit命令的参数，如： smit mklv等）
金证科技
SHENZHEN KINGDOM TECHNOLOGY CO.LTD.
谢谢！
金证科技
SHENZHEN KINGDOM TECHNOLOGY CO.LTD.
• 文件是AIX文件系统的基本单位，共有 三种不同类型的AIX文件。 普通文件 目录文件 特殊文件 • 文件和目录的存取权
金证科技
SHENZHEN KINGDOM TECHNOLOGY CO.LTD.
普通文件
• 以字节为单位的数据信息的集合，包括 文本文件和程序文件。 • 基本属性包括文件名、文件索引号、文 件大小、最近访问时间、一组存取权、 属组名和属主名。
• 存取权分为三个级别：读权“r”、写权 “w”、执行权“x”。 • 存取用户分三类：文件属主、属组、其 它用户。 • 为文件赋权限是用数字表示，如755为 rwxr-xr-x
金证科技
SHENZHEN KINGDOM TECHNOLOGY CO.LTD.
访问系统的简单命令
• 用户管理操作 • 目录管理操作 pwd、ls、cd、mkdir、rmdir、rm等 • 文件管理操作 cp、rm、find等 • 改变目录/文件属性 chown、chgrp、chmod
AIX-系统管理工具优秀课件
SMIT的热键(2)
F8或ESC-8 抓图Image — — 将当前屏幕抓图并 存储到$HOME/smit.log文件 F9或ESC-9 启动子shell — — 暂时推出smit菜单 并切换到shell命令状态，完成一些命令操作后， 执行exit返回到刚才的smit界面 F10或ESC-0 退出Exit — — 立即退出SMIT
2.1.1 早期的系统管理
命令(带有大量记不完的参数)
installp restore
errpt mount
backup
/etc/qconfig /etc/filesystems
系统管理
/etc/passwd
adduser devices
枯燥文件 (不同配置文件有不同格式)
不一致的用户操作菜单 (界面不友好)
dev 设备管理 diag 诊断 jfs 定期档案系统管理 lvm 逻辑卷管理 nfs NFS管理
installp 软件安装及维护 spooler 打印队列管理 system 系统管理 tcpip TCP/IP管理 user 用户管理
2.2.1 熟悉WebSM管理界面
熟悉WebSM管理界面(2)
系统管理与ODM
组织命令 的方式
ODM
正文窗口
系统管理工具
系统管理与ODM(2)
ODM：Object Data Manager
ODM是AIX特有的一个管理数据库，储存软件安装， 系统配置等很多的关键信息，也包括SMIT界面和命 令管理
建议不要手工去修改ODM内容； SMIT的系统管理 操作和高级命令会自动正确修改ODM，手工修改危 险太大
2.1.2 SMIT界面简介
SMIT分为字符界面和图形界面，但他们的功能一样 菜单与子菜单 SMIT有一个层次菜单它把典型的系统管理任务分在 相关的区域，一些子菜单可以显示在多层次适当的 位置
IBM认证有几个方向
IBM认证有几个方向：IBM认证分类：DB2 Database AdministratorDB2 Application DeveloperMQSeries EngineerVisualAge For Java Developer AssociateIBM专业认证经验总结 2005-04-22 作者：前言：以下内容为针对电子商务（811），Linux（101，102），AIX（191），AS/400（052，053），DB2（512，513）认证考试的学习心得与经验总结，由2002年度IBM暑期夏令营全体营员经过讨论，整理，总结而成，希望可以给将要参加相应的认证培训的学生提供帮助。
电子商务：811（由南京大学王智超，颜小君同学，厦门大学王丹同学整理）考试号：811名称：IBM Certified for e-business - Solution Designer考试时间：75分钟一、考试重点及难点1、IBM电子商务应用的三层结构图：<略>这部分内容很多，经常考到，是考试重点，必须掌握。
2、IBM产品分类并熟悉相应作用。
* 用于Building的开发类工具：如VisualAge for Java，WebSphere Studio等* 用于支持运行的Server类：如WebSphere家族，各种Application Server。
* 用于网络管理：如Tivoli等3、Java技术的熟悉* Client端的applet技术（何时应用）* Server端的servlet，JSP技术，两者的区别与联系* 用语连接DB的JDBC，重点是connect pool技术4、EJB技术EJB的分类：Session Bean与Entity Bean的区别，EJB container概念等等5、e-Business的生命周期（Cycle）* 内容：Jransform - Build - Run - Leverage* 各阶段的特点及区别与联系* 各阶段IBM都有哪些产品6、提高Performance技术例如：Connect Pool、filter、cache、dispatch等等7、对CRM、SCM的了解主要包括基本概念，区别，如何应用，以及与e-Business的关系，如何应用IBM产品等等8、各种Protocol的了解例如：IBM某种产品不支持哪种Protocol，某种产品应用哪中Protocol等等9、安全性技术* 加密、认证技术：了解过程与区别* 访问控制机制10、对具体应用的了解根据企业的某种需求，提供解决方案，应用IBM产品。
AIX的用户和组管理
AIX的用户和组管理管理IBM AIX 中的用户和组是管理员的重要责任之一。
可以以许多种方式管理用户和组：可以通过AIX System Management Interface Tool (SMIT) 管理它们，也可以手工编辑配置文件或使用命令行命令。
本文讨论AIX 上与用户和组相关的配置文件，以及用来帮助管理用户和组的命令行工具。
先了解文件，然后了解命令在学习AIX 中用来创建、修改和维护用户和组的命令之前，一定要了解在幕后发生的情况。
例如，应该了解相关文件及其作用。
下面是影响用户本身的一些文件：AIX 中的命令请记住，本文讨论的命令和方法应该可以在配置文件中有本地用户和组的AIX 系统上使用。
如果系统处理来自远程源（例如Network Information System，即NIS）的用户和组，那么不应该使用chuser 和chgroup 等命令。
/etc/passwd/etc/security/.profile/etc/security/limits/etc/security/passwd/etc/security/user/usr/lib/security/mkuser.default/etc/passwd/etc/passwd 文件包含用户的基本信息，它可能是UNIX? 和Linux? 用户最熟知的用户管理文件。
清单1 给出/etc/passwd 文件的示例。
清单1. /etc/passwd 文件示例root:!:0:0::/:/usr/bin/kshdaemon:!:1:1::/etc:bin:!:2:2::/bin:sys:!:3:3::/usr/sys:adm:!:4:4::/var/adm:uucp:!:5:5::/usr/lib/uucp:guest:!:100:100::/home/guest:nobody:!:4294967294:4294967294::/:lpd:!:9:4294967294::/:lp:*:11:11::/var/spool/lp:/bin/false invscout:*:6:12::/var/adm/invscout:/usr/bin/kshsnapp:*:200:13:snapp loginuser:/usr/sbin/snapp:/usr/sbin/snappdipsec:*:201:1::/etc/ipsec:/usr/bin/kshnuucp:*:7:5:uucp loginuser:/var/spool/uucppublic:/usr/sbin/uucp/uucicopconsole:*:8:0::/var/adm/pconsole:/usr/bin/kshesaadmin:*:10:0::/var/esa:/usr/bin/kshsshd:*:206:201::/var/empty:/usr/bin/kshatc:!:8000:400:Adam Cormany,Sr UNIXAdmin:/home/atc:/bin/kshamdc:!:8001:401:AMDC:/home/amdc:/bin/kshpac:!:8002:400:PAC,Jr UNIX Admin:/home/pac:/bin/kshatc2:!:8003:402:ATCv2:/home/atc2:/bin/ksh可以看到这个文件使用冒号(:) 作为分隔符，每个条目按以下格式包含7 个字段（为了便于阅读，在分隔符前后添加了空格）：Username : Password Flag : UID : GID : GECOS : Home : Shell/Command下面逐一解释这些字段：Username。
AIX系统管理
IBMAIX 操 作 系 统 管 理 手 册目录一、AIX操作系统介绍 (5)1．模块化内核 (5)2．动态调整内核 (5)3．线程内核 (5)4．高效输入/输出 (5)5．日志文件系统 (6)6．存储管理 (6)7．系统管理 (6)二、系统启动和关机 (7)2.1多用户引导模式 (7)2.2单用户引导模式 (8)2.3系统关机 (9)三、用户登录和退出 (10)3.1启动CDE (10)3.2登录 (10)3.3退出 (11)3.4用户属性 (11)四、设备管理 (16)4.1设备管理介绍 (16)4.2 对象数据库 (17)4.3 添加设备（命令行） (18)4.4 添加设备（SIMT） (18)4.5 ODM未定义的设备 (20)4.6 删除设备 (21)五、磁盘和文件系统 (22)5.1 系统目录 (22)5.2 逻辑卷管理 (23)5.3 安装磁盘 (24)5.4 创建逻辑卷 (25)5.5 创建文件系统 (26)5.6 管理调页空间 (28)5.7 总结 (28)六、进程管理 (29)6.1 显示/修改进程属性 (29)6.1.1 显示进程属性 (29)6.1.2 修改进程优先级 (29)6.2 停止进程 (29)6.3 性能检测 (30)6.4 系统资源控制器SRC (30)6.5 进程的定时启动 (35)七、备份和恢复 (37)7.1.1 rootvg的备份 (38)7.1.2 Non-rootvg 的备份 (39)7.1.3文件系统的备份 (40)7.2 恢复 (41)7.2.1文件系统的恢复 (42)7.3 映象备份 (42)7.4 磁带驱动器 (43)八、TCP/IP (45)8.1 配置IP地址和主机名 (45)8.2 路由管理 (46)8.3 网卡配置 (47)8.4 配置域名服务器 (47)8.5 编辑一些重要文件 (48)8.6 管理其它服务 (49)8.7 BSD配置风格 (50)九、域名服务 (52)9.1服务器配置文件 (52)9.2主域名服务器 (52)9.3次域名服务器 (53)9.4代理（Cache-Only）域名服务器 (54)9.5域名服务客户机 (54)9.6域名解析顺序 (55)10、网络信息系统 (56)10.1服务器配置文件 (56)10.2 设置本机为住NIS服务器 (56)10.3设置本机为次NIS服务器 (57)10.4设置本机为NIS客户机 (58)10.5描述图和命令 (58)10.6 NIS守护进程 (60)11、网络文件系统 (62)11.1 NFS守侯进程 (62)11.2 NFS服务器 (62)11.3 NFS客户机 (63)11.4 其他命令 (65)11.5 自动mount (65)12、邮件 (67)12.1 邮件系统配置文件 (67)12.2 邮件系统守侯进程 (67)12.3 邮件别名 (68)12.4 邮件队列 (68)12.5 邮件日志和统计 (69)13、X window (70)13.1文件和目录结构 (70)13.3退出X环境 (72)13.4终端仿真 (73)13.5 字体服务器 (73)13.6显示管理器 (73)13.7 X11互操作性 (74)13.7.1 远地主机的显示输出 (74)13.7.2 把工作站变为X终端 (75)13.8 CDE互操作性 (75)14、打印 (77)14．1队列系统 (77)14．2本地打印机 (78)14．3远程打印机 (80)15、日常维护常用命令 (84)15.1 smitty (84)15.2 lsdev (85)15.3 lsattr (86)15.4 lsvg (87)15.5 lspv (87)15.6 netstat (88)15.7 df (88)15.8 du (88)15.9 fsck (89)15.10 lssrc (89)15.11 sar (90)15.12 errpt (90)15.13 mail (92)16、HACMP日常维护命令 (93)16.1 HA的启动 (93)16.2 HA的停止 (93)16.3监控HA (93)16.4同步HA (93)16.5注意事项 (94)17、系统日常管理的主要工作 (95)17.1必须完成的任务 (95)17.2经常任务 (95)17.3不经常任务 (95)17.4定期任务 (96)17.5偶尔任务 (96)18、TSM磁带库的操作 (97)18.1 备份操作 (97)18.2恢复 (98)相关系统资源 (99)一、AIX操作系统介绍AIX全名为Advanced Interactive eXecutive, 俗称“An IBM Unix”或“Advanced IBM Unix”。
IBMp系列的AIX操作系统管理员可能因为各种原因对应用H
简介：IBMp系列的AIX操作系统管理员可能因为各种原因对应用HACMP和EtherChannel的组合感兴趣，如一些软件可用性方案“反对”HACMP额外的备卡，通过使用EtherChannel, HACMP 的设置可以“遮掩”备卡，从而给这些用户一个他们熟悉的外部表现。
此外，一些用户可能喜欢EtherChannel带宽聚集，负载平衡以及高可用性，等等。
在给出的实例测试中，我们使用AIX5.2中的EtherChannel 功能实现一个“单一网卡”的IPAT。
EtherChannel 负责提供独立于HACMP之外的本地网卡交换。
HACMP是完全独立的，根本不知道EtherChannel的存在。
在HACMP中一般不只使用一个网卡，但是EtherChannel使这种情况可以接受，因为在一个EtherChannel 的伪设备中实际上有很多个物理网卡的存在。
因此，可以忽略集群(Cluster)同步时没有足够的网卡的警告信息。
本测试在不使用交换机的情况下实现EtherChannel，用“交叉网线”直接连接两个系统。
尽管PCI的热插拔以及硬件地址接管没有包括在HACMP的支持声明中，从我们的测试结果看来，PCI的热插拔在2004年5月软件升级中新加入的DAM (Adapter Membership)特点的支持下也能工作。
这意味着在SMIT中可以从一个运行的EtherChannel中移走网卡。
用户可以利用热插拔的特点更换网卡。
AIX EtherChannel 概述EtherChannel(EC)是一种端口聚合方法，多到八个以太网卡可以被定义作一个EtherChannel 通道，对于远端的系统而言，只能看到一个IP地址和MAC地址，但是得到了八倍的网络带宽。
数据流将按照标准的方法分布到各个网卡，如果某一个网卡不能够正常工作，数据将会被自动地发送到其它可用的网卡上，而不会中断连接，当主EC上只有一个连接活动的时候，一个“失效”测试将触发一个对可选备份网卡的快速检测。
《AIX高级系统管理》LAB
《AIX高级系统管理》LABODMLog in as teamxx and su to root. Before interfacing with and modifying the ODM in this exercise, first make a backup copy of the files of the ODM that you will be manipulating. Use the tar command to create a backup of all the ODM files in /etc/objrepos. Use /home/teamxx/odmbak as the output file for the tar command.Using the lsdev command with the options below, display configuration data information associated with the fixed disk of your machine. Then answer the questions and complete the chart.Using the information obtained from above complete the chart.Was the above configuration data retrieved from the predefined database or the customized database?List the six file names, found in /etc/objrepos directory, that identify the six object classes that make up the customized database containing the information needed to maintain the configuration of fixed disks. In addition, challenge yourself to write down what the file names stand for.Using the odmshow command, identify which descriptors of the CuDv object class store the fixed disk configuration data that was displayed in the above step.How many total descriptors are a part of the object class?What are the names of the descriptors that identify the data that was displayed with the lsdev –H –Cc disk command line?Use the odmget command with the appropriate options to retrieve the object from the customized database that represents the first fixed disk configured on the system.In your home directory create a stanza file named toast1 that contains one object, retrieved from the object class PdDv, that represents the 8mm tape drive device definition. Two of the descriptors that are associated with the object to be retrieved are type with a value of 8mm and class with a value of tape.Edit the stanza in the file toast1 that is in your home directory and change the values of the attributes in the stanza to match the values below:type = gadgetclass = toastxxprefix = toastuniquetype = toastxx/scsi/gadgetUsing the odmadd command add the objects to the predefined database.HardwareinitLog in as a regular user and su to root. Determine what SCSI adapters and fixed disks are configured in the exercise machine and make note of their location codes.Identify which disks are contained within the root volume group and which rootvg disk is the bootable disk (contains logical volume hd5, the boot logical volume).Execute the command that will show you which boot image is on your system.Execute the program /home/workshop/ex2pro1. When the prompt is returned shut down and reboot the system. As the system reboots, you may wish to write down some of the LED codes and later look them up in Appendix A to identify what task the machine was performing. Solve the problem created by the ex2pro1 program.When the machine has successfully booted, log in as root and execute the program /home/workshop/ex2pro2, shut down and reboot. Fill out a new Problem Summary Form as you work through the new problem.Boot your system and access the System Management Services program on your system.Change the default boot devices set up for your system toinclude the CD-ROM. When completed, reboot the system.Log in as regular user and su to root. Determine what SCSI adapters and fixed disks are configured in the exercise machine and make note of their location codes.Identify which disk(s) are contained within the root volume group and which rootvg disk is the bootable disk (contains logical volume hd5, the boot logical volume).Execute the command that will show you which boot image is on your system.Boot your system and access the System Management Services program on your system.View the default boot devices set up for your system. When completed, change the bootlist to include the CD-ROMs and reboot the system.Log in as a regular user and su to root. Determine what SCSI adapters and fixed disks are configured in the exercise machine and make note of their location codes.Identify which disk(s) are contained within the root volume group and which rootvg disk is the bootable disk (contains logical volume hd5, the boot logical volume).Execute the command that will show you which bootimage is on your system.Softwareinitlogin as a regular user and su to root. Run the script /home/workshop/ex3pro1. This will take several minutes. Take a break. When you return, and the script is finished (the prompt returned), power off and then power your system back on.Boot up your system and note the LED code that is produced. Using this value you should be able to correct this problem.You should now find that your system hangs on a different LED code. Follow similar steps to the above to correct the problem.You will find that the Logical V olume Control Block for the JFSLOG(hd8) has not been totally fixed. Execute the getlvcb with the proper option (A and N) to display and correct this problem respectively.Log in as a regular user and su to root. Run the script /home/workshop/ex3pro1. This will take several minutes. Take a break. When you return, and the script is finished (the prompt returned), power off and then power your system back on.Boot up your system. Note that it won‟t boot to AIX but it passes all four phases of the firmware tests. Boot in maintenance mode from your media and try to determine what the problem is.Be sure to watch the error messages after selecting to access the root volume group.Correct the problem. Be sure to shutdown and reboot in normal mode.You should find that your system still does not boot. Once again, boot in maintenance mode. There is less evidence this time of what might be causing the problem. This is a trial and error process, so begin checking obvious potential problems like a corrupted /dev directory or corrupted /etc/inittab file.You will find that the Logical V olume Control Block for the JFSLOG(hd8) has not been totally fixed. Execute the getlvcb with the proper option (A and N) to display and correct this problem respectively.Disk_Managementlogin and su to root. The output of the commands in this section will be important should the system data become corrupted. Make a note of all the output, or append this output to a file. Use the lsdev command to establish the configuration of your system. Record the number of disks on the system.List the physical volumes and their contents using the lspv commandList the volume groups and their contents using the lsvg command.View the information in the Logical V olume Control Block and the V olume Group Descriptor Area using the getlvcb and lqueryvg commands.Read the PVID number from the disk itself using the dd command.(it is held in address 200)create a logical volume in rootvg. Make it one non-mirrored logical partition. Call it lvxx(where xx is your teamid). You will be using this logical volume as a test logical volume in the next few instructions.Try to remove the logical volume that you just created. Use SMIT to do this At the SMIT rmlv menu make a point of pressing F4 to get a list of Logical V olumes. What happens?Try removing the logical volume bye typing in the command rmlv or continue in SMIT by providing the name of the logical volume. What happens?List the information of the physical volumes and logical volumes using the same commands used in steps 2 and 3. You will probably see some error messages now. Write down the error messages.Run lqueryvg and getlvcb. Do these commands work?What does this imply?From the above commands you can conclude that the problem is with the ODM rather than the VGDA. Try and determine specifically what has been corrupted in the ODM. (search in the CuAt object class)To fix the corruption. Using the ODM commands to manipulate and correct the corrupted stanzas in the CuAt object class. You will require the information that you saved in the first section to fix the problem.Test to see if the problems were fixed by using the same commands used in instructions 2 and 3.Log in and su to root. In this section you will be carrying out a procedure referred to by the student notes as Procedure 1 to remove a disk from the root volume group. This exercise is written specifically for systems where the root volume group is installed across two disks and there is sufficient space on one of the disks to house all of the root volume group. First, identify which disks belong to the rootvg.Next, identify the number of USED physical partitions on the disk you want to replace. The disk you want to replace is the one with the boot logical volume.Then, identify the number of FREE physical partitions on allother disks belonging to the same volume group as the disk you want to replace.Check that the number of USED physical partitions on the remaining disks in the same volume group. If the used is smaller than the free then the procedure you are about to do can be used to replace the disk. If not, Procedure 1 is not applicable and you should select an alternative approach.Identify the names of all logical volumes that fully or partially reside on the disk you want to replace.If the disk you want to replace contains the boot logical volume hd5, you will need to migrate the blv. The blv must reside on one physical partition.Once the migration of the blv is complete, recreate the boot image and update the boot record on the disk to which the blv has been migrated.Update the boot devices list for both normal mode and service mode for the classical system only in NVRAM.Save information about base customized devices in the device configuration database onto the boot device.Erase the boot record from the disk you want to replace.The other logical volume that needs special attention is the default dump logical volume, if there is one. In AIX Version 4,the default dump device is paging space. Some installations will create a separate dump logical volume. If your site has done this, and if it is on the volume you are replacing, before migrating the rest of the contents of the disk to be replaced, you will need to temporarily change the primary dump device. A quick way of doing this is to asign the primary dump device to a null device; that is, /dev/sysdumpnull. Since the exercise systems are set up to use paging space, then you will not need to do this. However, check to where your primary and secondary dump devices are assigned.Move all logical volumes from the disk you want to replace to other disks in the same volume group that have enough free physical partitions.Check that the disk you want to replace is free; that is, no physical partitions are allocated to any logical volumes.Reduce the volume group by removing the disk you want to replace from its volume group.Remove the disk as a device from the system and from the ODM database.Do a shutdown followed by a reboot and verify that the “removed” disk does not belong to any volume group.If you do not replace the disk (as in this exercise) then youwould want to check out the position of the logical volumes in rootvg on the disk. You would not, for example, want to have two fragmented paging spaces at either edge of the disk, or the boot or dump logical volumes occupying physical partitions on the center of the disk. Check to see whether you now have a sensible placement of logical volumes on the disk.In this section you will be carrying out a procedure to unconfigure and replace a hard disk when it belongs to a non-rootvg volume group and the disk or data on it cannot be accessed. This procedure ensures that the system will left in a sound state after the disk is replaced; that is, no ODM database or VDGA corruptions will occur and the disks will have consecutive numbers. The following instructions will use the disk that has just been removed from rootvg. First, create a new volume group on the spare disk and vary it online. Name the volume group datavg.Create a file system in the datavg volume group and mount it at /tmp/newvgfs. Verify that it was mounted and note the logical volume name associated with it.Export the volume group which contains the simulated failed disk. This will remove all references to the volume group and all logical volumes and file systems belonging to it from the ODMdatabase, /dev directory, and /etc/filesystems file.Check to see if the /etc/filesystems file has any stanzas left form the file systems that belonged to the exported volume group. If there are any stanzas left, delete them by using your favorite editor. Also, check the /dev/directory to delete them by using your favorite editor. Also, check the /dev/directory to see if the logical volume associated with the file system was removed.Remove the failed disk as a device from the system and from the ODM database.Confirm that the failed disk is not known to the system any moreShut the system down. At this point, in a real situation, the IBM service engineer would replace the disk being sure the new disk has the same SCSI address as the old one, and that any terminators on the new disk are removed.Reboot the system. This will configure the new disk into the system through the running of cfgmgr during normal mode boot. Check to see if the system configured the disk.Recreate the volume group on the replacement disk (and if more than 1 disk all other disks that used to belong to the volume group) and activate the volume group. Check to see if itis active.If this had been a real situation, you would then restore your volume group from a tape that was created using the savevg command. If you didn‟t use the savevg command you would need to recreate the logical volumes and file systems that were in the volume group before the disk failure and then restore the data.Error_logUsing the file command. Identify what type of file the error log is.Execute the command that will display the error log attributes.Look at the various error IDs that are present on your system.Use smit to generate a detailed report on errors that have a resource name value of SYSDUMP. When finished. Experiment with various error reports by trying different values in the dialog screen fields.After exiting smit, use the errorpt command to generate the following reports:A. a summary report of all errors.B. a detailed report of all errors.C. a summary report of all errors that occurred during the past 24hours.D. a detailed report of temporary type errors.E. a detailed report of all errors logged in the past 24 hours.Use the appropriate command to stop the error daemon. Once it has been stopped, restart it.Using your lft and tty, but not AIX-windows, start concurrent error logging via smit. From the tty system, generate an operator message that says “I am testing concurrent error logging.” What happened?Note: The error messages will be sent to your console which is the lft, AIX-windows not work.Increase the buffer size by 4k and verify that it has been increased.Decrease the buffer size to 8k and make sure that the change has taken effect.DiagnosticsInvestigate the hardware diagnostics package that is available with AIX. One of the ways to start the hardware diagnostics package is to execute the command diag. Execute the diag command. When the first screen is displayed pressEnter. At the next screen, highlight and select the TASKS SELECTION LIST option. Page up and down at the TASKS SELECTION LIST screen. Familiarize yourself with some of the options.Using hardware diagnostics display an …ERROR ANALYSIS SUMMARY‟.Using hardware diagnostics perform system verification. Exit back to the initial diagnostics screen.Execute the diagnostics package. Locate, select, and browse the Display Service Hints option.Execute the diag command with the appropriate option to commit any changes to the configuration database.Bring the system to single-user mode.Using hardware diagnostics enable Include Error Log Analysis.The next two instructions are designed to demonstrate how to get to an AIX prompt from within diagnostics. These two steps are for the Classical RS/6000s only. If you are using a PCI RS/6000 system (w/LED), skip this step and the next step. This will allow you to do some software maintenance, if necessary, to fix a problem. Gracefully shut down and reboot the machine into standalone diagnostics.Access the machine via a shell and then gracefully shut down and reboot the machine to normal mode.On the PCI RS/6000 (w/LED), there is no key for Service Mode. You must shut down and reboot your system. When you hear the first beep, press the F1 key to start the System Management Services from firmware. After starting the SMS on the PCI system, then you can example the diagnostic options.DumpLog in as teamxx and su to root. Execute the command to display the estimated size of a dump. Also, determine what your primary and secondary dump devices are and where the copy directory is.Verify that there is enough space in the file system which holds the copy directory. If there is not enough space, increase the size of the file system.Execute the following command:# xinit# smit dumpSelect Start a Dump to the Primary Dump DeviceAfter the dump completes, reboot the machine in Normal mode. Execute the crash command on the dump image that wascreated.Use the crash subcommands to show the system name and time of the dump. The possible symptom of the crash, the process which was schedule to run, the processes running and the machine state area. Exit the crash program.The output from the above step may have scrolled off your screen before you had a chance to examine the output. Reenter the crash commands after entering the following commands. Then page through the file out to examine your output.NOTE: you should use the man page for crash to interpret the output.Run the snap –a command and review the output. This will produce a list of all the directories to where the sanp command writes its output. The files listed are directories. In these directories you will find files that end in .snap which are ASCII files. Review the content of a few. Note that this command will take approximately 10 minutes to run.The /tmp filesystem will not be large enough to create all of the snap command files. Create a new filesystem 16mb in size and mount point at /tmp/ibmsupt.PerformanceLog in as teamxxUse ps to identify current processes on your system. Try ps aux and ps –el.NOTE: CPU and memory usage along with current priorities.Examine the threads for your processes with ps –mo THREADIf there is not enough activity, try issuing a couple of find commands in the background. Redirect the output and errors to /dev/null so they don‟t come to the terminal. Then, repeat the ps commands listed above. Be sure to kill any backgroud jobs that are still running when you are done.In order to run sar you need to be root or a member of the system group. Su to root. Execute the sar command that shows CPU usage displaying the output on the screen. Set it up to collect the data at two second intervals for five times. Before running it, generate some system activity. One way to do this is with the find command running in the background.Using sar, check the run queue. Use the same collection interval as above. Display the output on the screen. Before running it, generate some system activity. One way to do this is with the find command running in the backgroundUsing the sar command, collect the data in a file to be usedlater. Put this data in the file /home/teamxx/sar.collect. Have the sar command run for two second intervals five times. Notice that the sar data for CPU usage is still displayed on the screen even while the output is being saved in /home/teamxx/sar.collect. if you don‟t want to display the data while sar is running, then redirect it to /dev/null (the “bit bucket”). Before running it, generate some system activity. One way to do this is with the find command running in the background. If you are on a particularly fast system, like the RS/6000 40P, you may wish to run the sar data collection before running the commands.Once the data has been collected, run the sar CPU and run queue reports separately.Sar does not provide usage statistics on disk drives, but iostat does. If the io category on the sar –u report was high, use iostat to determine if disks could be the bottleneck by not being balanced in their usage. Look at iostat disk information for two second intervals five times. Before running it, generate some system activity. One way to do this is with the find command running in the background.Vmstat provides a good snapshot picture of memory utilization. Run vmstat at two second intervals for five times. If time permits, try vmstat –s. This provides information from boottime. If need be, generate some system activity with the find command.If you believe that you have found a possible performance problem in AIX, there are tools and procedures for reporting the problem and supplying problem-analysis data. When reporting a problem, there are several pieces of basic information that need to be supplied along with the data collected using the supplied collection tools. For a complete list of the information that should accompany the data collected, please refer to AIX Version 3.2 and 4.1 Performance Tuning Guide, SC23-2365 In this exercise you‟ll concen trate on running the program that gathers performance data, called perfpmr, and viewing some of that data. Check to be sure perfpmr is on your system and update your PATH variable to include the directory that contains the perfpmr executables.Track system activity for five minutes. Make sure you run the perfpmr program in the bvackground and provide an enter key equivalent input to handle the request to press enter after reading the header information and redirect the output.When completed, look in the /var/perf/tmp directory to see what data has been collected. Look at the contents of the following files:If you were going to send this data on to the IBM Support Center you would then need to create a tar file, compress it, and put it on a diskette in tar format. For further information on this procedure, refer to AIX Version 3.2 and 4.1 Performance Tuning Guide, SC23-2365.Identify the biggest CPU-consuming processes on your system using tprof. Enter tprof –x sleep 60, then after 1 minute, examine the _prof.all report file that has been created in the current directory. If there is time, examine the other _* files that were created.Locate the largest user of RAM with svmon. Try svmon –Pau 1.(You must be root user to run svmon.)Find your I/O hot-spots with filemon. Enter filemon –o output –O all, and kick off some I/O activity – look through the manual pages for filemon for example. When you think you can take no more, run trcstop to halt the data collection, and examine your output file for the hot-files.Securitylog in as teamxx and su to root. Display the file name associated with your terminal port. Edit /etc/security/login.cfg to disable logins on your port between the hours of 8:00 am and6:00 pm.List the times that logins are allowed on your terminal port.Log some unsuccessful login attempts to root. Log out and attempt to log in as root two times using an invalid password each time.Log in as teamxx and switch to root. List the number of unsuccessful log in attempts to root since roo t‟s last successful login.Log in as teamxx. Edit your $HOME/.profile file. Set and export the TMOUT variable specifying 15 seconds as the inactive time the shell will wait before exiting. As a system administrator. You can uncomment the TMOUT variable in /etc/profile, if you want the TMOUT variable to be a system-wide default.Reinvoke your .profile. Execute the date command and then wait for 15 seconds to see if the TMOUT variable is invoked.The 15-second inactive time was appropriate for this exercise, but it will become a nuisance while trying to perform the rest of the exercise. Either comment out or delete the TMOUT variable or increase the inactive time.Log in as teamxx and switch to root. Create two new users named teamxx0 and teamxx00 where 0 and 00 are added to yourteamxx login. Assign a password the same as the login names. These two accounts will be used to demonstrate ACLs.Return to teamxx. Create a shell script in your home directory named sample to contain the following:tput clearbanner We love AIXecho End of ProgramThen set the base permissions for sample to 700. Verify that the script works. Log out.Log in as teamxx0. Change directory to /home/teamxx. Try to cat the sample script. Try to execute sample. You should not be able to do either. Log out.Login as teamxx. Edit your .profile file and set and export the EDITOR variable to vi. Reinvoke .profile so the changes are picked up. Use the acledit command to chang the extended permissions of the sample script so that teamxx0 can rwx the script, and teamxx00 can only r-x the script. Apply the modified ACL. Do a long listing of the sample script to verify that extended permissions were set. Log out.Log in as teamxx0. Change to the /home/teamxx directory and test the extended permissions by trying to add the date command to the end of the script and executing the sample script. Log off. Repeat for teamxx00 to verify that teamxx00 cannot edit the script.Log in as teamxx. Change the base and extended permissions to the sample script so that members of the staff group can read and execute the script. EXCEPT for teamxx0. Apply the modified ACL.Log in as teamxx0. Issue the groups command to ensure you are part of the staff group. Change directory to /home/teamxx. You could execute sample in instruction 17. Try to execute it now. you should not be able to. Being the curious user that you are, check to see if extended permissions are set using ls. Now, take a look at the extended permissions that are set. Log out.Log in as teamxx. Create a new file named sample2. Type a couple of lines in the file. Use aclget to see that no extended permissions are set on sample2.Using aclget and aclput, copy the access control information of the file sample to the new file sample2. Verify that the ACLs were copied over to sample2.Using aclget, copy and save the access control list information of the sample script to an output file named aclinfo. Page through the aclinfo file.Edit aclinfo and change deny to permit.Create a file named sample3. Type a few lines in the file. Set the ACLs for sample3 with the information stored in the aclinfofile. Verify that the extended permissions for sample3 are the same as they are in aclinfoAs teamxx, do a chmod 700 on sample. Then do an acledit on sample. What is different? What should you always do after doing a chmod on file?As root, edit the /etc/security/login.cfg file and add the following stanza to the configuration fileUsing smit, set the Trusted Path to always for teamxx.Before you start, log out. At the login screen, press the Enter key, then press the SAK key. (<ctrl-x ctrl-r>). Log in as the user, teamxx, whose Trusted Path was set to always. What kind of command line prompt do you get?Log out and log in as root. Do a more on /etc/security /sysck.cfg to find out what files should be trusted. Then do an ls –e on some of the files in sysck.cfg. if a file is marked as trusted, or the ACL for a file is enabled, or both, a + will show up after the nine permission bits; i.e. , rwxr-xr-x + .tcbck, when run with the y, p to t option, will fix any discrepancies between file definitions in sysck.cfg and what the files actually look like on disk. It does so by altering the file。
AIX系统管理指南
IBM SystemP AIX培训教材目录第1 章RS/6000产品概述 (11)1.1 IBM RISC芯片技术 (11)1.2 对称多处理技术（Symmetric Mulit-Processor , SMP） (12)1.2.1 传统SMP的缺点 (12)1.2.2 RS/6000的解决方案 (12)1.3 SP技术 (13)1.4 RS/6000的体系结构 (13)1.4.1 MAC (13)1.4.2 PCI (14)1.5 系统的可靠性 (14)1.6 高可靠性群集多处理软件HACMP (15)第2 章AIX操作系统简介 (16)2.1 AIX的来历 (16)2.2 AIX操作系统的主要特点 (17)2.2.1 遵循众多工业标准 (17)2.2.2 先进的系统设计 (17)2.2.3 AIX的连接性 (18)2.2.4 终端支持 (19)2.3 命令语言解释器（ksh） (19)2.4 AIX文本编辑器 (19)2.5 AIX系统中的DOS工具 (19)2.6 AIX系统的用户界面 (19)2.7 联机帮助 (20)2.8 AIX的几个重要技术 (20)2.8.1 LVM-Logical Volume Manager (20)2.8.2 JFS-Journal File System (20)2.8.3 系统管理接口工具（smit） (20)第3 章AIX基本命令使用 (21)3.1 基本系统使用命令 (21)3.1.1 系统进入和退出 (21)3.1.1.1 系统进入 (21)3.1.1.2 系统退出 (21)3.1.2 系统关闭和重启 (22)3.1.3 修改密码passwd (22)3.1.4 日期和日历 (22)3.1.5 CLEAR、ECHO、BANNER (23)3.1.6 who、who am i、finger (23)3.1.7 mail (23)3.1.8 查找命令find (24)3.1.9 grep (26)3.1.10 UNAME命令 (26)3.1.11 查看命令帮助 (27)3.2 DOS工具 (27)第4 章文件和目录操作 (28)4.1 文件和目录 (28)4.2 文件命名规则 (28)4.3 路径 (29)4.4 显示当前工作目录 (30)4.5 改变目录层次 (30)4.6 创建目录mkdir (31)4.7 删除目录rmdir (31)4.8 文件操作命令 (31)4.8.1 列文件ls (31)4.8.2 文件拷贝cp (31)4.8.3 文件移动mv (32)4.8.4 文件删除rm (32)4.8.5 查看文件内容cat、more、pg (32)4.8.6 测试文件wc (32)4.8.7 链接ln (33)4.9 文件权限 (33)4.9.1 文件所有权 (34)4.9.2 文件权限 (34)4.9.3 改变文件所有权 (35)4.9.4 改变文件权限 (35)4.10 设备文件 (36)第5 章SHELL入门 (37)5.1 命令结构 (37)5.2 通配符 (37)5.3 环境变量 (38)5.4 PS1环境变量 (39)5.5 PS2环境变量 (39)5.6 标准输入、输出、出错和重定向 (40)5.6.1 标准输入、输出和出错 (40)5.6.2 重定向 (40)5.6.3 重定向的组合 (41)5.7 文件结束标记 (41)5.8 管道线和过滤器 (42)5.9 tee—分叉 (42)5.10 命令返回值 (42)5.11 反引号操作符 (43)5.12 命令序列 (43)5.13 反斜线操作符 (43)第6 章vi 使用 (44)6.1 vi简介 (44)6.2 vi的进入与离开 (44)6.3 vi 的文本输入模式 (45)6.4 删除文本 (45)6.5 更改文本 (46)6.6 vi常用功能 (47)6.7 文件处理子命令 (47)6.8 vi 基本编辑命令 (48)第7 章系统管理工具 (52)7.1 传统UNIX系统管理方法 (52)7.2 三个系统管理工具 (52)7.2.1 SMIT (52)7.2.2 DSMIT (53)7.2.3 VSM (53)7.3 系统管理工具工作方式 (53)7.4 各种系统管理工具功能及使用介绍 (54)7.4.1 SMIT功能及使用方法介绍 (54)7.4.1.1 SMIT用户界面组件 (54)7.4.1.2 SMIT的启动与使用 (55)7.4.1.3 SMIT主要功能及主菜单的使用 (56)7.4.1.4 smit对话屏幕的使用 (57)7.4.1.5 输出屏幕 (60)7.4.1.6 smit屏幕及脚本记录文件 (60)7.4.2 DSMIT简介 (61)7.4.3 可视化系统管理器（VSM）简介 (61)第8 章系统及软件安装 (64)8.1 操作系统安装 (64)8.1.1 安装介质和方式 (64)8.1.2 安装前的准备工作 (64)8.1.3 基本操作系统（BOS）的安装步骤 (65)8.1.4 安装辅助菜单 (70)8.2 软件安装与维护 (70)8.2.1 软件包的定义 (70)8.2.2 Bundle (71)8.2.3 Package命名 (72)8.2.4 代码服务 (73)8.2.5 软件更新 (74)8.2.6 安装状态 (74)8.2.7 软件安装 (75)8.2.8 软件清单 (76)8.2.9 软件维护 (76)8.2.10 instfix命令 (77)第9 章系统启动和关闭 (78)9.1 系统启动 (78)9.1.1 系统启动的几个阶段 (78)9.1.2 BIST – POST阶段 (78)9.1.2.1 基于MCA体系的系统 (78)9.1.2.2 基于PCI体系的系统 (79)9.1.3 Boot phase 1阶段 (81)9.1.4 Boot phase 2阶段 (81)9.1.5 Boot phase 3阶段 (82)9.2 查看启动信息 (82)9.3 /etc/inittab文件 (82)9.4 系统资源控制器 (84)9.4.1 SRC概念 (84)9.4.2 SRC命令 (84)9.5 系统关闭 (85)第10 章ODM管理 (86)10.1 ODM概述 (86)10.2 ODM概念: (86)10.3 ODM命令 (87)第11 章设备管理 (89)11.1 设备术语 (89)11.2 设备文件 (89)11.3 ODM预定义和定制设备数据库 (90)11.4 lsdev命令 (91)11.4.1 列出所有被支持的设备 (91)11.4.2 列出所有定义了的设备 (92)11.5 设备状态 (93)11.6 设备寻址 (94)11.7 设备配置 (94)11.7.1 自动配置设备 (94)11.7.2 手工配置 (95)11.7.2.1 SMIT设备菜单 (95)11.7.2.2 增加配置设备 (96)11.8 获取硬件配置信息 (97)第12 章存储管理概述 (98)12.1 AIX4.3版本存储组件 (98)12.2 传统UNIX磁盘存储 (98)12.3 LVM的优点 (98)12.4 物理存储 (99)12.4.1 物理存储概念 (99)12.4.2 卷组考虑 (100)12.4.3 卷组描述字段 (100)12.5 逻辑存储 (101)12.5.1 逻辑存储概念 (101)12.5.2 逻辑卷用途 (103)12.5.3 显示逻辑卷信息 (103)12.6 文件系统 (104)12.6.1 文件系统概念 (104)12.6.2 文件系统优点 (104)12.6.3 AIX 4.3的标准文件系统 (105)12.6.4 /etc/filesystems文件 (105)12.6.5 文件系统挂接（MOUNT） (106)12.6.6 文件系统列表 (108)第13 章逻辑卷管理(LVM) (110)13.1 卷组管理 (110)13.1.1 显示卷组信息 (111)13.1.2 增加和删除卷组 (113)13.1.3 修改卷组特性 (113)13.1.4 增加或删除卷组中的物理卷 (114)13.1.5 重组卷组 (115)13.1.6 激活和停止卷组 (115)13.1.7 引入/导出卷组 (116)13.2 逻辑存储 (117)13.2.1 基本概念 (117)13.2.1.1 镜像（mirror） (117)13.2.1.2 条带化（striping） (118)13.2.1.3 逻辑卷分配策略 (119)13.2.2 逻辑卷的管理 (119)13.2.2.1 显示逻辑卷信息 (120)13.2.2.2 增加逻辑卷 (121)13.2.2.3 删除逻辑卷 (122)13.2.2.4 设置逻辑卷的特性 (123)13.2.2.5 增加/删除逻辑卷拷贝 (123)13.3 物理卷管理 (125)13.3.1 显示物理卷信息 (125)13.3.2 增加磁盘 (127)13.3.3 迁移物理卷内容 (127)13.4 获取存储系统的配置信息 (127)第14 章文件系统管理 (128)14.1 基本概念 (128)14.1.1 日志文件系统的结构 (128)14.1.2 inode节点结构 (128)14.1.3 磁盘分段（fragmentation） (129)14.1.4 inode节点的数目 (130)14.1.5 文件系统压缩 (130)14.1.6 JFS文件系统日志 (131)14.2 文件系统管理 (131)14.2.1 列出文件系统 (132)14.2.1.1 列出系统中定义的所有文件系统 (132)14.2.1.2 列出系统中已挂接的文件系统 (133)14.2.2 增加文件系统 (133)14.2.2.1 在已有逻辑卷上创建文件系统 (133)14.2.2.2 直接创建JFS文件系统 (135)14.2.3 文件系统的挂接和拆卸 (136)14.2.4 更改/显示日志文件系统特性 (137)14.2.5 删除文件系统 (138)14.2.6 整理文件系统碎片 (138)14.2.7 文件系统检查 (139)14.2.8 获取文件系统信息 (139)14.3 磁盘空间管理 (139)14.3.1 显示文件系统空间使用情况 (140)14.3.2 控制增长较快的文件 (140)14.3.3 显示磁盘使用情况 (141)第15 章系统交换区管理 (142)15.1 换页空间的概念 (142)15.2 为什么使用换页空间 (143)15.3 如何提高换页空间的性能 (143)15.4 换页空间相关命令和文件 (143)15.5 增加换页空间 (144)15.6 修改换页空间 (145)15.7 删除换页空间 (145)15.8 换页空间问题解决 (145)第16 章系统备份和恢复 (147)16.1 概念与术语 (147)16.1.1 备份和恢复 (147)16.1.2 恢复 (148)16.1.3 备份的类型 (148)16.1.4 备份的策略 (148)16.1.5 备份用设备 (149)16.1.5.1 软盘 (149)16.1.5.2 磁带 (150)16.2 备份和恢复的实施 (151)16.2.1 备份及恢复的SMIT菜单 (151)16.2.2 rootvg的备份与恢复 (151)16.2.2.1 rootvg的备份－mksysb (151)16.2.2.2 rootvg的/image.data文件： (152)16.2.2.3 rootvg的/bosinst.data文件： (154)16.2.2.4 rootvg的恢复 (155)16.2.3 非rootvg卷组的备份与恢复 (156)16.2.3.1 非rootvg卷组的备份 (156)16.2.3.2 非rootvg卷组的恢复 (157)16.2.4 文件和目录的备份与恢复 (158)16.2.4.1 备份文件或目录 (158)16.2.4.2 恢复文件或目录 (159)16.2.5 文件系统的备份与恢复 (159)16.2.5.1 备份文件系统 (159)16.2.5.2 文件系统的恢复 (161)16.2.6 其它UNIX备份和恢复命令 (162)16.2.6.1 tar命令 (162)16.2.6.2 cpio命令 (163)16.2.6.3 dd命令 (163)16.2.7 其他与备份相关命令 (163)16.2.8 备份文档的策略 (164)第17 章网络管理 (165)17.1 TCP/IP基本概念 (165)17.2 互联网实例 (165)17.3 TCP/IP配置 (167)17.4 配置IP地址和主机名 (168)17.5 修改IP地址和主机名 (169)17.6 相关文件 (169)17.7 路由管理 (169)17.7.1 查看路由 (169)17.7.2 增加/ 删除静态路由 (170)17.8 基本TCP/IP工具 (170)17.8.1 检验连通性ping (170)17.8.2 文件传输ftp (170)17.8.3 远程登陆 (171)17.8.3.1 telnet (171)17.8.3.2 rlogin (171)17.8.4 远程执行 (171)17.8.4.1 rcp (171)17.8.4.2 rexec (172)第18 章用户和组管理 (173)18.1 概述 (173)18.1.1 用户和组 (173)18.1.2 用户登录和初始化 (173)18.1.2.1 用户登录过程 (173)18.1.2.2 用户初始化文件 (175)18.1.3 组的分类 (176)18.1.4 用户划分 (176)18.1.5 安全性和用户菜单 (177)18.2 用户管理 (178)18.2.1 显示系统中所有用户 (178)18.2.2 添加用户 (179)18.2.3 修改/显示用户属性 (180)18.2.4 删除用户 (181)18.2.5 设置、更改用户口令 (181)18.2.6 紧急情况下删除root口令 (182)18.3 组管理 (183)18.3.1 显示系统中所有的组 (183)18.3.2 添加组 (184)18.3.3 修改//显示组属性 (185)18.3.4 删除组 (185)18.4 系统管理员与用户通讯的工具 (186)18.4.1 motd文件 (186)18.4.2 write和wall命令 (186)18.4.3 talk命令 (187)18.4.4 mesg命令 (187)第 1 章RS/6000产品概述RS/6000是IBM公司的出色产品。
AIXforSystemAdministrators
AIXforSystemAdministratorsHMC command line:The 2 mostly used commands to gather info about managed systems and lpars:lssyscfg: info about managed system, lpar (i.e. running or not) or profile configurationlshwres: info about the resources (cpu/mem/vscsi..) of a managed system or lpar------------------------------------------------------------------------------------------------------------------------lssyscfgLists managed-systems, partitions, partition profiles and attibutes of them. When you give resource type you can choose from: sys, lpar or prof.If sys or lpar has been chosen it does not list resources like cpu/mem settings or vscsi/vfc adapter config, only general info about the system/lpar, like lpar is activated or not, what is the cpu mode, or rmc state...If prof is chosen, it lists cpu,mem,vscsi... config from the lpar profile. (lshwres command shows these data from the running partition, not from the profile.)lssyscfg -m <sys> -r <res> --filter "<name>=<value>,<value>" -F <attr>,<attr> --header-m name of the managed system (if omitted all managed systems will be listed)-r resource typesys gives general indo about managed systemlpar gives general info about lparprof gives specific infos (cpu, mem, vscsi..) from the lpar profile--filter select values for a specific resource only (lpar_ids, lpar_names and profile_names)"lpar_ids=...,...""lpar_names=...,.""profile_names=.."-F display only the given attributes (name of the attr. will not be displayed and delimeter can be specified)--header show header of the displayed values------------------------------------------------------------lssyscfg -r sys -F name lists name of managed systems (this name can be used in other commands)lssyscfg -m <sys> -r lpar lists general info of lpars on themanaged sys.lssyscfg -m <sys> -r prof lists all settings in the lpar profiles on the managed sys.other example:lssyscfg -m <sys> -r lpar -F name,state --header lists lpars and if it is activated or not lssyscfg -m <sys> -r prof -F lpar_name,virtual_eth_adapters lists lpars with eth. adapters (vlan tags will be shown as well)lssyscfg -m <sys> -r prof --filter "lpar_names=<lpar>" -F name,virtual_fc_adapters lists vfc adapters (with wwpn) of an lpar------------------------------------------------------------------------------------------------------------------------lshwres:Lists hardware resources of the managed-system and lpars, including physical I/O, virtual I/O, cpu/mem settings, (shared) processor pool, etc.lshwres -m <sys> -r <res> --rsubtype <subtype> --level <lpar/sys> --filter "<name>=<value>,<value>" -F <attr>,<attr> --header-m name of the managed system (lssyscfg -r sys -F name)-r resource typeio physical iomem memoryproc processing unitvirtualio virtual io--rsubtype subtype of the resource given previously (it works for io and virualio)io slot, slotchildresn (these can be used for the resource 'io')virtualio eth, fc, scsi, vswitch (these can be used for the resource 'virtualio')--level display info of managed system or lpar (it works for mem, proc and virtualio)lpar info is taken from lpar level (i.e memory values of the lpars)sys info is taken from system level (i.e memory value of the managed system)--filter select values for a specific resource only (not all value can be used as filter)"lpar_ids=...,...""lpar_names=...,.""vlans=...,...,.."-F display given attributes (the name of the attribute will not be displayed and delimeter can be specified)--header show header of the displayed values------------------------------------------------------------Physical I/O (io):lshwres -m <sys> -r io --rsubtype slot/slotchildren shows io slot information (or children devices of slots)MEM/PROC (mem/proc):lshwres -m <sys> -r mem/proc --level lpar/sys shows mem/proc info of all lpars or the managed systemVIRTUAL I/O (virtualio):lshwres -m <sys> -r virualio --rsubtype vswitch shows virtual switches with configured vlan ids on themlshwres -m <sys> -r virualio --rsubtype eth --level lpar shows virt. ethernet adapters with lpar_name,slot_id, vlan_id....lshwres -m <sys> -r virualio --rsubtype fc --level lpar shows virt. fc adapters with lpar_name,slot_id, wwpns...lshwres -m <sys> -r virualio --rsubtype scsi --level lpar shows vscsi adapters with lpar_name,slot_id...other example:lshwres -m <sys> -r virtualio --rsubtype eth --level lpar --filter "lpar_names=<lpar>" -F slot_num:addl_vlan_ids shows lpar virt. adapters and vlans------------------------------------------------------------------------------------------------------------------------Other commands:TAB-TAB shows all commands available for the user (commands have --help option and man pages)chsysstate -m <sys> -o standby -r sys power on a system to standbychsysstate -m <sys> -r sys -o off normal power off the managed systemchsysstate -m <sys> -r sys -o off --immed fast power off the managed systemchsysstate -m <sys> -r lpar -n <lpar> -o shutdown --restart it will reboot an lpar with dumpchsysstate -m <sys> -r lpar -n <lpar> -o shutdown --immed --restart it will reboot an lpar immediately (without dump)chsysstate -m <sys> -r lpar -n <lpar> -o shutdown --immed it will shutdown the operating systemchsysstate -m <sys> -r lpar -n <lpar> -o on -f default it will activate an lparmigrlpar perform partition migrationslslparmigr lists info about lpar migrationlslparmigr -m <sys> -r lpar list lpars and migration state (not migrating or migrating..)lslparmigr -r sys -m <managed system> | sed "s/,/\n/g" shows how many concurrent migr. is possiblelsnportlogin -m sys> --filter "lpar_names=<lpar>" list all npiv (wwpn) info of an lparlsnportlogin -m sys> --filter "lpar_names=<lpar>" -F wwpn lists only wwpn of given lparlspartition -dlpar shows dlpar capable partitions(it will show if RMC connection is OK between the HMC and LPAR)lssacfg -t email shows email notification settingslssysconn -r all to see what IPs are assigned by the HMCmksysconn -o auto tells HMC to re-discover all servers' IP addresslssvcevents -t console -d 60 lists console events in the past 60 dayslssvcevents -t hardware -d 0 list serviceable events which occured todaylssvcevents -t console -d 300 | grep DLPAR list DLPAR operations of last 300 days (you can grep more to mem or proc) lssvcevents -t console -d 7 | grep Migration list last 7 days LPMslshmc -V hmc versionlshmv -v hmc modellshmc -n lists the network settings of the hmchmcshutdown -t now -r reboot the HMC (-t: timing inminutes, -r: reboot)lslogon -r webui -u lists users logged in gui (lslogon -r webui -t <--lists running tasks)lslogon -r ssh -u lists users logged in cli (lslogon -r ssh -t <--lists running tasks)termtask -r { webgui | ssh } -s (session) -t (task) terminate a running task (or all tasks)monhmc -r mem -n 0 shows total, used and free mamory of HMCmonhmc -r disk -n 0 shows filesystems and usage info (same as "df -k")monhmc -r proc -n 0 shows cpu usage of each processor monhmc -r swap -n 0 shows paging space usagesendfile transfer files with ftp from HMC to another servervtmenu hmc menu options (console session can be opened as well)logout: ~~. (2 tilde and a dot)for i in `lssyscfg -r sys -F name`;do echo $i;lssyscfg -r lpar -m $i -F name|grep <LPARNAME>;echo;done <--shows man. system of given LPARfor i in `lssyscfg -r sys -F name`;do lssyscfg -r prof -m $i -F lpar_name,virtual_eth_adapters | grep vio | grep <VLAN>;echo; done <--shows spec. VLANfor i in `lssyscfg -r sys -F name` ; do echo $i; lssyscfg -rprof -m $i -F name,lpar_name --header; done <--show all lpar profilesfor sys in `lssyscfg -r sys -F name`; do for vio in `lssyscfg -r lpar -m $sys -F name,lpar_env | grep vioserver | cut -f 1 -d, | sort`; do echo $vio; viosvrcmd -m $sys -p $vio -c errlog; done; done <--runs a command (here errlog) on VIOS servers------------------------------------Default root password: passw0rd (try su -)------------------------------------/usr/samples/tcpip/anon.ftpIf you want to use remote FTP installs on HMC, an FTP user will be needed on the remote (AIX) server.There is a default script on AIX which creates an ftp or anonymous user for this FTP connection: /usr/samples/tcpip/anon.ftpThis scripts should be used to create FTP user, otherwise connection will work but files won’t be reachable by HMC.------------------------------------opening/closing virtual terminal from hmc:lssyscfg -r sys -F name <--get managed system namelssyscfg -r lpar -m <managed system> -F name <--get lpar namemkvterm -m <managed system> -p <lpar> <--opens a terminal windowrmvterm -m <managed system> -p <lpar> <--closes a terminal window~~. <--logout from the session (not necessary to leave AIX)------------------------------------Adding/removing VLAN TAG dynamically:(it will not add to profile)adding:chhwres -r virtualio --rsubtype eth -m <man.sys.> -o s -p <LPAR> -s <adapter id> -a "addl_vlan_ids+=<VLAN TAG>"removing:chhwres -r virtualio --rsubtype eth -m <man.sys.> -o s -p <LPAR> -s <adapter id> -a "addl_vlan_ids-=<VLAN TAG>"------------------------------------Changing LPAR weight:lshwres -r proc -m <MAN_SYS> --level lpar --filter lpar_names=<LPAR_NAME> list actual runningconfigchhwres -r proc -m <MAN_SYS> -p <LPAR_NAME> -o s -a "uncap_weight=32" changes weight of actual running configlssyscfg -r prof -m <MAN_SYS> --filter lpar_names=<LPAR_NAME> list profile chsyscfg -r prof -m <MAN_SYS> -i "name=<PROFILE_NAME>,lpar_name=<LPAR_NAME>,uncap _weight=32" changes weight in given profile。
AIX小型机操作系统学习指南-系统管理概述
整理ppt
15
P550 服务器外观
整理ppt
16
P5系列指示灯状态及意义
整理ppt
17
P5系列控制盘简介1
整理ppt
18
P5系列控制盘简介2
A Power button B On/off power symbol C Type and serial number label D Function/Data display E Ethernet connector F Power on light
IntelliStation POWER 185
整理ppt
9
IBM SN 的命名方式
型号的命名方式:
4位的（model）和3位的type号码组成的，model是一个系列的号码， 而type是他这款机型的一个代码.
SN的命名方式:
IBM的产品为7位, 前两位是代表工厂的编号 （比如 65 、 10 都代表 USA 、75代表匈牙利等等）后5位代码是这台机器的序列号.
整理ppt
5
IBM unix cpu 发展历史
Copper 代表铜芯片技术 SOI 代表绝缘硅技术 Low-K 代表Low-K绝缘整介理质p技p术t
*IBM特有的SMP（对称多处理器技术） 6
RS6000系列产品
7025-6F1（F85） 7025-6F0 （F80）
7026-6H1（H85） 7026-H80（H80）
location. This function is available only in the manual operating mode and
from power on standby.
整理ppt
21
1.1.3 工作站配置
AIX系统管理手册
索引1 命令索引2 存储管理2.1 概述AIX下磁盘首先是一个物理卷（PV），几个物理卷组成一个巻组（VG）。
定义巻组过程中，需要指定分区大小（PP），这个尺寸用于逻辑卷（LV）的定义。
Fget_config –Av2.2 物理卷定义（PV）系统扫描到磁盘以后，首先给他增加一个pvid，使其变成PV，命令如下：Chdev –l hdisk7 –a pv=yes删除pvid，命令如下：Chdev –l hdisk7 –a pv=clear查看物理卷的详细信息，使用lspv命令。
2.3 巻组定义（VG）使用lsvg –l查看巻组的详细信息，包括此巻组分成了几个逻辑卷，这几个逻辑卷又挂载在那个文件系统上。
创建一个卷组使用mkvg命令。
Extendvg：将一个物理卷添加到已有卷中。
Chvg：更改卷组属性。
Reducevg：删除或者导出一个物理卷。
Lsvg列出vg列表。
2.4 逻辑卷定义（LV）使用lslv查看逻辑卷的详细定义。
Mklv：创建一个逻辑卷。
Chlv：修改一个逻辑卷的名称或者特征。
Extendlv：增加逻辑卷分配的逻辑分区的数据。
Cplv：复制逻辑卷。
Rmlv：除去逻辑卷。
Mklvcopy：增加逻辑卷的副本数目，用于逻辑卷镜像。
Rmlvcopy：减少逻辑卷的副本数目，用于删除逻辑卷镜像。
Crfs：为逻辑卷创建一个文件系统。
2.5 交换空间（PS）Mkps：创建新的页面空间。
Chps：修改页面空间属性。
Lsps –a：显示页面空间列表。
Rmps：移除页面空间。
Swapon，swapoff：激活或者禁用页面空间。
2.6 文件系统命令Backup、restore：备份和还原。
Chfs：修改jfs文件属性，例如，为文件系统扩容。
Dd：将数据从一个存储设备直接复制到另一个存储设备。
Df：获得文件已使用空间大小。
Fsck：检查文件系统的一致性，并修复。
Crfs：在卷组上直接创建文件系统。
Mkfs：在逻辑卷上创建文件系统。
3_系统管理工具
第三章.系统管理工具本章内容：本章介绍了系统管理中有用的工具3.1本章学习目标:z 描述AIX 版本4中可用的系统管理工具的用处z 定义SMIT 的功能,以及画面显示的不同类型z 定义如何进入SMIT 的各种行为z 定义DSMIT 的使用z 列出VSM 的应用3.2早期的系统管理Print kill mountErrptbackupPasswd restoreTrace updatep备注:UNIX 及AIX 中版本3之前的系统管理的主要缺点是没有一个共同的接口以执行系统管理任务,系统管理员必须十分熟悉系统是如何工作的。
以下是经常用到的技巧：z Commands(命令集):许多命令在执行系统管理功能是十分有用的。
有从不同的版本中继承下来（如AT&T 、Berkeley 及IBM ），并不在所有的系统中能被运行。
z Front Ends:有一些菜单或命令用来执行系统管理。
遗憾地是它们相互之间接口不一致，并且不能被交互使用。
（也即是要从Shell 脚本中执行）z Flat Files:编辑各种系统配置文件有各种不同的格式,容易导致输入错误及需要掌握系统编辑器知识3.3 AIX版本4管理备注:(1)AIX版本4提供菜单驱动的系统管理接口工具SMIT,可以在一个一致的环境中提供众多的常规系统管理功能。
(2)SMIT并没有直接执行系统管理功能,它是一个高级命令的用户接口,在用户需要时执行。
有关的那些命令也可以直接输入执行一样的任务。
z高级命令:是可被用户执行的标准AIX命令(是Shell脚本或C程序)他们执行多个低级或中级命令以执行系统管理功能z低级命令:有关AIX系统调用或核心设备的AIX命令(不能被用户直接调用)z中级命令:这是有关AIX的特别组成部分如系统资源控制器(SRC)及对象数据管理器(ODM) (这些命令很少被用户直接执行)(3)SMIT并没有覆盖每一个可能的系统管理任务,所以有时也很有必要直接运行AIX命令或编辑ASCⅡ文件。
aix系统管理指南
系统管理指南：操作系统与设备比较不同机器上的文件系统如果万一存在于不同机器上的文件系统是相同的，但您怀疑有一个系统已破坏，则可以比较文件系统。
以下过程描述如何将驻留在您当前主机（在该方案中，称为orig_host）上的文件系统的属性与远程主机上的相同文件系统的属性比较。
1.以 root 用户身份登录到远程主机。
例如：2.tn 3.4.5.AIX V56.(C) Copyrights by IBM and by others 1982, 2002.7.登录：root 用户root 用户的密码：8.使用您最喜欢的编辑器，编辑主机的.rhosts文件以添加允许 root 用户执行安全远程命令的节。
对于新节，请使用以下格式：orig_host root产生的.rhosts文件可能看起来类似如下： root root rootorig_ root9.保存更改并退出远程连接。
10.使用orig_host上的超级权限，用您最喜欢的编辑器创建另一个文件。
对于该方案，新文件命名为compareFS。
例如：vi compareFS11.在该文件中插入以下正文，其中FSname是您想要比较的文件系统的名称，remote_host是比较文件系统所驻留的主机的名称：12.FSname -> remote_hostinstall -v ;注:在该文件的install命令行中，-v参数与分号（;）之间必须有一个空格。
例如：/home/jane/* -> install -v ;13.保存文件并退出编辑器。
对于以下步骤中的rdist命令，将compareFS文件用作distfile。
14.在命令提示符处输入以下内容：/usr/bin/rdist -f compareFS或者，如果期望从比较中获取大量的输出，则将输出发送到文件名。
例如：/usr/bin/rdist -f compareFS > compareFS_output输出列出了文件系统之间的任何差别。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
to administer an AIX system ( "managed machine" ) from a remote PC or another AIX system using graphics terminal ("managing machine")
enter 200 Carriage Return
Change takes effect on next boot
? Enable Full Core Dumps
smitty System Environments
Change/Show Characteristics of Operating System Enable Full Core Dump (Hit F4 and pick "true" )
Web-based System Manager
(WSM)
? A web-based system administration tool ? Enables a user to access and manage multiple remote machines ? Modes of operation
SMIT (Continued)
? smitty -x -s /tmp/mysmit.scripts
-x do not execute the commands generated -s write the commands generated to script file specified.
For Input device/directory for software enter /dev/cd0
For Software to install hit F4 Type /perf to locate installation packages containing the string 'perf' select 'bos.perf' with F7, hit 'n' to continue search select 'perfagent.tools' with F7
smit Examples
? Change the number of AIX licensed users
smitty
System Environments
Change/Show Number of License UsersMaximum Number of Fixed Licenses
Standalone Application Mode
to perform system administration functions on the AIX system you are currently running on ( type /usr/websm/bin/wsm ) fastpaths are supported ( ex : wsm users )
?
?
Boot Process (Continued)
? bosboot Command
Creates the boot image
bosboot -Action [-d Device][-Options....] bosboot -a
Creates a complete boot image on the default boot logical volume on the fixed disk from which the system is booted.
Creates and maintains a fixed-size log file
man alog for more detail alog -o -t boot
Displays the boot log
alog -L -t boot
Displays the boot log file name and attributes
ODM
? Data Not Managed by the ODM
Filesystem Information
maintained in ASCII file, /etc/filesystems
User/Security Information
maintained in ASCII files, /etc/passwd, etc/security/user, /etc/security/passwd, /etc/group .
Boot Process (Continued)
? Multiboot AIX with bootlist
? ? ?
Install AIX 5.3 on hdisk0
Install AIX 5.1 on hdisk1
Set the boot device to hdisk0 or hdisk1 on the bootlist command to boot in AIX 5.3 or 5.1 respectively.
Queues and Queue Devices
maintained in ASCII file, /etc/qconfig
? Location of ODM Repositories
/etc/objrepos and /usr/lib/objrepos
Boot Process
? Boot Log
Example: Installing bos.perf and perfagent.tools
? Insert the AIX 5.1 Installation CD in the CD-ROM.
Type smitty install Select Install and Update Software Select Install Software
Object Data Manager (ODM)
?
? ? ?
A database intended for storing system information and to manage data for application programs.
It provides a more robust, secure, sharable resource than the ASCII files previously used in AIX. Information is stored and maintained as objects with associated characteristics. Stored in binary format, can only be worked using ODM commands, such as odmget, odmdelete, odmcreate
Applet Mode
install a web server on managed machine use the following command to enable machine to be managed: /usr/websm/bin/wsm -host [managing machine host] managing machine must have browser configured from a browser, use URL: http://<managing machine>/wsm.html
Provided for menus, menu choices, and input and output fields. In ASCII mode, press the F1 Help key to display context-sensitive help. In the graphical mode, select the desired help from the Help menu.
®
AIX System Administration
Wayne Huang
huangw@ wyhuang@
AIX System Administration Topics
? AIX Benefits for System Administrators
? Boot Process ? SMIT ? Creating Users and Groups ? Logical Volume Manager (LVM) ? Paging Space ? TCP/IP
?
Data Managed by the ODM
Device Configuration Data Software Vital Product Data (SW VPD) System Resource Controller Data (SRC) TCP/IP Configuration Data Error Log and Dump Information SMIT menus and commands
?
?
System management activity logging
smit.script and smit.log
Fast paths to system management tasks
Command strings entered with the SMIT command can take you directly to the menu or dialog screen for the specific test
? Benefits
?
Benchmark comparison of performance between AIX 5.3 and 5.1.
Migrating up in AIX maintenance level, maintaining multiple versions of AIX. Installing AIX 5.x in 32-bit mode on hdisk0 and in 64-bit