AIX 6.1操作系统与设备管理指南

需积分: 9 94 浏览量更新于2024-08-02 收藏 7.31MB PDF 举报

"Aix 6.1 操作系统和设备管理是IBM的高级UNIX操作系统版本，专注于系统管理和设备管理的指南。本指南适用于AIX 6.1及其后续发布版本，旨在提供有关如何有效地管理AIX环境的详细指导。文档包含了重要的注意事项、读者评论表单以及版权信息。" 在深入探讨AIX 6.1的操作系统和设备管理之前，首先要理解AIX的核心特性。AIX，全称为Advanced Interactive eXecutive，是IBM开发的一种强大的、稳定且安全的多用户、多任务操作系统，广泛用于IBM Power Systems服务器。AIX 6.1版本提供了许多增强功能，包括改进的性能、安全性、可管理性和兼容性。系统管理方面，该指南可能涵盖以下内容： 1. **安装与升级**：详细介绍了如何安装AIX 6.1，包括基本安装、定制安装以及从早期版本升级的过程，确保数据和配置的安全。 2. **系统配置**：涵盖了网络配置、用户管理、文件系统管理（如JFS2）、存储管理（如LVM - Logical Volume Manager）和硬件配置。 3. **性能监控与调优**：提供工具和方法来分析系统性能，包括CPU、内存、I/O等，并给出优化建议，以确保系统运行高效。 4. **安全管理**：涉及用户权限管理、认证机制、防火墙设置、加密技术以及审计功能，以保护系统免受未经授权的访问。 5. **备份与恢复**：讲解如何制定备份策略，使用备份工具（如TSM或NIM），以及在灾难发生时如何恢复系统和数据。 6. **故障诊断与排错**：提供错误日志分析、故障排除步骤和维护技巧，帮助管理员快速定位和解决问题。 7. **软件包管理**：介绍如何使用Package Management Facility (PMF) 和 RPM 安装、更新和管理软件。设备管理则可能涉及： 1. **设备驱动程序**：详细说明如何识别、安装和更新设备驱动，以确保硬件与操作系统兼容。 2. **存储管理**：涵盖磁盘、磁带和其他存储设备的配置、分区和格式化，以及RAID级别和存储池的管理。 3. **网络设备**：讨论网络接口卡(NIC)的配置，包括IP地址分配、DNS设置和网络故障排查。 4. **打印服务**：解释如何设置和管理打印机，包括本地和网络打印机的配置。 5. **虚拟化**：可能涵盖PowerVM虚拟化技术，如何创建和管理虚拟机（LPar）以及资源共享。 6. **设备监控**：介绍如何使用系统监控工具跟踪设备状态，预防硬件故障。 7. **硬件故障处理**：提供硬件故障的诊断流程和更换指南，确保最小化系统停机时间。此外，文档中的"读者评论表单"鼓励用户提供反馈，以便IBM持续改进其产品和支持文档。版权信息强调了文档的法律权益，同时也指出IBM有权使用提供的任何信息，但不承担义务。 AIX 6.1操作系统和设备管理指南是一本全面的参考书，对任何希望深入了解和管理AIX环境的IT专业人员来说都极其有价值。通过学习这些知识，可以有效地维护和优化AIX系统的运行，提高组织的IT基础设施效率。

For example, to add a record for tty2, type the following at a command prompt:

mkitab tty002:2:respawn:/usr/sbin/getty /dev/tty2

In the above example:

tty002 Identifies the object whose run level you are defining.

2 Specifies the run level at which this process runs.

respawn Specifies the action that the init command should take for this

process.

/usr/sbin/getty /dev/tty2 Specifies the shell command to be executed.

Changing records - chitab command

To change a record to the /etc/inittab file, type the following at a command prompt:

chitab Identifier:Run Level:Action:Command

For example, to change a record for tty2 so that this process runs at run levels 2 and 3, type:

chitab tty002:23:respawn:/usr/sbin/getty /dev/tty2

In the above example:

tty002 Identifies the object whose run level you are defining.

23 Specifies the run levels at which this process runs.

respawn Specifies the action that the init command should take for this

process.

/usr/sbin/getty /dev/tty2 Specifies the shell command to be executed.

Listing records - lsitab command

To list all records in the /etc/inittab file, type the following at a command prompt:

lsitab -a

To list a specific record in the /etc/inittab file, type:

lsitab Identifier

For example, to list the record for tty2, type: lsitab tty2.

Removing records - rmitab command

To remove a record from the /etc/inittab file, type the following at a command prompt:

rmitab Identifier

For example, to remove the record for tty2, type: rmitab tty2.

Related concepts

“System run level” on page 13

The system run level specifies the system state and defines which processes are started.

Reactivation

of an inactive system:

Your system can become inactive because of a hardware problem, a software problem, or a combination

of both.

8 AIX Version 6.1 Operating system and device management

This procedure guides you through steps to correct the problem and restart your system. If your system is

still inactive after completing the procedure, refer to the problem-determination information in your

hardware documentation.

Use the following procedures to reactivate an inactive system:

Hardware check:

There are several procedures you can use to check your hardware.

Check your hardware by:

Checking the power:

If the Power-On light on your system is active, go to Checking the operator panel display, below.

If the Power-On light on your system is not active, check that the power is on and the system is plugged

in.

Checking the operator panel display:

If your system has an operator panel display, check it for any messages.

If the operator panel display on your system is blank, go to Activating your display or terminal, below.

If the operator panel display on your system is not blank, go to the service guide for your unit to find

information concerning digits in the Operator Panel Display.

Activating your display or terminal:

Check several parts of your display or terminal, as follows:

v Make sure the display cable is securely attached to the display and to the system unit.

v Make sure the keyboard cable is securely attached.

v Make sure the mouse cable is securely attached.

v Make sure the display is turned on and that its Power-On light is lit.

v Adjust the brightness control on the display.

v Make sure the terminal’s communication settings are correct.

If your system is now active, your hardware checks have corrected the problem.

Related tasks

“Restarting the system” on page 11

addition to checking the hardware and checking the processes, you can restart you system to reactivate

an inactive system.

“Checking the processes”

A stopped or stalled process might make your system inactive.

Checking

the processes:

A stopped or stalled process might make your system inactive.

Check your system processes by:

1. Restarting line scrolling

2. Using the Ctrl+D key sequence

Operating system and device management 9

3. Using the Ctrl+C key sequence

4. Logging in from a remote terminal or host

5. Ending stalled processes remotely

Restarting line scrolling:

Restart line scrolling halted by the Ctrl-S key sequence by doing the following:

1. Activate the window or shell with the problem process.

2. Press the Ctrl-Q key sequence to restart scrolling. The Ctrl-S key sequence stops line scrolling, and

the Ctrl-Q key sequence restarts line scrolling.

your scroll check did not correct the problem with your inactive system, go to the next section, Using

the Ctrl-D key sequence.

Using the Ctrl-D key sequence:

1. Activate the window or shell with the problem process.

2. Press the Ctrl-D key sequence. The Ctrl-D key sequence sends an end of file (EOF) signal to the

process. The Ctrl-D key sequence may close the window or shell and log you out.

the Ctrl-D key sequence did not correct the problem with your inactive system, go to the next section,

Using the Ctrl-C key sequence.

Using the Ctrl-C key sequence:

End a stopped process by doing the following:

1. Activate the window or shell with the problem process.

2. Press the Ctrl-C key sequence. The Ctrl-C key sequence stops the current search or filter.

the Ctrl-C key sequence did not correct the problem with your inactive system, go to the next section,

Logging in from a remote terminal or host:.

Logging in from a remote terminal or host:

v Log in to the system from another terminal if more than one terminal is attached to your system.

v Log in from another host on the network (if your system is connected to a network) by typing the tn

command as follows:

tn YourSystemName

The system asks for your regular login name and password when you use the tn command.

you were able to log in to the system from a remote terminal or host, go to the next section, Ending

stalled processes remotely.

If you were not able to log in to the system from a remote terminal or host you need to restart the system.

You can also start a system dump to determine why your system became inactive.

Ending stalled processes remotely:

End a stalled process from a remote terminal by doing the following:

1. List active processes by typing the following ps command:

ps -ef

10 AIX Version 6.1 Operating system and device management

The -e and -f flags identify all active and inactive processes.

2. Identify the process ID of the stalled process.

For help in identifying processes, use the grep command with a search string. For example, to end the

xlock process, type the following to find the process ID:

ps -ef | grep xlock

The grep command allows you to search on the output from the ps command to identify the process

ID of a specific process.

3. End the process by typing the following kill command:

Note: You must have root user authority to use the kill command on processes you did not initiate.

kill -9 ProcessID

If you cannot identify the problem process, the most recently activated process might be the cause of

your inactive system. End the most recent process if you think that is the problem.

your process checks have not corrected the problem with your inactive system you need to restart the

system.

Related concepts

“Hardware check” on page 9

There are several procedures you can use to check your hardware.

tasks

“Restarting the system”

addition to checking the hardware and checking the processes, you can restart you system to reactivate

an inactive system.

Related information

System Dump Facility

Restarting

the system:

In addition to checking the hardware and checking the processes, you can restart you system to reactivate

an inactive system.

If the procedures for “Hardware check” on page 9 and “Checking the processes” on page 9 fail to correct

the problem that makes your system inactive, you need to restart your system.

Note: Before restarting your system, complete a system dump.

1. Check the state of the boot device.

Your system boots with either a removable medium, an external device, a small computer system

interface (SCSI) device, an integrated device electronics (IDE) device, or a local area network (LAN).

Decide which method applies to your system, and use the following instructions to check the boot

device:

v For a removable medium, such as tape, make sure the medium is inserted correctly.

v For IDE devices, verify that the IDE device ID settings are unique per adapter. If only one device is

attached to the adapter, the IDE device ID must be set to the master device.

v For an externally attached device, such as a tape drive, make sure:

– The power to the device is turned on.

– The device cables are correctly attached to the device and to the system unit.

– The ready indicator is on (if the device has one).

For external SCSI devices, verify that the SCSI address settings are unique.

v For a LAN, verify that the network is up and operable.

Operating system and device management 11

If the boot device is working correctly, continue to the next step.

2. Load your operating system by doing the following:

a. Turn off your system’s power.

b. Wait one minute.

c. Turn on your system’s power.

d. Wait for the system to boot.

the operating system failed to load, boot the hard disk from maintenance mode or hardware diagnostics.

If you are still unable to restart the system, use an SRN to report the problem with your inactive system to

your service representative.

Related concepts

“Hardware check” on page 9

There

are several procedures you can use to check your hardware.

Related tasks

“Checking the processes” on page 9

A stopped or stalled process might make your system inactive.

information

System Dump Facility

Creating boot images

To install the base operating system or to access a system that will not boot from the system hard drive,

you need a boot image. This procedure describes how to create boot images. The boot image varies for

each type of device.

When the system is first installed, the bosboot command creates a boot image from a RAM (random

access memory) disk file system image and the operating system kernel. The boot image is transferred to

a particular media such as the hard disk. When the machine is rebooted, the boot image is loaded from

the media into memory. For more information about the bosboot command, see bosboot.

The associated RAM disk file system contains device configuration routines for the following devices:

v Disk

v Tape

v CD-ROM

v Network Token-Ring, Ethernet, or FDDI device

You must have root user authority to use the bosboot command.

v The /tmp file system must have at least 20 MB of free space.

v The physical disk must contain the boot logical volume. To determine which disk device to specify, type

the following at a command prompt:

lsvg -l rootvg

The lsvg -l command lists the logical volumes on the root volume group (rootvg). From this list you can

find the name of the boot logical volume.

Then type the following at a command prompt:

lsvg -M rootvg

The lsvg -M command lists the physical disks that contain the various logical volumes.

Creating

a boot image on a boot logical volume:

12 AIX Version 6.1 Operating system and device management

剩余565页未读，继续阅读

taojianxuan

粉丝: 0
资源: 1

AIX 6.1操作系统与设备管理指南

aix 6.1小机系统镜像

AIX_5.3Operating system and device management

aix6.1安装python

aix 6.1 如何安装zabbix agent

aix cc vs gcc

aix系统如何使用命令安装curl

aix系统如何安装curl命令

aix系统安装运行库xlC13.1.3.1

aix系统卸载运行库xlC16.1.0.8，然后安装运行库xlC13.1.3.1

gdb aix6 ppc_aix.rpm

最新资源