/****************************************************************************/ /* Document : UNIX command examples, mainly based on Solaris, AIX, HP */ /* and ofcourse, also Linux. */ /* Doc. Version : 102 */ /* File : unix.txt */ /* Purpose : some usefull examples for the Oracle, DB2, SQLServer DBA */ /* Date : 10-03-2008 */ /* Compiled by : Albert van der Sel */ /* Best use : Use find/search in your editor to find a string, command, */ /* or any identifier */ /****************************************************************************/
##################################### SECTION 1. COMMANDS AND ARCHITECTURE: ##################################### ========================== 1. HOW TO GET SYSTEM INFO: ==========================
1.1 Short version: ================== See section 1.2 for more detailed commands and options. Memory: ------AIX:
Linux: HP:
bootinfo -r lsattr -E -lmem0 /usr/sbin/lsattr -E -l sys0 -a realmem or use a tool as "topas" or "nmon" (these are utilities) cat /proc/meminfo /usr/sbin/dmesg | grep "Physical" free (the free command) /usr/sam/lbin/getmem grep MemTotal /proc/meminfo /etc/dmesg | grep -i phys wc -c /dev/mem or us a tool as "glance", like entering "glance -m" from prompt (is a
utility) Solaris: /usr/sbin/prtconf | grep "Memory size" Tru64: /bin/vmstat -P | grep "Total Physical Memory" Swap: ----AIX: HP: Solaris: Linux:
/usr/sbin/lsps -a /usr/sbin/swapinfo -a /usr/sbin/swap -l /sbin/swapon -s
cat /proc/swaps cat /proc/meminfo OS version: ----------HP: Linux: Solaris: Tru64: AIX:
uname -a cat /proc/version uname -a /usr/sbin/sizer -v oslevel -r lslpp -h bos.rte
AIX firmware: lsmcode -c lsmcode -r -d scraid0 scraid0 lsmcode -A prtconf etc..
display the system firmware level and service processor display the adapter microcode levels for a RAID adapter display the microcode level for all supported devices shows many setting including memory, firmware, serial#
cpu: ---HP:
ioscan -kfnC processor getconf CPU_VERSION getconf CPU_CHIP_TYPE model
AIX:
prtconf | grep proc pmcycles -m lsattr -El procx (x is 0,2, etc..) lscfg | grep proc
Linux:
cat /proc/cpuinfo
Solaris:
psrinfo -v prtconf
Notes about lpars: -----------------For AIX: The uname -L command identifies a partition on a system with multiple LPARS. The LPAR id can be useful for writing shell scripts that customize system settings such as IP address or hostname. The output of the command looks like: # uname -L 1 lpar01 The output of uname -L varies by maintenance level. For consistent output across maintenance levels, add a -s flag. For illustrate, the following command assigns the partition number to the variable
"lpar_number" and partiton name to "lpar_name". For HP-UX: Use commands like "parstatus" or "getconf PARTITION_IDENT" to get npar information.
patches: -------AIX:
Is a certain fix (APAR) installed? instfix -ik APAR_number instfix -a -ivk APAR_number To determine your platform firmware level, at the command prompt, type: lscfg -vp | grep -p Platform
The last six digits of the ROM level represent the platform firmware date in the format, YYMMDD. HP:
/usr/sbin/swlist -l patch swlist | grep patch Linux: rpm -qa Solaris: showrev -p pkginfo -i package_name Tru64: /usr/sbin/dupatch -track -type kit Netcards: --------AIX:
lsdev -Cc adapter lsdev -Cc adapter | grep ent lsdev -Cc if lsattr -E -l ent1 ifconfig -a Solaris: prtconf -D / prtconf -pv prtdiag | grep "card" svcs -x ifconfig -a (up plumb)
/
prtconf | grep "card"
1.2 More Detail: ================ 1.2.1 Show memory in Solaris: ============================= prtconf: -------Use this command to obtain detailed system information about your Sun Solaris installation # /usr/sbin/prtconf
# prtconf -v Displays the size of the system memory and reports information about peripheral devices Use this command to see the amount of memory: # /usr/sbin/prtconf | grep "Mem" sysdef -i reports on several system resource limits. Other parameters can be checked on a running system using adb -k : # adb -k /dev/ksyms /dev/mem parameter-name/D ^D (to exit)
1.2.2 Show memory in AIX: ========================= >> Show Total memory: --------=====-------# bootinfo -r # lsattr -El sys0 -a realmem # prtconf (you can grep it on memory) >> Show Details of memory: -------------------------You can have a more detailed and comprehensive look at AIX memory by using "vmstat -v" and "vmo -L" or "vmo -a": For example: # vmstat -v 524288 493252 67384 7 131820 80.0 20.0 80.0 25.4 125727 0.0 0 25.4 80.0 125575 0 14557 6526890 18631 0 49038
memory pages lruable pages free pages memory pools pinned pages maxpin percentage minperm percentage maxperm percentage numperm percentage file pages compressed percentage compressed pages numclient percentage maxclient percentage client pages remote pageouts scheduled pending disk I/Os blocked with no pbuf paging space I/Os blocked with no psbuf filesystem I/Os blocked with no fsbuf client filesystem I/Os blocked with no fsbuf external pager filesystem I/Os blocked with no fsbuf
0 Virtualized Partition Memory Page Faults 0.00 Time resolving virtualized partition memory page faults The vmo command really gives lots of output. In the following example only a small fraction of the output is shown: # vmo -L .. lrubucket 128K 128K 128K 64K 4KB pages D -------------------------------------------------------------------------------maxclient% 80 80 80 1 100 % memory D maxperm% minperm% -------------------------------------------------------------------------------maxfree 1088 1088 1088 8 200K 4KB pages D minfree memory_frames -------------------------------------------------------------------------------maxperm 394596 394596 S -------------------------------------------------------------------------------maxperm% 80 80 80 1 100 % memory D minperm% maxclient% -------------------------------------------------------------------------------maxpin 424179 424179 S .. .. >> To further look at your virtual memory and its causes, you can use a combination of: -------------------------------------------------------------------------------------# # # # #
ipcs -bm lsps -a vmo -a or vmo -L svmon -G svmon -U
(shared memory) (paging) (virtual memory options) (basic memory allocations) (virtual memory usage by user)
To print out the memory usage statistics for the users root and steve taking into account only working segments, type: svmon -U root steve -w To print out the top 10 users of the paging space, type: svmon -U -g -t 10 To print out the memory usage statistics for the user steve, including the list of the process identifiers, type: svmon -U steve -l svmon -U emcdm -l
Note: sysdumpdev -e Although the sysdumpdev command is used to show or alter the dumpdevice for a system dump, you can also use it to show how much real memory is used. The command # sysdumpdev -e provides an estimated dump size taking into account the current memory (not pagingspace) currently in use by the system. Note: the rmss command: The rmss (Reduced-Memory System Simulator) command is used to ascertain the effects of reducing the amount of available memory on a system without the need to physically remove memory from the system. It is useful for system sizing, as you can install more memory than is required and then use rmss to reduce it. Using other performance tools, the effects of the reduced memory can be monitored. The rmss command has the ability to run a command multiple times using different simulated memory sizes and produce statistics for all of those memory sizes. The rmss command resides in /usr/bin and is part of the bos.perf.tools fileset, which is installable from the AIX base installation media. Syntax rmss -p -c -r Options -p Print the current value -c MB Change to M size (in Mbytes) -r Restore all memory to use -p Print the current value Example: find out how much memory you have online rmss -p Example: Change available memory to 256 Mbytes rmss -c 256 Example: Undo the above rmss -r Warning: rmss can damage performance very seriously Don't go below 25% of the machines memory Never forget to finish with rmss -r
1.2.3 Show memory in Linux: =========================== # /usr/sbin/dmesg | grep "Physical:" # cat /proc/meminfo
The ipcs, vmstat, iostat and that type of commands, are ofcourse more or less the same in Linux as they are in Solaris or AIX.
1.2.4 Show aioservers in AIX: ============================= # lsattr -El aio0 autoconfig available fastpath enable kprocprio 39 maxreqs 4096 maxservers 10 minservers 1
STATE to be configured at system restart State of fast path Server PRIORITY Maximum number of REQUESTS MAXIMUM number of servers per cpu MINIMUM number of servers
True True True True True True
# pstat -a | grep -c aios 20 # ps -k | grep aioserver 331962 - 0:15 aioserver 352478 - 0:14 aioserver 450644 - 0:12 aioserver 454908 - 0:10 aioserver 565292 - 0:11 aioserver 569378 - 0:10 aioserver 581660 - 0:11 aioserver 585758 - 0:17 aioserver 589856 - 0:12 aioserver 593954 - 0:15 aioserver 598052 - 0:17 aioserver 602150 - 0:12 aioserver 606248 - 0:13 aioserver 827642 - 0:14 aioserver 991288 - 0:14 aioserver 995388 - 0:11 aioserver 1007616 - 0:12 aioserver 1011766 - 0:13 aioserver 1028096 - 0:13 aioserver 1032212 - 0:13 aioserver What are aioservers in AIX5?: With IO on filesystems, for example if a database is involved, you may try to tune the number of aioservers (asynchronous IO) AIX 5L supports asynchronous I/O (AIO) for database files created both on file system partitions and on raw devices. AIO on raw devices is implemented fully into the AIX kernel, and does not require database processes to service the AIO requests. When using AIO on file systems, the kernel database processes (aioserver) control each request from the time a request is taken off the queue until it completes. The kernel database processes are also used with I/O with virtual shared disks (VSDs) and HSDs with
FastPath disabled. By default, FastPath is enabled. The number of aioserver servers determines the number of AIO requests that can be executed in the system concurrently, so it is important to tune the number of aioserver processes when using file systems to store Oracle Database data files. - Use one of the following commands to set the number of servers. This applies only when using asynchronous I/O on file systems rather than raw devices: # smit aio # chdev -P -l aio0 -a maxservers='128' -a minservers='20' - To set asynchronous IO to �Available�: # chdev -l aio0 -P -a autoconfig=available You need to restart the Server: # shutdown -Fr 1.2.5 aio on Linux distro's: ============================ On some Linux distro's, Oracle 9i/10g supports asynchronous I/O but it is disabled by default because some Linux distributions do not have libaio by default. For Solaris, the following configuration is not required - skip down to the section on enabling asynchronous I/O. On Linux, the Oracle binary needs to be relinked to enable asynchronous I/O. The first thing to do is shutdown the Oracle server. After Oracle has shutdown, do the following steps to relink the binary: su - oracle cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk async_on make -f ins_rdbms.mk ioracle
1.2.6 The ipcs and ipcrm commands: ================================== The "ipcs" command is really a "listing" command. But if you need to intervene in memory structures, like for example if you need to "clear" or remove a shared memory segment, because a faulty or crashed application left semaphores, memory identifiers, or queues in place, you can use to "ipcrm" command to remove those structures. Example ipcrm command usage: ---------------------------Suppose an application crashed, but it cannot be started again. The following might help,
if you happened to know which IPC identifier it used. Suppose the app used 47500 as the IPC key. Calcultate this decimal number to hex which is, in this example, B98C. No do the following: # ipcs -bm | grep B89C This might give you, for example, the shared memory identifier "50855977". Now clear the segment: # ipcrm -m 50855977 It might also be, that still a semaphore and/or queue is still "left over". In that case you might also try commands like the following example: ipcs -q ipcs -s # ipcrm -s 2228248 # ipcrm -q 5111883
(remove semaphore) (remove queue)
Note: in some cases the "slibclean" command can be used to clear unused modules in kernel and library memory. Just give as root the command: # slibclean Other Example: -------------If you run the following command to remove a shared memory segment and you get this error: # ipcrm -m 65537 ipcrm: 0515-020 shmid(65537) was not found. However, if you run the ipcs command, you still see the segment there: # ipcs | grep 65537 m 65537 0x00000000 DCrw------- root system If you look carefully, you will notice the "D" in the forth column. The "D" means: D If the associated shared memory segment has been removed. It disappears when the last process attached to the segment detaches it. So, to clear the shared memory segment, find the process which is still associated with the segment: # ps -ef | grep process_owner where process_owner is the name of the owner using the shared segment Now kill the process found from the ps command above
# kill -9 pid Running another ipcs command will show the shared memory segment no longer exists: # ipcs | grep 65537 Example ipcrm -m 65537
1.2.7 Show patches, version, systeminfo: ======================================== Solaris: ======== showrev: -------#showrev Displays system summary information. #showrev -p Reports which patches are installed sysdef and dmesg: ----------------The follwing commands also displays configuration information # sysdef # dmesg versions: --------==> To check your Solaris version: # uname -a or uname -m # cat /etc/release # isainfo -v ==> To check your AIX version: # oslevel # oslevel -r
tells you which maintenance level you have.
>> To find the known recommended maintenance levels: # oslevel -rq >> To find all filesets lower than a certain maintenance level: # oslevel -rl 5200-06 >> To find all filesets higher than a certain maintenance level: # oslevel -rg 5200-05 >> To list all known recommended maintenance and technology levels on the system,
type: # oslevel -q -s Known Service Packs ------------------5300-05-04 5300-05-03 5300-05-02 5300-05-01 5300-05-00 5300-04-CSP 5300-04-03 5300-04-02 5300-04-01 5300-03-CSP >> How can I determine which fileset updates are missing from a particular AIX level? To determine which fileset updates are missing from 5300-04, for example, run the following command: # oslevel -rl 5300-04 >> What SP (Service Pack) is installed on my system? To see which SP is currently installed on the system, run the oslevel -s command. Sample output for an AIX 5L Version 5.3 system, with TL4, and SP2 installed would be: # oslevel �s 5300-04-02 >> Is a CSP (Concluding Service Pack) installed on my system? To see if a CSP is currently installed on the system, run the oslevel -s command. Sample output for an AIX 5L Version 5.3 system, with TL3, and CSP installed would be: # oslevel �s 5300-03-CSP
==> To check your HP machine: # model 9000/800/rp7410 : machine info on AIX How do I find out the Chip type, System name, Node name, Model Number etc.? The uname command provides details about your system. uname -p type of the system. For example, powerpc. uname -r uname -s
Displays the release number of the operating system. Displays the system name. For example, AIX.
Displays the chip
uname uname uname uname uname uname
-n -a -M -v -m -u
Displays Displays Displays Displays Displays Displays
the the the the the the
name of the node. system name, nodename,Version, Machine id. system model name. For example, IBM, 7046-B50. operating system version machine ID number of the hardware running the system. system ID number.
Architecture: ------------To see if you have a CHRP machine, log into the machine as the root user, and run the following command: # lscfg | grep Architecture # lscfg -pl sysplanar0 | more
or use:
The bootinfo -p command also shows the architecture of the pSeries, RS/6000 # bootinfo -p chrp 1.2.8 Check whether you have a 32 bit or 64 bit version: ======================================================== - Solaris: # iasinfo -vk If /usr/bin/isainfo cannot be found, then the OS only supports 32-bit process address spaces. (Solaris 7 was the first version that could run 64-bit binaries on certain SPARC-based systems.) So a ksh-based test might look something like if [ -x /usr/bin/isainfo ]; then bits=`/usr/bin/isainfo -b` else bits=32 fi - AIX: Command: committed. -orsuch as: /bin/locale64: 32-bit machine.
/bin/lslpp -l bos.64bit
...to see if bos.64bit is installed &
/bin/locale64
...error message if on 32bit machine Could not load program Cannot run a 64-bit program on a
Or use: # bootinfo -K # bootinfo -y # bootinfo -p the
displays the current kernel wordsize of "32" or "64" tells if hardware is 64-bit capable If it returns the string 32 it is only capable of running
Or use:
32-bit kernel. If it returns the string chrp the machine is capable of running the 64-bit kernel or the 32-bit kernel.
# /usr/bin/getconf HARDWARE_BITMODE This command should return the following output: 64
Note: ----HOW TO CHANGE KERNEL MODE OF IBM AIX 5L (5.1) --------------------------------------------The AIX 5L has pre-configured kernels. These are listed below for Power processors: /usr/lib/boot/unix_up /usr/lib/boot/unix_mp /usr/lib/boot/unix_64
32 bit uni-processor 32 bit multi-processor kernel 64 bit multi-processor kernel
Switching between kernel modes means using different kernels. This is simply done by pointing the location that is referenced by the system to these kernels. Use symbolic links for this purpose. During boot AIX system runs the kernel in the following locations: /unix /usr/lib/boot/unix The base operating system 64-bit runtime fileset is bos.64bit. Installing bos.64bit also installs the /etc/methods/cfg64 file. The /etc/methods/cfg64 file provides the option of enabling or disabling the 64-bit environment via SMIT, which updates the /etc/inittab file with the load64bit line. (Simply adding the load64bit line does not enable the 64-bit environment). The command lslpp -l bos.64bit reveals if this fileset is installed. The bos.64bit fileset is on the AIX media; however, installing the bos.64bit fileset does not ensure that you will be able to run 64-bit software. If the bos.64bit fileset is installed on 32-bit hardware, you should be able to compile 64-bit software, but you cannot run 64-bit programs on 32-bit hardware. The syscalls64 extension must be loaded in order to run a 64-bit executable. This is done from the load64bit entry in the inittab file. You must load the syscalls64 extension even when running a 64-bit kernel on 64-bit hardware. To determine if the 64-bit kernel extension is loaded, at the command line, enter genkex |grep 64.
Information similar to the following displays: 149bf58 a3ec /usr/lib/drivers/syscalls64.ext To change the kernel mode follow steps below: 1. Create of the 2. Create 3. Reboot
symbolic link from /unix and /usr/lib/boot/unix to the location desired kernel. boot image. AIX.
Below lists the detailed actions to change kernel mode: To change to 32 bit uni-processor mode: # # # #
ln -sf /usr/lib/boot/unix_up ln -sf /usr/lib/boot/unix_up bosboot -ad /dev/ipldevice shutdown -r
/unix /usr/lib/boot/unix
To change to 32 bit multi-processor mode: # # # #
ln -sf /usr/lib/boot/unix_mp ln -sf /usr/lib/boot/unix_mp bosboot -ad /dev/ipldevice shutdown -r
/unix /usr/lib/boot/unix
To change to 64 bit multi-processor mode: # # # #
ln -sf /usr/lib/boot/unix_64 ln -sf /usr/lib/boot/unix_64 bosboot -ad /dev/ipldevice shutdown -r
/unix /usr/lib/boot/unix
IMPORTANT NOTE: If you are changing the kernel mode to 32-bit and you will run 9.2 on this server, the following line should be included in /etc/inittab: load64bit:2:wait:/etc/methods/cfg64 >/dev/console 2>&1 # Enable 64-bit execs This allows 64-bit applications to run on the 32-bit kernel. Note that this line is also mandatory if you are using the 64-bit kernel. In AIX 5.2, the 32-bit kernel is installed by default. The 64-bit kernel, along with JFS2 (enhanced journaled file system), can be enabled at installation time. Checking if other unixes are in 32 or 64 mode: ---------------------------------------------- Digital UNIX/Tru64:
This OS is only available in 64bit form.
- HP-UX(Available in 64bit starting with HP-UX 11.0): Command: /bin/getconf KERNEL_BITS ...returns either 32 or 64 - SGI:
This OS is only available in 64bit form.
- The remaining supported UNIX platforms are only available in 32bit form. scinstall: ---------# scinstall -pv Displays Sun Cluster software release and package version information 1.2.9 Info about CPUs: ====================== Solaris: -------# psrinfo -v Shows the number of processors and their status. # psrinfo -v|grep "Status of processor"|wc -l Shows number of cpu's Linux: -----# cat /proc/cpuinfo # cat /proc/cpuinfo | grep processor|wc �l Especially with Linux, the /proc directory contains special "files" that either extract information from or send information to the kernel HP-UX: -----# # # #
ioscan -kfnC processor /usr/sbin/ioscan -kf | grep processor grep processor /var/adm/syslog/syslog.log /usr/contrib/bin/machinfo (Itanium)
Several ways as, 1. 2. 3. 4. 5. 6.
sam -> performance monitor -> processor print_manifest (if ignite-ux installed) machinfo (11.23 HP versions) ioscan -fnC processor echo "processor_count/D" | adb /stand/vmunix /dev/kmem top command to get cpu count
The "getconf" command can give you a lot of interesting info. The parameters are: ARG_MAX BS_SCALE_MAX CHAR_BIT CHILD_MAX CPU_CHIP_TYPE CS_PATH HW_CPU_SUPP_BITS
_BC_BASE_MAX BC_STRING_MAX CHAR_MAX CLK_TCK CS_MACHINE_IDENT CS_MACHINE_SERIAL HW_32_64_CAPABLE
BC_DIM_MAX CHARCLASS_NAME_MAX CHAR_MIN COLL_WEIGHTS_MAX CS_PARTITION_IDENT EXPR_NEST_MAX INT_MAX
INT_MIN LONG_BIT MACHINE_IDENT MB_LEN_MAX NL_LANGMAX NL_SETMAX OPEN_MAX _POSIX_ARG_MAX _POSIX_OPEN_MAX _POSIX_STREAM_MAX POSIX_ARG_MAX POSIX_LINK_MAX POSIX_NAME_MAX POSIX_PATH_MAX POSIX_SSIZE_MAX POSIX_VERSION POSIX2_BC_SCALE_MAX POSIX2_C_DEV POSIX_CHILD_MAX POSIX2_FORT_DEV POSIX2_LOCALEDEF POSIX2_UPE SC_XOPEN_VERSION SHRT_MAX
KERNEL_BITS LONG_MAX MACHINE_MODEL NGROUPS_MAX NL_MSGMAX NL_TEXTMAX PARTITION_IDENT _POSIX_JOB_CONTROL _POSIX_SAVED_IDS _POSIX_TZNAME_MAX POSIX_CHILD_MAX POSIX_MAX_CANON POSIX_NGROUPS_MAX POSIX_PIPE_BUF POSIX_STREAM_MAX POSIX2_BC_BASE_MAX POSIX2_BC_STRING_MAX POSIX2_C_VERSION POSIX2_COLL_WEIGHTS_MAX POSIX2_FORT_RUN POSIX2_RE_DUP_MAX POSIX2_VERSION SCHAR_MAX SHRT_MIN
Example: # getconf CPU_VERSION sample function in shell script: get_cpu_version() { case `getconf CPU_VERSION` in # ???) echo "Itanium[TM] 2" ;; 768) echo "Itanium[TM] 1" ;; 532) echo "PA-RISC 2.0" ;; 529) echo "PA-RISC 1.2" ;; 528) echo "PA-RISC 1.1" ;; 523) echo "PA-RISC 1.0" ;; *) return 1 ;; esac return 0
AIX: ---# pmcycles Cpu 0 runs Cpu 1 runs Cpu 2 runs Cpu 3 runs
-m at at at at
1656 1656 1656 1656
MHz MHz MHz MHz
LINE_MAX LONG_MIN MACHINE_SERIAL NL_ARGMAX NL_NMAX NZERO PATH _POSIX_NGROUPS_MAX _POSIX_SSIZE_MAX _POSIX_VERSION POSIX_JOB_CONTROL POSIX_MAX_INPUT POSIX_OPEN_MAX POSIX_SAVED_IDS POSIX_TZNAME_MAX POSIX2_BC_DIM_MAX POSIX2_C_BIND POSIX2_CHAR_TERM POSIX2_EXPR_NEST_MAX POSIX2_LINE_MAX POSIX2_SW_DEV SC_PASS_MAX SCHAR_MIN SSIZE_MAX
# lscfg | grep proc More cpu information on AIX: # lsattr -El procx (where x is the number of the cpu) type powerPC_POWER5 Processor type False frequency 165600000 Processor speed False .. .. where False means that the value cannot be changed through an AIX command. To view CPU scheduler tunable parameters, use the schedo command: # schedo -a In AIX 5L on Power5, you can switch from Simultaneous Multithreading SMT, or Single Threading ST, as follows (smtcl) # smtctl -m off will set SMT mode to disabled # smtctl -m on will set SMT mode to enabled # smtctl -W boot makes SMT effective on next boot # smtctl -W now effects SMT now, but will not persist across reboots When you want to keep the setting across reboots, you must use the bosboot command in order to create a new boot image. 1.2.10 Other stuff: =================== runlevel: --------To show the init runlevel: # who -r Top users: ---------To get a quick impression about the top 10 users in the system at this time: ps auxw | sort �r +3 |head �10 ps auxw | sort �r +2 |head �10
-Shows top 10 memory usage by process -Shows top 10 CPU usage by process
shared memory: -------------To check shared memory segment, semaphore array, and message queue limits, issue the ipcs -l command. # ipcs The following tools are available for monitoring the performance of your UNIXbased system. pfiles: ------/usr/proc/bin/pfiles This shows the open files for this process, which helps you diagnose whether you
are having problems caused by files not getting closed. lsof: ----This utility lists open files for running UNIX processes, like pfiles. However, lsof gives more useful information than pfiles. You can find lsof at ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/. Example of lsof usage: You can see CIO (concurrent IO) in the FILE-FLAG column if you run lsof +fg, e.g.: tarunx01:/home/abielewi:# /p570build/LSOF/lsof-4.76/usr/local/bin/lsof +fg /baanprd/oradat COMMAND PID USER FD TYPE FILE-FLAG DEVICE SIZE/OFF NODE NAME oracle 434222 oracle 16u VREG R,W,CIO,DSYN,LG;CX 39,1 6701056 866 /baanprd/oradat (/dev/bprdoradat) oracle 434222 oracle 17u VREG R,W,CIO,DSYN,LG;CX 39,1 6701056 867 /baanprd/oradat (/dev/bprdoradat) oracle 442384 oracle 15u VREG R,W,CIO,DSYN,LG;CX 39,1 1174413312 875 /baanprd/oradat (/dev/bprdoradat) oracle 442384 oracle 16u VREG R,W,CIO,DSYN,LG;CX 39,1 734011392 877 /baanprd/oradat (/dev/bprdoradat) oracle 450814 oracle 15u VREG R,W,CIO,DSYN,LG;CX 39,1 1174413312 875 /baanprd/oradat (/dev/bprdoradat) oracle 450814 oracle 16u VREG R,W,CIO,DSYN,LG;CX 39,1 1814044672 876 /baanprd/oradat (/dev/bprdoradat) oracle 487666 oracle 15u VREG R,W,CIO,DSYN,LG;CX 39,1 1174413312 875 /baanprd/oradat (/dev/bprdoradat You should also see O_CIO in your file open calls if you run truss, e.g.: open("/opt/oracle/rcat/oradat/redo01.log", O_RDWR|O_CIO|O_DSYNC|O_LARGEFILE) = 18
VMSTAT SOLARIS: --------------# vmstat This command is ideal for monitoring paging rate, which can be found under the page in (pi) and page out (po) columns. Other important columns are the amount of allocated virtual storage (avm) and free virtual storage (fre). This command is useful for determining if something is suspended or just taking a long time. Example: kthr r b w
memory swap free
re
page disk mf pi po fr de sr m0 m1 m3 m4
faults sy
in
cpu cs us sy id
0 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 0 0 0 0
2163152 2119080 2118960 2112992 2112088 2116288 2117744
1716720 1729352 1729232 1723264 1722352 1726544 1727960
157 141 1179 1 0 1 0 0 0 0 167 0 0 0 0 1261 0 0 0 0 248 0 0 0 4 80 0 0 0 4 2 30 0 0
1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 0 0 0 0
0 1 0 0 0 0 0
0 680 1737 855 10 0 345 658 346 1 0 402 1710 812 4 0 1026 5253 1848 10 0 505 2822 1177 5 0 817 4015 1530 6 0 473 1421 640 2
3 1 2 5 2 4 2
87 98 94 85 92 90 97
procs/r: Run queue length. procs/b: Processes blocked while waiting for I/O. procs/w: Idle processes which have been swapped. memory/swap: Free, unreserved swap space (Kb). memory/free: Free memory (Kb). (Note that this will grow until it reaches lotsfree, at which point the page scanner is started. See "Paging" for more details.) page/re: Pages reclaimed from the free list. (If a page on the free list still contains data needed for a new request, it can be remapped.) page/mf: Minor faults (page in memory, but not mapped). (If the page is still in memory, a minor fault remaps the page. It is comparable to the vflts value reported by sar -p.) page/pi: Paged in from swap (Kb/s). (When a page is brought back from the swap device, the process will stop execution and wait. This may affect performance.) page/po: Paged out to swap (Kb/s). (The page has been written and freed. This can be the result of activity by the pageout scanner, a file close, or fsflush.) page/fr: Freed or destroyed (Kb/s). (This column reports the activity of the page scanner.) page/de: Freed after writes (Kb/s). (These pages have been freed due to a pageout.) page/sr: Scan rate (pages). Note that this number is not reported as a "rate," but as a total number of pages scanned. disk/s#: Disk activity for disk # (I/O's per second). faults/in: Interrupts (per second). faults/sy: System calls (per second). faults/cs: Context switches (per second). cpu/us: User CPU time (%). cpu/sy: Kernel CPU time (%). cpu/id: Idle + I/O wait CPU time (%). When analyzing vmstat output, there are several metrics to which you should pay attention. For example, keep an eye on the CPU run queue column. The run queue should never exceed the number of CPUs on the server. If you do notice the run queue exceeding the amount of CPUs, it�s a good indication that your server has a CPU bottleneck. To get an idea of the RAM usage on your server, watch the page in (pi) and page out (po) columns of vmstat�s output. By tracking common virtual memory operations such as page outs, you can infer the times that the Oracle database is performing a lot of work. Even though UNIX page ins must correlate with the vmstat�s refresh rate to accurately predict RAM swapping, plotting page ins can tell you
when the server is having spikes of RAM usage. Once captured, it's very easy to take the information about server performance directly from the Oracle tables and plot them in a trend graph. Rather than using an expensive statistical package such as SAS, you can use Microsoft Excel. Copy and paste the data from the tables into Excel. After that, you can use the Chart Wizard to create a line chart that will help you view server usage information and discover trends. # VMSTAT AIX: ------------This is virtually equal to the usage of vmstat under solaris. vmstat can be used to give multiple statistics on the system. For CPU-specific work, try the following command: # vmstat -t 1 3 This will take 3 samples, 1 second apart, with timestamps (-t). You can, of course, change the parameters as you like. The output is shown below. kthr ----r b 0 0 0 0 2 0
memory page faults cpu time ----------- ------------------------ ------------ ----------- -------avm fre re pi po fr sr cy in sy cs us sy id wa hr mi se 45483 221 0 0 0 0 1 0 224 326 362 24 7 69 0 15:10:22 45483 220 0 0 0 0 0 0 159 83 53 1 1 98 0 15:10:23 45483 220 0 0 0 0 0 0 145 115 46 0 9 90 1 15:10:24
In this output some of the things to watch for are: "avm", which is Active Virtual Memory. Ideally, under normal conditions, the largest avm value should in general be smaller than the amount of RAM. If avm is smaller than RAM, and still exessive paging occurs, that could be due to RAM being filled with file pages. avm x 4K = number of bytes Columns r (run queue) and b (blocked) start going up, especially above 10. This usually is an indication that you have too many processes competing for CPU. If cs (contact switches) go very high compared to the number of processes, then you may need to tune the system with vmtune. In the cpu section, us (user time) indicates the time is being spent in programs. Assuming Java is at the top of the list in tprof, then you need to tune the Java application).
In the cpu section, if sys (system time) is higher than expected, and you still have id (idle) time left, this may indicate lock contention. Check the tprof for lock related calls in the kernel time. You may want to try multiple instances of the JVM. It may also be possible to find deadlocks in a javacore file. In the cpu section, if wa (I/O wait) is high, this may indicate a disk bottleneck, and you should use iostat and other tools to look at the disk usage. Values in the pi, po (page in/out) columns paging and need more memory. It may be possible that you have the stack instances. It could also mean that you have allocated on the system. Of course, you may also have other applications using taking up too much of the memory
are non-zero may indicate that you are size set too high for some of your JVM a heap larger than the amount of memory memory, or that file pages may be
Other example: -------------# vmstat 1 System configuration: lcpu=2 mem=3920MB kthr ----r b 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
memory ----------avm fre 229367 332745 229367 332745 229367 332745 229367 332745 229367 332745 229367 332745 229367 332745 229367 332745 229367 332745 229367 332745 229367 332745
page faults cpu ------------------------ ------------ ----------re pi po fr sr cy in sy cs us sy id wa 0 0 0 0 0 0 3 198 69 0 0 99 0 0 0 0 0 0 0 3 33 66 0 0 99 0 0 0 0 0 0 0 2 33 68 0 0 99 0 0 0 0 0 0 0 80 306 100 0 1 97 1 0 0 0 0 0 0 1 20 68 0 0 99 0 0 0 0 0 0 0 2 36 64 0 0 99 0 0 0 0 0 0 0 2 33 66 0 0 99 0 0 0 0 0 0 0 2 21 66 0 0 99 0 0 0 0 0 0 0 1 237 64 0 0 99 0 0 0 0 0 0 0 2 19 66 0 0 99 0 0 0 0 0 0 0 6 37 76 0 0 99 0
The most important fields to look at here are: r -- The average number of runnable kernel threads over whatever sampling interval you have chosen. b -- The average number of kernel threads that are in the virtual memory waiting queue over your sampling interval. r should always be higher than b; if it is not, it usually means you have a CPU bottleneck. fre -- The size of your memory free list. Do not worry so much if the amount is really small. More importantly, determine if there is any paging going on if this amount is small. pi -- Pages paged in from paging space. po -- Pages paged out to paging space.
CPU section: us sy id wa Let's look at the last section, which also comes up in most other CPU monitoring tools, albeit with different headings: us sy id wa
-----
user time system time idle time waiting on I/O
# IOSTAT: --------This command is useful for monitoring I/O activities. You can use the read and write rate to estimate the amount of time required for certain SQL operations (if they are the only activity on the system). This command is also useful for determining if something is suspended or just taking a long time. Basic synctax is iostat
interval
count
option - let you specify the device for which information is needed like disk , cpu or terminal. (-d , -c , -t or -tdc ) . x options gives the extended statistics . interval - is time period in seconds between two samples . iostat data at each 4 seconds interval. count - is the number of times the data is needed . 4 seconds interval 5 times.
4
will give
iostat 4 5 will give data at
Example: $ iostat -xtc 5 2 disk r/s sd0 2.6 sd1 4.2 sd2 0.0 sd3 10.2 disk r/s w/s Kr/s Kw/s wait actv %w empty) %b
w/s 3.0 1.0 0.0 1.6
extended disk statistics Kr/s Kw/s wait actv svc_t %w %b 20.7 22.7 0.1 0.2 59.2 6 19 33.5 8.0 0.0 0.2 47.2 2 23 0.0 0.0 0.0 0.0 0.0 0 0 51.4 12.8 0.1 0.3 31.2 3 31
tty cpu tin tout us sy wt id 0 84 3 85 11 0
name of the disk reads per second writes per second kilobytes read per second kilobytes written per second average number of transactions waiting for service (Q length) average number of transactions actively being serviced (removed from the queue but not yet completed) percent of time there are transactions waiting for service (queue nonpercent of time the disk is busy
(transactions in progress)
The values to look from the iostat output
are:
Reads/writes per second (r/s , w/s) Percentage busy (%b) Service time (svc_t) If a disk shows consistently high reads/writes along with , the percentage busy (%b) of the disks is greater than 5 percent, and the average service time (svc_t) is greater than 30 milliseconds, then action needs to be taken. # netstat This command lets you know the network traffic on each node, and the number of error packets encountered. It is useful for isolating network problems. Example: To find out all listening services, you can use the command # netstat -a -f inet
1.2.11 Some other utilities for Solaris: ======================================== # top For example: load averages: 0.66, 0.54, 0.56 11:14:48 187 processes: 185 sleeping, 2 on cpu CPU states: % idle, % user, % kernel, % iowait, Memory: 4096M real, 1984M free, 1902M swap in use, 2038M swap free PID 2795 2294 13907 14138 2797 2787 2799 2743 2011 2007 2009 2804 2013 2035 114
USERNAME THR PRI NICE SIZE RES STATE oraclown 1 59 0 265M 226M sleep root 11 59 0 8616K 7672K sleep oraclown 11 59 0 271M 218M cpu2 oraclown 12 59 0 270M 230M sleep oraclown 1 59 0 189M 151M sleep oraclown 11 59 0 191M 153M sleep oraclown 1 59 0 190M 151M sleep oraclown 11 59 0 191M 155M sleep oraclown 11 59 0 191M 149M sleep oraclown 11 59 0 191M 149M sleep oraclown 11 59 0 191M 149M sleep oraclown 1 51 0 1760K 1296K cpu2 oraclown 11 59 0 191M 148M sleep oraclown 11 59 0 191M 149M sleep root 10 59 0 5016K 4176K sleep
TIME 0:13 10:54 4:02 9:03 0:01 0:06 0:02 0:25 2:50 2:22 1:54 0:00 0:36 2:44 23:34
CPU 4.38% 3.94% 2.23% 1.76% 0.96% 0.69% 0.45% 0.35% 0.27% 0.26% 0.20% 0.19% 0.14% 0.13% 0.05%
% swap
COMMAND oracle bpbkar oracle oracle oracle oracle oracle oracle oracle oracle oracle top oracle oracle picld
Process ID This column shows the process ID (pid) of each process. The process ID is a positive number,
usually less than 65536. It is used for identification during the life of the process. Once a process has exited or been killed, the process ID can be reused. Username This column shows the name of the user who owns the process. The kernel stores this information as a uid, and top uses an appropriate table (/etc/passwd, NIS, or NIS+) to translate this uid in to a name. Threads This column displays the number of threads for the current process. This column is present only in the Solaris 2 port of top. For Solaris, this number is actually the number of lightweight processes (lwps) created by the threads package to handle the threads. Depending on current resource utilization, there may not be one lwp for every thread. Thus this number is actually less than or equal to the total number of threads created by the process. Nice This column reflects the "nice" setting of each process. A process's nice is inhereted from its parent. Most user processes run at a nice of 0, indicating normal priority. Users have the option of starting a process with a positive nice value to allow the system to reduce the priority given to that process. This is normally done for long-running cpu-bound jobs to keep them from interfering with interactive processes. The Unix command "nice" controls setting this value. Only root can set a nice value lower than the current value. Nice values can be negative. On most systems they range from -20 to 20. The nice value influences the priority value calculated by the Unix scheduler. Size This column shows the total amount of memory allocated by each process. This is virtual memory and is the sum total of the process's text area (program space), data area, and dynamically allocated area (or "break"). When a process allocates additional memory with the system call "brk", this value will increase. This is done indirectly by the C library function "malloc". The number in this column does not reflect the amount of physical memory currently in use by the process. Resident Memory This column reflects the amount of physical memory currently allocated to each process. This is also known as the "resident set size" or RSS. A process can have a large amount of virtual memory allocated (as indicated by the SIZE column) but still be using very little physical memory. Process State
This column reflects the last observed state of each process. State names vary from system to system. These states are analagous to those that appear in the process states line: the second line of the display. The more common state names are listed below. cpu - Assigned to a CPU and currently running run - Currently able to run sleep - Awaiting an external event, such as input from a device stop - Stopped by a signal, as with control Z swap - Virtual address space swapped out to disk zomb - Exited, but parent has not called "wait" to receive the exit status CPU Time This column displayes the accumulated CPU time for each process. This is the amount of time that any cpu in the system has spent actually running this process. The standard format shows two digits indicating minutes, a colon, then two digits indicating seconds. For example, the display "15:32" indicates fifteen minutes and thirty-two seconds. When a time value is greater than or equal to 1000 minutes, it is displayed as hours with the suffix H. For example, the display "127.4H" indicates 127 hours plus four tenths of an hour (24 minutes). When the number of hours exceeds 999.9, the "H" suffix is dropped so that the display continues to fit in the column. CPU Percentage This column shows the percentage of the cpu that each process is currently consuming. By default, top will sort this column of the output. Some versions of Unix will track cpu percentages in the kernel, as the figure is used in the calculation of a process's priority. On those versions, top will use the figure as calculated by the kernel. Other versions of Unix do not perform this calculation, and top must determine the percentage explicity by monitoring the changes in cpu time. On most multiprocessor machines, the number displayed in this column is a percentage of the total available cpu capacity. Therefore, a single threaded process running on a four processor system will never use more than 25% of the available cpu cycles. Command This column displays the name of the executable image that each process is running. In most cases this is the base name of the file that was invoked with the most recent kernel "exec" call. On most systems, this name is maintained separately from the zeroth argument. A program that changes its zeroth argument will not affect the output of this column.
# modinfo The modinfo command provides information about the modules currently loaded by the
kernel. The /etc/system file: Available for Solaris Operating Environment, the /etc/system file contains definitions for kernel configuration limits such as the maximum number of users allowed on the system at a time, the maximum number of processes per user, and the inter-process communication (IPC) limits on size and number of resources. These limits are important because they affect DB2 performance on a Solaris Operating Environment machine. See the Quick Beginnings information for further details. # more /etc/path_to_inst To see the mapping between the kernel abbreviated instance name for physical device names, view the /etc/path_to_inst file. # uptime uptime - show how long the system has been up /export/home/oraclown>uptime 11:32am up 4:19, 1 user,
load average: 0.40, 1.17, 0.90
1.2.12 Wellknown tools for AIX: =============================== 1. commands: -----------CPU Memory Subsystem I/O Subsystem Network Subsystem --------------------------------------------------------------------------------vmstat vmstat iostat netstat iostat lsps vmstat ifconfig ps svmon lsps tcpdump sar filemon filemon tprof ipcs lvmstat nmon and topas can be used to monitor those subsystems in general. 2. topas: --------topas is a useful graphical interface that will give you immediate results of what is going on in the system. When you run it without any command-line arguments, the screen looks like this: Topas Monitor for host: Mon Apr 16 16:16:50 2001 Kernel User Wait Idle
63.1 36.8 0.0 0.0
aix4prt Interval:
|################## |########## | |
2 | | | |
EVENTS/QUEUES Cswitch 5984 Syscall 15776 Reads 8 Writes 2469 Forks 0 Execs 0 Runqueue 11.5
FILE/TTY Readch Writech Rawin Ttyout Igets Namei Dirblk
4864 34280 0 0 0 4 0
Network KBPS lo0 213.9 tr0 34.7 Disk hdisk0
I-Pack 2154.2 16.9
Busy% 0.0
Name java java lrud aixterm topas ksh gil
KBPS 0.0
O-Pack 2153.7 34.4
KB-In 107.0 0.9
KB-Out 106.9 33.8
TPS KB-Read KB-Writ 0.0 0.0 0.0
PID CPU% PgSp Owner 16684 83.6 35.1 root 12192 12.7 86.2 root 1032 2.7 0.0 root 19502 0.5 0.7 root 6908 0.5 0.8 root 18148 0.0 0.7 root 1806 0.0 0.0 root
Waitqueue PAGING Faults Steals PgspIn PgspOut PageIn PageOut Sios
0.0 3862 1580 0 0 0 0 0
NFS (calls/sec) ServerV2 0 ClientV2 0 ServerV3 0
MEMORY Real,MB % Comp % Noncomp % Client
1023 27.0 73.9 0.5
PAGING SPACE Size,MB 512 % Used 1.2 % Free 98.7 Press: "h" for help
The information on the bottom left side shows the most active processes; here, java is consuming 83.6% of CPU. The middle right area shows the total physical memory (1 GB in this case) and Paging space (512 MB), as well as the amount being used. So you get an excellent overview of what the system is doing in a single screen, and then you can select the areas to concentrate based on the information being shown here. Note: about waits: -----------------Don't get caught up in this whole wait i/o thing. a single cpu system with 1 i/o outstanding and no other runable threads (i.e. idle) will have 100% wait i/o. There was a big discussion a couple of years ago on removing the kernel tick as it has confused many many many techs. So, if you have only 1 or few cpu, then you are going to have high wait i.o figures, it does not neccessarily mean your disk subsystem is slow.
3. trace: --------trace captures a sequential flow of time-stamped system events. The trace is a valuable tool for observing system and application execution. While many of the other tools provide high level statistics such as CPU and I/O utilization, the trace facility helps expand the information as to where the events happened, which process is responsible, when the events took place, and how they are affecting the system. Two post processing tools that can extract information from the trace are utld (in AIX 4) and curt (in AIX 5). These provide statistics on CPU utilization and process/thread activity. The third post processing tool is splat which stands for Simple Performance Lock Analysis Tool. This tool is used to analyze lock activity in the AIX kernel and kernel extension for simple locks.
4. nmon: -------nmon is a free software tool that gives much of the same information as topas, but saves the information to a file in Lotus 123 and Excel format. The download site is http://www.ibm.com/developerworks/eserver/articles/analyze_aix/. The information that is collected included CPU, disk, network, adapter statistics, kernel counters, memory and the "top" process information. 5. tprof: --------tprof is one of the AIX legacy tools that provides a detailed profile of CPU usage for every AIX process ID and name. It has been completely rewritten for AIX 5.2, and the example below uses the AIX 5.1 syntax. You should refer to AIX 5.2 Performance Tools update: Part 3 for the new syntax. The simplest way to invoke this command is to use: # tprof -kse -x "sleep 10" # tprof -ske -x "sleep 30" At the end of ten seconds, or 30 seconds, a new file __prof.all, or sleep.prof, is generated that contains information about what commands are using CPU on the system. Searching for FREQ, the information looks something like the example below:
...
Process ======= oracle java wait
FREQ === 244 247 16
Total Kernel ===== ====== 10635 3515 3970 617 1515 1515
User Shared ==== ====== 6897 223 0 2062 0 0
Other ===== 0 1291 0
======= Total
=== 1060
===== ====== 19577 7947
==== ====== 7252 3087
===== 1291
This example shows that over half the CPU time is associated with the oracle application and that Java is using about 3970/19577 or 1/5 of the CPU. The wait usually means idle time, but can also include the I/O wait portion of the CPU usage. svmon: -----The svmon command captures a snapshot of the current state om memory. use it with the -G switch to get global statistics for the whole system.
svmon is the most useful tool at your disposal when monitoring a Java process, especially native heap. The article "When segments collide" gives examples of how to use svmon -P -m to monitor the native heap of a Java process on AIX. But there is another variation, svmon -P -m -r, that is very effective in identifying native heap fragmentation. The -r switch prints the address range in use, so it gives a more accurate view of how much of each segment is in use. As an example, look at the partially edited output below: Pid Command 10556 java
Inuse 681613
Vsid 22ac4 21047 126a2 7908c b2ad6 b1475 30fe5 91072 6bced b1035
Esid 9 8 a 7 b -
e0f9f 19100 c965a 7910c
5 3 4 6
e801d
d
a0fb7
f
21127
2
a8535
1
Type mmap mmap mmap mmap mmap work work work work work Addr work work work work Addr work Addr work Addr work Addr pers Addr
Pin 2316
Description mapped to sid mapped to sid mapped to sid mapped to sid mapped to sid
Pgsp Virtual 64-bit Mthrd LPage 2461 501080 N Y N
b1475 30fe5 91072 6bced b1035
Range: 0..45055 shmat/mmap shmat/mmap shmat/mmap shmat/mmap Range: 0..50453 shared library text Range: 0..30861 shared library data Range: 0..2521 process private Range: 65300..65535 code,/dev/q109waslv:81938 Range: 0..11
LPage -
Inuse 0 0 0 0 0 65536 65536 65536 65536 45054
Pin Pgsp Virtual 0 0 0 0 0 0 282 65536 0 285 65536 0 54 65536 0 261 65536 0 0 45054
-
48284 46997 46835 37070
0 0 0 0
3 463 281 0
48284 47210 46953 37070
-
9172
0
0
9220
-
105
0
1
106
-
50
2
1
51
-
11
0
-
-
Other example: # svmon -G -i 2 5 memory size inuse 16384 16250 16384 16250 16384 16250 16384 16250 16384 16250
free 134 134 134 134 134
# sample five times at two second intervals
pin 2006 2006 2006 2006 2006
in use work pers 10675 2939 10675 2939 10675 2939 10675 2939 10675 2939
clnt 2636 2636 2636 2636 2636
work 2006 2006 2006 2006 2006
pin pers 0 0 0 0 0
clnt 0 0 0 0 0
pg space size inuse 40960 12674 40960 12674 40960 12674 40960 12674 40960 12674
In this example, there are 16384 pages of total size of memory. Multuply this number by 4096 to see the total real memory size. In this case the total memory is 64 MB.
filemon: -------filemon can be used to identify the files that are being used most actively. This tool gives a very comprehensive view of file access, and can be useful for drilling down once vmstat/iostat confirm disk to be a bottleneck. Example: # filemon -o /tmp/filemon.log; sleep 60; trcstop The generated log file is quite large. Some sections that may be useful are: Most Active Files -----------------------------------------------------------------------#MBs #opns #rds #wrs file volume:inode -----------------------------------------------------------------------25.7 83 6589 0 unix /dev/hd2:147514 16.3 1 4175 0 vxe102 /dev/mailv1:581 16.3 1 0 4173 .vxe102.pop /dev/poboxv:62 15.8 1 1 4044 tst1 /dev/mailt1:904 8.3 2117 2327 0 passwd /dev/hd4:8205 3.2 182 810 1 services /dev/hd4:8652 ... -----------------------------------------------------------------------Detailed File Stats -----------------------------------------------------------------------FILE: /var/spool/mail/v/vxe102 volume: /dev/mailv1 (/var/spool2/mail/v) inode: 581 opens: 1 total bytes xfrd: 17100800 reads: 4175 (0 errs) read sizes (bytes): avg 4096.0 min 4096 max 4096 sdev 0.0 read times (msec): avg 0.543 min 0.011 max 78.060 sdev 2.753 ... curt: ----curt Command Purpose The CPU Utilization Reporting Tool (curt) command converts an AIX trace file into a number of statistics related to CPU utilization and either process, thread or pthread activity. These statistics ease the tracking of specific application activity. curt works with both uniprocessor and multiprocessor AIX Version 4 and AIX Version 5 traces. Syntax curt -i inputfile [-o outputfile] [-n gennamesfile] [-m trcnmfile] [-a pidnamefile] [-f timestamp]
[-l timestamp] [-ehpstP] Description The curt command takes an AIX trace file as input and produces a number of statistics related to processor (CPU) utilization and process/thread/pthread activity. It will work with both uniprocessor and multiprocessor AIX traces if the processor clocks are properly synchronized.
1.2.13 Not so well known tools for AIX: the proc tools: ======================================================= --proctree Displays the process tree containing the specified process IDs or users. To display the ancestors and all the children of process 12312, enter: # proctree 21166 11238 /usr/sbin/srcmstr 21166 /usr/sbin/rsct/bin/IBM.AuditRMd To display the ancestors and children of process 21166, including children of process 0, enter: #proctree �a 21166 1 /etc/init 11238 /usr/sbin/srcmstr 21166 /usr/sbin/rsct/bin/IBM.AuditRMd
-- procstack Displays the hexadecimal addresses and symbolic names for each of the stack frames of the current thread in processes. To display the current stack of process 15052, enter: # procstack 15052 15052 : /usr/sbin/snmpd d025ab80 select (?, ?, ?, ?, ?) + 90 100015f4 main (?, ?, ?) + 1814 10000128 __start () + 8c Currently, procstack displays garbage or wrong information for the top stack frame, and possibly for the second top stack frame. Sometimes it will erroneously display "No frames found on the stack," and sometimes it will display: deadbeef ???????? (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ...) The fix for this problem had not been released at the writing of this article. When the fix becomes available, you need to download the APAR IY48543 for 5.2. For AIX 5.3 it all should work OK. -- procmap
Displays a process address map. To display the address space of process 13204, enter: # procmap 13204 13204 : /usr/sbin/biod 6 10000000 3K read/exec 20000910 0K read/write d0083100 79K read/exec 20013bf0 41K read/write d007a100 34K read/exec 20011378 4K read/write d0074000 11K read/exec d0077130 8K read/write d00730f8 2K read/exec f03c7508 0K read/write d01d4e20 1997K read/exec f0337e90 570K read/write
biod biod /usr/lib/libiconv.a /usr/lib/libiconv.a /usr/lib/libi18n.a /usr/lib/libi18n.a /usr/lib/nls/loc/en_US /usr/lib/nls/loc/en_US /usr/lib/libcrypt.a /usr/lib/libcrypt.a /usr/lib/libc.a /usr/lib/libc.a
-- procldd Displays a list of libraries loaded by a process. To display the list of dynamic libraries loaded by process 11928, enter # procldd 11928. T 11928 : -sh /usr/lib/nls/loc/en_US /usr/lib/libcrypt.a /usr/lib/libc.a -- procflags Displays a process tracing flags, and the pending and holding signals. To display the tracing flags of process 28138, enter: # procflags 28138 28138 : /usr/sbin/rsct/bin/IBM.HostRMd data model = _ILP32 flags = PR_FORK /64763: flags = PR_ASLEEP | PR_NOREGS /66315: flags = PR_ASLEEP | PR_NOREGS /60641: flags = PR_ASLEEP | PR_NOREGS /66827: flags = PR_ASLEEP | PR_NOREGS /7515: flags = PR_ASLEEP | PR_NOREGS /70439: flags = PR_ASLEEP | PR_NOREGS /66061: flags = PR_ASLEEP | PR_NOREGS /69149: flags = PR_ASLEEP | PR_NOREGS -- procsig Lists the signal actions for a process. To list all the signal actions defined for process 30552, enter: # procsig 30552 30552 : -ksh HUP caught INT caught QUIT caught
ILL caught TRAP caught ABRT caught EMT caught FPE caught KILL default RESTART BUS caught -- proccred Prints a process' credentials. To display the credentials of process 25632, enter: # proccred 25632 25632: e/r/suid=0
e/r/sgid=0
-- procfiles Prints a list of open file descriptors. To display status and control information on the file descriptors opened by process 20138, enter: # procfiles �n 20138 20138 : /usr/sbin/rsct/bin/IBM.CSMAgentRMd Current rlimit: 2147483647 file descriptors 0: S_IFCHR mode:00 dev:10,4 ino:4178 uid:0 gid:0 rdev:2,2 O_RDWR name:/dev/null 2: S_IFREG mode:0311 dev:10,6 ino:250 uid:0 gid:0 rdev:0,0 O_RDWR size:0 name:/var/ct/IBM.CSMAgentRM.stderr 4: S_IFREG mode:0200 dev:10,6 ino:255 uid:0 gid:0 rdev:0,0 -- procwdx Prints the current working directory for a process. To display the current working directory of process 11928, enter: # procwdx 11928 11928 : /home/guest -- procstop Stops a process. To stop process 7500 on the PR_REQUESTED event, enter: # procstop 7500 . -- procrun Restart a process. To restart process 30192 that was stopped on the PR_REQUESTED event, enter: # procrun 30192 . -- procwait Waits for all of the specified processes to terminate. To wait for process 12942 to exit and display the status, enter # procwait -v 12942 . 12942 : terminated, exit status 0
1.2.14 Other monitoring: ======================== Nagios: open source Monitoring for most unix systems: ----------------------------------------------------Nagios is an open source host, service and network monitoring program. Latest versions: 2.5 (stable) Overview Nagios is a host and service monitor designed to inform you of network problems before your clients, end-users or managers do. It has been designed to run under the Linux operating system, but works fine under most *NIX variants as well. The monitoring daemon runs intermittent checks on hosts and services you specify using external "plugins" which return status information to Nagios. When problems are encountered, the daemon can send notifications out to administrative contacts in a variety of different ways (email, instant message, SMS, etc.). Current status information, historical logs, and reports can all be accessed via a web browser. System Requirements The only requirement of running Nagios is a machine running Linux (or UNIX variant) and a C compiler. You will probably also want to have TCP/IP configured, as most service checks will be performed over the network. You are not required to use the CGIs included with Nagios. However, if you do decide to use them, you will need to have the following software installed... - A web server (preferrably Apache) - Thomas Boutell's gd library version 1.6.3 or higher (required by the statusmap and trends CGIs)
rstat: Monitoring Machine Utilization with rstat: ------------------------------------------------rstat stands for Remote System Statistics service Ports exist for most unixes, like Linux, Solaris, AIX etc.. -- rstat on Linux, Solaris: rstat is an RPC client program to get and print statistics from any machine
running the rpc.rstatd daemon, its server-side counterpart. The rpc.rstad daemon has been used for many years by tools such as Sun's perfmeter and the rup command. The rstat program is simply a new client for an old daemon. The fact that the rpc.rstatd daemon is already installed and running on most Solaris and Linux machines is a huge advantage over other tools that require the installation of custom agents. The rstat client compiles and runs on Solaris and Linux as well and can get statistics from any machine running a current rpc.rstatd daemon, such as Solaris, Linux, AIX, and OpenBSD. The rpc.rstatd daemon is started from /etc/inetd.conf on Solaris. It is similar to vmstat, but has some advantages over vmstat: You can get statistics without logging in to the remote machine, including over the Internet. It includes a timestamp. The output can be plotted directly by gnuplot. The fact that it runs remotely means that you can use a single central machine to monitor the performance of many remote machines. It also has a disadvantage in that it does not give the useful scan rate measurement of memory shortage, the sr column in vmstat. rstat will not work across most firewalls because it relies on port 111, the RPC port, which is usually blocked by firewalls. To use rstat, simply give it the name or IP address of the machine you wish to monitor. Remember that rpc.rstatd must be running on that machine. The rup command is extremely useful here because with no arguments, it simply prints out a list of all machines on the local network that are running the rstatd demon. If a machine is not listed, you may have to start rstatd manually. To start rpc.rstatd under Red Hat Linux, run # /etc/rc.d/init.d/rstatd start
as root.
On Solaris, first try running the rstat client because inetd is often already configured to automatically start rpc.rstatd on request. If it the client fails with the error "RPC: Program not registered," make sure you have this line in your /etc/inet/inetd.conf and kill -HUP your inetd process to get it to re-read inetd.conf, as follows: rstatd/2-4 tli rpc/datagram_v wait root /usr/lib/netsvc/rstat/rpc.rstatd rpc.rstatd Then you can monitor that machine like this: % rstat enkidu 2001 07 10 10 36 08
0
0
0 100
0
27
54
1
0
0
12
0.1
This command will give you a one-second average and then it will exit. If you want to continuously monitor, give an interval in seconds on the command line. Here's an example of one line of output every two seconds: % rstat 2001 07 2001 07 2001 07 2001 07 2001 07 ^C
enkidu 2 10 10 36 10 10 36 10 10 36 10 10 36 10 10 36
28 30 32 34 36
0 0 0 0 0
0 0 0 0 0
1 0 0 0 0
98 100 100 100 100
0 0 0 0 0
0 0 0 5 0
7 0 0 10 46
2 2 2 2 2
0 0 0 0 0
0 0 0 0 0
61 15 15 19 108
0.0 0.0 0.0 0.0 0.0
To get a usage message, the output format, the version number, and where to go for updates, just type rstat with no parameters: % rstat usage: rstat machine [interval] output: yyyy mm dd hh mm ss usr wio sys idl pgin pgout intr ipkts opkts coll docs and src at http://patrick.net/software/rstat/rstat.html
cs load
Notice that the column headings line up with the output data. -- AIX: In order to get rstat working on AIX, you may need to configure rstatd. As root 1. Edit /etc/inetd.conf Uncomment or add entry for rstatd Eg rstatd sunrpc_udp udp wait root /usr/sbin/rpc.rstatd rstatd 100001 1-3 2. Edit /etc/services Uncomment or add entry for rstatd Eg rstatd 100001/udp 3. Refresh services refresh -s inetd 4. Start rstatd /usr/sbin/rpc.rstatd
================================== 2. NFS and Mount command examples: ================================== 2.1 NFS:
======== We will discuss the most important feaures of NFS, by showing how its implemented on Solaris, Redhat and SuSE Linux. Most of this applies to HP-UX and AIX as well. 2.1.1 NFS and Redhat Linux: --------------------------Linux uses a combination of kernel-level support and continuously running daemon processes to provide NFS file sharing, however, NFS support must be enabled in the Linux kernel to function. NFS uses Remote Procedure Calls (RPC) to route requests between clients and servers, meaning that the portmap service must be enabled and active at the proper runlevels for NFS communication to occur. Working with portmap, various other processes ensure that a particular NFS connection is allowed and may proceed without error: rpc.mountd � The running process that receives the mount request from an NFS client and checks to see if it matches with a currently exported file system. rpc.nfsd � The process that implements the user-level part of the NFS service. It works with the Linux kernel to meet the dynamic demands of NFS clients, such as providing additional server threads for NFS clients to uses. rpc.lockd � A daemon that is not necessary with modern kernels. NFS file locking is now done by the kernel. It is included with the nfs-utils package for users of older kernels that do not include this functionality by default. rpc.statd � Implements the Network Status Monitor (NSM) RPC protocol. This provides reboot notification when an NFS server is restarted without being gracefully brought down. rpc.rquotad � An RPC server that provides user quota information for remote users. Not all of these programs are required for NFS service. The only services that must be enabled are rpc.mountd, rpc.nfsd, and portmap. The other daemons provide additional functionality and should only be used if your server environment requires them. NFS version 2 uses the User Datagram Protocol (UDP) to provide a stateless network connection between the client and server. NFS version 3 can use UDP or TCP running over an IP. The stateless UDP connection minimizes network traffic, as the NFS server sends the client a cookie after the client is authorized to access the shared volume. This cookie is a random value stored on the server's side and is passed with along with RPC requests from the client. The NFS server can be restarted
without affecting the clients and the cookie will remain intact. NFS only performs authentication when a client system attempts to mount a remote file system. To limit access, the NFS server first employs TCP wrappers. TCP wrappers reads the /etc/hosts.allow and /etc/hosts.deny files to determine if a particular client should be permitted or prevented access to the NFS server. After the client is allowed past TCP wrappers, the NFS server refers to its configuration file, "/etc/exports", to determine whether the client has enough privileges to mount any of the exported file systems. After granting access, any file and directory operations are sent to the server using remote procedure calls. Warning NFS mount privileges are granted specifically to a client, not a user. If you grant a client machine access to an exported file system, any users of that machine will have access to the data. When configuring the /etc/exports file, be extremely careful about granting readwrite permissions (rw) to a remote host. -- NFS and portmap NFS relies upon remote procedure calls (RPC) to function. portmap is required to map RPC requests to the correct services. RPC processes notify portmap when they start, revealing the port number they are monitoring and the RPC program numbers they expect to serve. The client system then contacts portmap on the server with a particular RPC program number. portmap then redirects the client to the proper port number to communicate with its intended service. Because RPC-based services rely on portmap to make all connections with incoming client requests, portmap must be available before any of these services start. If, for some reason, the portmap service unexpectedly quits, restart portmap and any services running when it was started. The portmap service can be used with the host access files (/etc/hosts.allow and /etc/hosts.deny) to control which remote systems are permitted to use RPC-based services on your machine. Access control rules for portmap will affect all RPC-based services. Alternatively, you can specify each of the NFS RPC daemons to be affected by a particular access control rule. The man pages for rpc.mountd and rpc.statd contain information regarding the precise syntax of these rules. -- portmap Status As portmap provides the coordination between RPC services and the port numbers used to communicate with them, it is useful to be able to get a picture of the current RPC services using portmap when troubleshooting.
The rpcinfo command shows each RPC-based service with its port number, RPC program number, version, and IP protocol type (TCP or UDP). To make sure the proper NFS RPC-based services are enabled for portmap, rpcinfo -p can be useful: # rpcinfo -p program vers proto 100000 2 tcp 100000 2 udp 100024 1 udp 100024 1 tcp 100011 1 udp 100011 2 udp 100005 1 udp 100005 1 tcp 100005 2 udp 100005 2 tcp 100005 3 udp 100005 3 tcp 100003 2 udp 100003 3 udp 100021 1 udp 100021 3 udp 100021 4 udp
port 111 111 1024 1024 819 819 1027 1106 1027 1106 1027 1106 2049 2049 1028 1028 1028
portmapper portmapper status status rquotad rquotad mountd mountd mountd mountd mountd mountd nfs nfs nlockmgr nlockmgr nlockmgr
The -p option probes the portmapper on the specified host or defaults to localhost if no specific host is listed. Other options are available from the rpcinfo man page. From the output above, various NFS services can be seen running. If one of the NFS services does not start up correctly, portmap will be unable to map RPC requests from clients for that service to the correct port. In many cases, restarting NFS as root (/sbin/service nfs restart) will cause those service to correctly register with portmap and begin working. # /sbin/service nfs restart -- NFS Server Configuration Files Configuring a system to share files and directories using NFS is straightforward. Every file system being exported to remote users via NFS, as well as the access rights relating to those file systems, is located in the /etc/exports file. This file is read by the exportfs command to give rpc.mountd and rpc.nfsd the information necessary to allow the remote mounting of a file system by an authorized host. The exportfs command allows you to selectively export or unexport directories without restarting the various NFS services. When exportfs is passed the proper options, the file systems to be exported are written to /var/lib/nfs/xtab. Since rpc.mountd refers to the xtab file when deciding access privileges to a file system, changes to the list of exported file systems take effect immediately.
Various options are available when using exportfs: -r � Causes all directories listed in /etc/exports to be exported by constructing a new export list in /etc/lib/nfs/xtab. This option effectively refreshes the export list with any changes that have been made to /etc/exports. -a � Causes all directories to be exported or unexported, depending on the other options passed to exportfs. -o options � Allows the user to specify directories to be exported that are not listed in /etc/exports. These additional file system shares must be written in the same way they are specified in /etc/exports. This option is used to test an exported file system before adding it permanently to the list of file systems to be exported. -i � Tells exportfs to ignore /etc/exports; only options given from the command line are used to define exported file systems. -u � Unexports directories from being mounted by remote users. The command exportfs -ua effectively suspends NFS file sharing while keeping the various NFS daemons up. To allow NFS sharing to continue, type exportfs -r. -v � Verbose operation, where the file systems being exported or unexported are displayed in greater detail when the exportfs command is executed. If no options are passed to the exportfs command, it displays a list of currently exported file systems. Changes to /etc/exports can also be read by reloading the NFS service with the service nfs reload command. This keeps the NFS daemons running while re-exporting the /etc/exports file. -- /etc/exports The /etc/exports file is the standard for controlling which file systems are exported to which hosts, as well as specifying particular options that control everything. Blank lines are ignored, comments can be made using #, and long lines can be wrapped with a backslash (\). Each exported file system should be on its own line. Lists of authorized hosts placed after an exported file system must be separated by space characters. Options for each of the hosts must be placed in parentheses directly after the host identifier, without any spaces separating the host and the first parenthesis. In its simplest form, /etc/exports only needs to know the directory to be exported and the hosts permitted to use it:
/some/directory bob.domain.com /another/exported/directory 192.168.0.3 n5111sviob After re-exporting /etc/exports with the "/sbin/service nfs reload" command, the bob.domain.com host will be able to mount /some/directory and 192.168.0.3 can mount /another/exported/directory. Because no options are specified in this example, several default NFS preferences take effect. In order to override these defaults, you must specify an option that takes its place. For example, if you do not specify rw, then that export will only be shared read-only. Each default for every exported file system must be explicitly overridden. Additionally, other options are available where no default value is in place. These include the ability to disable sub-tree checking, allow access from insecure ports, and allow insecure file locks (necessary for certain early NFS client implementations). See the exports man page for details on these lesser used options. When specifying hostnames, you can use the following methods: single host � Where one particular host is specified with a fully qualified domain name, hostname, or IP address. wildcards � Where a * or ? character is used to take into account a grouping of fully qualified domain names that match a particular string of letters. Wildcards are not to be used with IP addresses; however, they may accidently work if reverse DNS lookups fail. However, be careful when using wildcards with fully qualified domain names, as they tend to be more exact than you would expect. For example, the use of *.domain.com as wildcard will allow sales.domain.com to access the exported file system, but not bob.sales.domain.com. To match both possibilities, as well as sam.corp.domain.com, you would have to provide *.domain.com *.*.domain.com. IP networks � Allows the matching of hosts based on their IP addresses within a larger network. For example, 192.168.0.0/28 will allow the first 16 IP addresses, from 192.168.0.0 to 192.168.0.15, to access the exported file system but not 192.168.0.16 and higher. netgroups � Permits an NIS netgroup name, written as @, to be used. This effectively puts the NIS server in charge of access control for this exported file system, where users can be added and removed from an NIS group without affecting /etc/exports. Warning The way in which the /etc/exports file is formatted is very important, particularly concerning the use of
space characters. Remember to always separate exported file systems from hosts and hosts from one another with a space character. However, there should be no other space characters in the file unless they are used in comment lines. For example, the following two lines do not mean the same thing: /home bob.domain.com(rw) /home bob.domain.com (rw) The first line allows only users from bob.domain.com read-write access to the /home directory. The second line allows users from bob.domain.com to mount the directory readonly (the default), but the rest of the world can mount it read-write. Be careful where space characters are used in /etc/exports. -- NFS Client Configuration Files - What to do on a client? Any NFS share made available by a server can be mounted using various methods. Of course, the share can be manually mounted, using the mount command, to acquire the exported file system at a particular mount point. However, this requires that the root user type the mount command every time the system restarts. In addition, the root user must remember to unmount the file system when shutting down the machine. Two methods of configuring NFS mounts include modifying the /etc/fstab or using the autofs service. > /etc/fstab Placing a properly formatted line in the /etc/fstab file has the same effect as manually mounting the exported file system. The /etc/fstab file is read by the /etc/rc.d/init.d/netfs script at system startup. The proper file system mounts, including NFS, are put into place. A sample /etc/fstab line to mount an NFS export looks like the following: : nfs 0 0 The relates to the hostname, IP address, or fully qualified domain name of the server exporting the file system. The tells the server what export to mount. The specifies where on the local file system to mount the exported directory. This mount point must exist before /etc/fstab is read or the mount will fail. The nfs option specifies the type of file system being mounted. The area specifies how the file system is to be mounted. For example, if the options area states rw,suid on a particular mount, the exported file system will be mounted read-write and the
user and group ID set by the server will be used. Note, parentheses are not to be used here.
2.1.2 NFS and SuSE Linux: -------------------------- Importing File Systems with YaST Any user authorized to do so can mount NFS directories from an NFS server into his own file tree. This can be achieved most easily using the YaST module �NFS Client�. Just enter the host name of the NFS server, the directory to import, and the mount point at which to mount this directory locally. All this is done after clicking �Add� in the first dialog. -- Importing File Systems Manually File systems can easily be imported manually from an NFS server. The only prerequisite is a running RPC port mapper, which can be started by entering the command # rcportmap start as root. Once this prerequisite is met, remote file systems exported on the respective machines can be mounted in the file system just like local hard disks using the command mount with the following syntax: # mount host:remote-path local-path If user directories from the machine sun, for example, should be imported, the following command can be used: # mount sun:/home /home -- Exporting File Systems with YaST With YaST, turn a host in your network into an NFS server � a server that exports directories and files to all hosts granted access to it. This could be done to provide applications to all coworkers of a group without installing them locally on each and every host. To install such a server, start YaST and select �Network Services� -> �NFS Server� Next, activate �Start NFS Server� and click �Next�. In the upper text field, enter the directories to export. Below, enter the hosts that should have access to them. There are four options that can be set for each host: single host, netgroups, wildcards, and IP networks. A more thorough explanation of these options is provided by man exports. �Exit� completes the configuration.
-- Exporting File Systems Manually If you do not want to use YaST, make sure the following systems run on the NFS server: RPC portmapper (portmap) RPC mount daemon (rpc.mountd) RPC NFS daemon (rpc.nfsd) For these services to be started by the scripts "/etc/init.d/portmap" and "/etc/init.d/nfsserver" when the system is booted, enter the commands # insserv /etc/init.d/nfsserver # insserv /etc/init.d/portmap.
and
Also define which file systems should be exported to which host in the configuration file "/etc/exports". For each directory to export, one line is needed to set which machines may access that directory with what permissions. All subdirectories of this directory are automatically exported as well. Authorized machines are usually specified with their full names (including domain name), but it is possible to use wild cards like * or ? (which expand the same way as in the Bash shell). If no machine is specified here, any machine is allowed to import this file system with the given permissions. Set permissions for the file system to export in brackets after the machine name. The most important options are: ro File system is exported with read-only permission (default). rw File system is exported with read-write permission. root_squash This makes sure the user root of the given machine does not have root permissions on this file system. This is achieved by assigning user ID 65534 to users with user ID 0 (root). This user ID should be set to nobody (which is the default). no_root_squash Does not assign user ID 0 to user ID 65534, keeping the root permissions valid. link_relative Converts absolute links (those beginning with /) to a sequence of ../. This is only useful if the entire file system of a machine is mounted (default). link_absolute Symbolic links remain untouched. map_identity User IDs are exactly the same on both client and server (default). map_daemon Client and server do not have matching user IDs. This tells nfsd to create a conversion table for user IDs. The ugidd daemon is required for this to work. /etc/exports is read by mountd and nfsd. If you change anything in this file, restart mountd and nfsd for your changes to take effect. This can easily be done with "rcnfsserver restart".
Example SuSE /etc/exports # # /etc/exports # /home /usr/X11 /usr/lib/texmf / /home/ftp # End of exports
sun(rw) venus(rw) sun(ro) venus(ro) sun(ro) venus(rw) earth(ro,root_squash) (ro)
2.2 Mount command: ================== The standard form of the mount command, is mount -F typefs device mountdir (solaris, HP-UX) mount -t typefs device mountdir (many other unix's) This tells the kernel to attach the file system found on "device" (which is of type type) at the directory "dir". The previous contents (if any) and owner and mode of dir become invisible, and as long as this file system remains mounted, the pathname dir refers to the root of the file system on device. The syntax is: mount [options] [type] [device] [mountpoint] -- mounting a remote filesystem: syntax: mount -F nfs -O # mount -F nfs hpsrv:/data /data # mount -F nfs -o hard,intr thor:/data
:
/data
- standard mounts are determined by files like /etc/filesystems (AIX) or /etc/vfstab etc..
/etc/fstab (HP-UX) or
2.2.1 Where are the standard mounts defined? ============================================ In Solaris: =========== - standard mounts are determined by /etc/vfstab etc.. - NFS mounts are determined by the file /etc/dfs/dfstab. Here you will find share commands. - currently mounted filesystems are listed in /etc/mnttab
In Linux: ========= - standard mounts are determined by most Linux distros by "/etc/fstab". In AIX: ======= - standard mounts and properties are determined by the file "/etc/filesystems". In HP-UX: ========= There is a /etc/fstab which contains all of the filesystems are mounted at boot time. The filesystems that are OS related are / , /var, /opt , /tmp, /usr , /stand The filesystem that is special is /stand, this is where your kernel is built and resides. Notice that the filesystem type is "hfs". HPUX kernels MUST reside on an hfs filesystem
An example of /etc/vfstab: -------------------------starboss:/etc $ more vfstab #device device mount FS #to mount to fsck point type # fd /dev/fd fd no /proc /proc proc no /dev/md/dsk/d1 swap no /dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 /dev/md/dsk/d4 /dev/md/rdsk/d4 /usr ufs 1 /dev/md/dsk/d3 /dev/md/rdsk/d3 /var ufs 1 /dev/md/dsk/d7 /dev/md/rdsk/d7 /export ufs 2 /dev/md/dsk/d5 /dev/md/rdsk/d5 /usr/local ufs /dev/dsk/c2t0d0s0 /dev/rdsk/c2t0d0s0 /export2 logging swap - /tmp tmpfs - yes size=512m
fsck pass
mount mount at boot options
no no no yes 2 ufs
logging logging logging logging yes logging 2 yes
mount adds an entry, umount deletes an entry. mounting applies to local filesystemes, or remote filesystems via NFS At Remote server: share, shareall, or add entry in /etc/dfs/dfstab # share -F nfs /var/mail Unmount a mounted FS First check who is using it # fuser -c mountpoint # umount mointpoint
2.2.2 Mounting a NFS filesystem in HP-UX: ========================================= Mounting Remote File Systems You can use either SAM or the mount command to mount file systems located on a remote system. Before you can mount file systems located on a remote system, NFS software must be installed and configured on both local and remote systems. Refer to Installing and Administering NFS for information. For information on mounting NFS file systems using SAM, see SAM's online help. To mount a remote file system using HP-UX commands, You must know the name of the host machine and the file system's directory on the remote machine. Establish communication over a network between the local system (that is, the "client") and the remote system. (The local system must be able to reach the remote system via whatever hosts database is in use.) (See named(1M) and hosts(4).) If necessary, test the connection with /usr/sbin/ping; see ping(1M). Make sure the file /etc/exports on the remote system lists the file systems that you wish to make available to clients (that is, to "export") and the local systems that you wish to mount the file systems. For example, to allow machines called rolf and egbert to remotely mount the /usr file system, edit the file /etc/exports on the remote machine and include the line: /usr rolf egbert Execute /usr/sbin/exportfs -a on the remote system to export all directories in /etc/exports to clients. For more information, see exportfs(1M). NOTE: If you wish to invoke exportfs -a at boot time, make sure the NFS configuration file /etc/rc.config.d/nfsconf on the remote system contains the following settings: NFS_SERVER=1 and START_MOUNTD=1. The client's /etc/rc.config.d/nfsconf file must contain NFS_CLIENT=1. Then issue the following command to run the script: /sbin/init.d/nfs.server start Mount the file system on the local system, as in: # mount -F nfs remotehost:/remote_dir /local_dir
Just a bunch of mount command examples: --------------------------------------# # # # # # # # # # #
mount mount -a mountall -l mount -t type device dir mount -F pcfs /dev/dsk/c0t0d0p0:c /pcfs/c mount /dev/md/dsk/d7 /u01 mount sun:/home /home mount -t nfs 137.82.51.1:/share/sunos/local /usr/local mount /dev/fd0 /mnt/floppy mount -o ro /dev/dsk/c0t6d0s1 /mnt/cdrom mount -V cdrfs -o ro /dev/cd0 /cdrom
2.2.3 Solaris mount command: ============================ The unix mount command is used to mount a filesystem, and it attaches disks, and directories logically rather than physically. It takes a minimum of two arguments: 1) the name of the special device which contains the filesystem 2) the name of an existing directory on which to mount the file system Once the file system is mounted, the directory becomes the mount point. All the file systems will now be usable as if they were subdirectories of the file system they were mounted on. The table of currently mounted file systems can be found by examining the mounted file system information file. This is provided by a file system that is usually mounted on /etc/mnttab. Mounting a file system causes three actions to occur: 1. The superblock for the mounted file system is read into memory 2. An entry is made in the /etc/mnttab file 3. An entry is made in the inode for the directory on which the file system is mounted which marks the directory as a mount point The /etc/mountall command mounts all filesystems as described in the /etc/vfstab file. Note that /etc/mount and /etc/mountall commands can only be executed by the superuser. OPTIONS -F FSType Used to specify the FSType on which to operate. The FSType must be specified or must be determinable from /etc/vfstab, or by consulting /etc/default/fs or /etc/dfs/fstypes. -a [ mount_points. . . ] Perform mount or umount operations in parallel, when possible.
If mount points are not specified, mount will mount all file systems whose /etc/vfstab "mount at boot" field is "yes". If mount points are specified, then /etc/vfstab "mount at boot" field will be ignored. If mount points are specified, umount will only umount those mount points. If none is specified, then umount will attempt to unmount all file systems in /etc/mnttab, with the exception of certain system required file systems: /, /usr, /var, /var/adm, /var/run, /proc, /dev/fd and /tmp. -f Forcibly unmount a file system. Without this option, umount does not allow a file system to be unmounted if a file on the file system is busy. Using this option can cause data loss for open files; programs which access files after the file system has been unmounted will get an error (EIO). -p Print the list of mounted file systems in the /etc/vfstab format. Must be the only option specified. -v Print the list of mounted file systems in verbose format. Must be the only option specified. -V Echo the complete command line, but do not execute the command. umount generates a command line by using the options and arguments provided by the user and adding to them information derived from /etc/mnttab. This option should be used to verify and validate the command line. generic_options Options that are commonly supported by most FSType-specific command modules. The following options are available: -m Mount the file system without making an entry in /etc/mnttab. -g Globally mount the file system. On a clustered system, this globally mounts the file system on all nodes of the cluster. On a non-clustered system this has no effect. -o Specify FSType-specific options in a comma separated (without spaces) list of suboptions and keyword-attribute pairs for interpretation by the FSType-specific module of the command. (See mount_ufs(1M)) -O Overlay mount. Allow the file system to be mounted over an existing mount point, making the underlying file system inaccessible. If a mount is attempted on a preexisting mount point without setting this flag, the mount will fail, producing the error "device busy". -r Mount the file system read-only.
Example mountpoints and disks: -----------------------------Mountpunt / /usr /var /home /opt /u01 /u02 /u03 /u04 /u05 /u06 /u07
Device /dev/md/dsk/d1 /dev/md/dsk/d3 /dev/md/dsk/d4 /dev/md/dsk/d5 /dev/md/dsk/d6 /dev/md/dsk/d7 /dev/md/dsk/d8 /dev/md/dsk/d9 /dev/md/dsk/d10 /dev/md/dsk/d110 /dev/md/dsk/d120 /dev/md/dsk/d123
Omvang Doel 100 Unix Root-filesysteem 1200 Unix usr-filesysteem 200 Unix var-filesysteem 200 Unix opt-filesysteem 4700 Oracle_Home 8700 Oracle datafiles 8700 Oracle datafiles 8700 Oracle datafiles 8700 Oracle datafiles 8700 Oracle datafiles 8700 Oracle datafiles 8650 Oracle datafiles
Suppose you have only 1 disk of about 72GB, 2GB RAM: Entire disk= Slice 2 / swap /export /var /opt /usr /u01
Slice 0, partition about 2G Slice 1, partition about 4G Slice 3, partition about 50G, maybe you link it to /u01 Slice 4, partition about 2G Slice 5, partition about 10G if you plan to install apps here Slice 6, partition about 2G Slice 7, partition optional, standard it's /home Depending on how you configure /export, size could be around 20G
find . -name dfctowdk\*.zip | while read file; do pkzip25 -extract -translate=unix -> 2.2.4 mount command on AIX: =========================== Typical examples: # mount -o soft 10.32.66.75:/data/nim /mnt # mount -o soft abcsrv:/data/nim /mnt # mount -o soft n580l03:/data/nim /mnt Note 1: ------mount [ -f ] [ -n Node ] [ -o Options ] [ -p ] [ -r ] [ -v VfsName ] [ -t Type | [ Device | Node:Directory ] Directory | all | -a ] [-V [generic_options] special_mount_points If you specify only the Directory parameter, the mount command takes it to be the name of the directory or file on which a file system, directory, or file is usually mounted (as defined in the /etc/filesystems file). The mount command looks up the associated device, directory, or file and mounts it. This is the most convenient way of using the mount command,
because it does not require you to remember what is normally mounted on a directory or file. You can also specify only the device. In this case, the command obtains the mount point from the /etc/filesystems file. The /etc/filesystems file should include a stanza for each mountable file system, directory, or file. This stanza should specify at least the name of the file system and either the device on which it resides or the directory name. If the stanza includes a mount attribute, the mount command uses the associated values. It recognizes five values for the mount attributes: automatic, true, false, removable, and readonly. The mount all command causes all file systems with the mount=true attribute to be mounted in their normal places. This command is typically used during system initialization, and the corresponding mounts are referred to as automatic mounts. Example mount command on AIX: ----------------------------$ mount node mounted -------- --------------/dev/hd4 /dev/hd2 /dev/hd9var /dev/hd3 /dev/hd1 /proc /dev/hd10opt /dev/fslv00 /dev/fslv01 /dev/fslv02 /dev/oralv /dev/db2lv /dev/fslv03 /dev/homepeter /dev/bmclv /dev/u01 /dev/u02 /dev/u05 /dev/u03 /dev/backuo /dev/u02back /dev/u01back /dev/u05back /dev/u04back /dev/u03back /dev/u04
mounted over --------------/ /usr /var /tmp /home /proc /opt /XmRec /tmp/m2 /software /opt/app/oracle /db2_database /bmc_home /home/peter /bcict/stage /u01 /u02 /u05 /u03 /backup_ora /u02back /u01back /u05back /u04back /u03back /u04
Example /etc/filesystems file: /var:
vfs -----jfs2 jfs2 jfs2 jfs2 jfs2 procfs jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2
date -----------Jun 06 17:15 Jun 06 17:15 Jun 06 17:15 Jun 06 17:15 Jun 06 17:16 Jun 06 17:16 Jun 06 17:16 Jun 06 17:16 Jun 06 17:16 Jun 06 17:16 Jun 06 17:25 Jun 06 19:54 Jun 07 12:11 Jun 13 18:42 Jun 15 15:21 Jun 22 00:22 Jun 22 00:22 Jun 22 00:22 Jun 22 00:22 Jun 22 00:22 Jun 22 00:22 Jun 22 00:22 Jun 22 00:22 Jun 22 00:22 Jun 22 00:22 Jun 22 10:25
options --------------rw,log=/dev/hd8 rw,log=/dev/hd8 rw,log=/dev/hd8 rw,log=/dev/hd8 rw,log=/dev/hd8 rw rw,log=/dev/hd8 rw,log=/dev/hd8 rw,log=/dev/hd8 rw,log=/dev/hd8 rw,log=/dev/hd8 rw,log=/dev/loglv00 rw,log=/dev/hd8 rw,log=/dev/hd8 rw,log=/dev/hd8 rw,log=/dev/loglv01 rw,log=/dev/loglv01 rw,log=/dev/loglv01 rw,log=/dev/loglv01 rw,log=/dev/loglv02 rw,log=/dev/loglv03 rw,log=/dev/loglv03 rw,log=/dev/loglv03 rw,log=/dev/loglv03 rw,log=/dev/loglv03 rw,log=/dev/loglv01
/tmp:
/opt:
dev vfs log mount check type vol free
= = = = = = = =
/dev/hd9var jfs2 /dev/hd8 automatic false bootfs /var false
dev vfs log mount check vol free
= = = = = = =
/dev/hd3 jfs2 /dev/hd8 automatic false /tmp false
dev vfs log mount check vol free
= = = = = = =
/dev/hd10opt jfs2 /dev/hd8 true true /opt false
Example of the relation of Logigal Volumes and mountpoints: /dev/lv01 /dev/lv02 /dev/lv03 /dev/lv04 /dev/lv00
= = = = =
/u01 /u02 /u03 /data /spl
2.2.5 mounting a CDROM: ======================= AIX: ---# mount -r -v cdrfs /dev/cd0 /cdrom SuSE Linux: ----------# mount -t iso9660 /dev/cdrom /cdrom # mount -t iso9660 /dev/cdrom /media/cdrom Redhat Linux: ------------# mount -t iso9660 /dev/cdrom /media/cdrom Solaris:
-------# mount -r -F hsfs /dev/dsk/c0t6d0s2 /cdrom HPUX: ----mount -F cdfs -o rr /dev/dsk/c1t2d0 /cdrom Other commands on Linux: -----------------------Sometimes on some Linux, and some scsi CDROM devices, you might try # mount /dev/sr0 /mount_point # mount -t iso9660 /dev/sr0 /mount_point
2.2.6 Some other commands related to mounts: =========================================== fsstat command: --------------On some unixes, the fsstat command is available. It provides filesystem statitstics. It can take a lot of switches, thus be sure to check the man pages. On Solaris, the following example shows the statistics for each file operation for �/� (using the -f option): $ fsstat -f / Mountpoint: / operation #ops open 8.54K close 9.8K read 43.6K write 1.57K ioctl 2.06K setfl 4 getattr 40.3K setattr 38 access 9.19K lookup 203K create 595 remove 56 link 0 rename 9 mkdir 19 rmdir 0 readdir 2.02K symlink 4 readlink 8.31K fsync 199 inactive 2.96K
bytes 65.9M 2.99M
2.27M
fid rwlock rwunlock seek cmp frlock space realvp getpage putpage map addmap delmap poll dump pathconf pageio dumpctl dispose getsecattr setsecattr shrlock vnevent
0 47.2K 47.2K 29.1K 42.9K 4.45K 8 3.25K 104K 2.69K 13.2K 34.4K 33.4K 287 0 54 0 0 23.8K 697 0 0 0
fuser command: -------------AIX: Purpose Identifies processes using a file or file structure. Syntax fuser [ -c | -d | -f ] [ -k ] [ -u ] [ -x ] [ -V ]File ... Description The fuser command lists the process numbers of local processes that use the local or remote files specified by the File parameter. For block special devices, the command lists the processes that use any file on that device. Flags -c Reports on any open files in the file system containing File. -d Implies the use of the -c and -x flags. Reports on any open files which haved been unlinked from the file system (deleted from the parent directory). When used in conjunction with the -V flag, it also reports the inode number and size of the deleted file. -f Reports on open instances of File only. -k Sends the SIGKILL signal to each local process. Only the root user can kill a process of another user. -u Provides the login name for local processes in parentheses after the process
number. -V Provides verbose output. -x Used in conjunction with -c or -f, reports on executable and loadable objects in addition to the standard fuser output. To list the process numbers of local processes using the /etc/passwd file, enter: # fuser /etc/passwd To list the process numbers and user login names of processes using the /etc/filesystems file, enter: # fuser -u /etc/filesystems To terminate all of the processes using a given file system, enter: #fuser -k -x -u /dev/hd1 -OR#fuser -kxuc /home Either command lists the process number and user name, and then terminates each process that is using the /dev/hd1 (/home) file system. Only the root user can terminate processes that belong to another user. You might want to use this command if you are trying to unmount the /dev/hd1 file system and a process that is accessing the /dev/hd1 file system prevents this. To list all processes that are using a file which has been deleted from a given file system, enter: # fuser -d /usr
Examples on linux distro's: - To kill all processes accessing the file system /home in any way. # fuser -km /home - invokes something if no other process is using /dev/ttyS1. if fuser -s /dev/ttyS1; then :; else something; fi - shows all processes at the (local) TELNET port. # fuser telnet/tcp A similar command is the lsof command. 2.2.7 Starting and stopping NFS: ================================ Short note on stopping and starting NFS. See other sections for more detail. On all unixes, a number of daemons should be running in order for NFS to be functional, like for example the rpc.* processes, biod, nfsd and others. Once nfs is running, and in order to actually "share" or "export" your filesystem on your server, so remote clients are able to mount the nfs mount, in most cases you should edit the "/etc/exports" file.
See other sections in this document (search on exportfs) on how to accomplish this. -- AIX: The following subsystems are part of the nfs group: nfsd, biod, rpc.lockd, rpc.statd, and rpc.mountd. The nfs subsystem (group) is under control of the "resource controller", so starting and stopping nfs is actually easy # startsrc -g nfs # stopsrc -g nfs Or use smitty. -- Redhat Linux: # /sbin/service nfs restart # /sbin/service nfs start # /sbin/service nfs stop -- On some other Linux distros # /etc/init.d/nfs start # /etc/init.d/nfs stop # /etc/init.d/nfs restart -- Solaris: If the nfs daemons aren't running, then you will need to run: # /etc/init.d/nfs.server start -- HP-UX: Issue the following command on the NFS server to start all the necessary NFS processes (HP): # /sbin/init.d/nfs.server start Or if your machine is only a client: # cd /sbin/init.d # ./nfs.client start
=========================================== 3. Change ownership file/dir, adding users: =========================================== 3.1 Changing ownership: ----------------------chown -R user[:group] file/dir chown -R user[.group] file/dir (-R recursive dirs)
(SVR4) (bsd)
Examples: chown -R oracle:oinstall chown -R oracle:oinstall chown -R oracle:oinstall chown -R oracle:oinstall
/opt/u01 /opt/u02 /opt/u03 /opt/u04
-R means all subdirs also. chown rjanssen file.txt # # # # # # #
- Give permissions as owner to user rjanssen.
groupadd dba useradd oracle mkdir /usr/oracle mkdir /usr/oracle/9.0 chown -R oracle:dba /usr/oracle touch /etc/oratab chown oracle:dba /etc/oratab
Note: Not owner message: ----------------------->>> Solaris: it is possible to turn the chown command on or off (i.e., allow it to be used or disallow its use) on a system by altering the /etc/system file. The /etc/system file, along with the files in /etc/default should be thought of a "system policy files" -- files that allow the systems administrator to determine such things as whether root can login over the network, whether su commands are logged, and whether a regular user can change ownership of his own files. On a system disallowing a user to change ownership of his files (this is now the default), the value of rstchown is set to 1. Think of this as saying "restrict chown is set to TRUE". You might see a line like this in /etc/system (or no rstchown value at all): set rstchown=1 On a system allowing chown by regular users, this value will be set to 0 as shown here: set rstchown=0 Whenever the /etc/system file is changed, the system will have to be rebooted for the changes to take effect. Since there is no daemon process associated with commands such a chown, there is no process that one could send a hangup (HUP) to effect the change in policy "on the fly". Why might system administrators restrict access to the chown command? For a system on which disk quotas are enforced, they might not want to allow files to be "assigned" by one user to another user's quota. More importantly, for a system on which accountability is deemed important, system administrators will want to know who
created each file on a system - whether to track down a potential system abuse or simply to ask if a file that is occupying space in a shared directory or in /tmp can be removed. When a system disallows use of the chown command, you can expect to see dialog like this: % chown wallace myfile chown: xyz: Not owner Though it would be possible to disallow "chowning" of files by changing permissions on /usr/bin/chown, such a change would not slow down most Unix users. They would simple copy the /usr/bin/chown file to their own directory and make their copy executable. Designed to be extensible, Unix will happily comply. Making the change in the /etc/system file blocks any chown operation from taking effect, regardless of where the executable is stored, who owns it, and what it is called. If usage of chown is restricted in /etc/system, only the superuser can change ownership of files.
3.2 Add a user in Solaris: -------------------------Examples: # useradd -u 3000 -g other -d /export/home/tempusr -m -s /bin/ksh -c "temporary user" tempusr # useradd -u 1002 -g dba -d /export/home/avdsel -m -s /bin/ksh -c "Albert van der Sel" avdsel # useradd -u 1001 -g oinstall -G dba -d /export/home/oraclown -m -s /bin/ksh -c "Oracle owner" oraclown # useradd -u 1005 -g oinstall -G dba -d /export/home/brighta -m -s /bin/ksh -c "Bright Alley" brighta useradd -u 300 -g staff -G staff -d /home/emc -m -s /usr/bin/ksh -c "EMC user" emc a password cannot be specified using the useradd command. Use passwd to give the user a password: # passwd tempusr UID must be unique and is typically a number between 100 and 60002 GID is a number between 0 and 60002 3.3 Add a user in AIX:
---------------------You can also use the useradd command, just as in Solaris. Or use the native "mkuser" command. # mkuser albert The mkuser command does not create password information for a user. It initializes the password field with an * (asterisk). Later, this field is set with the passwd or pwdadm command. New accounts are disabled until the passwd or pwdadm commands are used to add authentication information to the /etc/security/passwd file. You can use the Users application in Web-based System Manager to change user characteristics. You could also use the System Management Interface Tool (SMIT) "smit mkuser" fast path to run this command. The /usr/lib/security/mkuser.default file contains the default attributes for new users. This file is an ASCII file that contains user stanzas. These stanzas have attribute default values for users created by the mkuser command. Each attribute has the Attribute=Value form. If an attribute has a value of $USER, the mkuser command substitutes the name of the user. The end of each attribute pair and stanza is marked by a new-line character. There are two stanzas, user and admin, that can contain all defined attributes except the id and admin attributes. The mkuser command generates a unique id attribute. The admin attribute depends on whether the -a flag is used with the mkuser command. A typical user stanza looks like the following: user: pgroup = staff groups = staff shell = /usr/bin/ksh home = /home/$USER auth1 = SYSTEM # mkuser [ -de | -sr ] [-attr Attributes=Value [ Attribute=Value... ] ] Name # mkuser [ -R load_module ] [ -a ] [ Attribute=Value ... ] Name
To create the davis user account with the default values in the /usr/lib/security/mkuser.default file, type: # mkuser davis To create the davis account with davis as an administrator, type: # mkuser -a davis Only the root user or users with the UserAdmin authorization can create davis as an administrative user.
To create the davis user account and set the su attribute to a value of false, type: # mkuser su=false davis To create the davis user account that is identified and authenticated through the LDAP load module, type: # mkuser -R LDAP davis To add davis to the groups finance and accounting, enter: chuser groups=finance,accounting davis -- Add a user with the smit utility: -- --------------------------------Start SMIT by entering smit From the Main Menu, make the following selections: -Security and Users -Users -Add a User to the System The utility displays a form for adding new user information. Use the and keys to move through the form. Do not use until you are finished and ready to exit the screen. Fill in the appropriate fields of the Create User form (as listed in Create User Form) and press . The utility exits the form and creates the new user. -- Using SMIT to Create a Group: -- ----------------------------Use the following procedure to create a group. Start SMIT by entering the following command: smit The utility displays the Main Menu. From the Main Menu, make the following selections: -Security and Users -Users -Add a Group to the System The utility displays a form for adding new group information. Type the group name in the Group Name field and press . The group name must be eight characters or less. The utility creates the new group, automatically assigns the next available GID, and exits the form Primary Authentication method of system: ----------------------------------------
To check whether root has a primary authentication method of SYSTEM, use the following command: # lsuser -a auth1 root If needed, change the value by using # chuser auth1=SYSTEM root 3.4 Add a user in HP-UX: ------------------------- Example 1: Add user john to the system with all of the default attributes. # useradd john Add the user john to the system with a UID of 222 and a primary group of staff. # useradd -u 222 -g staff john -- Example 2: => => => => =>
Add a user called guestuser as per following requirements Primary group member of guests Secondary group member of www and accounting Shell must be /usr/bin/bash3 Home directory must be /home/guestuser
# useradd -g guests -G www,accounting -d /home/guests -s /home/guestuser/ -m guestuser # passwd guestuser
3.5 Add a user in Linux Redhat: ------------------------------You can use tools like useradd or groupadd to create new users and groups from the shell prompt. But an easier way to manage users and groups is through the graphical application, User Manager. Users are described in the /etc/passwd file Groups are stored on Red Hat Linux in the /etc/group file. Or invoke the Gnome Linuxconf GUI Tool by typing "linuxconf". In Red Hat Linux, linuxconf is found in the /bin directory.
================================ 4. Change filemode, permissions:
================================ Permissions are given to: u = user g = group o = other/world a = all file/directory permissions (or also called "filemodes") are: r = read w = write x = execute special modes are: X = sets execute if already set (this one is particularly sexy, look below) s = set setuid/setgid bit t = set sticky bit
Examples: --------readable by all, everyone % chmod a+r essay.001 to remove read write and execute permissions on the file biglist for the group and others % chmod go-rwx biglist make executable: % chmod +x mycommand set mode: % chmod 644 filename rwxrwxrwx=777 rw-rw-rw-=666 rw-r--r--=644 corresponds to umask 022 r-xr-xr-x=555 rwxrwxr-x=775 1 = execute 2 = write 4 = read note that the total is 7 execute and read are: 1+4=5 read and write are: 2+4=6 read, write and exec: 1+2+4=7 and so on directories must always be executable... so a file with, say 640, means, the owner can read and write (4+2=6), the group can read (4) and everyone else has no permission to use the file (0).
chmod -R a+X . This command would set the executable bit (for all users) of all directories and executables below the current directory that presently have an execute bit set. Very helpful when you want to set all your binary files executable for everyone other than you without having to set the executable bit of all your conf files, for instance. *wink* chmod -R g+w . This command would set all the contents below the current directory writable by your current group. chmod -R go-rwx This command would remove permissions for group and world users without changing the bits for the file owner. Now you don't have to worry that 'find . -type f -exec chmod 600 {}\;' will change your binary files non-executable. Further, you don't need to run an additional command to chmod your directories. chmod u+s /usr/bin/run_me_setuid This command would set the setuid bit of the file. It's simply easier than remembering which number to use when wanting to setuid/setgid, IMHO.
======================== 5. About the sticky bit: ======================== - This info is valid for most Unix OS including Solaris and AIX: ---------------------------------------------------------------A 't' or 'T' as the last character of the "ls -l" mode characters indicates that the "sticky" (save text image) bit is set. See ls(1) for an explanation the distinction between 't' and 'T'. The sticky bit has a different meaning, depending on the type of file it is set on... sticky bit on directories ------------------------[From chmod(2)] If the mode bit S_ISVTX (sticky bit) is set on a directory, files inside the directory may be renamed or removed only by the owner of the file, the owner of the directory, or the superuser (even if the modes of the directory would otherwise allow such an operation). [Example] drwxrwxrwt
104 bin
bin
14336 Jun
7 00:59 /tmp
Only root is permitted to turn the sticky bit on or off. In addition the sticky bit applies to anyone who accesses the file. The syntax for setting the sticky bit on a dir /foo
directory is as follows: chmod +t /foo sticky bit on regular files --------------------------[From chmod(2)] If an executable file is prepared for sharing, mode bit S_ISVTX prevents the system from abandoning the swap-space image of the program-text portion of the file when its last user terminates. Then, when the next user of the file executes it, the text need not be read from the file system but can simply be swapped in, thus saving time. [From HP-UX Kernel Tuning and Performance Guide] Local paging. When applications are located remotely, set the "sticky bit" on the applications binaries, using the chmod +t command. This tells the system to page the text to the local disk. Otherwise, it is "retrieved" across the network. Of course, this would only apply when there is actual paging occurring. More recently, there is a kernel parameter, page_text_to_local, which when set to 1, will tell the kernel to page all NFS executable text pages to local swap space. [Example] -r-xr-xr-t /usr/bin/vi
6 bin
bin
24111111111664 Nov 14
2000
Solaris: -------The sticky bit on a directory is a permission bit that protects files within that directory. If the directory has the sticky bit set, only the owner of the file, the owner of the directory, or root can delete the file. The sticky bit prevents a user from deleting other users' files from public directories, such as uucppublic: castle% ls -l /var/spool/uucppublic drwxrwxrwt 2 uucp uucp castle%
512 Sep 10 18:06 uucppublic
When you set up a public directory on a TMPFS temporary file system, make sure that you set the sticky bit manually. You can set sticky bit permissions by using the chmod command to assign the octal value 1 as the first number in a series of four octal values. Use the following steps to set the sticky bit on a directory: 1. If you are not the owner of the file or directory, become superuser. 2. Type chmod and press Return. 3. Type ls -l and press Return to verify that the permissions of the file have changed. The following example sets the sticky bit permission on the pubdir directory:
castle% chmod 1777 pubdir castle% ls -l pubdir drwxrwxrwt 2 winsor staff castle%
512 Jul 15 21:23 pubdir
================ 6. About SETUID: ================ Each process has three user ID's: the real user ID (ruid) the effective user ID (euid) and the saved user ID (suid) The real user ID identifies the owner of the process, the effective uid is used in most access control decisions, and the saved uid stores a previous user ID so that it can be restored later. Similar, a process has three group ID's. When a process is created by fork, it inherits the three uid's from the parent process. When a process executes a new file by exec..., it keeps its three uid's unless the set-user-ID bit of the new file is set, in which case the effective uid and saved uid are assigned the user ID of the owner of the new file. When setuid (set-user identification) permission is set on an executable file, a process that runs this file is granted access based on the owner of the file (usually root), rather than the user who created the process. This permission enables a user to access files and directories that are normally available only to the owner. The setuid permission is shown as an s in the file permissions. For example, the setuid permission on the passwd command enables a user to change passwords, assuming the permissions of the root ID are the following: castle% ls -l /usr/bin/passwd -r-sr-sr-x 3 root sys castle%
96796 Jul 15 21:23 /usr/bin/passwd
You setuid permissions by using the chmod command to assign the octal value 4 as the first number in a series of four octal values. Use the following steps to setuid permissions: 1. If you are not the owner of the file or directory, become superuser. 2. Type chmod and press Return. 3. Type ls -l and press Return to verify that the permissions of the file have changed. The following example sets setuid permission on the myprog file: #chmod 4555 myprog
-r-sr-xr-x #
1 winsor
staff
12796 Jul 15 21:23 myprog
The setgid (set-group identification) permission is similar to setuid, except that the effective group ID for the process is changed to the group owner of the file and a user is granted access based on permissions granted to that group. The /usr/bin/mail program has setgid permissions: castle% ls -l /usr/bin/mail -r-x�s�x 1 bin mail castle%
64376 Jul 15 21:27 /usr/bin/mail
When setgid permission is applied to a directory, files subsequently created in the directory belong to the group the directory belongs to, not to the group the creating process belongs to. Any user who has write permission in the directory can create a file there; however, the file does not belong to the group of the user, but instead belongs to the group of the directory. You can set setgid permissions by using the chmod command to assign the octal value 2 as the first number in a series of four octal values. Use the following steps to set setgid permissions: 1. If you are not the owner of the file or directory, become superuser. 2. Type chmod and press Return. 3. Type ls -l and press Return to verify that the permissions of the file have changed. The following example sets setuid permission on the myprog2 file: #chmod 2551 myprog2 #ls -l myprog2 -r-xr-s�x 1 winsor #
staff
26876 Jul 15 21:23 myprog2
========================= 7. Find command examples: ========================= Introduction The find command allows the Unix user to process a set of files and/or directories in a file subtree. You can specify the following: where to search (pathname) what type of file to search for (-type: directories, data files, links) how to process the files (-exec: run a process against a selected file) the name of the file(s) (-name) perform logical operations on selections (-o and -a) Search for file with a specific name in a set of files (-name) EXAMPLES
-------# find . -name "rc.conf" -print This command will search in the current directory and all sub directories for a file named rc.conf. Note: The -print option will print out the path of any file that is found with that name. In general -print wil print out the path of any file that meets the find criteria. # find . -name "rc.conf" -exec chmod o+r '{}' \; This command will search in the current directory and all sub directories. All files named rc.conf will be processed by the chmod -o+r command. The argument '{}' inserts each found file into the chmod command line. The \; argument indicates the exec command line has ended. The end results of this command is all rc.conf files have the other permissions set to read access (if the operator is the owner of the file). # find . -exec grep "www.athabasca" '{}' \; -print This command will search in the current directory and all sub directories. All files that contain the string will have their path printed to standard output. # find / -xdev -size +2048 -ls | sort -r +6 This command will find all files in the root directory larger than 1 MB. # find .
-exec grep "CI_ADJ_TYPE" {} \; -print
This command search all subdirs all files to find text CI_ADJ_TYPE Other examples: --------------# find . -name file -print # find / -name $1 -exec ls -l {} \; # find / -user nep -exec ls -l {} \; >nepfiles.txt In English: search from the root directory for any files owned by nep and execute an ls -l on the file when any are found. Capture all output in nepfiles.txt. # find $HOME -name \*.txt -print In order to protect the asterisk from being expanded by the shell, it is necessary to use a backslash to escape the asterisk as in: # find / -atime +30 -print This prints files that have not been accessed in the last 30 days # find / -atime +100 -size +500000c -print The find search criteria can be combined. This command will locate and list all files that were last accessed more than 100 days ago, and whose size exceeds 500,000 bytes.
# find /opt/bene/process/logs -name 'ALBRACHT*' # # # # # # # # # # # # # #
-mtime +90 -exec rm {} \;
find /example /new/example -exec grep -l 'Where are you' {} \; find / \( -name a.out -o -name '*.o' \) -atime +7 -exec rm {} \; find . -name '*.trc' -mtime +3 -exec rm {} \; find / -fsonly hfs -print cd /; find . ! -path ./Disk -only -print | cpio -pdxm /Disk cd /; find . -path ./Disk -prune -o -print | cpio -pdxm /Disk cd /; find . -xdev -print | cpio -pdm /Disk find -type f -print | xargs chmod 444 find -type d -print | xargs chmod 555 find . -atime +1 -name '*' -exec rm -f {} \; find /tmp -atime +1 -name '*' -exec rm -f {} \; find /usr/tmp -atime +1 -name '*' -exec rm -f {} \; find / -name core -exec rm -f {} \; find . -name "*.dbf" -mtime -2 -exec ls {} \;
* Search and list all files from current directory and down for the string ABC: find ./ -name "*" -exec grep -H ABC {} \; find ./ -type f -print | xargs grep -H "ABC" /dev/null egrep -r ABC * * Find all files of a given type from current directory on down: find ./ -name "*.conf" -print * Find all user files larger than 5Mb: find /home -size +5000000c -print * Find all files owned by a user (defined by user id number. see /etc/passwd) on the system: (could take a very long time) find / -user 501 -print * Find all files created or updated in the last five minutes: (Great for finding effects of make install) find / -cmin -5 * Find all users in group 20 and change them to group 102: (execute as root) find / -group 20 -exec chown :102 {} \; * Find all suid and setgid executables: find / \( -perm -4000 -o -perm -2000 \) -type f -exec ls -ldb {} \; find / -type f -perm +6000 -ls Example: -------cd /database/oradata/pegacc/archive archdir=`pwd` if [ $archdir=="/database/oradata/pegacc/archive" ] then find . -name "*.dbf" -mtime +5 -exec rm {} \; else echo "error in onderhoud PEGACC archives" >> /opt/app/oracle/admin/log/archmaint.log fi Example: -------The following example shows how to find files larger than 400 blocks in the
current directory: # find . -size +400 -print REAL COOL EXAMPLE: -----------------This example could even help in recovery of a file: In some rare cases a strangely-named file will show itself in your directory and appear to be un-removable with the rm command. Here is will the use of ls -li and find with its -inum [inode] primary does the job. Let's say that ls -l shows your irremovable as -rw-------
1 smith
smith
0 Feb
1 09:22 ?*?*P
Type: ls -li to get the index node, or inode. 153805 -rw-------
1 smith
smith
0 Feb
1 09:22 ?*?^P
The inode for this file is 153805. Use find -inum [inode] to make sure that the file is correctly identified. % find -inum 153805 -print ./?*?*P Here, we see that it is. Then used the -exec functionality to do the remove. . % find . -inum 153805 -print -exec /bin/rm {} \; Note that if this strangely named file were not of zero-length, it might contain accidentally misplaced and wanted data. Then you might want to determine what kind of data the file contains and move the file to some temporary directory for further investigation, for example: % find . -inum 153805 -print -exec /bin/mv {} unknown.file \; Will rename the file to unknown.file, so you can easily inspect it.
Note: difference betweeen mtime and atime: -----------------------------------------In using the find command where you want to delete files older than a certain date, you can use commands like find . -name "*.log" -mtime +30 -exec rm {} \; or find . -name "*.dbf" -atime +30 -exec rm {} \;
Why should you choose, or not choose, between atime and mtime? It is important to distinguish between a file or directory's change time (ctime), access time (atime), and modify time (mtime). ctime -- In UNIX, it is not possible to tell the actual creation time of a file. The ctime--change time-is the time when changes were made to the file or directory's inode (owner, permissions, etc.). The ctime is also updated when the contents of a file change. It is needed by the dump command to determine if the file needs to be backed up. You can view the ctime with the ls -lc command. atime -- The atime--access time--is the time when the data of a file was last accessed. Displaying the contents of a file or executing a shell script will update a file's atime, for example. mtime -- The mtime--modify time--is the time when the actual contents of a file was last modified. This is the time displayed in a long directoring listing (ls -l). Thats why backup utilities use the mtime when performing incremental backups: When the utility reads the data for a file that is to be included in a backup, it does not affect the file's modification time, but it does affect the file's access time. So for most practical reasons, if you want to delete logfiles (or other files) older than a certain date, its best to use the mtime attribute. How to make those times visible? "ls -l" "ls -lc" "ls -lm"
shows atime shows ctime shows mtime
"istat filename" will show all three. pago-am1:/usr/local/bb>istat bb18b3.tar.gz Inode 20 on device 10/9 File Protection: rw-r--r-Owner: 100(bb) Group: 100(bb) Link count: 1 Length 427247 bytes Last updated: Last modified: Last accessed:
Tue Aug 14 11:01:46 2001 Thu Jun 21 07:36:32 2001 Thu Nov 01 20:38:46 2001
=================== 7. Crontab command:
=================== Cron is uded to schedule or run periodically all sorts of executable programs or shell scripts, like backupruns, housekeeping jobs etc.. The crond daemon makes it all happen. Who has access to cron, is on most unixes determined by the "cron.allow" and "cron.deny" files. Every allowed user, can have it's own "crontab" file. The crontab of root, is typically used for system administrative jobs. On most unixes the relevant files can be found in: /var/spool/cron/crontabs or /var/adm/cron or /etc/cron.d For example, on Solaris the /var/adm/cron/cron.allow and /var/adm/cron/cron.deny files control which users can use the crontab command. Most common usage: - if you just want a listing: crontab -l - if you want to edit and change: crontab -e crontab [ -e | -l | -r | -v | File ] -e: edit, submit
-r remove, -l list
A crontab file contains entries for each cron job. Entries are separated by newline characters. Each crontab file entry contains six fields separated by spaces or tabs in the following form: minute
hour
day_of_month
month
0
0
*
8
weekday *
command /u/harry/bin/maintenance
Notes: -----Note 1: start and stop cron: ----------------------------- Solaris and some other unixes: The proper way to stop and restart cron are: # /etc/init.d/cron stop # /etc/init.d/cron start In Solaris 10 you could use the following command as well: # svcadm refresh cron # svcadm restart cron
-- Other way to restart cron: In most unixes, cron is started by init and there is a record in the /etc/initab file which makes that happen. Check if your system has indeed a record of cron in the inittab file. The type of start should be "respawn", which means that should the superuser do a "kill -9 crond", the cron daemon is simply restarted again. Again, preferrably, there should be a stop and start script to restart cron. Especially on AIX, there is no true way to restart cron in a neat way. Not via the Recourse Control startscr command, or script, a standard method is available. Just kill crond and it will be restarted. -- On many linux distros: to restart the cron daemon, you could do either a "service crond restart" or a "service crond reload". Note 2: ------Create a cronjobs file You can do this on your local computer in Notepad or you can create the file directly on your Virtual Server using your favorite UNIX text editor (pico, vi, etc). Your file should contain the following entries: MAILTO="
[email protected]" 0 1 1 1-12/3 * /usr/local/bin/vnukelog This will run the command "/usr/local/bin/vnukelog" (which clears all of your log files) at 1 AM on the first day of the first month of every quarter, or January, April, July, and October (1-12/3). Obviously, you will need to substitute a valid e-mail address in the place of "
[email protected]". If you have created this file on your local computer, FTP the file up to your Virtual Server and store it in your home directory under the name "cronjobs" (you can actually use any name you would like). Register your cronjobs file with the system After you have created your cronjobs file (and have uploaded it to your Virtual Server if applicable), you need to Telnet to your server and register the file with the cron system daemon. To do this, simply type: crontab cronjobs Or if you used a name other than "cronjobs", substitute the name you selected for the occurrence of "cronjobs" above.
Note 3: ------# use /bin/sh to run commands, no matter what /etc/passwd says SHELL=/bin/sh # mail any output to `paul', no matter whose crontab this is MAILTO=paul # # run five minutes after midnight, every day 5 6-18 * * * /opt/app/oracle/admin/scripts/grepora.sh # run at 2:15pm on the first of every month -- output mailed to paul 15 14 1 * * $HOME/bin/monthly # run at 10 pm on weekdays, annoy Joe 0 22 * * 1-5 mail -s "It's 10pm" joe%Joe,%%Where are your kids?% 23 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., everyday" 5 4 * * sun echo "run at 5 after 4 every sunday" 2>&1 means: It means that standard error is redirected along with standard output. Standard error could be redirected to a different file, like ls > toto.txt 2> error.txt If your shell is csh or tcsh, you would redirect standard output and standard error like this lt >& toto.txt Csh or tcsh cannot redirect standard error separately. Note 4: ------thread Q: > > > >
Isn't there a way to refresh cron to pick up changes made using crontab -e? I made the changes but the specified jobs did not run. I'm thinking I need to refresh cron to pick up the changes. Is this true? Thanks.
A: Crontab -e should do that for you, that's the whole point of using it rather than editing the file yourself. Why do you think the job didn't run? Post the crontab entry and the script. Give details of the version of Tru64 and the patch level. Then perhaps we can help you to figure out the real cause of the problem. Hope this helps A: I have seen the following problem when editing the cron file for another user: crontab -e idxxxxxx This changed the control file, when I verified with crontab -l the contents was correctly shown,
but the cron daemon did not execute the new contents. To solve the problem, I needed to follow the following commands: su - idxxxxxx crontab -l |crontab This seems to work ... since then I prefer the following su - idxxxxxx crontab -e which seems to work also ... Note 5: ------On AIX it is observed, that if the "daemon=" attribute of a user is set to be false, this user cannot use crontab, even if the account is placed in cron.allow. You need to set the attribute to "daemon=true". * daemon *
Defines whether the user can execute programs using the system resource controller (SRC). Possible values: true or false.
Note 6: ------If you want to quick test the crontab of a user: su - user and put the following in the crontab of that user: * * * * *
date >/tmp/elog
=========================== 8. Job control, background: =========================== To put a sort job (or other job) in background: # sort < foo > bar & To show jobs: # jobs To show processes: # ps # ps -ef | grep ora Job in foreground -> background: Ctrl-Z (suspend) #bg or bg jobID
Job in background -> foreground: # fg %jobid Stop a process: # kill -9 3535
(3535 is the pid, process id)
Stop a background process you may try this: # kill -QUIT 3421 -- Kill all processes of a specific users: -- --------------------------------------To kill all processes of a specific user, enter: # ps -u [user-id] -o pid | grep -v PID | xargs kill -9 Another Use who related # fuser
way: to check out your current users and their terminals. Kill all processes to a specific terminal: -k /dev/pts[#]
Yet another method: Su to the user-id you wish to kill all processes of and enter: # su - [user-id] -c kill -9 -1 Or su - to that userid, and use the killall command, which is available on most unix'es, like for example AIX. # killall The nohup command: -----------------When working with the UNIX operating system, there will be times when you will want to run commands that are immune to log outs or unplanned login session terminations. This is especially true for UNIX system administrators. The UNIX command for handling this job is the nohup (no hangup) command. Normally when you log out, or your session terminates unexpectedly, the system will kill all processes you have started. Starting a command with nohup counters this by arranging for all stopped, running, and background jobs to ignore the SIGHUP signal. The syntax for nohup is: nohup command [arguments] You may optionally add an ampersand to the end of the command line to run the job in the background: nohup command [arguments] & If you do not redirect output from a process kicked off with nohup, both standard output (stdout) and standard error (stderr) are sent to a file named nohup.out. This file will be created in $HOME (your home directory) if it cannot be created in the working directory. Real-time monitoring of what is being written to nohup.out can be accomplished with the "tail -f nohup.out" command.
Although the nohup command is extremely valuable to UNIX system administrators, it is also a must-know tool for others who run lengthy or critical processes on UNIX systems The nohup command runs the command specified by the Command parameter and any related Arg parameters, ignoring all hangup (SIGHUP) signals. Use the nohup command to run programs in the background after logging off. To run a nohup command in the background, add an & (ampersand) to the end of the command. Whether or not the nohup command output is redirected to a terminal, the output is appended to the nohup.out file in the current directory. If the nohup.out file is not writable in the current directory, the output is redirected to the $HOME/nohup.out file. If neither file can be created nor opened for appending, the command specified by the Command parameter is not invoked. If the standard error is a terminal, all output written by the named command to its standard error is redirected to the same file descriptor as the standard output. To run a command in the background after you log off, enter: $ nohup find / -print & After you enter this command, the following is displayed: 670 $ Sending output to nohup.out The process ID number changes to that of the background process started by & (ampersand). The message Sending output to nohup.out informs you that the output from the find / -print command is in the nohup.out file. You can log off after you see these messages, even if the find command is still running. Example of ps -ef on a AIX5 system: [LP 1]root@ol16u209:ps -ef UID PID PPID C STIME TTY TIME root 1 0 0 Oct 17 - 0:00 root 4198 1 0 Oct 17 - 0:00 root 5808 1 0 Oct 17 - 1:15 oracle 6880 1 0 10:27:26 - 0:00 root 6966 1 0 Oct 17 - 0:00 root 7942 43364 0 Oct 17 - 0:00 alberts 9036 9864 0 20:41:49 - 0:00 root 9864 44426 0 20:40:21 - 0:00 root 27272 36280 1 20:48:03 pts/0 0:00 oracle 27856 1 0 10:27:26 - 0:01 oracle 31738 1 0 10:27:26 - 0:00 oracle 31756 1 0 10:27:26 - 0:00 alberts 32542 9036 0 20:41:49 pts/0 0:00 maestro 33480 34394 0 05:59:45 - 0:00 -parm 32000 root 34232 33480 0 05:59:45 - 0:00 maestro 34394 45436 0 05:59:45 - 0:00 -parm 32000 -- 2002 OL16U209 CONMAN UNIX 6.
CMD /etc/init /usr/lib/errdemon /usr/sbin/syncd 60 ora_lgwr_SPLDEV1 /usr/ccs/bin/shlap sendmail: accepting connections sshd: alberts@pts/0 sshd: alberts [priv] ps -ef ora_smon_SPLDEV1 ora_dbw0_SPLDEV1 ora_reco_SPLDEV1 -ksh /prj/maestro/maestro/bin/batchman /prj/maestro/maestro/bin/jobman /prj/maestro/maestro/bin/mailman
root 34708 1 0 13:55:51 lft0 0:00 /usr/sbin/getty /dev/console oracle 35364 1 0 10:27:26 - 0:01 ora_cjq0_SPLDEV1 oracle 35660 1 0 10:27:26 - 0:04 ora_pmon_SPLDEV1 root 36280 32542 0 20:45:06 pts/0 0:00 -ksh root 36382 43364 0 Oct 17 - 0:00 /usr/sbin/rsct/bin/IBM.ServiceRMd root 36642 43364 0 Oct 17 - 0:00 /usr/sbin/rsct/bin/IBM.CSMAgentRMd root 36912 43364 0 Oct 17 - 0:03 /usr/opt/ifor/bin/i4lmd -l /var/ifor/logdb -n clwts root 37186 43364 0 Oct 17 - 0:00 /etc/ncs/llbd root 37434 43364 0 Oct 17 - 0:17 /usr/opt/ifor/bin/i4llmd -b -n wcclwts -l /var/ifor/llmlg root 37738 37434 0 Oct 17 - 0:00 /usr/opt/ifor/bin/i4llmd -b -n wcclwts -l /var/ifor/llmlg root 37946 1 0 Oct 17 - 0:00 /opt/hitachi/HNTRLib2/bin/hntr2mon -d oracle 38194 1 0 Oct 17 - 0:00 /prj/oracle/product/9.2.0.3/bin/tnslsnr LISTENER -inherit root 38468 43364 0 Oct 17 - 0:00 /usr/sbin/rsct/bin/IBM.AuditRMd root 38716 1 0 Oct 17 - 0:00 /usr/bin/itesmdem itesrv.ini /etc/IMNSearch/search/ imnadm 39220 1 0 Oct 17 - 0:00 /usr/IMNSearch/httpdlite/httpdlite -r /etc/IMNSearch/httpdlite/httpdlite.con root 39504 36912 0 Oct 17 - 0:00 /usr/opt/ifor/bin/i4lmd -l /var/ifor/logdb -n clwts root 39738 43364 0 Oct 17 - 0:01 /usr/DynamicLinkManager/bin/dlmmgr root 40512 43364 0 Oct 17 - 0:01 /usr/sbin/rsct/bin/rmcd -r root 40784 43364 0 Oct 17 - 0:00 /usr/sbin/rsct/bin/IBM.ERrmd root 41062 1 0 Oct 17 - 0:00 /usr/sbin/cron was 41306 1 0 Oct 17 - 2:10 /prj/was/java/bin/java -Xmx256m -Dwas.status.socket=32776 -Xms50m -Xbootclas oracle 42400 1 0 10:27:26 - 0:02 ora_ckpt_SPLDEV1 root 42838 1 0 Oct 17 - 0:00 /usr/sbin/uprintfd root 43226 43364 0 Oct 17 - 0:00 /usr/sbin/nfsd 3891 root 43364 1 0 Oct 17 - 0:00 /usr/sbin/srcmstr root 43920 43364 0 Oct 17 - 0:00 /usr/sbin/aixmibd root 44426 43364 0 Oct 17 - 0:00 /usr/sbin/sshd -D root 44668 43364 0 Oct 17 - 0:00 /usr/sbin/portmap root 44942 43364 0 Oct 17 - 0:00 /usr/sbin/snmpd root 45176 43364 0 Oct 17 - 0:00 /usr/sbin/snmpmibd maestro 45436 1 0 Oct 17 - 0:00 /prj/maestro/maestro/bin/netman root 45722 43364 0 Oct 17 - 0:00 /usr/sbin/inetd root 45940 43364 0 Oct 17 - 0:00 /usr/sbin/muxatmd root 46472 43364 0 Oct 17 - 0:00 /usr/sbin/hostmibd root 46780 43364 0 Oct 17 - 0:00 /etc/ncs/glbd root 46980 43364 0 Oct 17 - 0:00 /usr/sbin/qdaemon root 47294 1 0 Oct 17 - 0:00 /usr/local/sbin/syslog-ng -f /usr/local/etc/syslog-ng.conf root 47484 43364 0 Oct 17 - 0:00 /usr/sbin/rpc.lockd daemon 48014 43364 0 Oct 17 - 0:00 /usr/sbin/rpc.statd root 48256 43364 0 Oct 17 - 0:00 /usr/sbin/rpc.mountd root 48774 43364 0 Oct 17 - 0:00 /usr/sbin/biod 6 root 49058 43364 0 Oct 17 - 0:00 /usr/sbin/writesrv [LP 1]root@ol16u209: Another example of ps -ef on a AIX5 system: # ps -ef
UID PID PPID C STIME root 1 0 0 Jan 23 root 69706 1 0 Jan 23 root 81940 1 0 Jan 23 root 86120 1 2 Jan 23 root 98414 1 0 Jan 23 root 114802 81940 0 Jan 23 /usr/sbin/rsct/bin/IBM.CSMAgentRMd root 135366 81940 0 Jan 23 root 139446 81940 0 Jan 23 root 143438 1 0 Jan 23 root 147694 1 0 Jan 23 root 155736 1 0 Jan 23 /usr/local/etc/syslog-ng.conf root 163996 81940 0 Jan 23 root 180226 81940 0 Jan 23 /usr/sbin/rsct/bin/IBM.ServiceRMd root 184406 81940 0 Jan 23 root 200806 1 0 Jan 23 /opt/hitachi/HNTRLib2/bin/hntr2mon -d root 204906 81940 0 Jan 23 root 217200 1 0 Jan 23 root 221298 81940 0 Jan 23 /usr/DynamicLinkManager/bin/dlmmgr root 614618 1 0 Apr 03 reserve 1364024 1548410 0 07:10:10 root 1405140 1626318 1 08:01:38 root 1511556 614618 2 07:45:52 reserve 1548410 1613896 0 07:10:10 root 1613896 135366 0 07:10:01 root 1626318 1364024 1 07:19:13
TTY TIME CMD - 0:33 /etc/init - 0:00 /usr/lib/errdemon - 0:00 /usr/sbin/srcmstr - 236:39 /usr/sbin/syncd 60 - 0:00 /usr/ccs/bin/shlap64 - 0:32 -
0:00 0:07 0:00 0:26 0:00
-
0:00 /usr/sbin/rsct/bin/IBM.ERrmd 0:00
-
0:00 /usr/sbin/qdaemon 0:08
-
0:00 /usr/sbin/rsct/bin/IBM.AuditRMd 0:00 ./mflm_manager 1:41
lft0 pts/0 pts/0 lft0 pts/0
0:00 0:00 0:00 0:41 0:00 0:00 0:00
/usr/sbin/sshd -D /usr/sbin/rsct/bin/rmcd -r /usr/sbin/uprintfd /usr/sbin/cron /usr/local/sbin/syslog-ng -f
-ksh -ksh ps -ef tar -cf /dev/rmt1.1 /spl sshd: reserve@pts/0 sshd: reserve [priv] -ksh
Some more examples: # nohup somecommand & sleep 1; tail -f preferred-name # nohup make bzImage & # tail -f nohup.out # nohup make modules 1> modules.out 2> modules.err & # tail -f modules.out
========================================== 9. Backup commands, TAR, and Zipped files: ========================================== For SOLARIS as well as AIX, the following commands can be used: tar, cpio, dd, gzip/gunzip, compress/uncompress, backup and restore 9.1 tar: Short for �Tape Archiver�: ===================================
Some examples should explain the usage of "tar" to create backups, or to create easy to transport .tar files. Create a backup to tape device 0hc of file sys01.dbf # tar -cvf /dev/rmt/0hc /u01/oradata/sys01.dbf # tar -rvf /dev/rmt/0hc /u02/oradata/data_01.dbf -c -r -x -v -t
create append extract verbose list
Extract the contents of example.tar and display the files as they are extracted. # tar -xvf example.tar Create a tar file named backup.tar from the contents of the directory /home/ftp/pub # tar -cf backup.tar /home/ftp/pub list contents of example.tar to the screen # tar -tvf example.tar to restore the file /home/bcalkins/.profile from the archive: - First we do a backup: # tar -cvf /dev/rmt/0 /home/bcalkins - And later we do a restore: # tar -xcf /dev/rmt/0 /home/bcalkins/.profile If you use an absolute path, you can only restore in "a like" destination directory. If you use a relative path, you can restore in any directory. In this case, use tar with a relative pathname, for example if you want to backup /home/bcalkins change to that directory and use # tar -cvf backup_oracle_201105.tar ./* To extract the directory conv: # tar -xvf /dev/rmt0 /u02/oradata/conv Example: -------mt -f /dev/rmt1 rewind mt -f /dev/rmt1.1 fsf 6 tar -xvf /dev/rmt1.1 /data/download/expdemo.zip
Most common errors messages with tar: -------------------------------------- 0511-169: A directory checksum error on media: MediaName not equal to Number Possible Causes
From the command line, you issued the tar command to extract files from an archive that was not created with the tar command. -- 0511-193: An error occurred while reading from the media Possible Causes You issued the tar command to read an archive from a tape device that has a different block size than when the archive was created. Solution: # chdev -l rmt0 -a block_size=0 -- File too large:
Extra note of tar command on AIX: --------------------------------If you need to backup multiple large mountpoints to a large tape, you might think you can use something like: tar tar tar tar tar tar tar tar tar tar tar
-cvf -rvf -rvf -rvf -rvf -rvf -rvf -rvf -rvf -rvf -rvf
/dev/rmt1 /dev/rmt1 /dev/rmt1 /dev/rmt1 /dev/rmt1 /dev/rmt1 /dev/rmt1 /dev/rmt1 /dev/rmt1 /dev/rmt1 /dev/rmt1
/spl /prj /opt /usr /data /backups /u01/oradata /u02/oradata /u03/oradata /u04/oradata /u05/oradata
Actually on AIX this is not OK. The tape will rewind after each tar command, effectively you will end up with ONLY the last backupstatement. You should use the non-rewinding class instead, like for example: tar -cf /dev/rmt1.1 /spl tar -cf /dev/rmt1.1 /apps tar -cf /dev/rmt1.1 /prj tar -cf /dev/rmt1.1 /software tar -cf /dev/rmt1.1 /opt tar -cf /dev/rmt1.1 /usr tar -cf /dev/rmt1.1 /data tar -cf /dev/rmt1.1 /backups #tar -cf /dev/rmt1.1 /u01/oradata #tar -cf /dev/rmt1.1 /u02/oradata #tar -cf /dev/rmt1.1 /u03/oradata #tar -cf /dev/rmt1.1 /u04/oradata #tar -cf /dev/rmt1.1 /u05/oradata
Use this table to decide on which class to use: The following table shows the names of the rmt special files and their characteristics. Special File /dev/rmt* /dev/rmt*.1 /dev/rmt*.2 /dev/rmt*.3 /dev/rmt*.4 /dev/rmt*.5 /dev/rmt*.6 /dev/rmt*.7
Rewind on Close Retension on Open Density Setting Yes No #1 No No #1 Yes Yes #1 No Yes #1 Yes No #2 No No #2 Yes Yes #2 No Yes #2
To restore an item from a logical tape, use commands as in the following example: mt -f /dev/rmt1 rewind mt -f /dev/rmt1.1 fsf 2
in order to put the pointer to the beginning of block 3.
mt -f /dev/rmt1.1 fsf 7
in order to put the pointer to the beginning of block 8.
Now you can use a command like for example: tar -xvf /dev/rmt1.1 /backups/oradb/sqlnet.log Another example: mt -f /dev/rmt1 rewind mt -f /dev/rmt1.1 fsf 8 tar -xvf /dev/rmt1.1 /u01/oradata/spltrain/temp01.dbf
Example Backupscript on AIX: ---------------------------#!/usr/bin/ksh # # # #
BACKUP-SCRIPT SPL SERVER PSERIES 550 DIT IS DE PRIMAIRE BACKUP, NAAR DE TAPEROBOT RMT1. OPMERKING: ER LOOPT NAAST DEZE BACKUP, OOK NOG EEN BACKUP VAN DE /backup DISK NAAR DE INTERNE TAPEDRIVE RMT0.
# OMDAT WE NOG NIET GEHEEL IN BEELD HEBBEN OF WE VOORAF DE BACKUP APPLICATIES MOETEN # STOPZETTEN, IS DIT SCRIPT NOG IN REVISIE. # VERSIE: 0.1 # DATUM : 27-12-2005 # DOEL VAN HET SCRIPT: # - STOPPEN VAN DE APPLICATIES # - VERVOLGENS BACKUP NAAR TAPE # - STARTEN VAN DE APPLICATIES
# CONTROLEER VOORAF OF DE TAPELIBRARY GELADEN IS VIA "/opt/backupscripts/load_lib.sh" BACKUPLOG=/opt/backupscripts/backup_to_rmt1.log export BACKUPLOG DAYNAME=`date +%a`;export DAYNAME DAYNO=`date +%d`;export DAYNO ######################################## # 1. REGISTRATIE STARTTIJD IN EEN LOG # ######################################## echo "-----------------" >> ${BACKUPLOG} echo "Start Backup 550:" >> ${BACKUPLOG} date >> ${BACKUPLOG} ######################################## # 2. STOPPEN APPLICATIES # ######################################## #STOPPEN VAN ALLE ORACLE DATABASES su - oracle -c "/opt/backupscripts/stop_oracle.sh" sleep 30 #STOPPEN VAN WEBSPHERE cd /prj/was/bin ./stopServer.sh server1 -username admin01 -password vga88nt sleep 30 #SHUTDOWN ETM instances: su - cissys -c '/spl/SPLDEV1/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLDEV2/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLCONF/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLPLAY/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLTST3/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLTST1/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLTST2/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLDEVP/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLPACK/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLDEVT/bin/splenviron.sh sleep 2
#STOPPEN SSH DEMON
-e SPLDEV1 -c "spl.sh -t stop"' -e SPLDEV2 -c "spl.sh -t stop"' -e SPLCONF -c "spl.sh -t stop"' -e SPLPLAY -c "spl.sh -t stop"' -e SPLTST3 -c "spl.sh -t stop"' -e SPLTST1 -c "spl.sh -t stop"' -e SPLTST2 -c "spl.sh -t stop"' -e SPLDEVP -c "spl.sh -t stop"' -e SPLPACK -c "spl.sh -t stop"' -e SPLDEVT -c "spl.sh -t stop"'
stopsrc -s sshd sleep 2 date >> /opt/backupscripts/running.log who >> /opt/backupscripts/running.log ######################################## # 3. BACKUP COMMANDS # ######################################## case $DAYNAME in Tue) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; Wed) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; Thu) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; Fri) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; Sat) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; Mon) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; esac
move 256 4116 4101 256 move 256 4117 4100 256 move 256 4118 4099 256 move 256 4119 4098 256 move 256 4120 4097 256 move 256 4121 4096 256
sleep 50 echo "Starten van de backup zelf" >> ${BACKUPLOG} mt -f /dev/rmt1 rewind tar -cf /dev/rmt1.1 /spl tar -cf /dev/rmt1.1 /apps tar -cf /dev/rmt1.1 /prj tar -cf /dev/rmt1.1 /software tar -cf /dev/rmt1.1 /opt tar -cf /dev/rmt1.1 /usr tar -cf /dev/rmt1.1 /data tar -cf /dev/rmt1.1 /backups tar -cf /dev/rmt1.1 /u01/oradata tar -cf /dev/rmt1.1 /u02/oradata tar -cf /dev/rmt1.1 /u03/oradata tar -cf /dev/rmt1.1 /u04/oradata tar -cf /dev/rmt1.1 /u05/oradata tar -cf /dev/rmt1.1 /u06/oradata tar -cf /dev/rmt1.1 /u07/oradata tar -cf /dev/rmt1.1 /u08/oradata tar -cf /dev/rmt1.1 /home tar -cf /dev/rmt1.1 /backups3 sleep 10
# TIJDELIJKE ACTIE date >> /opt/backupscripts/running.log ps -ef | grep pmon >> /opt/backupscripts/running.log ps -ef | grep BBL >> /opt/backupscripts/running.log ps -ef | grep was >> /opt/backupscripts/running.log who >> /opt/backupscripts/running.log defragfs /prj # EIND TIJDELIJKE ACTIE ######################################## # 4. STARTEN APPLICATIES # ######################################## #STARTEN SSH DEMON startsrc -s sshd sleep 2 #STARTEN VAN ALLE ORACLE DATABASES su - oracle -c "/opt/backupscripts/start_oracle.sh" sleep 30 #STARTEN ETM instances: su - cissys -c '/spl/SPLDEV1/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLDEV2/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLCONF/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLPLAY/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLTST3/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLTST1/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLTST2/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLDEVP/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLPACK/bin/splenviron.sh sleep 2 su - cissys -c '/spl/SPLDEVT/bin/splenviron.sh sleep 2
-e SPLDEV1 -c "spl.sh -t start"' -e SPLDEV2 -c "spl.sh -t start"' -e SPLCONF -c "spl.sh -t start"' -e SPLPLAY -c "spl.sh -t start"' -e SPLTST3 -c "spl.sh -t start"' -e SPLTST1 -c "spl.sh -t start"' -e SPLTST2 -c "spl.sh -t start"' -e SPLDEVP -c "spl.sh -t start"' -e SPLPACK -c "spl.sh -t start"' -e SPLDEVT -c "spl.sh -t start"'
#STARTEN VAN WEBSPHERE cd /prj/was/bin ./startServer.sh server1 -username admin01 -password vga88nt sleep 30 ######################################## # 5. REGISTRATIE EINDTIJD IN EEN LOG # ######################################## #Laten we het tapenummer en einddtijd registreren in de log:
tapeutil -f /dev/smc0 inventory | head -88 | tail -2
>> ${BACKUPLOG}
echo "Einde backup 550:" >> ${BACKUPLOG} date >> ${BACKUPLOG}
9.2 compress and uncompress: ============================ # compress -v bigfile.exe Would compress bigfile.exe and rename that file to bigfile.exe.Z. # uncompress *.Z would uncompress the files *.Z 9.3 gzip: ========= To compress a file using gzip, execute the following command: # gzip filename.tar This will become filename.tar.gz To decompress: # gzip -d filename.tar.gz # gunzip filename.tar.gz # gzip �d users.dbf.gz 9.4 bzip2: ========== #bzip2 filename.tar This will become filename.tar.bz2 9.5 dd: ======= Solaris: -------# dd if= of= to duplicate a tape: # dd if=/dev/rmt/0 of=/dev/rmt/1 to clone a disk with the same geometry: # dd if=/dev/rdsk/c0t1d0s2 of=/dev/rdsk/c0t4d0s2 bs=128 AIX:
---same command syntax apply to IBM AIX. Here is an AIX pSeries machine with floppydrive example: clone a diskette: # dd if=/dev/fd0 of=/tmp/ddcopy # dd if=/tmp/ddcopy of=/dev/fd0 Note: On Linux distros the device associated to the floppy drive is also /dev/fd0 9.6 cpio: ========= solaris: -------cpio copy-out: cpio -o copy_in : cpio -i pass : cpio -p # # # #
cd /var/bigspace cpio -idmv Linux9i_Disk1.cpio.gz cpio -idmv Linux9i_Disk2.cpio.gz cpio -idmv Linux9i_Disk3.cpio.gz
#
cpio -idmv < 9204_solaris_release.cpio
# cd /work # ls -R | cpio -ocB > /dev/rmt/0 # cd /work # cpio -icvdB < /dev/rmt/0 d c v c
will create directories as needed will create header information in ascii format for portability verbose character heading in file
AIX: ---AIX uses the same syntax. Usually, you should use the following command: # cpio -idmv < filename.cpio Copying directories with cpio: -----------------------------cpio is very good in cloning directories, or making backups, because it copies files and directories
inclusive their ownership and permissions. Example: -------Just cd to the directory that you want to clone and use a command similar to the following examples. # find . -print | cpio -pdl /u/disk11/jdoe/fiber # find . -print | cpio -pdm /a/dev # find . -print | cpio -pdl /home/jim/newdir # find . -print | cpio -pdmv /backups2/CONV2-0212 # find . -print | cpio -pdmv /backups2/SPLcobAS40 # find . -print | cpio -pdmv /backups2/SPLcobAS40sp2 # find . -print | cpio -pdmv /backups2/runtime/SPLTST2 The p in the flags, stands for pass-through cd /spl/SPLDEV1 find . -print | cpio -pdmv /spl/SPLDEVT find . -print | cpio -pdmv /backups2/data # find # find # find # find find .
. -print . -print . -print . -print -print |
| cpio -pdmv /data/documentum/dmadmin/backup_1008/dba_cluster | cpio -pdmv /data/documentum/dmadmin/backup_1008/dmw_et3 | cpio -pdmv /data/documentum/dmadmin/backup_1008/dmw_et | cpio -pdmv /data/documentum/dmadmin/backup_1508/dmw_eu cpio -pdmv /data/emcdctm/home2
find . -print | cpio -pdmv /data/documentum/dmadmin/backup_1809/dmw_et find . -print | cpio -pdmv /data/documentum/dmadmin/backup_1809/dmw_et3
find find find find
. . . .
-print -print -print -print
| | | |
cpio cpio cpio cpio
-pdmv -pdmv -pdmv -pdmv
/data/documentum/dmadmin/appl/l13appl /data/documentum/dmadmin/appl/l14appl /data/documentum/dmadmin/backup_3110/dmw_et /appl/emcdctm/dba_save_311007
Example: -------Use cpio copy-pass to copy a directory structure to another location: # find path -depth -print | cpio -pamVd /new/parent/dir Example: --------
Become superuser or assume an equivalent role. Change to the appropriate directory. # cd filesystem1 Copy the directory tree from filesystem1 to filesystem2 by using a combination of the find and cpio commands. # find . -print -depth | cpio -pdm filesystem2 Example: -------Copying directories Both cpio and tar may be used to copy directories while preserving ownership, permissions, and directory structure. cpio example: cd fromdir find . | cpio -pdumv todir tar example: cd fromdir; tar cf - . | (cd todir; tar xfp -) tar example over a compressed ssh tunnel: tar cvf - fromdir | gzip -9c | ssh user@host 'cd todir; gzip -cd | tar xpf -' Errors: ------Errors sometimes found with cpio: cpio: 0511-903 cpio: 0511-904 1.Try using with -c option: cpio -imdcv < filename.cpio
9.7 the pax command: ==================== Same for AIX and SOLARIS. The pax utility supports several archive formats, including tar and cpio. The syntax for the pax command is as follows: pax -r: Read mode .when -r is specified, pax extracts the filenames and directories found in the archive. The archive is read from disk or tape. If an extracted file is a directory, the hierarchy is extracted as well. The extracted files are created relative to the current directory.
None: List mode. When neither -r or -w is specified, pax displays the filenames and directories found in the archive file. The list is written to standard output. -w: Write mode. If you want to create an archive, you use -w. Pax writes the contents of the file to the standard output in an archive format specified by the -x option. -rw: Copy mode. When both -r and -w are specified, pax copies the specified files to the destination directory. most important options: -a = append to the end of an existing archive -b = block size, multiple of 512 bytes -c = you can specify filepatterns -f = specifies the pathname of the input or output archive -p = aemo a does not preserve file access time e preserve everything: user id, group id, filemode bits, etc.. m does not preserve file modification times o preserve uid and gid P preserve filemode bits -x = specifies the archive format. Examples: To copy current directory contents to tape, use -w mode and -f # pax -w -f /dev/rmt0 To list a verbose table of contents stored on tape rmt0, use None mode and f # pax -v -f /dev/rmt0 9.8 pkzip25: ============ PKZIP Usage: Usage: pkzip25 [command] [options] zipfile [@list] [files...] Examples: View .ZIP file contents: pkzip25 zipfile Create a .ZIP file: pkzip25 -add zipfile file(s)... Extract files from .ZIP: pkzip25 -extract zipfile These are only basic examples of PKZIP's capability About "-extract" switch: extract extract files from a .ZIP file. Its a configurable switch.
-- all - all files in .ZIP file -- freshen - only files in the .ZIP file that exist in the target directory and that are "newer" than those files will be extracted -- update - files in the .ZIP file which already exist in the target directory and that are "newer" than those files as well as files that are "not" in the target directory will be extracted default = all Example: # pkzip25 -ext=up save.zip
9.9 SOLARIS: ufsdump and ufsrestore: ==================================== level 0 is an full backup, 1-9 are incremental backups Examples: --------# ufsdump 0ucf /dev/rmt/0 /users # ufsdump 0ucf sparc1:/dev/rmt/0 /export/home # ufsrestore f /dev/rmt/0 filename # ufsrestore rf sparc1:/dev/rmt/0 filename 9.10 AIX: mksysb: ================ The mksysb command creates an installable image of the rootvg. This is synonym to say that mksysb creates a backup of the operating system (that is, the root volume group). You can use this backup to reinstall a system to its original state after it has been corrupted. If you create the backup on tape, the tape is bootable and includes the installation programs needed to install from the backup. To generate a system backup and create an /image.data file (generated by the mkszfile command) to a tape device named /dev/rmt0, type: # mksysb -i /dev/rmt0 To generate a system backup and create an /image.data file with map files (generated by the mkszfile command) to a tape device named /dev/rmt1, type: # mksysb -m /dev/rmt1 To generate a system backup with a new /image.data file, but exclude the files in directory /home/user1/tmp,
create the file "/etc/exclude.rootvg" containing the line /home/user1/tmp/, and type: # mksysb -i -e /dev/rmt1 This command will backup the /home/user1/tmp directory but not the files it contains. To generate a system backup file named /mksysb_images/node1 and a new /image.data file for that image, type: # mksysb -i /userimage/node1 There will be four images on the mksysb tape, and the fourth image will contain ONLY rootvg JFS or JFS2 mounted file systems. The target tape drive must be local to create a bootable tape. The following is a description of mksysb's four images. +---------------------------------------------------------+ | Bosboot | Mkinsttape | Dummy TOC | rootvg | | Image | Image | Image | data | |-----------+--------------+-------------+----------------| || Blksz defined | | | by the device | +---------------------------------------------------------+
Special notes: -------------Note 1: mksysb problem ---------------------Question: I'm attempting to restore a mksysb tape to a system that only has 18GB of drive space available for the Rootvg. Does the mksysb try to restore these mirrored LVs, or does it just make one copy? If it is trying to rebuild the mirror, is there a way that I can get around that? Answer: I had this same problem and received a successful resolution. I place those same tasks here: 1) Create a new image.data file, run mkszfile file. 2) Change the image.data as follows: a) cd / b) vi image.data c) In each lv_data stanza of this file, change the values of the copies line by one-half (i.e. copies = 2, change to copies = 1) Also, change the number of Physical Volumes "hdisk0 hdisk1" to "hdisk0". d) Save this file. 3) Create another mksysb from the command line that will utilize the newly edited image.data file by the command: mksysb /dev/rmt0 (Do not use smit and do not run with the -i flag, both will generate a new image.data file 4) Use this new mksysb to restore your system on other box without mirroring.
Note 2: How to restore specific files from a mksysb tape: --------------------------------------------------------$ tctl fsf 3 $ restore -xvf /dev/rmt0.1 ./your/file/name For example, if you need to get the vi command back, put the mksysb tape in the tape drive (in this case, /dev/rmt0) and do the following: cd /
# get to the root directory
tctl -f /dev/rmt0 rewind
# rewind the tape
tctl -f /dev/rmt0.1 fsf 3
# move the tape to the third file, no rewind
restore -xqf /dev/rmt0.1 -s 1 ./usr/bin/vi
# extract the vi binary, no rewind
Further explanation why you must use the fsf 3 (fast forward skip file 3): The format of the tape is as follows: 1. A BOS boot image 2. A BOS install image 3. A dummy Table Of Contents 4. The system backup of the rootvg So if you just need to restore some files, first forward the tape pointer to position 3, counting from 0. Note 3: How to restore specific files from a mksysb FILE -------------------------------------------------------See also note 2 view: restore -Tvqf [mksysb file] To restore: restore -xvqf [mksysb file] [file name] Note 4: How to restore a directory from a mksysb FILE -----------------------------------------------------Simply using the restore command. restore -xvdf ./your/directory The dot at the front of the path is important. The "-d" flag indicates that this is a directory and everything in it should be restored. If you omit that, you'll restore an empty directory.
The directory will be restored underneath whatever directory you're in. So if you're in your home directory it might create: /home/azhou/your/directory. With a mksysb image on disk you don't have any positioning to do, like with a tape. Note 5: Performing a mksysb migration with CD installation ---------------------------------------------------------You can perform a mksysb migration with a CD installation of AIX� 5.3 Step 1. Prepare your system for installation: Prepare for migrating to the AIX 5.3 BOS by completing the following steps: - Insert the AIX Volume 1 CD into the CD-ROM device. - Shut down the target system. If your machine is currently running, power it off by following these steps: Log in as the root user. Type shutdown -F. If your system does not automatically power off, place the power switch in the Off (0) position. Attention: You must not turn on the system unit until instructed to do so. - Turn on all attached external devices. External devices include the following: Terminals CD-ROM drives DVD-ROM drives Tape drives Monitors External disk drives Turning on the external devices first is necessary so that the system unit can identify each peripheral device during the startup (boot) process. - If your MKSYSB_MIGRATION_DEVICE is a tape, insert the tape for the mksysb in the tape drive. If your MKSYSB_MIGRATION_DEVICE is a CD or DVD, and there is an additional CD or DVD drive on the system (other than the one being used to boot AIX), insert the mksysb CD or DVD in the drive to avoid being prompted to swap medias. - Insert your customized bosinst.data supplemental diskette in the diskette drive. If the system does not have a diskette drive, use the network installation method for mksysb migration. Step 2. Boot from your installation media: The following steps migrate your current version of the operating system to AIX
5.3. If you are using an ASCII console that was not defined in your previous system, you must define it. For more information about defining ASCII consoles, see Step 3. Setting up an ASCII terminal. Turn the system unit power switch from Off (0) to On (|). When the system beeps twice, press F5 on the keyboard (or 5 on an ASCII terminal). If you have a graphics display, you will see the keyboard icon on the screen when the beeps occur. If you have an ASCII terminal (also called a tty terminal), you will see the word "keyboard" when the beeps occur. Note: If your system does not boot using the F5 key (or the 5 key on an ASCII terminal), refer to your hardware documentation for information about how to boot your system from an AIX product CD. The system begins booting from the installation media. The mksysb migration installation proceeds as an unattended installation (non-prompted) unless the MKSYSB_MIGRATION_DEVICE is the same CD or DVD drive as the one being used to boot and install the system. In this case, the user is prompted to switch the product CD for the mksysb CD or DVD(s) to restore the image.data and the /etc/filesystems file. After this happens the user is prompted to reinsert the product media and the installation continues. When it is time to restore the mksysb image, the same procedure repeats. The BOS menus do not currently support mksysb migration, so they cannot be loaded. In a traditional migration, if there are errors that can be fixed by prompting the user for information through the menus, the BOS menus are loaded. If such errors or problems are encountered during mksysb migration, the installation asserts and an error stating that the migration cannot continue displays. Depending on the error that caused the assertion, information specific to the error might be displayed. If the installation asserts, the LED shows "088". Note 6: create a mksysb tape MANUALLY ------------------------------------THIS NOTE DESCRIBES NOT A SUPPORTED METHOD, AND IS NOT CHECKED.. Here we do not mean the "mksysb -i /dev/rmtx" method, but...: Question: I have to clone a standalone 6H1 equipped with a 4mm tape, from another 6H1 which is node of an SP and which does not own a tape ! The consequence is that my source mksysb is a file that is recorded in /spdata/sys1/install/aixxxx/images
How will I copy this file to a tape to create the correct mksysb tape that could be used to restore on my target machine ? Answer: using the following method in the case the two server are in the same AIX level and kernel type (32/64 bits, jfs or jfs2) - the both servers must communicate over an IP network and have .rhosts file documented (for using rsh) cp /var/adm/ras/bosinst.data /bosinst.data mkszfile copy these files (bosinst.data and image.data) under "/" on the remote system on the server: tctl -f /dev/rmt0 status if the block size is not 512: # chdev -l /dev/rmt0 -a block_size=512 tctl -f /dev/rmt0 rewind bosboot -a -d /dev/rmt0.1 (create the boot image on the first file of mksysb) mkinsttape /dev/rmt0.1 (create the second file on the mksysb with image.data, bosinst.data, and oher files like drivers and commands) echo " Dummy tape TOC" | dd of=/dev/rmt0.1 conv=sync bs=512 > /dev/null 2>&1 (create the third file "dummy toc") create a named pipe: mknod /tmp/pipe p and run the mksysb as this: dd if=/tmp/pipe | rsh "server_hostname" dd of=/dev/rmt0.1 & mksysb /tmp/pipe this last command create the fourth file with "rootvg" in backup/restore format Note 7: Creating a root volume group backup on CD or DVD with the ISO9660 format -------------------------------------------------------------------------------Follow this procedure to create a root volume group backup on CD or DVD with the ISO9660 format. You can use Web-based System Manager or SMIT to create a root volume group backup on CD or DVD with the ISO9660 format, as follows:
Use the Web-based System Manager Backup and Restore application and select System backup wizard method. This method lets you create bootable or non-bootable backups on CD-R, DVD-R, or DVD-RAM media. OR To create a backup to CD, use the smit mkcd fast path. To create a backup to DVD, use the smit mkdvd fast path and select ISO9660 (CD format). The following procedure shows you how to use SMIT to create a system backup to CD. (The SMIT procedure for creating a system backup to an ISO9660 DVD is similar to the CD procedure.) Type the smit mkcd fast path. The system asks whether you are using an existing mksysb image. Type the name of the CD-R device. (This can be left blank if the Create the CD now? field is set to no.) If you are creating a mksysb image, select yes or no for the mksysb creation options, Create map files? and Exclude files?. Verify the selections, or change as appropriate. The mkcd command always calls the mksysb command with the flags to extend /tmp. You can specify an existing image.data file or supply a user-defined image.data file. See step 16. Enter the file system in which to store the mksysb image. This can be a file system that you created in the rootvg, in another volume group, or in NFS-mounted file systems with read-write access. If this field is left blank, the mkcd command creates the file system, if the file system does not exist, and removes it when the command completes. Enter the file systems in which to store the CD or DVD file structure and final CD or DVD images. These can be file systems you created in the rootvg, in another volume group, or in NFS-mounted file systems. If these fields are left blank, the mkcd command creates these file systems, and removes them when the command completes, unless you specify differently in later steps in this procedure. If you did not enter any information in the file systems' fields, you can select to have the mkcd command either create these file systems in the rootvg, or in another volume group. If the default of rootvg is chosen and a mksysb image is being created, the mkcd command adds the file systems to the exclude file and calls the mksysb command with the -e exclude files option. In the Do you want the CD or DVD to be bootable? field, select yes to have a boot image created on the CD or DVD. If you select no, you must boot from a product CD at the same version.release.maintenance level, and then select to install the system backup from the system backup CD. If you change the Remove final images after creating CD? field to no, the file system for the CD images (that you specified earlier in this procedure) remains after the CD has been
recorded. If you change the Create the CD now? field to no, the file system for the CD images (that you specified earlier in this procedure) remains. The settings that you selected in this procedure remain valid, but the CD is not created at this time. If you intend to use an Install bundle file, type the full path name to the bundle file. The mkcd command copies the file into the CD file system. You must have the bundle file already specified in the BUNDLES field, either in the bosinst.data file of the mksysb image or in a user-specified bosinst.data file. When this option is used to have the bundle file placed on the CD, the location in the BUNDLES field of the bosinst.data file must be as follows: /../usr/sys/inst.data/user_bundles/bundle_file_name To place additional packages on the CD or DVD, enter the name of the file that contains the packages list in the File with list of packages to copy to CD field. The format of this file is one package name per line. If you are planning to install one or more bundles after the mksysb image is restored, follow the directions in the previous step to specify the bundle file. You can then use this option to have packages listed in the bundle available on the CD. If this option is used, you must also specify the location of installation images in the next step. Enter the location of installation images that are to be copied to the CD file system (if any) in the Location of packages to copy to CD field. This field is required if additional packages are to be placed on the CD (see the previous step). The location can be a directory or CD device. You can specify the full path name to a customization script in the Customization script field. If given, the mkcd command copies the script to the CD file system. You must have the CUSTOMIZATION_FILE field already set in the bosinst.data file in the mksysb image or else use a user-specified bosinst.data file with the CUSTOMIZATION_FILE field set. The mkcd command copies this file to the RAM file system. Therefore, the path in the CUSTOMIZATION_FILE field must be as follows: /../filename You can use your own bosinst.data file, rather than the one in the mksysb image, by typing the full path name of your bosinst.data file in the User supplied bosinst.data file field. To turn on debugging for the mkcd command, set Debug output? to yes. The debug output goes to the smit.log. You can use your own image.data file, rather than the image.data file in the mksysb image, by typing the full path name of your image.data file for the User supplied image.data file field.
Note 8: 0301-150 bosboot: Invalid or no boot device specified! -------------------------------------------------------------== Technote: APAR status Closed as program error. Error description On a system, that does not have tape support installed, running mkszfile will show the following error: 0301-150 bosboot: Invalid or no boot device specified. Local fix Install device support for scsi tape devices. Problem summary Error message when creating backup if devices.scsi.tape.rte not installed even if the system does not have a tape drive. Problem conclusion Redirect message to /dev/null. Temporary fix Ignore message. Comments APAR information APAR number IY52551 IY95261 Reported component name AIX 5L POWER V5 Reported component ID 5765E6200 Reported release 520 Status CLOSED PER PE NoPE HIPER NoHIPER Submitted date 2004-01-12 Closed date 2004-01-12 Last modified date 2004-02-27 == Technote: APAR status Closed as program error. Error description If /dev/ipldevice is missing, mksfile will show the bosboot usage statement. 0301-150 bosboot: Invalid or no boot device specified! Local fix Problem summary If /dev/ipldevice is missing, mksfile will show the
bosboot usage statement. 0301-150 bosboot: Invalid or no boot device specified! Problem conclusion Do not run bosboot against /dev/ipldevice. Temporary fix Comments APAR information APAR number IY95261 Reported component name AIX 5.3 Reported component ID 5765G0300 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER Submitted date 2007-02-22 Closed date 2007-02-22 Last modified date 2007-06-06 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Publications Referenced Fix information Fixed component name AIX 5.3 Fixed component ID 5765G0300 == thread: Q: > > > > > > > > >
Someone out there knows the fix for this one; if you get a moment, would you mind giving me the fix? # mksysb -i /dev/rmt0 /dev/ipldevice not found
A: The ipldevice file is probably deleted from your /dev directory, or point to wrong entry. The '/dev/ipldevice' file is (re)created in boot time 2nd phase. For additional information look into /sbin/rc.boot script... The ipldevice entry type is hardlink. Usually point to /dev/rhdiskN, assuming that boot device is hdiskN.
Check your system and you should got similar find /dev -links 2 -ls .... 8305 0 crw------- 2 root system 14, 1 Feb 20 8305 0 crw------- 2 root system 14, 1 Feb 20 ... (The first cloumn of the output is the inode
... 2005 /dev/rhdisk0 2005 /dev/ipldevice number)
So, you can recreate the wrong, or missing ipdevice file. 'bootinfo -b' says the physical boot device name. For exapmle: ln -f /dev/rhdisk0 /dev/ipldevice I hope this will solve your bosboot problem. Q: I was installing Atape driver and noticed bosboot failure when installp calls bosboot with /dev/ipldevice. Messages below: 0503-409 installp: bosboot verification starting... 0503-497 installp: An error occurred during bosboot verification processing. Inspection of /dev showed no ipldevice file I was able to easily recreate the /dev/ipldevice using ln /dev/rhdisk0 /dev/ipldevice then successfully install the Atape driver software. After reboot /dev/ipldevice is missing again???. Environment is p5 520 AIX 5.3 ML1 mirrored internal drives hdisk0 and hdisk1 in rootvg I have 5.3 ML2 (but have not applied yet) I don't see any APAR's in ML2 regarding /dev/ipldevice problems. A: Are you using EMC disk? There is a known problem with the later Powerpath versions where the powerpath startup script removes the /dev/ipldevice file if there is more than one device listed in the bootlist. A: Yes, running EMC PowerPath 4.3 for AIX, with EMC Clariion CX600 Fibre disks attached to SAN. I always boot from, and mirror the OS on IBM internal disks. We order 4 internal IBM drives. Two for primary OS and mirror, the other two for alt_disk and mirrors. Thanks for the tip. I will investigate at EMC Powerlink site for fix. I know PowerPath 4.4 for AIX is out, but still pretty new.
A: ipldevice is a link to the rawdevice (rhdisk0 , not hdisk0) -----Original Message----From: IBM AIX Discussion List [mailto:
[email protected]] On Behalf Of Robert Miller Sent: Wednesday, April 07, 2004 6:13 PM To:
[email protected] Subject: Re: 64 Bit Kernel It may be one of those odd IBMisms where they want to call something a certain name so they put it in as a link to the actual critter... Looking on my box, the /dev/ipldevice has the same device major and minor numbers as hdisk0 - tho it is interesting that ipldevice is a character device, where a drive is usually a block device: mybox:rmiller$ ls crw------- 2 root mybox:rmiller$ ls brw------- 1 root
-l /dev/ipl* system 23, 0 Jan 15 2002 /dev/ipldevice -l /dev/hdisk0 system 23, 0 Sep 13 2002 /dev/hdisk0
A: > Hi, > > > >
AIX 5.3 I have a machine where /dev/ipldevice doesn't exit I can reboot it safely ? How I can I re-create it ?
> Thanks in advance I did this today, and there is probably a more accepted way. I made a hard link from my rhdiskX device to /dev/ipldevice. If your boot device is /dev/hdisk0, then the command line would be as follows: ln /dev/rhdisk0 /dev/ipldevice Again, there is probably a more acceptable way to achieve this, but it worked for me. == thread: how to recover from an invalid or no boot device error in AIX Description When running the command "bosboot -ad /dev/ipldevice" in IBM AIX, you get the following error:
0301-150 bosboot: Invalid or no boot device specified! A device specified with the bosboot -d command is not valid. The bosboot command was unable to finish processing because it could not locate the required boot device. The installp command calls the bosboot command with /dev/ipldevice. If this error does occur, it is probably because /dev/ipldevice does not exist. /dev/ipldevice is a link to the boot disk. To determine if the link to the boot device is missing or incorrect : 1) Verify the link exists: # ls -l /dev/ipldevice ls: 0653-341 The file /dev/ipldevice does not exist. 2) In this case, it does not exist. To identify the boot disk, enter "lslv -m hd5". The boot disk name displays. # lslv -m hd5 hd5:N/A LP PP1 PV1 PP2 PV2 PP3 PV3 0001 0001 hdisk4 0001 hdisk1 In this example the boot disk name is hdisk4 and hdisk1. 3) Create a link between the boot device indicated and the /dev/ipldevice file. Enter: # ln /dev/boot_device_name /dev/ipldevice (An example of boot_device_name is rhdisk0.) In my case, I ran: # ln /dev/rhdisk4 /dev/ipldevice 4) Now run the bosboot command again: # bosboot -ad /dev/ipldevice Example lslv -m hd5; ln /dev/rhdisk4 /dev/ipldevice; bosboot -ad /dev/ipldevice Note 9: Other mksysb errors on AIX 5.3: --------------------------------------It turns out, that on AIX 5.3, on certain ML/TL levels (below TL 6), an mksysb error turns up, if you have other volume groups defined other than rootvg, while there is NO filesystem created on those Volume groups. Solution: create a filesystem, even only a "test" or "dummy" filesystem, on those VG's.
>> thread 1: Q: Hi can't find any information about "backup structure of volume group, vios". included service: "savevgstruct vgname" working with errors: # lsvg rootvg vg_dev datavg_dbs # /usr/ios/cli/ioscli savevgstruct vg_dev Creating information file for volume group vg_dev.. Some error messages may contain invalid information for the Virtual I/O Server environment. cat: 0652-050 Cannot open /tmp/vgdata/vg_dev/fs_data_tmp. # ls -al /tmp/vgdata/vg_dev/ total 16 drwxr-xr-x 2 root staff 256 Apr 02 08:38 . drwxrwxr-x 5 root system 256 Apr 02 08:20 .. -rw-r--r-- 1 root staff 2002 Apr 02 08:35 filesystems -rw-r--r-- 1 root staff 1537 Apr 02 08:35 vg_dev.data # oslevel -r 5300-05 # df -k | grep tmp /dev/hd3 1310720 1309000 1% 42 1% /tmp A: I had this issue as well with VIO 1.3. I called IBM support about it and it is a known issue. The APAR is IY87935. The fix will not be released until AIX 5.3 TL 6, which is due out in June. It occurs when you run savevgstruct on a user defined volume group that contains volumes where at least one does not have a filesystem defined on it. The workaround is to define a filesystem on every volume in the user defined volume group. >> thread 2: IBM APAR Note: http://www-1.ibm.com/support/docview.wss?uid=isg1IY87935 IY87935: MKVGDATA/SAVEVG CAN FAIL APAR status Closed as program error.
Error description The mkvgdata command when executed on a volume group that does not have any mounted filesystems: # savevg -f /home/vgbackup -i vg00 Creating information file for volume group vg00..cat: 0652-050 Cannot open /tmp/vgdata/vg00/fs_data_tmp. /usr/bin/savevg 33 : BACKUPSHRINKSIZE = 16 + FSSHRINKSIZE : 0403-009 The specified number is not valid for this command. Local fix Problem summary The mkvgdata command when executed on a volume group that does not have any mounted filesystems: # savevg -f /home/vgbackup -i vg00 Creating information file for volume group vg00..cat: 0652-050 Cannot open /tmp/vgdata/vg00/fs_data_tmp. /usr/bin/savevg 33 : BACKUPSHRINKSIZE = 16 + FSSHRINKSIZE : 0403-009 The specified number is not valid for this command. Problem conclusion Check variable. Temporary fix Comments APAR information APAR number IY87935 Reported component name AIX 5.3 Reported component ID 5765G0300 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER Submitted date 2006-08-09 Closed date 2006-08-09 Last modified date 2006-08-09
9.11 AIX: the backup and restore commands: -----------------------------------------The backup command creates copies of your files on a backup medium, such as a magnetic tape or diskette. The copies are in one of the two backup formats: - Specific files and directories, backed up by name using the -i flag.
- Entire file system backed up by i-node, not using the -i flag, but instead using the Level and FileSystem parameters. Unless you specify another backupmedia with the -f parameter, the backup command automatically writes its output to /dev/rfd0 which is the diskette drive. (1) Backing up the user directory "userdirectory": # cd /userdirectory # find . -depth | backup -i -f /dev/rmt0
# or use find . -print
(2) Incremental backups: You can create full and incremental backups of filesystems as well, as shown in the following example. When the -u flag is used with the backup command, the system will do an incremental backup according to the -level number specified. For example, a level 5 backup will only back up the data that has changed after the level 4 was made. Levels can range from 0 to 9. Example; On Sunday: # backup -0 -uf /dev/rmt0 /data On Monday: # backup -1 -uf /dev/rmt0 /data .. .. On Saturday: # backup -6 -uf /dev/rmt0 /data Due to the -u parameter, information about the backups is written to the /etc/dumpdates file. To backup the / (root) file system, enter: # backup -0 -u -f /dev/rmt0 / Note that we do noy use the -i flag, but instead backup an entire fs "/". Other examples: --------------To backup all the files and subdirectories in current directory using relative pathnames, use # find . -print | backup -if /dev/rmt0 To backup the files /bosinst.data and /signature to the diskette, use # ls ./bosinst.dat ./signature | backup -iqv How to restore a file: ---------------------Suppose we want to restore the /etc/host file, because its missing. # tctl -f /dev/rmt0 rewind # - rewind tape # restore -x -d -v -q -s4 -f /dev/rmt0.1 ./etc/hosts
Another example: # restore -qvxf /dev/rmt0.1 "./etc/passwd" # restore -s4 -qTvf /dev/rmt0.1
Restore /etc/passwd file Lists contents of a mksysb tape
9.12 AIX: savevg and restvg: ---------------------------To backup, or clone, a VG, you can use the - mksysb command for the rootvg - savevg command for other user VG's To backup a user Volume Group (VG, see also sections 30 and 31) you can use savevg to backup a VG and restvg to restore a VG. # lsvg rootvg uservg
# - shows a list of online VG's
# savevg -if /dev/rmt0 uservg
# - now backup the uservg
9.13 AIX: tctl: --------------Purpose Gives subcommands to a streaming tape device. Syntax tctl [ -f Device ] [ eof | weof | fsf | bsf | fsr | bsr | rewind | offline | rewoffl | erase | retension | reset | status ] [ Count ] tctl [ -b BlockSize ] [ read | write }
-f Device ] [
-p BufferSize ] [
-v ] [
-n ] [
-B ] {
Description The tctl command gives subcommands to a streaming tape device. If you do not specify the Device variable with the -f flag, the TAPE environment variable is used. If the environment variable does not exist, the tctl command uses the /dev/rmt0.1 device. (When the tctl command gives the status subcommand, the default device is /dev/rmt0.) The Device variable must specify a raw (not block) tape device. The Count parameter specifies the number of end-of-file markers, number of file marks, or number of records. If the Count parameter is not specified, the default count is 1. Examples To rewind the rmt1 tape device, enter: tctl -f /dev/rmt1 rewind To move forward two file marks on the default tape device, enter: tctl fsf 2
To write two end-of-file markers on the tape in /dev/rmt0.6, enter: tctl -f /dev/rmt0.6 weof 2 To read a tape device formatted in 80-byte blocks and put the result in a file, enter: tctl -b 80 read > file To read variable-length records from a tape device formatted in 80-byte blocks and put the result in a file, enter: tctl -b 80 -n read > file To write variable-length records to a tape device using a buffer size of 1024 byes, enter: cat file | tctl -b 1024 -n -f/dev/rmt1 write To write to a tape device in 512-byte blocks and use a 5120-byte buffer for standard input, enter: cat file | tctl -v -f /dev/rmt1 -p 5120 -b 512 write Note: The only valid block sizes for quarter-inch (QIC) tape drives are 0 and 512. To write over one of several backups on an 8 mm tape, position the tape at the start of the backup file and issue these commands: tctl bsf 1 tctl
eof 1
9.14 AIX mt command: -------------------Purpose Gives subcommands to streaming tape device. Syntax mt [ -f TapeName ] Subcommand [ Count ] Description The mt command gives subcommands to a streaming tape device. If you do not specify the -f flag with the TapeName parameter, the TAPE environment variable is used. If the environment variable does not exist, the mt command uses the /dev/rmt0.1 device. The TapeName parameter must be a raw (not block) tape device. You can specify more than one operation with the Count parameter. Subcommands eof, weof Writes the number of end-of-file markers specified by the Count parameter at the current position on the tape. fsf Moves the tape forward the number of files specified by the Count parameter and positions it to the beginning of the next file.
bsf Moves the tape backwards the number of files specified by the Count parameter and positions it to the beginning of the last file skipped. If using the bsf subcommand would cause the tape head to move back past the beginning of the tape, then the tape will be rewound, and the mt command will return EIO. fsr Moves the tape forward the number of records specified by the Count parameter. bsr Moves the tape backwards the number of records specified by the Count parameter. rewoff1, rewind Rewinds the tape. The Count parameter is ignored. status Prints status information about the specified tape device. The output of the status command may change in future implementations Examples To rewind the rmt1 tape device, enter: mt -f /dev/rmt1 rewind To move forward two files on the default tape device, enter: mt fsf 2 To write two end-of-file markers on the tape in the /dev/rmt0.6 file, enter: mt -f /dev/rmt0.6 weof 2 9.14 AIX tapeutil command: -------------------------tapeutil -f - A program which came with the tape library to control it's working. Called without arguments gives a menu. Is useful for doing things like moving tapes from the slot to the drive. e.g. $ tapeutil -f /dev/smc0 move -s 10 -d 23 which moves the tape in slot 10 to the drive (obviously, this will depend on your own individual tape library, may I suggest the manual?). The fileset you need to install for 'tapeutil' command is: Atape.driver 7.1.5.0. Example: -------We are using 3583 automated tape library for backups.for tapeutil command u need to have a file atape.sys on ur system.to identify the positioning of tape drives and source just type tapeutil it will give u a number of options.choose element information to identify the source and tape drive numbers. In our case the tape drives numbers are 256 and 257 and the source number to insert the tape is 16. we usually give the following commands to load and move the tape. Loading Tape:-
tapeutil -f /dev/smc0 move -s 16 -d 256 (to insert the tape in tapedrive 1,where 16 is source and 256 is destination) to take the backup:find filesystem1 filesystem2 | backup -iqvf /dev/rmt1 ((filessystem name without mount point slash)) after taking the backup and unloading tape:tapeutil -f /dev/rmt1 unload tapeutil -f /dev/smc0 move -s 256 -d 16 (first unload the tape then move it to source destination) this might help u to use the taputil command in taking backup. Example: -------In order to move tapes in and out of the Library here is what I do. First I unload the tape with the command #tapeutil -f /dev/rmtx unload Where x is 0,1,2,3... then I move the tape from external slot (16) using the media changer, not the tape drive. #tapeutil -f /dev/smcx move 256 16 The above command moves the tape in your first tape drive (256) to the external slot. Note that you can also move from the internal slots to the external slot or the tape drive. To move the tape back from the external slot, I just switch 256 and 16 parameters. Example: -------The code I use to list the I/O station slots is: /usr/bin/tapeutil -f /dev/smc0 inventory | grep -p Station | egrep 'Station|Volume' | awk '{ if($1 =3D=3D "Import/Export") ioslot=3D$4; if($1 =3D=3D "Volume") { if(NF =3D=3D 4) volser=3D$4; else volser=3D"-open-"; print ioslot, volser; }}' The tapeutil command to move a tape is: /usr/bin/tapeutil -f /dev/smc0 move For example:
/usr/bin/tapeutil -f /dev/smc0 move 773 1037
You can get the slot numbers, and volsers in them, with the command: /usr/bin/tapeutil -f /dev/smc0 inventory
To find an open slot just look for a slot with a blank "Volume Tag". One little hitch, however. If a tape is currently mounted, the "tapeut=il inventory" command will show a slot as open ("Volume Tag" is blank), but TSM will have it reserved for= the mounted tape. So what I did in my script is to check the TSM device configuration file for each ope= n slot that I find and if that slot number appears in it then I skip that slot and go on to the next one. Example: -------#!/bin/ksh DEVICE=$1 HOST=$2 TAPE=$3 case $TAPE in 2) tapeutil -f tapeutil ;; 3) tapeutil -f tapeutil ;; 4) tapeutil -f tapeutil ;; 5) tapeutil -f tapeutil ;; esac
/dev/smc0 move 23 10 -f /dev/smc0 move 11 23 /dev/smc0 move 23 11 -f /dev/smc0 move 12 23 /dev/smc0 move 23 12 -f /dev/smc0 move 13 23 /dev/smc0 move 23 13 -f /dev/smc0 move 14 23
Example: -------tapeutil tapeutil tapeutil tapeutil tapeutil
-f -f -f -f -f
/dev/rmt1 /dev/smc0 /dev/smc0 /dev/smc0 /dev/smc0
unload move 257 16 move -s 256 -d 16 move 257 1025 move 16 257
tapeutil -f /dev/smc0 exchange 34 16 40 tapeutil -f /dev/smc0 inventory | more tctl -f/dev/rmt0 rewoffl tapeutil �f/dev/smc0 elementinfo tapeutil �f /dev/scm0 inventory
Example: -------tapeutil -f /dev/rmt1 unload sleep 20
DAYNO=`date +%d`;export DAYNO case $DAYNO in 01) tapeutil -f /dev/smc0 move 23 10 tapeutil -f /dev/smc0 move 11 23 ;; 02) tapeutil -f /dev/smc0 move 23 10 tapeutil -f /dev/smc0 move 11 23 ;; 03) tapeutil -f /dev/smc0 move 23 10 tapeutil -f /dev/smc0 move 11 23 ;; 04) tapeutil -f /dev/smc0 move 23 10 tapeutil -f /dev/smc0 move 11 23 ;; 05) tapeutil -f /dev/smc0 move 23 10 tapeutil -f /dev/smc0 move 11 23 ;; 06) tapeutil -f /dev/smc0 move 23 10 tapeutil -f /dev/smc0 move 11 23 ;; 07) tapeutil -f /dev/smc0 move 23 10 tapeutil -f /dev/smc0 move 11 23 ;; esac Example: -------tapeutil -f /dev/rmt1 unload sleep 20 DAYNAME=`date +%a`;export DAYNAME case $DAYNAME in Sun) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; Mon) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; Tue) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; Wed) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; Thu) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; Fri) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; Sat) tapeutil -f /dev/smc0 tapeutil -f /dev/smc0 move ;; esac
move 256 4098 4099 256 move 256 4099 4100 256 move 256 4100 4113 256 move 256 4113 4114 256 move 256 4114 4109 256 move 256 4109 4124 256 move 256 4124 4110 256
tapeutil -f /dev/smc0 move 256 4098 tapeutil -f /dev/smc0 move 4099 256 Example: --------
tapeutil sleep 10 tapeutil sleep 10 tapeutil sleep 10 tapeutil sleep 10 tapeutil sleep 10 tapeutil sleep 10
-f /dev/smc0 move 16 4096 -f /dev/smc0 move 17 4097 -f /dev/smc0 move 18 4098 -f /dev/smc0 move 19 4099 -f /dev/smc0 move 20 4100 -f /dev/smc0 move 21 4101
Example: -------mt -f /dev/rmt1 rewind mt -f /dev/rmt1.1 fsf 6 tar -xvf /dev/rmt1.1 /data/download/expdemo.zip SPL bld About Ts3310: ------------Abstract Configuration Information for IBM TS3310 (IBM TotalStorage 3576) Content IBM TS3310 (IBM TotalStorage 3576) Drive Addresses Storage Slot Addresses Changer Address Entry/Exit Slot Address 256-261 4096-4223 1 16-21 Notes: 1. Barcodes are required. Without a barcode label, a volume will show as unknown media. 2. ELEMent=AUTODetect in the DEFINE/UPDATE DRIVE command is supported. 3. Device identification and firmware used during validation Library ID: IBM 3576-MTL --- Firmware: 0.62 4. The IBM device driver is required. The IBM device drivers are available at ftp://ftp.software.ibm.com/storage/devdrvr. 5. The library is available with IBM LTO Generation 3 drives.
6. For more information on IBM TS3310, see TS3310 Tape Library.
Example: -------First, list the tape device names: lsdev -Cc tape Assume it returns smc0 for the library, and rmt0 and rmt1 for the tape drives, and all devices are Available. Next, take an inventory of the library. tapeutil -f /dev/smc0 inventory | more Assume the inventory returns two drives with element numbers 256 and 257 and shows a tape stored in slot 1025. Then, start moving the tape to each drive in turn, and verify which device name it is associated with by running tctl or mt rewoffl. If it returns without error, the device name matches the element number. Move the tape from the tape slot to the first drive: tapeutil -f /dev/smc0 move 1025 256 tctl -f/dev/rmt0 rewoffl If the command returns with no errors, then element # 256 matches device name /dev/rmt0. Move the tape to the next drive tapeutil -f /dev/smc0 move 256 257 tctl -f/dev/rmt1 rewoffl If the command returns with no errors, then element # 257 matches device name /dev/rmt1 Move the tape back to the storage slot it came from: tapeutil -f /dev/smc0 move 257 1025 If at any point, the tctl command returns with errors, then try another device name until it returns without errors. NOTE: the 'rewoffl' flag on tctl simply rewinds and ejects the tape from the drive. 9.15 Recover from AIX OS failure: --------------------------------Recover from OS failure. Contents: 1. How to view the bootlist: 2. How to change the bootlist: 3. How to make a device bootable: 4. How to make a backup of the OS: 5. Shutdown a pSeries AIX system in the most secure way:
6. How to restore specific files from a mksysb tape: 7. Recovery of rootvg 1. How to view the bootlist: At boottime, once the POST is completed, the system will search the boot list for a bootable image. The system will attempt to boot from the first entry in the bootlist. Its always a good idea to see what the OS thinks are the bootable devices and the order of what the OS thinks it should use. Use the bootlist command to view the order: # bootlist -m normal -o As the first item returned, you will see hdisk0, the bootable harddisk. If you need to check the bootlist in "service mode", for example if you want to boot from tape to restore the rootvg, use # bootlist -m service -o 2. How to change the bootlist: The bootlist, in normal operations, can be changed using the same command as used in section 1, for example # bootlist -m normal hdisk0 cd0 This command makes sure the hdisk0 is the first device used to boot the system. If you want to change the bootlist for the system in service mode, you can change the list in order to use rmt0 if you need to restore the rootvg. # bootlist -m service rmt0 3. How to make a device bootable: To make a device bootable, use the bosboot command: # bosboot -ad /dev/ipldevice So, if hdisk0 must be bootable, or you want to be sure its bootable, use # bosboot -ad /dev/hdisk0 4. How to make a backup of the OS:
The mksysb command creates an installable image of the rootvg. This is synonym to say that mksysb creates a backup of the operating system (that is, the root volume group). You can use this backup to reinstall a system to its original state after it has been corrupted. If you create the backup on tape, the tape is bootable and includes the installation programs needed to install from the backup. To generate a system backup and create an /image.data file (generated by the mkszfile command) to a tape device named /dev/rmt0, type: # mksysb -i /dev/rmt0 If a backup tape was created with the -e switch, like in: # mksysb -i -e /dev/rmt0 then a number of directories are NOT included in the backup. These exclusions are listed in the "/etc/exclude.rootvg" file. The mksysb command should be used regularly. It must certainly be done after installing apps or devices. In normal conditions, the OS does not change, and a bootable tape should be created at some frequency. 5. Shutdown a pSeries AIX system in the most secure way: 1. Shut down all applications in a controlled way. 2. Make sure no users are on the system. 3. Use the shutdown command: shutdown -r shutdown -m
to reboot the system to reboot in maintenance mode
6. How to restore specific files from a mksysb tape: $ tctl fsf 3 $ restore -xvf /dev/rmt0.1 ./your/file/name For example, if you need to get the vi command back, put the mksysb tape in the tape drive (in this case, /dev/rmt0) and do the following: cd /
# get to the root directory
tctl -f /dev/rmt0 rewind
# rewind the tape
tctl -f /dev/rmt0.1 fsf 3
# move the tape to the third file, no rewind
restore -xqf /dev/rmt0.1 -s 1 ./usr/bin/vi
# extract the vi binary, no rewind
Further explanation why you must use the fsf 3 (fast forward skip file 3): The format of the tape is as follows: 1. A BOS boot image 2. A BOS install image 3. A dummy Table Of Contents 4. The system backup of the rootvg So if you just need to restore some files, first forward the tape pointer to position 3, counting from 0. 7. Recovery of rootvg 7.1 Check if the system can boot from tape: # bootinfo -e If a 1 is returned, the system can boot from tape, if a 0 is returned a boot from tape is not supported. 7.2 Recover the rootvg: One possible method is the following: 1. Check whether the tape is in front of the disk with the bootlist command: # bootlist -m normal -o 2. Insert the mksysb tape 3. Power on the machine. The system will boot from the tape. 4. The Installation and Maintenance Menu will be displayed.
Welcome to Base Operating System Installation and Maintenance Type the number of your choice and press Enter.
Choice is indicated by >>>.
>>> 1 Start Install Now with Default Settings 2 Change/Show Installation Settings and Install 3 Start Maintenance Mode for System Recovery Type 3 and press enter to start maintenance mode. The next screen you should see is :Maintenance Type the number of your choice and press Enter. >>> 1 Access a Root Volume Group 2 Copy a System Dump to Removable Media
3 Access Advanced Maintenance Functions 4 Install from a System Backup >>> Choice [1]: Type 4 and press enter to install from a system backup. The next screen you should see is :Choose Tape Drive Type the number of the tape drive containing the system backup to be installed and press Enter. Tape Drive
Path Name
>>> 1 tape/scsi/ost
/dev/rmt0
>>> Choice [1]: Type the number that corresponds to the tape drive that the mysysb tape is in and press enter. The next screen you should see is :Welcome to Base Operating System Installation and Maintenance Type the number of your choice and press Enter.
Choice is indicated by >>>.
>>> 1 Start Install Now with Default Settings 2 Change/Show Installation Settings and Install 3 Start Maintenance Mode for System Recovery
88 99
Help ? Previous Menu
+----------------------------------------------------|Select 1 or 2 to install from tape device /dev/rmt0 | |
>>> Choice [1]: You can now follow your normal mksysb restore procedures. 9.16 HP-UX make_net_recovery: ----------------------------There are two ways you can recover from a tape with make_net_recovery. The method you choose depends on your needs. - Use make_medialif This method is useful when you want to create a totally self-contained recovery tape. The tape will be bootable and will contain everything needed to recover your system, including the archive of your system. During recovery, no access to an Ignite-UX server is needed. Using make_medialif is described beginning on
�Create a Bootable Archive Tape via the Network� and also on the Ignite-UX server in the file: /opt/ignite/share/doc/makenetrec.txt - Use make_boot_tape This method is useful when you do not have the ability to boot the target machine via the network, but are still able to access the Ignite-UX server via the network for your archive and configuration data. This could happen if your machine does not support network boot or if the target machine is not on the same subnet as the Ignite-UX server. In these cases, use make_boot_tape to create a bootable tape with just enough information to boot and connect with the Ignite-UX server. The configuration files and archive are then retrieved from the Ignite-UX server. See the make_boot_tape(1M) manpage for details. -- make_boot_tape: make_boot_tape(1M)
make_boot_tape(1M)
NAME make_boot_tape - make a bootable tape to connect to an Ignite-UX server SYNOPSIS /opt/ignite/bin/make_boot_tape [-d device-file-for-tape] [-f configfile] [-t tmpdir] [-v] /opt/ignite/bin/make_boot_tape [-d device-file-for-tape] [-g gateway] [-m netmask] [-t tmpdir] [-v] DESCRIPTION The tape created by make_boot_tape is a bootable tape that contains just enough information to boot the system and then connect to the Ignite-UX server where the tape was created. Once the target system has connected with the Ignite-UX server, it can be installed or recovered using Ignite-UX. The tape is not a fully self-contained install tape; an Ignite-UX server must also be present. The configuration information and software to be installed on the target machine reside on the Ignite-UX server, not on the tape. If you need to build a fully self-contained recovery tape, see make_recovery(1m) or make_media_lif(1m). make_boot_tape is used in situations when you have target machines that cannot boot via the network from the Ignite-UX server. This happens either because the machine does not support booting from the network or because it is not on the same subnet as the Ignite-UX server. In this case, booting from a tape generated by make_boot_tape means you do not need to set up a boot helper system. A tape created by make_boot_tape can be used to kick off a normal Ignite-UX installation. It can also be used to recover from recovery configurations saved on the Ignite-UX server. There is no "target-specific" information on the boot tape. Only information about the Ignite-UX server is placed on the tape. Thus, it is possible to initiate an installation of any target machine from
the same boot tape provided that the same Ignite-UX server is used. Likewise, the target machine can be installed with any operating system configuration that is available on the Ignite-UX server. Typically, the make_boot_tape command is run from the Ignite-UX server that you wish to connect with when booting from the tape later on. A key file that contains configuration information is called INSTALLFS. This file exists on the Ignite-UX server at /opt/ignite/boot/INSTALLFS and is also present on the tape created by make_boot_tape. See instl_adm(4) for details on the configuration file syntax. Unless the -f option is used, the configuration information already present in the INSTALLFS file is used on the tape as well. The make_boot_tape command will never alter the INSTALLFS file on the Ignite-UX server; it will only change the copy that is placed on the tape. Examples: --------Create a boot tape on the default tape drive (/dev/rmt/0m). # make_boot_tape Create a boot tape on a specified (non-default) tape drive. Create a DDS1 device file for the tape drive first. Show as much information about the tape creation as is possible. ioscan -fC tape # to get the hardware path mksf -v -H -b DDS1 -n -a make_boot_tape -d /dev/ -v Create a boot tape and replace the configuration information contained in the INSTALLFS file. Use the /tmp directory for all temporary files instead of the default /var/tmp. # instl_adm -d > tmp_config_file ## edit tmp_config_file as appropriate # make_boot_tape -f tmp_config_file -t /tmp Create a boot tape and specify a different gateway IP address. Set the netmask value as well. All other configuration information is from what is already in /opt/ignite/boot/INSTALLFS. # make_boot_tape -g 15.23.34.123 -m 255.255.248.0
============= 10. uuencode: ============= Unix to Unix Encoding. A method for converting files from Binary to ASCII so that they can be sent across the Internet via e-mail. Encode binary file (to uuencoded ASCII file)
uuencode file remotefile uudecode file Example: Encode binary file uuencode example example.en Decode encoded file uudecode example.en
uuencode converts a binary file into an encoded representation that can be sent using mail(1) . It encodes the contents of source-file, or the standard input if no source-file argument is given. The decode_pathname argument is required. The decode_pathname is included in the encoded file's header as the name of the file into which uudecode is to place the binary (decoded) data. uuencode also includes the permission modes of source-file, (except setuid , setgid, and sticky-bits), so that decode_pathname is recreated with those same permission modes. example: The following example packages up a source tree, compresses it, uuencodes it and mails it to a user on another system. When uudecode is run on the target system, the file ``src_tree.tar.Z'' will be created which may then be uncompressed and extracted into the original tree. # tar cf - src_tree | compress | uuencode src_tree.tar.Z | mail sys1!sys2!user example: uuencode > | | note: here, file_a is encoded and a new file named uufile is produced | | when you decode file uufile a file named file_b is produced | # uuencode dipl.doc dipl.doc >dipl.uu Hier wird die Datei dipl.doc (z.B. ein WinWord-Dokument) in die Datei dipl.uu umgewandelt. Dabei legen wir fest, dasz die Datei nach dem Decodieren wieder dipl.doc heiszen soll. example: uuencode long_name.tar.Z arc.trz > arc.uue 11. grep command: ================= # # # # #
grep grep grep grep grep
Sally people "Sally Smith" people -v "^$" people.old > people -v "^ *$" people.old > people "S.* D.*" people.old > people
# deletes all blank lines
12. sort command: ================= sort files by size, largest first... # ls -al | sort +4 -r | more # # # # # #
sort sort sort sort sort sort
+1 -2 people +2b people +2n +1 people +1 -2 *people > everybody -u +1 hardpeople softpeople > everybody -t: +5 /etc/passw
# -u=unique # -t field sep.
cp /etc/hosts /etc/hosts.`date +%o%b%d` 13. SED: ======== Can be used to replace a character sting with a different string. # sed s/string/newstring file #sed s/Smith/White/ people.old > people #sed "s/Sally Smith/Sally White/" people.old > people you can also use a regular expression, for instance we can put a left margin of 5 spaces on the people file # sed "s/^/ /" people.old > people # sed "s/[0-9]*$//" people.old > people # sed -e "s/^V^M//" filename > outputfilename
(remove numbers)
14. AWK: ======== When lines containing `foo' are found, they are printed, because `print $0' means print the current line: # awk '/foo/ { print $0 }' BBS-list looks for all files in the ls listing that matches Nov and it prints the total of bytes: # ls -l | awk '$5 == "Nov" { sum += $4 } END { print sum }' only print the lines containing Smith from file people: # awk /Smith/ people # # # #
awk awk awk awk
'/gold/' coins.txt '/gold/ {print $0}' coins.txt '/gold/ {print $5,$6,$7,$8}' coins.txt '{if ($3 < 1980) print $3, " ",$5,$6,$7,$8}' coins.txt
# awk '/Smith/ {print $1 "-" $3}' people # ls -l /home | awk '{total += $5}; END {print total}'
# ls -lR /home | awk '{total += $5}; END {print total}' Example: -------Suppose you have a text file with lines much longer than, for example, 72 characters, and you want to have a file with lines with a maximum of 72 chars, then you might use awk in the following way: -- Shell file r13.sh: #!/bin/bash DIR=/cygdrive/c/exports FILE=result24.txt awk -f r13.awk ${DIR}/${FILE} > ${DIR}/${FILE}.new -- r13.awk BEGIN { maxlength=72 } { l=length(); if (l > 72) { i=(l/72) for (j=0; j people remove blank lines: # tr -s "\012" < people.old > people
to remove the evil microsoft carriage return. # tr -d '\015' < original.file > new.file # cat filename1 | tr -d "^V^M" > newfile #! /bin/sh # # recursive dark side repair technique # eliminates spaces in file names from current directory down # useful for supporting systems where clueless vendors promote NT # for name in `find . -depth -print` do na=`echo "$name" | tr ' ' '_'` if [ "$na" != "$name" ] then echo "$name" fi done note: > > > > > > > > > >
I have finally competed setting up the samba server and setup the share between NT and Samba server. However, when I open a unix text file in Windows NT using notepad, i see many funny characters and the text file is not in order (Just like when I ftp the unix text file out into NT in binary format) ...I think this has to be something to do with whether the file transfer is in Binary format or ASCII ... Is there a parameter to set for this ? I have checked the documents ... but couldn't find anything on this ...
This is a FAQ, but it brief, it's like this. Unix uses a single newline character to end a line ("\n"), while DOS/Win/NT use a carriage-return/newline pair ("\r\n"). FTP in ASCII mode translates these for you. FTP in binary mode, or other forms of file transfer, such as Samba, leave the file unaltered. Doing so would be extremely dangerous, as there's no clear way to isolate which files should be translated You can get Windows editors that understand Unix line-end conventions (Ultra Edit is one), or you can use DOS line endings on the files, which will then look odd from the Unix side. You can stop using notepad, and use Wordpad instead, which will deal appropriately with Unix line endings. You can convert a DOS format text file to Unix with this:tr -d '\r' < dosfile.txt > unixfile.txt The best solution to this seems to be using a Windows editor that can handle working with Unix line endings. HTH Mike.
Note: There are two ways of moving to a new line...carriage return, which is chr(13), and new line which is chr(10). In windows you're supposed to use a sequence of a carriage return followed by a new line. For example, in VB you can use Wrap$=Chr$(13)+Chr$(10) which creates a wrap character. 16. cut and paste: ================== cutting columns: # cut -c17, 18, 19 people # cut -c17- people > phones # cut -c1-16 people > names cutting fields: #cut -d" " -f1,2 people > names
# -d field seperator
paste: # paste -d" " firstname lastname phones > people
17. mknod: ========== mknod creates a FIFO (named pipe), character special file, or block special file with the specified name. A special file is a triple (boolean, integer, integer) stored in the filesystem. The boolean chooses between character special file and block special file. The two integers are the major and minor device number. Thus, a special file takes almost no place on disk, and is used only for communication with the operating system, not for data storage. Often special files refer to hardware devices (disk, tape, tty, printer) or to operating system services (/dev/null, /dev/random). Block special files usually are disk-like devices (where data can be accessed given a block number, and e.g. it is meaningful to have a block cache). All other devices are character special files. (Long ago the distinction was a different one: I/O to a character special file would be unbuffered, to a block special file buffered.) The mknod command is what creates files of this type. The argument following name specifies the type of file to make: p b
for a FIFO for a block (buffered) special file
c
for a character (unbuffered) special file
When making a block or character special file, the major and minor device numbers must be given after the file type (in decimal, or in octal with leading 0; the GNU version also allows hexadecimal with leading 0x). By default, the mode of created files is 0666 (`a/rw') minus the bits set in the umask. In /dev # mknod # mknod # mknod
we find logical devices, created by the mknod command. /dev/kbd c 11 0 /dev/sunmouse c 10 6 /dev/fb0 c 29 0
create a pipe in /dev called 'rworldlp' # mknod /dev/rworldlp p; chmod a+rw /dev/rworldlp If one cannot afford to buy extra disk space one can run the export and compress utilities simultaneously. This will prevent the need to get enough space for both the export file AND the compressed export file. Eg: # Make a pipe mknod expdat.dmp p # or mkfifo pipe # Start compress sucking on the pipe in background compress < expdat.dmp > expdat.dmp.Z & # Wait a second or two before kicking off the export sleep 5 # Start the export exp scott/tiger file=expdat.dmp Create a compressed export on the fly. # create a named pipe mknod exp.pipe p # read the pipe - output to zip file in the background gzip < exp.pipe > scott.exp.gz & # feed the pipe exp userid=scott/tiger file=exp.pipe ...
18. Links: ========== A symbolic link is a pointer or an alias to another file. The command # ln -s fromfile /other/directory/tolink makes the file fromfile appear to exist at /other/directory/tolink simultaneously. The file is not copied, it merely appears to be a part of the file tree in two
places. Symbolic links can be made to both files and directories. The usage of the link command is. %ln -s ActualFilename LinkFileName Where -s indicates a symbolic link. ActualFilename is the name of the file which is to be linked to, and LinkFileName is the name by which the file should be known. You should use full paths in the command. This example shows copying three files from a directory into the current working directory. [2]%cp ~team/IntroProgs/MoreUltimateAnswer/more* [3]%ls -l more* -rw-rw-r-1 mrblobby mrblobby 632 Sep 21 18:12 moreultimateanswer.adb -rw-rw-r-1 mrblobby mrblobby 1218 Sep 21 18:19 moreultimatepack.adb -rw-rw-r-1 mrblobby mrblobby 784 Sep 21 18:16 moreultimatepack.ads The three files take a total of 2634 bytes. The equivalent ln commands would be: [2]%ln -s ~team/IntroProgs/MoreUltimateAnswer/moreultimateanswer.adb . [3]%ln -s ~team/IntroProgs/MoreUltimateAnswer/moreultimatepack.adb . [4]%ln -s ~team/IntroProgs/MoreUltimateAnswer/moreultimatepack.adb . [5]%ls -l lrwxrwxrwx 1 mrblobby mrblobby 35 Sep 22 08:50 moreultimateanswer.adb -> db
/users/team/IntroProgs/MorUltimateAnswer/moreultimateanswer.a lrwxrwxrwx
1
lrwxrwxrwx
1
mrblobby
mrblobby
37 Sep 22 08:49 moreultimatepack.adb ->
/users/team/IntroProgs/MorUltimateAnswer/moreultimatepack.adb mrblobby mrblobby 37 Sep 22 08:50 moreultimatepack.ads -> /users/team/IntroProgs/MorUltimateAnswer/moreultimatepack.ads
19. Relink van Oracle: ====================== info: showrev -p pkginfo -i relink: mk -f $ORACLE_HOME/rdbms/lib/ins_rdbms.mk install mk -f $ORACLE_HOME/svrmgr/lib/ins_svrmgr.mk install mk -f $ORACLE_HOME/network/lib/ins_network.mk install
20. trace: ========== 20.1 truss on Solaris: ---------------------truss -aef -o /tmp/trace svrmgrl To trace what a Unix process is doing enter: truss -rall -wall -p truss -p $ lsnrctl dbsnmp_start NOTE: The "truss" command works on SUN and Sequent. Use "tusc" on HP-UX, "strace" on Linux, "trace" on SCO Unix or call your system administrator to find the equivalent command on your system. Monitor your Unix system: Solaris: Truss is used to trace the system/library calls (not user calls) and signals made/received by a new or existing process. It sends the output to stderr. NOTE: Trussing a process throttles that process to your display speed. Use -wall and -rall sparingly. Truss usage truss truss
-a -a
-e -e
-f -f
-rall -rall
-wall -wall
-p
-a -e -f
Show arguments passed to the exec system calls Show environment variables passed to the exec system calls Show forked processes (they will have a different pid: in column 1) -rall Show all read data (default is 32 bytes) -wall Show all written data (default is 32 bytes) -p Hook to an existing process (must be owner or root) Specify a program to run Truss examples # truss -rall -wall -f -p # truss -rall -wall lsnrctl start # truss -aef lsnrctl dbsnmp_start 20.2 syscalls command on AIX: ----------------------------1. syscalls Command Purpose Provides system call tracing and counting for specific processes and the system. Syntax To Create or Destroy Buffer:
syscalls [ [ -enable
bytes ]| -disable
]
To Print System Call Counts: syscalls -c To Print System Call Events or Start Tracing: syscalls [ -o filename ] [ -t ] { [ [ -p pid ] -start | -stop
] | -x
program }
Description The syscalls (system call tracing) command, captures system call entry and exit events by individual processes or all processes on the system. The syscalls command can also maintain counts for all system calls made over long periods of time. Notes: System call events are logged in a shared-memory trace buffer. The same shared memory identifier may be used by other processes resulting in a collision. In such circumstances, the -enable flag needs to be issued. The syscalls command does not use the trace daemon. The system crashes if ipcrm -M sharedmemid is run after syscalls has been run. Run stem -shmkill instead of running ipcrm -M to remove the shared memory segment. Flags -c Prints a summary of system call counts for all processes. The counters are not reset. -disable Destroys the system call buffer and disables system call tracing and counting. -enable bytes Creates the system call trace buffer. If this flag is not used, the syscalls command creates a buffer of the default size of 819,200 bytes. Use this flag if events are not being logged in the buffer. This is the result of a collision with another process using the same shared memory buffer ID. -o filename
Prints output to filename rather than standard out.
-p pid When used with the -start flag, only events for processes with this pid will be logged in the syscalls buffer. When used with the -stop option, syscalls filters the data in the buffer and only prints output for this pid. -start Resets the trace buffer pointer. This option enables the buffer if it does not exist and resets the counters to zero. -stop Stops the logging of system call events and prints the contents of the buffer. -t
Prints the time associated with each system call event alongside the event.
-x program Runs program while logging events for only that process. The buffer is enabled if needed.
Security Access Control: You must be root or a member of the perf group to run this command. Examples To collect system calls for a particular program, enter: syscalls -x /bin/ps Output similar to the following appears: PID TTY TIME CMD 19841 pts/4 0:01 /bin/ksh 23715 pts/4 0:00 syscalls -x /bin/ps 30720 pts/4 0:00 /bin/ps 34972 pts/4 0:01 ksh PID System Call 30720 .kfork Exit , return=0 Call preceded tracing. 30720 .getpid () = 30720 30720 .sigaction (2, 2ff7eba8, 2ff7ebbc) = 0 30720 .sigaction (3, 2ff7eba8, 2ff7ebcc) = 0 30720 .sigprocmask (0, 2ff7ebac, 2ff7ebdc) = 0 30720 .sigaction (20, 2ff7eba8, 2ff7ebe8) = 0 30720 .kfork () = 31233 30720 .kwaitpid (2ff7ebfc, 31233, 0, 0) = 31233 30720 .sigaction (2, 2ff7ebbc, 0) = 0 30720 .sigaction (3, 2ff7ebcc, 0) = 0 30720 .sigaction (20, 2ff7ebe8, 0) = 0 30720 .sigprocmask (2, 2ff7ebdc, 0) = 0 30720 .getuidx (4) = 0 30720 .getuidx (2) = 0 30720 .getuidx (1) = 0 30720 .getgidx (4) = 0 30720 .getgidx (2) = 0 30720 .getgidx (1) = 0 30720 ._load NoFormat, (0x2ff7ef54, 0x0, 0x0, 0x2ff7ff58) = 537227760 30720 .sbrk (65536) = 537235456 30720 .getpid () = 30720 To produce a count of system calls made by all processes, enter: syscalls -start followed by entering: syscalls -c Output similar to the following appears: System Call Counts for all processes 5041 .lseek 4950 .kreadv 744 .sigaction 366 .close 338 .sbrk 190 .kioctl 120 .getuidx 116 .kwritev 108 .kfcntl 105 .getgidx 95 .kwaitpid 92 .gettimer 92 .select 70 .getpid
70 52 51 51 35 35 33 33 28 27 16 15 15 15 10 9 4 3 3 3 2 2 2 1 1 1 1 1 1 1 1 1
Files /usr/bin/syscalls
.sigprocmask .execve ._exit .kfork .open ._load .pipe .incinterval .sigreturn .access .brk .times .privcheck .gettimerid .statx .STEM_R10string .sysconfig .P2counters_accum .shmget .shmat .setpgid .shmctl .kioctl .Patch_Demux_Addr_2 .Patch_Demux_Addr_High .STEM_R3R4string .shmdt .Stem_KEX_copy_demux_entry .STEM_R3R4string .Patch_Demux_Addr_1 .pause .accessx Contains the syscalls command.
20.3 truss command on AIX: -------------------------AIX 5.1,5.2,5.3 The truss command is also available for SVR4 UNIX-based environments. This command is useful for tracing system calls in one or more processes. In AIX 5.2, all base system call parameter types are now recognized. In AIX 5.1, only about 40 system calls were recognized. Truss is a /proc based debugging tool that executes and traces a command, or traces an existing process. It prints names of all system calls made with their arguments and return code. System call parameters are displayed symbolically. It prints information about all signals received by a process. The AIX 5.2 version supports library calls tracing. For each call, it prints parameters and return codes. It can also trace a subset of libraries and a subset of routines in a given library. The timestamps on each line
are also supported. In AIX 5.2, truss is packaged with bos.sysmgt.serv_aid, which is installable from the AIX base installation media. See the command reference for details and examples, or use the information below. -a Displays the parameter strings that are passed in each executed system call. # truss �a
sleep
execve("/usr/bin/sleep", 0x2FF22980, 0x2FF22988) argc: 1 argv: sleep sbrk(0x00000000) = 0x200007A4 sbrk(0x00010010) = 0x200007B0 getuidx(4) = 0 � � __loadx(0x01000080, 0x2FF1E790, 0x00003E80, 0x2FF22720, 0x00000000) = 0xD0077130 access("/usr/lib/nls/msg/en_US/sleep.cat", 0) = 0 _getpid() = 31196 open("/usr/lib/nls/msg/en_US/sleep.cat", O_RDONLY) = 3 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kfcntl(3, F_SETFD, 0x00000001) = 0 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, "\0\001 �\001\001 I S O 8".., 4096) = 123 lseek(3, 0, 1) = 123 lseek(3, 0, 1) = 123 lseek(3, 0, 1) = 123 _getpid() = 31196 lseek(3, 0, 1) = 123 Usage: sleep Seconds kwrite(2, " U s a g e : s l e e p".., 21) = 21 kfcntl(1, F_GETFL, 0x00000000) = 2 kfcntl(2, F_GETFL, 0x00000000) = 2 _exit(2) -c Counts traced system calls, faults, and signals rather than displaying trace results line by line. A summary report is produced after the traced command terminates or when truss is interrupted. If the -f flag is also used, the counts include all traced Syscalls, Faults, and Signals for child processes. # truss �c ls syscall execve __loadx _exit close kwrite lseek setpid getuidx getdirent kioctl open
.00 .00 .00
seconds .00 17 1 2 .00 .00 .00 .00 .00 .00 .00
calls 1
5 1 1 19 3 3 1
errors
statx getgidx sbrk access kfcntl sys totals: usr time: elapsed:
.00 .00 .00 .00 .00 ---.01 .00 .01
2 18 4 1 6 --85
--0
More truss examples: -------------------truss -o /tmp/tst -p 307214 root@zd93l14:/tmp#cat tst = 0 = 0 = 0 = 0 = 0 0x43548E38) 0x434C3E38) 0x4343FE38) 0x433BBE38) 0x432B2E38) 0x4322EE38) 0x431AAE38) 0x42F99E38) 0x4301DE38) 0x42E90E38) 0x42E0CE38) 0x43337E38) 0x42F14E38) = 0 thread_tsleep(0, 0xF033153C, 0x00000000, 0x42D03E38) _nsleep(0x4128B8E0, 0x4128B958) = 0 _nsleep(0x4128B8E0, 0x4128B958) _nsleep(0x4128B8E0, 0x4128B958) _nsleep(0x4128B8E0, 0x4128B958) _nsleep(0x4128B8E0, 0x4128B958) thread_tsleep(0, 0xF033159C, 0x00000000, thread_tsleep(0, 0xF0331594, 0x00000000, thread_tsleep(0, 0xF033158C, 0x00000000, thread_tsleep(0, 0xF0331584, 0x00000000, thread_tsleep(0, 0xF0331574, 0x00000000, thread_tsleep(0, 0xF033156C, 0x00000000, thread_tsleep(0, 0xF0331564, 0x00000000, thread_tsleep(0, 0xF0331554, 0x00000000, thread_tsleep(0, 0xF033154C, 0x00000000, thread_tsleep(0, 0xF0331534, 0x00000000, thread_tsleep(0, 0xF033152C, 0x00000000, thread_tsleep(0, 0xF033157C, 0x00000000, thread_tsleep(0, 0xF0331544, 0x00000000,
= = = = = = = = = = = = =
0 0 0 0 0 0 0 0 0 0 0 0 0
= 0
20.4 man pages for truss AIX: ----------------------------Purpose Traces a process's system calls, dynamically loaded user level function calls, received signals, and incurred machine faults. Syntax truss [ -f] [ -c] [ -a] [ -l ] [ -d ] [ -D ] [ -e] [ -i] [ { -t | -x} [!] Syscall [...] ] [ -s [!] Signal [...] ] [ { -m }[!] Fault [...]] [ { -r | -w} [!] FileDescriptor [...] ] [ { -u } [!]LibraryName [...]:: [!]FunctionName [ ... ] ] [ -o Outfile] {Command| -p pid [. . .]} Description
The truss command executes a specified command, or attaches to listed process IDs, and produces a trace of the system calls, received signals, and machine faults a process incurs. Each line of the trace output reports either the Fault or Signal name, or the Syscall name with parameters and return values. The subroutines defined in system libraries are not necessarily the exact system calls made to the kernel. The truss command does not report these subroutines, but rather, the underlying system calls they make. When possible, system call parameters are displayed symbolically using definitions from relevant system header files. For path name pointer parameters, truss displays the string being pointed to. By default, undefined system calls are displayed with their name, all eight possible argments and the return value in hexadecimal format. When the -o flag is used with truss, or if standard error is redirected to a non-terminal file, truss ignores the hangup, interrupt, and signals processes. This facilitates the tracing of interactive programs which catch interrupt and quit signals from the terminal. If the trace output remains directed to the terminal, or if existing processes are traced (using the -p flag), then truss responds to hangup, interrupt, and quit signals by releasing all traced processes and exiting. This enables the user to terminate excessive trace output and to release previously existing processes. Released processes continue to function normally. Flags -a Displays the parameter strings which are passed in each executed system call. -c Counts traced system calls, faults, and signals rather than displaying trace results line by line. A summary report is produced after the traced command terminates or when truss is interrupted. If the -f flag is also used, the counts include all traced Syscalls, Faults, and Signals for child processes. -d A timestamp will be included with each line of output. Time displayed is in seconds relative to the beginning of the trace. The first line of the trace output will show the base time from which the individual time stamps are measured. By default timestamps are not displayed. -D Delta time is displayed on each line of output. The delta time represents the elapsed time for the LWP that incurred the event since the last reported event incurred by that thread. By default delta times are not displayed. -e Displays the environment strings which are passed in each executed system call. -f Follows all children created by the fork system call and includes their signals, faults, and system calls in the trace output. Normally, only the first-level command or process is traced. When the -f flag is specified, the process id is included with each line of trace output to show which process executed the system call or received the signal. -i Keeps interruptible sleeping system calls from being displayed. Certain system calls on terminal devices or pipes, such as open and kread, can sleep for indefinite periods and are interruptible. Normally, truss reports such sleeping system calls if they remain asleep for more than one second. The system call is then reported a second time when it completes. The -i flag causes such system calls to be reported only once, upon completion. -l Display the id (thread id) of the responsible LWP process along with truss
output. By default LWP id is not displayed in the output. -m [!]Fault Traces the machine faults in the process. Machine faults to trace must be separated from each other by a comma. Faults may be specified by name or number (see the sys/procfs.h header file). If the list begins with the "!" symbol, the specified faults are excluded from being traced and are not displayed with the trace output. The default is -mall -m!fltpage. -o Outfile Designates the file to be used for the trace output. By default, the output goes to standard error. -p Interprets the parameters to truss as a list of process ids for an existing process rather than as a command to be executed. truss takes control of each process and begins tracing it, provided that the user id and group id of the process match those of the user or that the user is a privileged user. -r [!] FileDescriptor Displays the full contents of the I/O buffer for each read on any of the specified file descriptors. The output is formatted 32 bytes per line and shows each byte either as an ASCII character (preceded by one blank) or as a two-character C language escape sequence for control characters, such as horizontal tab (\t) and newline (\n). If ASCII interpretation is not possible, the byte is shown in two-character hexadecimal representation. The first 16 bytes of the I/O buffer for each traced read are shown, even in the absence of the -r flag. The default is -r!all. -s [!] Signal Permits listing Signals to trace or exclude. Those signals specified in a list (separated by a comma) are traced. The trace output reports the receipt of each specified signal even if the signal is being ignored, but not blocked, by the process. Blocked signals are not received until the process releases them. Signals may be specified by name or number (see sys/signal.h). If the list begins with the "!" symbol, the listed signals are excluded from being displayed with the trace output. The default is -s all. -t [!] Syscall Includes or excludes system calls from the trace process. System calls to be traced must be specified in a list and separated by commas. If the list begins with an "!" symbol, the specified system calls are excluded from the trace output. The default is -tall. -u [!] [LibraryName [...]::[!]FunctionName [...] ] Traces dynamically loaded user level function calls from user libraries. The LibraryName is a comma-separated list of library names. The FunctionName is a comma-separated list of function names. In both cases the names can include name-matching metacharacters *, ?, [] with the same meanings as interpreted by the shell but as applied to the library/function name spaces, and not to files. A leading ! on either list specifies an exclusion list of names of libraries or functions not to be traced. Excluding a library excludes all functions in that library. Any function list following a library exclusion list is ignored. Multiple -u options may be specified and they are honored left-to-right. By default no library/function calls are traced. -w [!] FileDescriptor Displays the contents of the I/O buffer for each write on any of the listed file descriptors (see -r). The default is -w!all. -x [!] Syscall Displays data from the specified parameters of traced sytem calls in raw format, usually hexadecimal, rather than symbolically. The default is -x!all.
Examples 1. To produce a trace of the find command on the terminal, type: truss find . -print >find.out 2. To trace the lseek, close, statx, and open system calls, type: truss -t lseek,close,statx,open find . -print > find.out 3. To display thread id along with regular output for find command, enter: truss -l find . -print >find.out 4. To display timestamps along with regular output for find command, enter: truss -d find . -print >find.out 5. To display delta times along with regular output for find command, enter: truss -D find . -print >find.out 6. To trace the malloc() function call and exclude the strlen() function call in the libc.a library while running the ls command, enter: truss -u libc.a::malloc,!strlen ls 7. To trace all function calls in the libc.a library with names starting with "m" while running the ls command, enter: truss -u libc.a::m*,!strlen ls 8. To trace all function calls from the library libcurses.a and exclude calls from libc.a while running executable foo, enter: truss -u libcurses.a,!libc.a::* foo 9. To trace the refresh() function call from libcurses.a and the malloc() function call from libc.a while running the executable foo, enter: truss -u libc.a::malloc -u libcurses.a::refresh foo
20.5 Note: How to trace an AIX machine: --------------------------------------The trace facility and commands are provided as part of the Software Trace Service Aids fileset named bos.sysmgt.trace. To see if this fileset is installed, use the following command: # lslpp -l | grep bos.sysmgt.trace Taking a trace: --------------The events traced are referenced by hook identifiers. Each hook ID uniquely refers to a particular activity that can be traced. When tracing, you can select the hook IDs of interest and exclude others that are not relevant to your problem. A trace hook ID is a 3 digit hexidecimal number
that identifies an event being traced. Trace hook IDs are defined in the "/usr/include/sys/trchkid.h" file. The currently defined trace hook IDs can be listed using the trcrpt command: # trcrpt -j | sort | pg 001 002 003 004 005 006 .. ..
TRACE ON TRACE OFF TRACE HEADER TRACEID IS ZERO LOGFILE WRAPAROUND TRACEBUFFER WRAPAROUND
The trace daemon configures a trace session and starts the collection of system events. The data collected by the trace function is recorded in the trace log. A report from the trace log can be generated with the trcrpt command. When invoked with the -a, -x, or -X flags, the trace daemon is run asynchronously (i.e. as a background task). Otherwise, it is run interactively and prompts you for subcommands. Some trace examples: # trace # trace -Pp -a # trace # trace
-adf -C all -r PURR -o trace.raw -Jfop fact proc procd filephys filepfsv filepvl filepvld locks -A786578 -Jfop fact proc procd filephys filepfsv filepvl filepvld locks -Pp -a -Jfop fact proc procd filephys filepfsv filepvl filepvld locks -Pp -a
Some trcrpt examples: Examples 1
To format the trace log file and print the result, enter:
2
trcrpt | qprt To send a trace report to the /tmp/newfile file, enter:
3
trcrpt -o /tmp/newfile To display process IDs and exec path names in the trace report, enter:
4
trcrpt pid=on,exec=on -O /tmp/newfile To create trace ID histogram data, enter:
5
trcrpt -O hist=on To produce a list of all event groups, enter:
6 specify:
trcrpt -G The format of this report is shown under the trcevgrp command. To generate back-to-back LMT reports from the common and rare buffers,
trcrpt -M all 7 If, in the above example, the LMT files reside at /tmp/mydir, and we want the LMT traces to be merged, specify: 8 specify:
trcrpt -m -M all:/tmp/mydir To merge the system trace with the scdisk.hdisk0 component trace,
trcrpt -m -l scdisk.hdisk0 /var/adm/ras/trcfile 9 To merge LMT with the system trace while not eliminating duplicate events, specify: trcrpt -O removedups=off -m -M all /var/adm/ras/trcfile 10 To merge all component traces in /tmp/mydir with the LMT traces in the default LMT directory while showing the source file for each trace event, specify: trcrpt -O filename=on -m -M all /tmp/mydir Note: This is equivalent to: trcrpt -O filename=on -m -M all -l all:/tmp/mydir Note: If the traces are from a 64-bit kernel, duplicate entries will be removed. However, on the 32-bit kernel, duplicate entries will not be removed since we do not know the CPU IDs of the entries in the components traces. Another example of the usage of trace: ------------------------------------->> Obtaining a Sample Trace File Trace data accumulates rapidly. We want to bracket the data collection as closely around the area of interest as possible. One technique for doing this is to issue several commands on the same command line. For example: $ trace -a -k "20e,20f" -o ./trcraw ; cp ../bin/track /tmp/junk ; trcstop captures the execution of the cp command. We have used two features of the trace command. The -k "20e,20f" option suppresses the collection of events from the lockl and unlockl functions. These calls are numerous and add volume to the report without adding understanding at the level we're interested in. The -o ./trc_raw option causes the raw trace output file to be written in our local directory. Note: This example is more educational if the input file is not already cached in system memory. Choose as the source file any file that is about 50KB and has not been touched recently. >> Formatting the Sample Trace
We use the following form of the trcrpt command for our report: $ trcrpt -O "exec=on,pid=on" trcraw > /tmp/cp.rpt This reports both the fully qualified name of the file that is execed and the process ID that is assigned to it. A quick look at the report file shows us that there are numerous VMM page assign and delete events in the trace, like the following sequence: 1B1 ksh 8525 page delete: V.S=00 00.150E ppage=1F7F
0.003109888
0.162816
VMM del
ete_in_progress proce ss_private working_storage 1B0 ksh 8525 0.003141376 page assign: V.S=00 00.2F33 ppage=1F7F delete_in_progress process_private working_ storage
0.031488
VMM
We are not interested in this level of VMM activity detail at the moment, so we reformat the trace with: $ trcrpt -k "1b0,1b1" -O "exec=on,pid=on" trcraw > cp.rpt2 The -k "1b0,1b1" option suppresses the unwanted VMM events in the formatted output. It saves us from having to retrace the workload to suppress unwanted events. We could have used the -k function of trcrpt instead of that of the trace command to suppress the lockl and unlockl events, if we had believed that we might need to look at the lock activity at some point. If we had been interested in only a small set of events, we could have specified -d "hookid1,hookid2" to produce a report with only those events. Since the hook ID is the left-most column of the report, you can quickly compile a list of hooks to include or exclude. A comprehensive list of Trace hook IDs is defined in /usr/include/sys/trchkid.h. >> Reading a Trace Report The header of the trace report tells you when and where the trace was taken, as well as the command that was used to produce it: Fri Nov 19 12:12:49 1993 System: AIX ptool Node: 3 Machine: 000168281000 Internet Address: 00000000 0.0.0.0 trace -ak 20e 20f -o -o ./trc_raw The body of the report, if displayed in a small enough font, looks as follows:
ID PROCESS NAME KERNEL INTERRUPT 101 ksh 101 ksh 134 cp ../bin/trk/junk
PID
ELAPSED_SEC
DELTA_MSEC
8525 7214 7214
0.005833472 0.012820224 0.014451456
0.107008 0.031744 0.030464
APPL
SYSCALL kfork execve exec cp
In cp.rpt you can see the following phenomena: The fork, exec, and page fault activities of the cp process The opening of the input file for reading and the creation of the /tmp/junk file The successive read/write system calls to accomplish the copy The process cp becoming blocked while waiting for I/O completion, and the wait process being dispatched How logical-volume requests are translated to physical-volume requests The files are mapped rather than buffered in traditional kernel buffers, and the read accesses cause page faults that must be resolved by the Virtual Memory Manager. The Virtual Memory Manager senses sequential access and begins to prefetch the file pages. The size of the prefetch becomes larger as sequential access continues. When possible, the disk device driver coalesces multiple file requests into one I/O request to the drive. The trace output looks a little overwhelming at first. This is a good example to use as a learning aid. If you can discern the activities described, you are well on your way to being able to use the trace facility to diagnose system-performance problems. >> Filtering of the Trace Report The full detail of the trace data may not be required. You can choose specific events of interest to be shown. For example, it is sometimes useful to find the number of times a certain event occurred. To answer the question "How many opens occurred in the copy example?" first find the event ID for the open system call. This can be done as follows: $ trcrpt -j | grep -i open You should be able to see that event ID 15b is the open event. Now, process the data from the copy example as follows: $ trcrpt -d 15b -O "exec=on" trc_raw The report is written to standard output, and you can determine the number of open subroutines that occurred. If you want to see only the open subroutines that were performed by the cp process, run the report command again using the following: $ trcrpt -d 15b -p cp -O "exec=on" trc_raw
A Wrapper around trace: ----------------------Simple instructions for using the AIX trace facility >> Five aix commands are used: -trace -trcon -trcoff -trcstop -trcrpt These are described in AIX Commands Reference, Volume 5, but hopefully you won't have to dig into that. Scripts to download I've provided wrappers for the trace and trcrpt commands since there are various command-line parameters to specify. -atrace -atrcrpt >> Contents atrace: # To change from the default trace file, set TRCFILE to # the name of the raw trace file name here; this should # match the name of the raw trace file in atrcrpt. # Don't do this on AIX 4.3.3 ML 10, where you'll need # to use the default trace file, /usr/adm/ras/trcfile #TRCFILE="-o /tmp/raw" # trace categories not to collect IGNORE_VMM="1b0,1b1,1b2,1b3,1b5,1b7,1b8,1b9,1ba,1bb,1bc,1bd,1be" IGNORE_LOCK=20e,20f IGNORE_PCI=2e6,2e7,2e8 IGNORE_SCSI=221,223 IGNORE_OTHER=100,10b,116,119,11f,180,234,254,2dc,402,405,469,7ff IGNORE="$IGNORE_VMM,$IGNORE_LOCK,$IGNORE_PCI,$IGNORE_SCSI,$IGNORE_LVM,$IGNORE_OTHE R" trace -a -d -k $IGNORE $TRCFILE >> Contents atrcrpt: # # # # # #
To change from the default trace file, set TRCFILE to the name of the raw trace file name here; this should match the name of the raw trace file in atrace. Don't do this on AIX 4.3.3 ML 10, where you'll need to use the default trace file, /usr/adm/ras/trcfile TRCFILE=/tmp/raw
# edit formatted trace file name here FMTFILE=/tmp/fmt trcrpt -O pid=on,tid=on,timestamp=1 $TRCFILE >$FMTFILE
Setup instructions edit atrace and atrcrpt and ensure that names of files for raw and formatted trace are appropriate Please see the comments in the scripts about 4.3.3 ML 10 being broken for trcrpt, such that the default file name needs to be used. You may find that specifying non-default filenames does not have the desired effect. make atrace and atrcrpt executable via chmod Data collection ./atrace (this is my wrapper for the trace command) trcon (at this point we're collecting the trace; wait for a bit of time to trace whatever the failure is) trcoff trcstop ./atrcrpt (this is my wrapper for formatting the report) After running atrcrpt, the formatted report will be in file /tmp/fmt. Sample section of formatted trace Note that failing system calls generally show "error Esomething" in the race, as highlighted below. The second column is the process id and the third column is the thread id. Once you see something of interest in the trace, you may want to use grep to pull out all records for that process id, since in general the trace is interleaved with the activity of all the processes in the system. 101 14690 19239 statx LR = D0174110 107 14690 19239 lookuppn: /usr/HTTPServer/htdocs/en_US/manual/ibm/index.htmlxxxxxxxxxxx 107 14690 19239 lookuppn: file not found 104 14690 19239 return from statx. error ENOENT [79 usec] 101 14690 19239 statx LR = D0174110 107 14690 19239 lookuppn: /usr/HTTPServer/htdocs/en_US/manual/ibm 104 14690 19239 return from statx [36 usec] Note about an AIX trace on Websphere: ------------------------------------In addition to the WebSphere� MQ trace, WebSphere MQ for AIX� users can use the standard AIX system trace. AIX system tracing is a two-step process: >> Gathering the data >> Formatting the results WebSphere MQ uses two trace hook identifiers: X'30D' This event is recorded by WebSphere MQ on entry to or exit from a subroutine.
X'30E' This event is recorded by WebSphere MQ to trace data such as that being sent or received across a communications network. Trace provides detailed execution tracing to help you to analyze problems. IBM� service support personnel might ask for a problem to be re-created with trace enabled. The files produced by trace can be very large so it is important to qualify a trace, where possible. For example, you can optionally qualify a trace by time and by component. There are two ways to run trace: >> Interactively. The following sequence of commands runs an interactive trace on the program myprog and ends the trace. trace -j30D,30E -o trace.file ->!myprog ->q >> Asynchronously. The following sequence of commands runs an asynchronous trace on the program myprog and ends the trace. trace -a -j30D,30E -o trace.file myprog trcstop You can format the trace file with the command: trcrpt -t /usr/mqm/lib/amqtrc.fmt trace.file > report.file report.file is the name of the file where you want to put the formatted trace output.
20.6 Nice example: Tracing with truss on AIX: --------------------------------------------Application tracing displays the calls that an application makes to external libraries and the kernel. These calls give the application access to the network, the file system, and the display. By watching the calls and their results, you can get some idea of what the application "expects", which can lead to a solution. Each UNIX� system provides its own commands for tracing. This article introduces you to truss, which Solaris and AIX� support. On Linux�, you perform tracing with the strace command. Although the command-line parameters might be slightly different, application tracing on other UNIX flavors might go by the names ptrace, ktrace, trace, and tusc. >> A classic file permissions problem
One class of problems that plagues systems administrators is file permissions. An application likely has to open certain files to do its work. If the open operation fails, the application should let the administrator know. However, developers often forget to check the result of functions or, to add to the confusion, perform the check, but don't adequately handle the error. For example, here's the output of an application that's failing to open: $ ./openapp This should never happen! After running the fictitious openapp application, I received the unhelpful (and false) error message, This should never happen!. This is a perfect time to introduce truss. Listing 1 shows the same application run under the truss command, which shows all the function calls that this program made to outside libraries. Listing 1. Openapp run under truss $ truss ./openapp execve("openapp", 0xFFBFFDEC, 0xFFBFFDF4) argc = 1 getcwd("/export/home/sean", 1015) = 0 stat("/export/home/sean/openapp", 0xFFBFFBC8) = 0 open("/var/ld/ld.config", O_RDONLY) Err#2 ENOENT stat("/opt/csw/lib/libc.so.1", 0xFFBFF6F8) Err#2 ENOENT stat("/lib/libc.so.1", 0xFFBFF6F8) = 0 resolvepath("/lib/libc.so.1", "/lib/libc.so.1", 1023) = 14 open("/lib/libc.so.1", O_RDONLY) = 3 memcntl(0xFF280000, 139692, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0 close(3) = 0 getcontext(0xFFBFF8C0) getrlimit(RLIMIT_STACK, 0xFFBFF8A0) = 0 getpid() = 7895 [7894] setustack(0xFF3A2088) open("/etc/configfile", O_RDONLY) Err#13 EACCES [file_dac_read] ioctl(1, TCGETA, 0xFFBFEF14) = 0 fstat64(1, 0xFFBFEE30) = 0 stat("/platform/SUNW,Sun-Blade-100/lib/libc_psr.so.1", 0xFFBFEAB0) = 0 open("/platform/SUNW,Sun-Blade-100/lib/libc_psr.so.1", O_RDONLY) = 3 close(3) = 0 This should never happen! write(1, " T h i s s h o u l d ".., 26) = 26 _exit(3)
Each line of the output represents a function call that the application made along with the return value, if applicable. (You don't need to know each function call, but for more information, you can call up the man page for the function, such as with the command man open.) To find the call that is potentially causing the problem, it's often easiest to start at the end (or as close as
possible to where the problems start). For example, you know that the application outputs This should never happen!, which appears near the end of the output. Chances are that if you find this message and work your way up through the truss command output, you'll come across the problem. Scrolling up from the error message, notice the line beginning with open("/etc/configfile"..., which not only looks relevant but also seems to return an error of Err#13 EACCES. Looking at the man page for the open() function (with man open), it's evident that the purpose of the function is to open a file -- in this case, /etc/configfile -- and that a return value of EACCES means that the problem is related to permissions. Sure enough, a look at /etc/configfile shows that the user doesn't have permissions to read the file. A quick chmod later, and the application is running properly. The output of Listing 1 shows two other calls, open() and stat(), that return an error. Many of the calls toward the beginning of the application, including the other two errors, are added by the operating system as it runs the application. Only experience will tell when the errors are benign and when they aren't. In this case, the two errors and the three lines that follow them are trying to find the location of libc.so.1, which they eventually do. You'll see more about shared library problems later.
>> The application doesn't start Sometimes, an application fails to start properly; but rather than exiting, it just hangs. This behavior is often a symptom of contention for a resource (such as two processes competing for a file lock), or the application is looking for something that is not coming back. This latter class of problems could be almost anything, such as a name lookup that's taking a long time to resolve, or a file that should be found in a certain spot but isn't there. In any case, watching the application under truss should reveal the culprit. While the first code example showed an obvious link between the system call causing the problem and the file, the example you're about to see requires a bit more sleuthing. Listing 2 shows a misbehaving application called Getlock run under truss. Listing 2. Getlock run under truss $ truss ./getlock execve("getlock", 0xFFBFFDFC, 0xFFBFFE04) argc = 1 getcwd("/export/home/sean", 1015) = 0 resolvepath("/export/home/sean/getlock", "/export/home/sean/getlock", 1023) = 25 resolvepath("/usr/lib/ld.so.1", "/lib/ld.so.1", 1023) = 12
stat("/export/home/sean/getlock", 0xFFBFFBD8) open("/var/ld/ld.config", O_RDONLY) stat("/opt/csw/lib/libc.so.1", 0xFFBFF708) stat("/lib/libc.so.1", 0xFFBFF708) resolvepath("/lib/libc.so.1", "/lib/libc.so.1", open("/lib/libc.so.1", O_RDONLY) close(3) getcontext(0xFFBFF8D0) getrlimit(RLIMIT_STACK, 0xFFBFF8B0) getpid() setustack(0xFF3A2088) open("/tmp/lockfile", O_WRONLY|O_CREAT, 0755) getpid() fcntl(3, F_SETLKW, 0xFFBFFD60) (sleeping...)
= 0 Err#2 ENOENT Err#2 ENOENT = 0 1023) = 14 = 3 = 0 = 0 = 10715 [10714] = 3 = 10715 [10714]
The final call, fcntl(), is marked as sleeping, because the function is blocking. This means that the function is waiting for something to happen, and the kernel has put the process to sleep until the event occurs. To determine what the event is, you must look at fcntl(). The man page for fcntl() (man fcntl) describes the function simply as "file control" on Solaris and "manipulate file descriptor" on Linux. In all cases, fcntl() requires a file descriptor, which is an integer describing a file the process has opened, a command that specifies the action to be taken on the file descriptor, and finally any arguments required for the specific function. In the example in Listing 2, the file descriptor is 3, and the command is F_SETLKW. (The 0xFFBFFD60 is a pointer to a data structure, which doesn't concern us now.) Digging further, the man page states that F_SETLKW opens a lock on the file and waits until the lock can be obtained. From the first example involving the open() system call, you saw that a successful call returns a file descriptor. In the truss output of Listing 2, there are two cases in which the result of open() returns 3. Because file descriptors are reused after they are closed, the relevant open() is the one just above fcntl(), which is for /tmp/lockfile. A utility like lsof lists any processes holding open a file. Failing that, you could trace through /proc to find the process with the open file. However, as is usually the case, a file is locked for a good reason, such as limiting the number of instances of the application or configuring the application to run in a user-specific directory. >> Attaching to a running process Sometimes, an application is already running when a problem occurs. Being able to run an already-running process under truss would be helpful. For example, notice that in the output of the Top application, a certain process has been consuming 95 percent of the CPU for quite some time, as shown in Listing
3. Listing 3. Top output showing a CPU-intensive process PID USERNAME LWP PRI NICE SIZE 11063 sean 1 0 0 1872K
RES STATE 952K run
TIME CPU COMMAND 87.9H 94.68% udpsend
The -p option to truss allows the owner of the process, or root, to attach to a running process and view the system call activity. The process id (PID) is required. In the example shown in Listing 3, the PID is 11063. Listing 4 shows the system call activity of the application in question. Listing 4. truss output after attaching to a running process $ truss -p 11063: sendto(3, sendto(3, sendto(3, sendto(3, sendto(3, sendto(3, sendto(3, sendto(3, . repeats
" a " a " a " a " a " a " a " a ...
b b b b b b b b
c", c", c", c", c", c", c", c",
3, 3, 3, 3, 3, 3, 3, 3,
0, 0, 0, 0, 0, 0, 0, 0,
0xFFBFFD58, 0xFFBFFD58, 0xFFBFFD58, 0xFFBFFD58, 0xFFBFFD58, 0xFFBFFD58, 0xFFBFFD58, 0xFFBFFD58,
16) 16) 16) 16) 16) 16) 16) 16)
= = = = = = = =
3 3 3 3 3 3 3 3
The sendto() function's man page (man sendto) shows that this function is used to send a message from a socket -- typically, a network connection. The output of truss shows the file descriptor (the first 3) and the data being sent (abc). Indeed, capturing a sample of network traffic with the snoop or tcpdump tool shows a large amount of traffic being directed to a particular host, which is likely not the result of a properly behaving application. Note that truss was not able to show the creation of file descriptor 3, because you had attached after the descriptor was created. This is one limitation of attaching to a running process and the reason why you should gather other information using a tool, such as a packet analyzer before jumping to conclusions. This example might seem somewhat contrived (and technically it was, because I wrote the udpsend application to demonstrate how to use truss), but it is based on a real situation. I was investigating a process running on a UNIX-based appliance that had a CPU-bound process. Tracing the application showed the same packet activity. Tracing with a network analyzer showed the packets were being directed to a host on the Internet. After escalating with the vendor, I determined that the problem was their application failing to perform proper error checking
on a binary configuration file. The file had somehow become corrupted. As a result, the application interpreted the file incorrectly and repeatedly hammered a random IP address with User Datagram Protocol (UDP) datagrams. After I replaced the file, the process behaved as expected.
>> Filtering output After a while, you'll get the knack of what to look for. While it's possible to use the grep command to go through the output, it's easier to configure truss to focus only on certain calls. This practice is common if you're trying to determine how an application works, such as which configuration files the application is using. In this case, the open() and stat() system calls point to any files the application is trying to open. You use open() to open a file, but you use stat() to find information about a file. Often, an application looks for a file with a series of stat() calls, and then opens the file it wants. For truss, you add filtering system calls with the -t option. For strace under Linux, you use -e. In either case, you pass a comma-separated list of system calls to be shown on the command line. By prefixing the list with the exclamation mark (!), the given calls are filtered out of the output. Listing 5 shows a fictitious application looking for a configuration file. Listing 5. truss output filtered to show only stat() and open() functions $ truss -tstat,open ./app stat("/export/home/sean/app", 0xFFBFFBD0) = 0 open("/var/ld/ld.config", O_RDONLY) Err#2 ENOENT stat("/opt/csw/lib/libc.so.1", 0xFFBFF700) Err#2 ENOENT stat("/lib/libc.so.1", 0xFFBFF700) = 0 open("/lib/libc.so.1", O_RDONLY) = 3 stat("/export/home/sean/.config", 0xFFBFFCF0) Err#2 ENOENT stat("/etc/app/configfile", 0xFFBFFCF0) Err#2 ENOENT stat("/etc/configfile", 0xFFBFFCF0) = 0 open("/etc/configfile", O_RDONLY) = 3 The final four lines are the key here. The stat() function for /export/home/sean/.config results in ENOENT, which means that the file wasn't found. The code then tries /etc/app/configfile before it finds the correct information in /etc/configfile. The significance of first checking in the user's home directory is that you can override the configuration by user.
>> Final thoughts
Whether your operating system uses truss, strace, trace, or something else, the ability to peer into an application's behavior is a powerful tool for problem solving. The methodology can be summed up as follows: Describe the problem. Trace the application. Start at the spot at which the problem occurs and work backward through the system calls to identify the problem. Use the man pages for help on interpreting the system calls. Correct the behavior and test. Tracing application behavior is a powerful troubleshooting tool, because you're observing the system calls that the application makes to the operating system. When the usual problem-solving methods fail, turn to application tracing.
20.7. snap command on AIX: -------------------------The snap command gathers system configuration information and compresses the information into a pax file. The information gathered with the snap command may be required to identify and resolve system problems. In normal conditions, the command "snap -gc" should be sufficient. The pax file will be stored in /tmp/ibmsupt # snap -gc create the following file: /tmp/ibmsupt/snap.pax.Z Further info: snap Command Purpose Gathers system configuration information. Syntax snap [ -a ] [ -A ] [ -b ] [ -B ] [ -c ] [ -C ] [ -D ] [ -f ] [ -g ] [ -G ] [ -i ] [ -k ] [ -l ] [ -L ][ -n ] [ -N ] [ -p ] [ -r ] [ -R ] [ -s ] [ -S ] [ -t ] [ -T Filename ] [ -w ] [ -o OutputDevice ] [ -d Dir ] [ -v Component ] [ -O FileSplitSize ] [ -P Files ] [ script1 script2 ... | All | file:filepath ] snap [ -a ] [ -A ] [ -b ] [ -B ] [ -c ] [ -C ] [ -D ] [ -f ] [ -g ] [ -G ]
[ -i ] [ -k ] [ -l ] [ -L ][ -n ] [ -N ] [ -p ] [ -r ] [ -R ] [ -s ] [ -S ] [ -t ] [ -T OutputDevice ] [ -d Dir ] [ -v Component ] [ -O FileSplitSize ] [ -P Files ] [ script1 script2 ... | All | file:filepath ]
Filename ] [ -o
snap -e [ -m Nodelist ] [ -d Dir ] Description The snap command gathers system configuration information and compresses the information into a pax file. The file may then be written to a device such as tape or DVD, or transmitted to a remote system. The information gathered with the snap command might be required to identify and resolve system problems. Note: Root user authority is required to execute the snap command. Use the snap -o /dev/cd0 command to copy the compressed image to DVD. Use the snap -o /dev/rmt0 command to copy the image to tape. Use the snap -o /dev/rfd0 command to copy the compressed image to diskette. Use the snap -o /dev/rmt0 command to copy the image to tape. Approximately 8MB of temporary disk space is required to collect all system information, including contents of the error log. If you do not gather all system information with the snap -a command, less disk space may be required (depending on the options selected). Note: If you intend to use a tape to send a snap image to IBM(R) for software support, the tape must be one of the following formats: * 8mm, 2.3 Gb capacity * 8mm, 5.0 Gb capacity * 4mm, 4.0 Gb capacity Using other formats prevents or delays IBM software support from being able to examine the contents. The snap -g command gathers general system information, including the following: * Error report * Copy of the customized Object Data Manager (ODM) database * Trace file * User environment * Amount of physical memory and paging space * Device and attribute information * Security user information The output of the snap -g command is written to the /tmp/ibmsupt/general/general.snap file. The snap command checks for available space in the /tmp/ibmsupt directory, the default directory for snap command output. You can write the output to another directory by using the -d flag. If there is not enough space to hold the snap command output, you must expand the file system. Each execution of the snap command appends information to previously created files. Use the -r flag to remove previously gathered and saved information.
Flags: -a
Gathers all system configuration information. This option requires approximately 8MB of temporary disk space. -A Gathers asynchronous (TTY) information. -b Gathers SSA information. -B Bypasses collection of SSA adapter dumps. The -B flag only works when the -b flag is also specified; otherwise, the -B flag is ignored. -c Creates a compressed pax image (snap.pax.Z file) of all files in the /tmp/ibmsupt directory tree or other named output directory. Note: Information not gathered with this option should be copied to the snap directory tree before using the -c flag. If a test case is needed to demonstrate the system problem, copy the test case to the /tmp/ibmsupt/testcase directory before compressing the pax file. -C Retrieves all the files in the fwdump_dir directory. The files are placed in the "general" subdirectory. The -C snap option behaves the same as -P*. -D Gathers dump and /unix information. The primary dump device is used. Notes: 1 If bosboot -k was used to specify the running kernel to be other than /unix, the incorrect kernel is gathered. Make sure that /unix is , or is linked to, the kernel in use when the dump was taken. 2 If the dump file is copied to the host machine, the snap command does not collect the dump image in the /tmp/ibmsupt/dump directory. Instead, it creates a link in the dump directory to the actual dump image. -d AbsolutePath Identifies the optional snap command output directory (/tmp/ibmsupt is the default). You must specify the absolute path. -e Gathers HACMP(TM) specific information. Note: HACMP specific data is collected from all nodes belonging to the cluster . This flag cannot be used with any other flags except -m and -d. -f Gathers file system information. -g Gathers the output of the lslpp -hac command, which is required to recreate exact operating system environments. Writes output to the /tmp/ibmsupt/general/lslpp.hBc file. Also collects general system information and writes the output to the /tmp/ibmsupt/general/general.snap file. -G Includes predefined Object Data Manager (ODM) files in general information collected with the -g flag. -i Gathers installation debug vital product data (VPD) information.
21. Logfiles: ============= Solaris: -------Unix message files record all system problems like disk errors, swap errors, NFS problems, etc. Monitor the following files on your system to detect system problems: tail -f /var/adm/SYSLOG tail -f /var/adm/messages tail -f /var/log/syslog You can also use the dmesg command. Messages are recorded by the syslogd demon. Diagnostics can be done from the OK prompt after a reboot, like probe-scsci, showdevs, show-disks, test memory etc.. You can also use SunVTS tool to run diagnostics. SunVTS is Suns's Validation Test package. System dumps: You can manage system dumps by using the dumpadm command. AIX: ---Periodical the following files have to be decreased in size. You can use cat /dev/null command Example: cat /dev/null >/var/adm/sulog /var/adm/sulog /var/adm/cron/log /var/adm/wtmp /etc/security/failedlogin Notes about the errorlog, thats the file /var/adm/ras/errlog. Do NOT use cat /dev/null to clear the errorlog. Use instead the following procedure: # /usr/lib/errstop (stop the error daemon) move the errlog file # /usr/lib/errstart (start the error daemon)
errdemon: --------On most UNIX systems, information and errors from system events and processes are managed by the
syslog daemon (syslogd); depending on settings in the configuration file /etc/syslog.conf, messages are passed from the operating system, daemons, and applications to the console, to log files, or to nowhere at all. AIX includes the syslog daemon, and it is used in the same way that other UNIXbased operating systems use it. In addition to syslog, though, AIX also contains another facility for the management of hardware, operating system, and application messages and errors. This facility, while simple in its operation, provides unique and valuable insight into the health and happiness of an AIX system. The AIX error logging facility components are part of the bos.rte and the bos.sysmgt.serv_aid packages, both of which are automatically placed on the system as part of the base operating system installation. Unlike the syslog daemon, which performs no logging at all in its default configuration as shipped, the error logging facility requires no configuration before it can provide useful information about the system. The errdemon is started during system initialization and continuously monitors the special file /dev/error for new entries sent by either the kernel or by applications. The label of each new entry is checked against the contents of the Error Record Template Repository, and if a match is found, additional information about the system environment or hardware status is added, before the entry is posted to the error log. The actual file in which error entries are stored is configurable; the default is /var/adm/ras/errlog. That file is in a binary format and so should never be truncated or zeroed out manually. The errlog file is a circular log, storing as many entries as can fit within its defined size. A memory buffer is set by the errdemon process, and newly arrived entries are put into the buffer before they are written to the log to minimize the possibility of a lost entry. The name and size of the error log file and the size of the memory buffer may be viewed with the errdemon command: [aixhost:root:/] # /usr/lib/errdemon -l Error Log Attributes -------------------------------------------Log File /var/adm/ras/errlog Log Size 1048576 bytes Memory Buffer Size 8192 bytes The parameters displayed may be changed by running the errdemon command with other flags, documented in the errdemon man page. The default sizes and values have always been sufficient on our systems, so I've never had reason to change them. Due to use of a circular log file, it is not necessary (or even possible) to rotate the error log.
Without intervention, errors will remain in the log indefinitely, or until the log fills up with new entries. As shipped, however, the crontab for the root user contains two entries that are executed daily, removing hardware errors that are older than 90 days, and all other errors that are older than 30 days. 0 11 0 12
* *
* *
* /usr/bin/errclear -d S,O 30 * /usr/bin/errclear -d H 90
The errdemon deamon constantly checks the /dev/error special file, and when new data is written, the deamon conducts a series of operations. - To determine the path to your system's error logfile, run the command: # /usr/lib/errdemon -l Error Log Attributes Log File /var/adm/ras/errlog Log Size 1048576 bytes Memory 8192 bytes - To change the maximum size of the error log file, enter: # /usr/lib/errdemon -s 200000 You can generate the error reports using smitty or through the errpt command. # smitty errpt information.
gives you a dialog screen where you can select types of
# errpt -a # errpt - d H # errpt -a|pg Produces a detailed report for each entry in the error log # errpt -aN hdisk1 Displays an error log for ALL errors occurred on this drive. If more than a few errors occur within a 24 hour period, execute the CERTIFY process under DIAGNOSTICS to determine if a PV is becoming marginal. If you use the errpt without any options, it generates a summary report. If used with the -a option, a detailed report is created. You can also display errors of a particular class, for example for the Hardware class. Examples using errpt: --------------------To display a complete summary report, enter: errpt To display a complete detailed report, enter: errpt -a To display a detailed report of all errors logged for the error identifier
E19E094F, enter: errpt -a -j E19E094F To display a detailed report of all errors logged in the past 24 hours, enter: errpt -a -s mmddhhmmyy where the mmddhhmmyy string equals the current month, day, hour, minute, and year, minus 24 hours. To list error-record templates for which logging is turned off for any error-log entries, enter: errpt -t -F log=0 To view all entries from the alternate error-log file /var/adm/ras/errlog.alternate, enter: errpt -i /var/adm/ras/errlog.alternate To view all hardware entries from the alternate error-log file /var/adm/ras/errlog.alternate, enter: errpt -i /var/adm/ras/errlog.alternate -d H To display a detailed report of all errors logged for the error label ERRLOG_ON, enter: errpt -a -J ERRLOG_ON To display a detailed report of all errors and group duplicate errors, enter: errpt -aD To display a detailed report of all errors logged for the error labels DISK_ERR1 and DISK_ERR2 during the month of August, enter: errpt -a -J DISK_ERR1,DISK_ERR2 -s 0801000004 -e 0831235904" errclear: Deletes entries in the error log Example: errclear 0 (Truncates the errlog to 0 bytes) Example errorreport: -------------------Example 1: ---------P550:/home/reserve $ errpt IDENTIFIER 0EC00096 0EC00096 0EC00096 0EC00096 F7DDA124 52715FA5 CAD234BE 613E5F38 613E5F38 613E5F38
TIMESTAMP 0130224507 0130224007 0130224007 0130223507 0130223507 0130223507 0130223507 0130223507 0130223507 0130223507
T P P P P U U U P P P
C U U U U H H H H H H
RESOURCE_NAME SYSPFS SYSPFS SYSPFS SYSPFS LVDD LVDD LVDD LVDD LVDD LVDD
DESCRIPTION STORAGE SUBSYSTEM FAILURE STORAGE SUBSYSTEM FAILURE STORAGE SUBSYSTEM FAILURE STORAGE SUBSYSTEM FAILURE PHYSICAL VOLUME DECLARED MISSING FAILED TO WRITE VOLUME GROUP STATUS AREA QUORUM LOST, VOLUME GROUP CLOSING I/O ERROR DETECTED BY LVM I/O ERROR DETECTED BY LVM I/O ERROR DETECTED BY LVM
0873CF9F 0EC00096 51E537B5 291D64C3 291D64C3 BFE4C025 51E537B5 291D64C3 291D64C3 51E537B5 291D64C3 291D64C3 BFE4C025 BFE4C025 BFE4C025 BFE4C025 BFE4C025 BFE4C025 0EC00096 BFE4C025 D2A1B43E D2A1B43E CD546B25 CD546B25 1ED0A744 CD546B25 D2A1B43E 1ED0A744 F7DDA124 52715FA5 CAD234BE 613E5F38 EAA3D429 613E5F38 613E5F38 41BF2110 613E5F38 CAD234BE F7DDA124 41BF2110 613E5F38 6472E03B FEC31570 C14C511C BFE4C025 FE2DEE00 FE2DEE00 B6048838 B6048838
0130191907 0130162407 0130161807 0130161807 0130161807 0130161807 0130161707 0130161707 0130161707 0130161707 0130161707 0130161707 0130161607 0130161407 0130161307 0130161307 0130161207 0130161207 0130161207 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130161107 0130144307 0130143207 0129100507 0129100307
T P P I I P P I I P I I P P P P P P P P P P I I P I P P U U U P U P P U P U U U P P P T P P P P P
S U H H H H H H H H H H H H H H H H U H U U O O U O U U H H H H S H H H H H H H H H H H H S S S S
pts/4 SYSPFS sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 sysplanar0 SYSPFS sysplanar0 SYSPFS SYSPFS SYSPFS SYSPFS SYSPFS SYSPFS SYSPFS SYSPFS LVDD LVDD LVDD LVDD LVDD LVDD LVDD LVDD LVDD LVDD LVDD LVDD LVDD sysplanar0 sisscsia2 scsi5 sysplanar0 SYSXAIXIF SYSXAIXIF SYSPROC SYSPROC
TTYHOG OVER-RUN STORAGE SUBSYSTEM FAILURE platform_dump saved to file platform_dump indicator event platform_dump indicator event UNDETERMINED ERROR platform_dump saved to file platform_dump indicator event platform_dump indicator event platform_dump saved to file platform_dump indicator event platform_dump indicator event UNDETERMINED ERROR UNDETERMINED ERROR UNDETERMINED ERROR UNDETERMINED ERROR UNDETERMINED ERROR UNDETERMINED ERROR STORAGE SUBSYSTEM FAILURE UNDETERMINED ERROR FILE SYSTEM CORRUPTION FILE SYSTEM CORRUPTION FILE SYSTEM RECOVERY REQUIRED FILE SYSTEM RECOVERY REQUIRED FILE SYSTEM LOGGING SUSPENDED FILE SYSTEM RECOVERY REQUIRED FILE SYSTEM CORRUPTION FILE SYSTEM LOGGING SUSPENDED PHYSICAL VOLUME DECLARED MISSING FAILED TO WRITE VOLUME GROUP STATUS AREA QUORUM LOST, VOLUME GROUP CLOSING I/O ERROR DETECTED BY LVM PHYSICAL PARTITION MARKED STALE I/O ERROR DETECTED BY LVM I/O ERROR DETECTED BY LVM MIRROR WRITE CACHE WRITE FAILED I/O ERROR DETECTED BY LVM QUORUM LOST, VOLUME GROUP CLOSING PHYSICAL VOLUME DECLARED MISSING MIRROR WRITE CACHE WRITE FAILED I/O ERROR DETECTED BY LVM EEH permanent error for adapter UNDETERMINED ERROR ADAPTER ERROR UNDETERMINED ERROR DUPLICATE IP ADDRESS DETECTED IN THE NET DUPLICATE IP ADDRESS DETECTED IN THE NET SOFTWARE PROGRAM ABNORMALLY TERMINATED SOFTWARE PROGRAM ABNORMALLY TERMINATED
You might create a script called alert.sh and call it from your .profile #!/usr/bin/ksh cd ~ rm -rf /root/alert.log echo "Important alerts in errorlog: " >> /root/alert.log errpt | grep -i STORAGE >> /root/alert.log
errpt | grep -i QUORUM >> /root/alert.log errpt | grep -i ADAPTER >> /root/alert.log errpt | grep -i VOLUME >> /root/alert.log errpt | grep -i PHYSICAL >> /root/alert.log errpt | grep -i STALE >> /root/alert.log errpt | grep -i DISK >> /root/alert.log errpt | grep -i LVM >> /root/alert.log errpt | grep -i LVD >> /root/alert.log errpt | grep -i UNABLE >> /root/alert.log errpt | grep -i USER >> /root/alert.log errpt | grep -i CORRUPT >> /root/alert.log cat /root/alert.log if [ `cat alert.log|wc -l` -eq 1 ] then echo "No critical errors found." fi echo " " echo "Filesystems that might need attention, e.g. %used:" df -k |awk '{print $4,$7}' |grep -v "Filesystem"|grep -v tmp cat /tmp/tmp.txt | sort -n | tail -3
> /tmp/tmp.txt
Example 2: ---------IDENTIFIER 173C787F 90D3329C AE3E3FAD AE3E3FAD AE3E3FAD AE3E3FAD AE3E3FAD AE3E3FAD AE3E3FAD C1348779 C1348779 C1348779 EAA3D429
TIMESTAMP 0710072007 0710072007 0710064907 0710064907 0710064907 0710064907 0710064907 0710064907 0710064907 0710061107 0710061107 0710061107 0710061007
T I P I I I I I I I I I I U
C S S O O O O O O O O O O S
RESOURCE_NAME topsvcs topsvcs SYSJ2 SYSJ2 SYSJ2 SYSJ2 SYSJ2 SYSJ2 SYSJ2 SYSJ2 SYSJ2 SYSJ2 LVDD
IDENTIFIER TIMESTAMP T C RESOURCE_NAME 12337A8D 0723152107 T S DR_KER_MEM
DESCRIPTION Possible malfunction on local adapter NIM read/write error FSCK FOUND ERRORS FSCK FOUND ERRORS FSCK FOUND ERRORS FSCK FOUND ERRORS FSCK FOUND ERRORS FSCK FOUND ERRORS FSCK FOUND ERRORS LOG I/O ERROR LOG I/O ERROR LOG I/O ERROR PHYSICAL PARTITION MARKED STALE DESCRIPTION Affected memory not available for DR rem
Some notes on disk related errors: ---------------------------------DISK_ERR4 is bad block relocation. Not a serious error. DISK_ERR2 is a hardware error as opposed to a media or corrected read error on disk. This is serious.
EAA3D429
0121151108 U S LVDD
PHYSICAL PARTITION MARKED STALE
Note 1: ------thread 1: Q: Has anyone seen these errors before? We're running 6239 fc cards on a CX600. AIX level is 52-03 with the latest patches for devices.pci.df1000f7 as well. I didn't of their ERR4s on should I
know that these adapters still used devices.pci.df1000f7 as part device driver set, but aparently they do. We're mostly seeing bootup and occassionaly throughout the day. They're TEMP but be concerned about this? Any help would be greatly appreciated!
LABEL: SC_DISK_ERR4 IDENTIFIER: DCB47997 A: DISK_ERR_4 are simply bad-block relocation errors. They are quite normal. However, I heard that if you get more than 8 in an 8-hour period, you should get the disk replaced as it is showing signs of impending failure. thread 2: Q: > Has anyone corrected this issue? SC_DISK_ERR2 with EMC Powerpath = > filesets listed below? I am using a CX-500.=20 > A: got those errors before using a CX700 and it turned out to be a firmware problem on the fibre adapter, model 6259. EMC recommended the 92X1 firmware and to find out IBM found problems with timeouts to the drives and recommended going back a level to 81X1. A: We have the same problem as well. EMC say its a firmware error on the FC adapters A: This is how to fix these errors, downgrading firware is not recommended. Correcting SCSI_DISK_ERR2's in the AIX Errpt Log - Navisphere Failover Wizard
1. In the Navisphere main screen, select tools and then click the Failover Setup Wizard. Click next to continue. 2. From the drop-down list select the host server you wish to modify and click next 3. Highlight the CX-500 and click next 4. Under the specify settings box be sure to select 1 for the failover setting and disable for array commpath. Click next to process. 5. The next screen is the opportunity to review your selections (host, failover mode and array commpath); click next to commit 6. The following screen displays a warning message to alert you are committing these changes. Click yes to process. 7. Next login to the AIX command prompt as root and perform the following commands to complete stopping the SCSI_DISK_ERR2. a. lsdev -Cc disk | grep LUNZ (Filter for disks with LUNZ in the description) b. rmdev -dl hdisk(#)'s (Note the disks and remove them from the ODM) c. errclear 0 (Clear the AIX system error log) d. cfgmgr -v (Attempt to re-add the LUNZ disks) e. lsdev -Cc disk | grep LUNZ (Double check to make sure the LUNZ disk does not add itself back to the system after the cfgmgr command) f. errpt -a (Monitor the AIX error log to insure the SCSI_DISK_ERR2's are gone) Task Complete... E87EF1BE 0512150008 P O dumpcheck The largest dump device is too small. ------------------------------------------------------------------------------
Problems with errpt: -------------------Invalid log, or other problems thread 1: Q: Hello ... the 'errpt' Command tells me: 0315-180 logread: UNEXPECTED EOF 0315-171 Unable to process the error log file
/var/adm/ras/errlog. 0315-132 The supplied error log is not valid: /var/adm/ras/errlog. # ls -l /var/adm/ras/errlog -rw-r--r-- 1 root system 0 Jun 14 17:31 /var/adm/ras/errlog How can I fix this problem? A: /usr/lib/errstop
# stop logging
rm /var/adm/ras/errlog
# get rid of that log.
/usr/lib/errdemon
# restart the daemon, creating a new error log.
diag command: ------------Whenever a hardware problem occurs in AIX, use the diag command to diagnose the problem. The diag command is the starting point to run a wide choice of tasks and service aids. Most of the tasks/service aids are platform specific. To run diagnostics on the scdisk0 device, without questions, enter: # diag -d scdisk0 -c System dumps: ------------A system dump is created when the system has an unexpected system halt or system failure. In AIX 5L the default dump device is /dev/hd6, which is also the default paging device. You can use the sysdumpdev command to manage system crash dumps. The sysdumpdev command changes the primary or secondary dump device designation in a system that is running. The primary and secondary dump devices are designated in a system configuration object. The new device designations are in effect until the sysdumpdev command is run again, or the system is restarted. If no flags are used with the sysdumpdev command, the dump devices defined in the SWservAt ODM object class are used. The default primary dump device is /dev/hd6. The default secondary dump device is /dev/sysdumpnull. Examples
To display current dump device settings, enter: sysdumpdev -l To designate logical volume hd7 as the primary dump device, enter: sysdumpdev -p /dev/hd7 To designate tape device rmt0 as the secondary dump device, enter: sysdumpdev -s /dev/rmt0 To display information from the previous dump invocation, enter: sysdumpdev -L To permanently change the database object for the primary dump device to /dev/newdisk1, enter: sysdumpdev -P -p /dev/newdisk1 To determine if a new system dump exists, enter: sysdumpdev -z If a system dump has occurred recently, output similar to the following will appear: 4537344 /dev/hd7 To designate remote dump file /var/adm/ras/systemdump on host mercury for a primary dump device, enter: sysdumpdev -p mercury:/var/adm/ras/systemdump A : (colon) must be inserted between the host name and the file name. To specify the directory that a dump is copied to after a system crash, if the dump device is /dev/hd6, enter: sysdumpdev -d /tmp/dump This attempts to copy the dump from /dev/hd6 to /tmp/dump after a system crash. If there is an error during the copy, the system continues to boot and the dump is lost. To specify the directory that a dump is copied to after a system crash, if the dump device is /dev/hd6, enter: sysdumpdev -D /tmp/dump This attempts to copy the dump from /dev/hd6 to the /tmp/dump directory after a crash. If the copy fails, you are prompted with a menu that allows you to copy the dump manually to some external media. Starting a system dump: ----------------------If you have the Software Service Aids Package installed, you have access to the sysdumpstart command. You can start the system dump by entering: # sysdumpstart -p You can also use: # smit dump Notes regarding system dumps: -----------------------------
note 1: ------The_Nail wrote: > I handle several AIX 5.1 servers and some of them warns me (via errpt) > about a lack of disk space for the dumpcheck ressource. > Here is a copy of the message : > > > > > > > > > > > > > > >
Description The copy directory is too small. Recommended Actions Increase the size of that file system. Detail Data File system name /var/adm/ras Current free space in kb 7636 Current estimated dump size in kb 207872
> I guess /dev/hd6 is not big enough to contain a system dump. So how > can i change that? The error message tells you something else. Read it, and you will understand! > How can i configure a secondary susdump space in case the primary > would be unavailable? sysdumpdev -s /dev/whatever > What does "copy directory /var/adm/ras" mean? That's where the crash dump will be put when you reboot after the crash. /dev/hd6 will be needed for other purposes (paging space), so you cannot keep your system dump there. And that file system is too small to contain the dump, that's the meaning of the error message. You have two options: - increase the /var file system (it should have ample free space anyway). - change the dump directory to something where you have more space:
sysdumpdev -D /something/in/rootvg/with/free/space Yours, Laurenz Albe Note 2: ------Suppose you find the following error: $ errpt IDENTIFIER TIMESTAMP T C RESOURCE_NAME F89FB899 0822150005 P O dumpcheck
DESCRIPTION The copy directory is too small
This message is the result of a dump device check. You can fix this by increasing the size of your dump device. If you are using the default dump device (/dev/hd6) then increase your paging size or go to smit dump and "select System Dump Compression". Myself, I don't like to use the default dump device so I create a sysdumplv and make sure I have enough space. To check space needed go to smit dump and select "Show Estimated Dump Size" this will give you an idea about the size needed. The copy directory is whatever sysdumpdev says it is. Run sysdumpdev and you will get something like #sysdumpdev primary /dev/hd6 secondary /dev/sysdumpnull copy directory /var/adm/ras forced copy flag TRUE always allow dump FALSE dump compression ON # sysdumpdev -e 0453-041 Estimated dump size in bytes: 57881395 Divide this number by 1024. This is the free space that is needed in your copy directory. Compare it to a df -k or divide this number by 512. This is the free space that is needed in your copy directory. Compare it to a df HP: ---
22. Diagnostic output: ====================== 0:Standard input
1: Standard output
2: Diagnostic output
redirect diag. outp. to file # cat somefile nofile 2>errfile # cat somefile nofile > outfile 2>errfile redirect diag. outp. to same place as standard outp. # cat firsthalf secondhalf > composite 2>1&
23. DOS2UNIX: ============= If you want to convert a ascii PC file to unix, you can use many tools like tr etc.. # tr -d '\015' < original.file > new.file Or scripts like: #!/bin/sh perl -p -i -e 'BEGIN { print "Converting DOS to UNIX.\n" ; } END { print "Done.\n" ; } s/\r\n$/\n/' $* perl -p -i.bak -e 's/^\r+//;s/\r+$//;s/\r/\n/gs' file Or, on many unixes You can use the utility " Just type: dos2unix
dos2unix " to remove the ^M [RETURN]
dos2unix [ -ascii ] [ -iso ] [ -7 ] originalfile convertedfile -ascii Removes extra carriage returns and converts end of file characters in DOS format text files to conform to SunOS requirements. -iso This is the default. It converts characters in the DOS extended character set to the corresponding ISO standard characters. -7 Convert 8 bit DOS graphics characters to 7 bit space characters so that SunOS can read the file. #!/bin/sh # a script to strip carriage returns from DOS text files if test -f $1 then tr -d '\r' $.tmp rm $1 mv $.tmp $1 fi # tr -d '\015' < original.file > new.file Note: Other formats on AIX: --------------------------1. nvdmetoa command: How to convert EBCDIC files to ASCII: On your AIX system, the tool nvdmetoa might be present. Examples: nvdmetoa AIXver3.dat
Converts an EBCDIC file taken off an AS400 and converts to an ASCII file for the pSeries or RS/6000 nvdmetoa 132 AIXver3.txt
Converts an EBCDIC file with a record length of 132 characters to an ASCII file with 132 bytes per line PLUS 1 byte for the linefeed character. 2. od command: The od command translate a file into other formats, like for example hexadecimal format. To translate a file into several formats at once, enter: # od -t cx a.out > a.xcd This command writes the contents of the a.out file, in hexadecimal format (x) and character format (c), into the a.xcd file.
24. Secure shell connections: ============================= ssh: ==== What is Open Secure Shell? Open Secure Shell (OpenSSH) is an open source version of the SSH protocol suite of network connectivity tools. The tools provide shell functions that are authenticated and encrypted. A shell is a command language interpreter that reads input from a command line string, stdin or a file. Why use OpenSSH? When you're running over unsecure public networks like the Internet, you can use the SSH command suite instead of the unsecure commands telnet, ftp, and r-commands. OpenSSH delivers code that communicates using SSH1 and SSH2 protocols. What's the difference? The SSH2 protocol is a re-write of SSH1. SSH2 contains separate, layered protocols, but SSH1 is one large set of code. SSH2 supports both RSA & DSA keys, but SSH1 supports only RSA, and SSH2 uses a strong crypto integrity check, where SSH1 uses a CRC-32 check. The Internet Engineering Task Force (IETF) maintains the secure shell standards.
Example 1: ----------
Go to a terminal on your local Unix system (Solaris, Linux, Mac OS X, etc.) and type the following command: ssh -l username acme.gatech.edu Replace "username" with your Prism ID. If this is your first time connecting to acme, you will see a warning similar to this: The authenticity of host 'acme.gatech.edu (130.207.165.23)' can't be established. DSA key fingerprint is 72:ce:63:c5:86:3a:cb:8c:cb:43:6c:da:00:0d:4c:1f. Are you sure you want to continue connecting (yes/no)? Type the word "yes" and hit . You should see the following warning: Warning: Permanently added 'acme.gatech.edu,130.207.165.23' (DSA) to the list of known hosts. Next, you will be prompted for your password. Type your password and hit . Example 2: ---------A secure shell 'terminal': # ssh �l oracle 193.172.126.193 # ssh
[email protected] pscp: ===== Example to Copy a file to a remote unix server: # pscp c:\documents\foo.txt
[email protected]:/tmp/foo To receive (a) file(s) from a remote server: pscp [options] [user@]host:source target So to copy the file /etc/hosts from the server example.com as user fred to the file c:\temp\example-hosts.txt, you would type: pscp
[email protected]:/etc/hosts c:\temp\example-hosts.txt To send (a) file(s) to a remote server: pscp [options] source [source...] [user@]host:target So to copy the local file c:\documents\foo.txt to the server example.com as user fred to the file /tmp/foo you would type: pscp c:\documents\foo.txt
[email protected]:/tmp/foo You can use wildcards to transfer multiple files in either direction, like this: pscp c:\documents\*.doc
[email protected]:docfiles
pscp
[email protected]:source/*.c c:\source Example of scripts using pscp with parameters; -----------------------------------@echo off REM Script om via pscp.exe een bestand van een UNIX systeem te copi�ren naar het werkstation. Echo Copy bestand van unix naar werkstation SET SET SET SET
/P /P /P /P
systemname=Geef volledige systeemnaam: remotefile=Geef UNIX path+filename: localfile=Geef local filename: username=Geef username:
echo pscp.exe %username%@%systemname%:%remotefile% %localfile% pscp.exe %username%@%systemname%:%remotefile% %localfile% echo bestand %remotefile% gecopieerd naar %localfile% pause -----------------------------------@echo off REM Script om via pscp.exe een bestand naar een UNIX systeem te copi�ren van het werkstation. Echo Copy bestand van werkstation naar unix SET SET SET SET
/P /P /P /P
systemname=Geef volledige systeemnaam: localfile=Geef local filename: remotefile=Geef UNIX path+filename: username=Geef username:
echo pscp.exe %localfile% %username%@%systemname%:%remotefile% pscp.exe %localfile% %username%@%systemname%:%remotefile% echo bestand %localfile% gecopieerd naar %remotefile% pause -----------------------------------scp: ==== Scp is a utility which allows files to be copied between machines. Scp is an updated version of an older utility named Rcp. It works the same, except that information (including the password used to log in) is encrypted. Also, if you have set up your .shosts file to allow you to ssh between machines without using a password as described in help on setting up your .shosts file, you will be able to scp files between machines without entering your password.
Either the source or the destination may be on the remote machine; i.e., you may copy files or directories into the account on the remote system OR copy them from the account on the remote system into the account you are logged into. Example: # scp conv1.tar.gz
[email protected]:/backups/520backups/splenvs # scp conv2.tar.gz
[email protected]:/backups/520backups/splenvs Example: # scp myfile xyz@sdcc7:myfile Example: To copy a directory, use the -r (recursive) option. # scp -r mydir xyz@sdcc7:mydir Example: cd /oradata/arc /usr/local/bin/scp *.arc
SPRAT:/oradata/arc
Example: While logged into xyz on sdcc7, copy file "letter" into file "application" in remote account abc on sdcc3: % scp letter abc@sdcc3:application While logged into abc on sdcc3, copy file "foo" from remote account xyz on sdcc7 into filename "bar" in abc: % scp xyz@sdcc7:foo bar To permit a connection (ssh or scp) from a local machine to a remote machine without always typing a password, on the remote machine, create the file ".shosts" in your home that contains the name of the local machine. The permissions on "e;.shosts"e; should be rw for the user and --- for everyone else (The command chmod 600 .shosts will set the permissions correctly). If you have the file ".rhosts", please delete it. SSH and SCP will use the ssh_know_hosts file. If the local machine is correctly entered in the user's .ssh/known_hosts file, then the connection will be permitted with out a password. To make this work, you may need to log back in from the remote machine to your local machine. For example, if your local machine is i7.msi.umn.edu and you want to connect to origin.msi.umn.edu, use the following procedure to set up connecting from i7 to origin without a password: Estiblish an ssh connection to origin: ssh -X origin.msi.umn.edu After typing a password and establishing a connection, Add i7.msi.umn.edu to the file "e;.shosts"e; in your home directory.
Extablish an ssh connection back to i7.msi.umn.edu. ssh -X i7.msi.umn.edu After typing a password on i7, you can exit from i7. ssh on AIX: =========== After you download the OpenSSL package, you can install OpenSSL and OpenSSH. Install the OpenSSL RPM package using the geninstall command: # geninstall -d/dev/cd0 R:openssl-0.9.6m Output similar to the following displays: SUCCESSES --------openssl-0.9.6m-3 Install the OpenSSH installp packages using the geninstall command: # geninstall -I"Y" -d/dev/cd0 I:openssh.base Use the Y flag to accept the OpenSSH license agreement after you have reviewed the license agreement. (Note: we have seen this line as well: # geninstall -Y -d/dev/cd0 I:openssh.base) Output similar to the following displays: Installation Summary -------------------Name Level Part Event Result ------------------------------------------------------------------------------openssh.base.client 3.8.0.5200 USR APPLY SUCCESS openssh.base.server 3.8.0.5200 USR APPLY SUCCESS openssh.base.client 3.8.0.5200 ROOT APPLY SUCCESS openssh.base.server 3.8.0.5200 ROOT APPLY SUCCESS You can also use the SMIT install_software fast path to install OpenSSL and OpenSSH. The following OpenSSH binary files are installed as a result of the preceding procedure: scp File copy program similar to rcp sftp Program similar to FTP that works over SSH1 and SSH2 protocol sftp-server SFTP server subsystem (started automatically by sshd daemon) ssh Similar to the rlogin and rsh client programs ssh-add Tool that adds keys to ssh-agent ssh-agent An agent that can store private keys ssh-keygen Key generation tool ssh-keyscan Utility for gathering public host keys from a number of hosts ssh-keysign Utility for host-based authentication ssh-rand-helper A program used by OpenSSH to gather random numbers. It is used only on AIX 5.1 installations. sshd Daemon that permits you to log in
The following general information covers OpenSSH: The /etc/ssh directory contains the sshd daemon and the configuration files for the ssh client command. The /usr/openssh directory contains the readme file and the original OpenSSH opensource license text file. This directory also contains the ssh protocol and Kerberos license text. The sshd daemon is under AIX SRC control. You can start, stop, and view the status of the daemon by issuing the following commands: startsrc -s sshd stopsrc -s sshd lssrc -s sshd
OR startsrc -g ssh OR stopsrc -g ssh OR lssrc -s ssh
(group)
More on ssh-keygen: =================== ssh-keygen: password-less SSH login SSH is often used to login from one system to another without requiring passwords. A number of methods may be used for that to work properly, one of which is to setup a .rhosts file (permission 600) with its content being the name of the remote system you trust, followed by the username your trust: nickel.sao.nrc.ca cantin would mean you trust user cantin from nickel.sao.nrc.ca to connect to your account, without requiring a password. But for that to work, SSH itself must be configured to trust .rhosts files (which it does not for most OpenSSH installations - but we do on most systems RCSG maintains), and the private/public key pair of each system must be properly set in the system-wide ssh_known_hosts public key file. This, of course, requires help from the local systems administrator. The second method does not require any help from the systems administrator. And it does not require modifications to the .rhosts file. Instead, it requires you generate your own personal set of private/public pair. ssh-keygen is used to generate that key pair for you. Here is a session where your own personal private/public key pair is created: cantin@sodium:~> ssh-keygen -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/home/cantin/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home/cantin/.ssh/id_rsa.
Your public key has been saved in /home/cantin/.ssh/id_rsa.pub. The key fingerprint is: f6:61:a8:27:35:cf:4c:6d:13:22:70:cf:4c:c8:a0:23 cantin@sodium The command ssh-keygen -t rsa initiated the creation of the key pair. No passphrase was entered (Enter key was pressed instead). The private key was saved in .ssh/id_rsa. This file is read-only and only for you. No one else must see the content of that file, as it is used to decrypt all correspondence encrypted with the public key. The public key is save in .ssh/id_rsa.pub. In this case, the content of file id_rsa.pub is ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEArkwv9X8eTVK4F7pMlSt45pWoiakFkZMw G9BjydOJPGH0RFNAy1QqIWBGWv7vS5K2tr+EEO+F8WL2Y/jK4ZkUoQgoi+n7DWQVOHsR ijcS3LvtO+50Np4yjXYWJKh29JL6GHcp8o7+YKEyVUMB2CSDOP99eF9g5Q0d+1U2WVdB WQM= cantin@sodium It is one line in length. Its content is then copied in file .ssh/authorized_keys of the system you wish to SSH to without being prompted for a password. The example shown here generated keys on sodium by user cantin. If the public key generated, file .ssh/id_rsa.pub, was copied to your account, file .ssh/authorized_keys on nickel.sao.nrc.ca, then user cantin@sodium is allowed to SSH into your own account on nickel.sao.nrc.ca without the use of a password. To summarize, a personal private/public key pair is generated using the ssh-keygen command. The public key is then copied onto a remote systems' .ssh/authorized_keys file. And you can now SSH to the remote systems's account without the use of a password. Example: -------The backup user bu520 on a p520, needs to copy backupfiles to a p550. The process is a cronjob which uses scp. The user should not be confronted with a pasword entry. On p520: /home/bu520/.ssh:>ls -al total 7 drwx-----2 bu520 staff drwxr-xr-x 3 bu520 staff -rw------1 bu520 staff -rw-r--r-1 bu520 staff -rw-r--r-1 bu520 staff
512 512 883 225 663
Apr Apr Apr Apr Jun
24 24 24 24 01
2006 2006 2006 2006 2006
. .. id_rsa id_rsa.pub known_hosts
/home/bu520/.ssh:>cat id_rsa -----BEGIN RSA PRIVATE KEY----MIICWgIBAAKBgQCq901MXZ+l+QFUkyLUgPskqEYz11eGR0nFr0ydVsUDrAnAQngE BGNyrURqGxC+vA2dhU1kdeDLa6PlrxrQ9j02hpcG4mSO369BzJ3QEg9C4yPnHxfJ L9/GauVRzgY3WjmCzwAm51GOsW6S/1s9SQWDG4uepvuUTasIZgf3fktcKQIBIwKB gQCNqFX9ciUxv7ClKXShci8tAHSunHu4ZvP7kT97DWFpcUnocZakPiaDluDqM67J 7EXLqPb7d50AUd+SbIPu9+mSOTrkXSBII+eVzMIM8yJKgy8+nrsctDE3vw/ZGb+l Gf8R6zwd2YR0Y2LBS0RSP5DNgf4B6FZO9o+VGTjMlvYkiwJBANfwcJL5G9EQmQkO zzVhkX4N/oXN3LmmbI9+QMPHhbXiXj2J0sqchx/gir+hcPo9PsRq5gHgtO2Hr+qS sAFWAMkCQQDKrvV1GFnIzcfVQ7Nwnso5hJ0F2tt5cLV5OXTz/x9Y09n5+M77tBEr QvunF+Sg9jHUuTHtzTCgfuJUMLqAJJBhAkB1OWGu3wB4zn72Sd4y69Kjg/CRx4Zz aPkaskBqR72dQF8LdrRCGnU9MMBZZkSlGe7fp76wj+0wfNvXHG4snGbTAkAXKfAq o7J9WViqqKbLCtVIZu1fwT2nephloCqfit8C1mIN8IyvDUPKbg4huZZ4y63sbO/D Z+hM200Q76BJKMALAkB/ocrU8gkAiTBqanu0HR8bsLpIQRM+bAohXc2+wGSOFeZG ZijMWsvl+FDtLWcFgEi3fB6dR86YSax5VFLhsLIL -----END RSA PRIVATE KEY----/home/bu520/.ssh:>cat id_rsa.pub ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAqvdNTF2fpfkBVJMi1ID7JKhGM9dXhkdJxa9MnVbFA6wJwEJ4BARjcq 1EahsQvrwNnYVNZHXgy2uj5a8a0PY9NoaXBuJkjt+vQcyd0BIPQuMj5x8XyS/fxmrlUc4GN1o5gs8AJudR jrFukv9bPUkFgxuLnqb7lE2rCGYH935LXCk= bu520@ol116u209 /home/bu520/.ssh:>cat id_rsa.pub ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAqvdNTF2fpfkBVJMi1ID7JKhGM9dXhkdJxa9MnVbFA6wJwEJ4BARjcq 1EahsQvrwNnYVNZHXgy2uj5a8a0PY9NoaXBuJkjt+vQcyd0BIPQuMj5x8XyS/fxmrlUc4GN1o5gs8AJudR jrFukv9bPUkFgxuLnqb7lE2rCGYH935LXCk= bu520@ol116u209 /home/bu520/.ssh:>cat known_hosts 192.168.2.2 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAx16h52LfGNbf5VIn4zDsIWSnFm668YZ3k2immcyA+ih5RRohh9f+Z8 lS9EFDvnNQsTLMwduPBpjXPZY3mZXOVDtpsu6rnKCWKNx9DFaxsLtBSk+1tV4Yr1u7nO6hxs/2vE5xwWys 5qQP0XABJ/m0+eY8IYMkE/LeXXw0to8iz7c= 192.168.2.3 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAzSFdlVb+RyI5k3pWcpsP0oMcAhMgmb7g/GKLfOyAtf1+c+MeVADz3j JzZywDKvzAJ+o409nhDSIuqvuoRQ2wva08jrPh16ewnSfGzjWY0n9aAMztMwWIvEXodowBNJVSBGV4SZdg tzqauQ06H22dl0vORdie0/4M5OHYYbV2lxE= 192.168.1.2 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAx16h52LfGNbf5VIn4zDsIWSnFm668YZ3k2immcyA+ih5RRohh9f+Z8 lS9EFDvnNQsTLMwduPBpjXPZY3mZXOVDtpsu6rnKCWKNx9DFaxsLtBSk+1tV4Yr1u7nO6hxs/2vE5xwWys 5qQP0XABJ/m0+eY8IYMkE/LeXXw0to8iz7c=
Automatic startup of sshd on boot: ---------------------------------For example, on AIX create the following script "Sssh" in /etc/rc.d/rc2.d root@zd110l14:/etc/rc.d/rc2.d#cat Ssshd #!/bin/ksh ################################################## # name: Ssshd # purpose: script that will start or stop the sshd daemon.
################################################## case "$1" in start ) startsrc -g ssh ;; stop ) stopsrc -g ssh ;; * ) echo "Usage: $0 (start | stop)" exit 1 esac
25. Pipelining and Redirecting: =============================== CONCEPT: UNIX allows you to connect processes, by letting the standard output of one process feed into the standard input of another process. That mechanism is called a pipe. Connecting simple processes in a pipeline allows you to perform complex tasks without writing complex programs. EXAMPLE: Using the more command, and a pipe, send the contents of your .profile and .shrc files to the screen by typing cat .profile .shrc | more to the shell. EXERCISE: How could you use head and tail in a pipeline to display lines 25 through 75 of a file? ANSWER: The command cat file | head -75 | tail -50 would work. The cat command feeds the file into the pipeline. The head command gets the first 75 lines of the file, and passes them down the pipeline to tail. The tail command then filters out all but the last 50 lines of the input it received from head. It is important to note that in the above example, tail never sees the original file, but only sees the part of the file that was passed to it by the head command. It is easy for beginners to confuse the usage of the input/output redirection symbols < and >, with the usage of the pipe. Remember that input/output redirection connects processes with files, while the pipe connects processes with other processes. Grep The grep utility is one of the most useful filters in UNIX. Grep searches line-by-
line for a specified pattern, and outputs any line that matches the pattern. The basic syntax for the grep command is grep [-options] pattern [file]. If the file argument is omitted, grep will read from standard input. It is always best to enclose the pattern within single quotes, to prevent the shell from misinterpreting the command. The grep utility recognizes a variety of patterns, and the pattern specification syntax was taken from the vi editor. Here are some of the characters you can use to build grep expressions: The The The The The
carat (^) matches the beginning of a line. dollar sign ($) matches the end of a line. period (.) matches any single character. asterisk (*) matches zero or more occurrences of the previous character. expression [a-b] matches any characters that are lexically between a and b.
EXAMPLE: Type the command grep 'jon' /etc/passwd to search the /etc/passwd file for any lines containing the string "jon". EXAMPLE: Type the command grep '^jon' /etc/passwd to see the lines in /etc/passwd that begin with the character string "jon". EXERCISE:List all the files in the /tmp directory owned by the user root. EXPLANATION: The command ls -l /tmp | grep 'root' would show all processes with the word "root" somewhere in the line. That doesn't necessarily mean that all the process would be owned by root, but using the grep filter can cut the down the number of processes you will have to look at. Redirecting: -----------CONCEPT: Every program you run from the shell opens three files: Standard input, standard output, and standard error. The files provide the primary means of communications between the programs, and exist for as long as the process runs. The standard input file provides a way to send data to a process. As a default, the standard input is read from the terminal keyboard. The standard output provides a means for the program to output data. As a default, the standard output goes to the terminal display screen.
The standard error is where the program reports any errors encountered during execution. By default, the standard error goes to the terminal display. CONCEPT: A program can be told where to look for input and where to send output, using input/output redirection. UNIX uses the "less than" and "greater than" special characters (< and >) to signify input and output redirection, respectively. Redirecting input Using the "less-than" sign with a file name like this: < file1 in a shell command instructs the shell to read input from a file called "file1" instead of from the keyboard. EXAMPLE:Use standard input redirection to send the contents of the file /etc/passwd to the more command: more < /etc/passwd Many UNIX commands that will accept a file name as a command line argument, will also accept input from standard input if no file is given on the command line. EXAMPLE: To see the first ten lines of the /etc/passwd file, the command: head /etc/passwd will work just the same as the command: head < /etc/passwd Redirecting output Using the "greater-than" sign with a file name like this: > file2 causes the shell to place the output from the command in a file called "file2" instead of on the screen. If the file "file2" already exists, the old version will be overwritten. EXAMPLE: Type the command ls /tmp > ~/ls.out to redirect the output of the ls command into a file called "ls.out" in your home directory. Remember that the tilde (~) is UNIX shorthand for your home directory. In this command, the ls command will list the contents of the /tmp directory. Use two "greater-than" signs to append to an existing file. For example: >> file2 causes the shell to append the output from a command to the end of a file called "file2". If the file "file2" does not already exist, it will be created.
EXAMPLE: In this example, I list the contents of the /tmp directory, and put it in a file called myls. Then, I list the contents of the /etc directory, and append it to the file myls: ls /tmp > myls ls /etc >> myls Redirecting error Redirecting standard error is a bit trickier, depending on the kind of shell you're using (there's more than one flavor of shell program!). In the POSIX shell and ksh, redirect the standard error with the symbol "2>". EXAMPLE: Sort the /etc/passwd file, place the results in a file called foo, and trap any errors in a file called err with the command: sort < /etc/passwd > foo 2> err
=========================== 27. UNIX DEVICES and mknod: =========================== 27.1 Note 1: ============ the files in the /dev directory are a little different used to in other operating systems. The very first thing to understand is that these files devices. Drivers are in the kernel itself (/unix etc..), and the files in /dev anything at all: they are just pointers to where the driver code can be is nothing more to it than that. These aren't programs, they aren't drivers,
from anything you may be are NOT the drivers for the do not actually contain found in the kernel. There they are just pointers.
That also means that if the device file points at code that isn't in the kernel, it obviously is not going to work. Existence of a device file does not necessarily mean that the device code is in the kernel, and creating a device file (with mknod) does NOT create kernel code. Unix actually even shows you what the pointer is. When you do a long listing of a file in /dev, you may have noticed that there are two numbers where the file size should be: brw-rw-rw-
2 bin
bin
2, 64 Dec
8 20:41 fd0
That "2,64" is a pointer into the kernel. I'll explain more about this in a minute, but first look at some more files:
brw-rw-rwbrw-rw-rwbrw-rw-rwbrw-rw-rwbrw-rw-rwbrw-rw-rw-
2 2 2 1 2 3
bin bin bin bin bin bin
bin bin bin bin bin bin
2, 2, 2, 2, 2, 2,
64 48 60 16 44 36
Dec Sep Feb Sep Sep Sep
8 15 12 15 15 15
20:41 16:13 10:45 16:13 16:13 16:13
fd0 fd0135ds15 fd0135ds18 fd0135ds21 fd0135ds36 fd0135ds9
A different kind of device would have a different major number. For example, here are the serial com ports: crw-rw-rwcrw-rw-rwcrw-rw-rwcrw-r--r--
1 1 1 1
bin root root uucp
bin root sys sys
5,128 5, 0 5,136 5, 8
Feb 14 05:35 tty1A Dec 9 13:13 tty1a Nov 25 07:28 tty2A Nov 25 07:16 tty2a
Notice the "b" and the "c" as the first characters in the mode of the file. It designates whether we have a block "b", or a character "c" device. Notice that each of these files shares the "5" part of the pointer, but that the other number is different. The "5" means that the device is a serial port, and the other number tells exactly which com port you are referring to. In Unix parlance, the 5 is the "major number" and the other is the "minor number". These numbers get created with a "mknod" command. For example, you could type "mknod /dev/myfloppy b 2 60" and then "/dev/myfloppy" would point to the same driver code that /dev/fd0135ds18 points to, and it would work exactly the same. This also means that if you accidentally removed /dev/fd0135ds18, you could instantly recreate it with "mknod". But if you didn't know that the magic numbers were "2,60", how could you find out? It turns out that it's not hard. First, have a look at "man idmknod". The idmknod command wipes out all nonrequired devices, and then recreates them. Sounds scary, but this gets called every time you answer "Y" to that "Rebuild Kernel environment?" question that follows relinking. Actually, on 5.0.4 and on, the existing /dev files don't get wiped out; the command simply recreates whatever it has to. idmknod requires several arguments, and you'd need to get them right to have success. You could make it easier by simply relinking a new kernel and answering "Y" to the "Rebuild" question, but that's using a fire hose to put out a candle. A less dramatic method would be to look at the files that idmknod uses to recreate the device nodes. These are found in /etc/conf/node.d
In this case, the file you want would be "fd". A quick look at part of that shows: fd fd fd fd fd fd fd
fd0 fd0135ds36 fd0135ds21 fd0135ds18 fd0135ds15 fd0135ds9 fd048
b b b b b b b
64 44 16 60 48 36 4
bin bin bin bin bin bin bin
bin bin bin bin bin bin bin
666 666 666 666 666 666 666
This gives you *almost* everything you need to know about the device nodes in the "fd" class. The only thing it doesn't tell you is the major number, but you can get that just by doing an "l" of any other fd entry: brw-rw-rw-
1 bin
bin
2, 60 Feb
5 09:45 fd096ds18
this shows you that the major number is "2". Armed with these two pieces of information, you can now do mknod chown chgrp chmod
/dev/fd0135ds18 b 2 60 bin /dev/fd0135ds18 bin /dev/fd0135ds18 666 /dev/fd0135ds18
If you examined the node file closely, you would also notice that /dev/rfd0135ds18 and /dev/fd0135ds18 differ only in that the "r" version is a "c" or character device and the other is "b" or block. If you had already known that, you wouldn't have even had to look at the node file; you'd simply have looked at an "l" of the /dev/rfd0135ds18 and recreated the block version appropriately. There are other fascinating things that can be learned from the node files. For example, fd096ds18 is also minor number 60, and can be used in the same way with identical results. In other words, if you z'd out (were momentarily innattentive, not CTRL-Z in a job control shell) and dd'd an image to /dev/fd096ds18, it would write to your hd floppy without incident. If you have a SCSI tape drive, notice what happens when you set it to be the "default" tape drive. It creates device files that have different names (rct0, etc.) but that have the same major and minor numbers. Knowing that it's easy to recreate missing device files also means that you can sometimes capture the output of programs that write directly to a device. For example, suppose some application prints directly to /dev/lp but you need to capture this to a file. In most situations, you can simply "rm /dev/lp" (after carefully noting its current ownership, permissions and, of course, major/minor numbers), and then "touch /dev/lp" to create an ordinary file. You'll need to chmod it for appropriate permissions, and then run your app. Unless the app has
tried to do ioctl calls on the device, the output will be there for your use. This can be particularly useful for examining control characters that the app is sending. What's the Difference? One question that comes up fairly often is "what's the difference between a block and a character device and when should I use one rather than the other?". To answer that question fully is hard, but I'm going to try to at least get you started here. The real difference lies in what the kernel does when a device file is accessed for reading or writing. If the device is a block device, the kernel gives the driver the address of a kernel buffer that the driver will use as the source or destination for data. Note that the address is a "kernel" address; that's important because that buffer will be cached by the kernel. If the device is raw , then the address it will use is in the user space of the process that is using the device. A block device is something you could make a filesystem on (a disk). You can move forward and backward, from the beginning of a block device to its end, and then back to the beginning again. If you ask to read a block that the kernel has buffered, then you get data from the buffer. If you ask for a block that has not yet been buffered, the kernel reads that block (and probably a few more following it) into the buffer cache. If you write to a block device, it goes to the buffer cache (eventually to the device, of course). A raw (or character) device is often something that doesn't have a beginning or end; it just gives a stream of characters that you read. A serial port is an excellent example- however, it is not at all unusual to have character (raw) drivers for things that do have a beginning and an end- a tape drive, for example. And many times there are BOTH character and block devices for the same physical device- disks, for example. Nor does using a raw device absolutely mean that you can't move forward and back, from beginning to end- you can move wherever you want with a tape or /dev/rfd0. And that's where the differences get confusing. It seems pretty reasonable that you'd use the block device to mount a disk. But which do you use for format? For fsck? For mkfs? Well, if you try to format /dev/fd0135ds18, you'll be told that it is not a formattable device. Does that make any sense? Well, the format process involves sequential access- it starts at the beginning and just keeps on going, so it seems to make sense that it wouldn't use the block device. But you can run "mkfs" on either the block or character device; it doesn't seem to care. The same is true for fsck. But although that's true for those programs on SCO OSR5, it isn't necessarily going to be true on some other UNIX, and the "required" device may make sense to whover wrote the program, but it may not make sense to you. You'd use a block device when you want to take advantage of the caching provided by the kernel. You'd use the raw device when you don't, or for ioctl operations like "tape status" or "stty -a".
27.2 Note 2: ============ One of the unique things about Unix as an operating system is that regards everything as a file. Files can be divided into three categories; ordinary or plain files, directories, and special or device files. Directories in Unix are properly known as directory files. They are a special type of file that holds a list of the other files they contain. Ordinary or plain files in Unix are not all text files. They may also contain ASCII text, binary data, and program input or output. Executable binaries (programs) are also files, as are commands. When a user enters a command, the associated file is retrieved and executed. This is an important feature and contributes to the flexibility of Unix. Special files are also known as device files. In Unix all physical devices are accessed via device files; they are what programs use to communicate with hardware. Files hold information on location, type, and access mode for a specific device. There are two types of device files; character and block, as well as two modes of access. - Block device files are used to access block device I/O. Block devices do buffered I/O, meaning that the the data is collected in a buffer until a full block can be transfered. - Character device files are associated with character or raw device access. They are used for unbuffered data transfers to and from a device. Rather than transferring data in blocks the data is transfered character by character. One transfer can consist of multiple characters. So what about a device that could be accessed in character or block mode? How many device files would it have? One. Two. There are no such devices. Some devices, such as disk partitions, may be accessed in block or character mode. Because each device file corresponds to a single access mode, physical devices that have more than one access mode will have more than one device file. Device files are found in the /dev directory. Each device is assigned a major and minor device number. The major device number identifies the type of device, i.e. all SCSI devices would have the same number as would all the keyboards. The minor device number identifies a specific device, i.e. the keyboard attached to this workstation.
Device files are created using the mknod command. The form for this command is: mknod device-name type major minor device-name is the name of the device file type is either "c" for character or "b" for block major is the major device number minor is the minor device number The major and minor device numbers are indexed to device switches. There are two types of device switches; c devsw for character devices and bdevsw for block devices. These switches are kernel structures that hold the names of all the control routines for a device and tell the kernel which driver module to execute. Device switches are actually tables that look something like this: 0 keyboard 1 SCSIbus 2 tty 3 disk Using the ls command in the /dev directory will show entries that look like: brw-r----- 1 root sys 1, 0 Aug 31 16:01 /dev/sd1a The "b" before the permissions indicates that this is a block device file. When a user enters /dev/sd1a the kernel sees the file opening, realizes that it's major device number 1, and calls up the SCSIbus function to handle it. ==================== 28. Solaris devices: ==================== Devices are described in three ways in the Solaris environment, using three distinct naming conventions: the physical device name, the instance name, and the logical device name. Solaris stores the entries for physical devices under the /devices directory, and the logical device entries behind the /dev directory. - A "physical device name" represents the full pathname of the device. Physical device files are found in the /devices directory and have a naming convention like the following example: /devices/sbus@1,f8000000/esp@0,40000/sd@3,0:a Each device has a unique name representing both the type of device and the location of that device in the system-addressing structure called the "device tree". The OpenBoot firmware builds the device tree for all devices from information gathered at POST. The device tree is loaded in memory and is used by the kernel during boot to identify all configured devices. A device pathname is a series of node names separated by slashes. Each device has the following form:
driver-name@unit-address:device-arguments - The "instance name" represents the kernel's abbreviated name for every possible device on the system. For example, sd0 and sd1 represents the instance names of two SCSI disk devices. Instance names are mapped in the /etc/path_to_inst file, and are displayed by using the commands dmesg, sysdef, and prtconf - The "Logical device names" are used with most Solaris file system commands to refer to devices. Logical device files in the /dev directory are symbolically linked to physical device files in the /devices directory. Logical device names are used to access disk devices in the following circumstances: - adding a new disk to the system and partitioning the disk - moving a disk from one system to another - accessing or mounting a file system residing on a local disk - backing up a local file system - repairing a file system Logical devices are organized in subdirs under the /dev directory by their device types /dev/dsk block interface to disk devices /dev/rdsk raw or character interface to disk devices. In commands, you mostly use raw logical devices, like for example # newfs /dev/rdsk/c0t3d0s7 /dev/rmt tape devices /dev/term serial line devices etc.. Logical device files have a major and minor number that indicate device drivers, hardware addresses, and other characteristics. Furthermore, a device filename must follow a specific naming convention. A logical device name for a disk drive has the following format: /dev/[r]dsk/cxtxdxsx where cx refers to the SCSI controller number, tx to the SCSI bus target number, dx to the disk number (always 0 except on storage arrays) and sx to the slice or partition number.
=========================== 29. filesystems in Solaris: =========================== Checks on the filesystems in Solaris: ------------------------------------1. used space etc..
#
df -k, df -h etc..
# du -ks /home/fred Shows only a summary of the disk usage of the /home/fred subdirectory (measured in kilobytes). # du -ks /home/fred/* Shows a summary of the disk usage of each subdirectory of /home/fred (measured in kilobytes). # du -s /home/fred Shows a total summary of /home/fred # du -sg /data Shows a total summary of /data in GB This command shows the diskusage of /dirname in GB # du -g /dirname 2. examining the disklabel # prtvtoc /dev/rdisk/c0t3d0s2 3. format just by itself shows the disks # format # format -> specify disk -> choose partition -> choose print to get the partition table 4. Display information about SCSI devices # cfgadm -al or, from the PROM, commands like probe-scsi Recovering disk partition information in Solaris: ------------------------------------------------Use the fmthard command to write the backup VTOC information back to the disk. The following example uses the fmthard command to recover a corrupt label on a disk named /dev/rdisk/c0t3d0s1. The backup VTOC information is in a file named c0t3d0 in the /vtoc directory. # fmthard -s /vtoc/c0t3d0s0 /dev/rdsk/c0t3d0s2 Remember that the format of /dev/(r)dsk/cWtXdYsZ means: W X Y Z
is is is is
the the the the
controller number, SCSI target number, logical unit number (LUN, almost always 0), slice or partition number
Make a new filesystem in Solaris: --------------------------------To create a UFS filesystem on a formatted disk that already has been divided into slices you need to know the raw device filename of the slice that will contain the filesystem. Example: # newfs /dev/rdsk/c0t3d0s7 defaults on UFS on Solaris: blocksize 8192 fragmentsize 1024 one inode for each 2K of diskspace FSCK in Solaris: ---------------If you just want to determine the state of a filesystem, whether it needs checking, you can use the fsck command while the fs is mounted. Example: # fsck -m /dev/rdsk/c0t0d0s6 The state flag in the superblock of the filesystem you specify is checked to see whether the filesystem is clean or requires checking. If you ommit the device argument, all the filesystems listed in /etc/vfstab a fsck pass value greater than 0 are checked.
with
Adding a disk in Solaris 2.6, 2.7, 8, 9, 10: -------------------------------------------In case you have just build in a new disk, its probably best, to first use the probe-scsi command from the OK prompt: ok probe-scsi .. Target 3 Unit 0 Disk ok boot -r
Seagate ST446452W
0001
Spcifying the -r flag when booting, tells Solaris to reconfigure itself by scanning for new hardware. Once the system is up, check the output for "dmesg" to find kernel messages relating to the new disk. You probably find complaints telling you stuff as "corrupt label - wrong magic number" etc.. That's good, because we now know that the kernel is aware of this new disk. In this example, our disk is SCSI target 3, so we can refer to the whole disks as /dev/rdsk/c0t3d0s2 # slice 2, or partition 2, s2 refers to the whole
disk Remember that the format of /dev/(r)dsk/cWtXdYsZ means: W X Y Z
is is is is
the the the the
controller number, SCSI target number, logical unit number (LUN, almost always 0), slice or partition number
We now use the format program to partition the disk, and afterwards create filesystems. # format /dev/rdsk/c0t3d0s2 (.. output..) FORMAT MENU: format>label Ready to label disk, continue? y format>partition PARTITION MENU: partition> Once you have created and sized the partitions, you can get a list with the "partition>print" command. Now, for example, you can create a filesystem like in the following command: # newfs /dev/rdsk/c0t3d0s0
================ 30. AIX devices: ================ In AIX 5.x, the device configuration information is stored in the ODM repository. The corresponding files are in /etc/objrepos /usr/lib/objrepos /usr/share/lib/objrepos There are 2 sections in ODM: - predefined: all of the devices in principle supported by the OS - customized: all devices already configured in the system Every device in ODM has a unique definition that is provided by 3 attributes: 1. Type 2. Class 3. Subclass
Information thats stored in the ODM: -
PdDv,PdAt, PdCn : Predefined device information CuDv, CuAt, CuDep : Customized device information lpp, inventory : Software vital product data smit menu's Error log, alog, and dump information System Resource Controller: SRCsubsys, SRCsubsrv NIM: nim_attr, nim_object, nim_pdattr
There are commands, representing an interface to ODM, so you can add, retrieve, drop and change objects. The following commands can be used with ODM: odmadd, odmdrop, odmshow, odmdelete, odmcreate, odmchange Examples: # odmget -q "type LIKE lv*" PdDv # odmget -q name=hdisk0 CuAt Logical devices and physical devices: ------------------------------------AIX includes both logical devices and physical devices in the ODM device configuration database. Logical devices include Volume Groups, Logical Volumes, network interfaces and so on. Physical devices are adapters, modems etc.. Most devices are selfconfiguring devices, only serial devices (modems, printers) are not selfconfigurable. The command that configures devices is "cfgmgr", the "configuration manager". When run, it compares the information from the device with the predefined section in ODM. If it finds a match, then it creates the entries in the customized section in ODM. The configuration manager runs every time the system is restarted. If you have installed an adapter for example, and you have put the software in a directory like /usr/sys/inst.images, you can call cfgmgr to install device drivers as well with # cfgmgr -i /usr/sys/inst.images $$
09-08-00-1,0 u5971-t1-l1-l0 Device information: ------------------The most important AIX command to show device info is "lsdev". This command queries the ODM, so we can use it to locate the customized or the predifined devices. The main - lsdev - lsattr - lscfg
commands in AIX to get device information are: : queries ODM : gets specific configuration attributes of a device : gets vendor name, serial number, type, model etc.. of the device
lsdev also shows the status of a device as Available (that is configured) or as Defined (that is predefined). lsdev examples: --------------If you need to see disk or other devices, defined or available, you can use the lsdev command as in the following examples: # lsdev -Cc tape rmt0 Available 10-60-00-5,0 # lsdev -Cc disk hdisk0 Available hdisk1 Available hdisk2 Available hdisk3 Available hdisk4 Available
SCSI 8mm Tape Drive
20-60-00-8,0 20-60-00-9,0 20-60-00-10,0 20-60-00-11,0 20-60-00-13,0
16 16 16 16 16
Bit Bit Bit Bit Bit
LVD LVD LVD LVD LVD
SCSI SCSI SCSI SCSI SCSI
Disk Disk Disk Disk Disk
Drive Drive Drive Drive Drive
Note: -C queries the Customized section of ODM, -P queries the Predefined section of ODM. Example if some of the disks are on a SAN (through FC adapters): # lsdev -Cc disk hdisk0 Available Virtual SCSI Disk Drive hdisk1 Available Virtual SCSI Disk Drive hdisk2 Available 02-08-02 SAN Volume Controller MPIO Device hdisk3 Available 02-08-02 SAN Volume Controller MPIO Device # lsattr -El hdisk2 PCM PCM/friend/sddpcm True PR_key_value none True algorithm load_balance True dist_err_pcnt 0 Error Percentage True dist_tw_width 50
(through FC adapter) (through FC adapter) PCM Reserve Key Algorithm Distributed Distributed
Error Sample Time True hcheck_interval 20 Interval True hcheck_mode nonactive Mode True location True lun_id 0x0 Number ID False lun_reset_spt yes LUN reset True max_transfer 0x40000 TRANSFER Size True node_name 0x50050768010029c8 False pvid 00cb5b9e66cc16470000000000000000 volume identifier False q_type simple True qfull_dly 20 seconds for SCSI TASK SET FULL True queue_depth 20 True reserve_policy no_reserve True rw_timeout 60 time out value True scbsy_dly 20 seconds for SCSI BUSY True scsi_id 0x611013 False start_timeout 180 time out value True unique_id 33213600507680190014E30000000000001E204214503IBMfcp Identification False ww_name 0x50050768014029c8 Name False
Health Check Health Check Location Label Logical Unit Support SCSI Maximum FC Node Name Physical Queuing TYPE delay in Queue DEPTH Reserve Policy READ/WRITE delay in SCSI ID START unit Device Unique FC World Wide
lsdev [ -C ][ -c Class ] [ -s Subclass ] [ -t Type ] [ -f File ] [ -F Format | -r ColumnName ] [ -h ] [ -H ] [ -l { Name | - } ] [ -p Parent ] [ -S State ] lsdev -P [ -c Class ] [ -s Subclass ] [ -t Type ] [ -f File ] [ -F Format | -r ColumnName ] [ -h ] [ -H ] Remark: For local attached SCSI devices, the general format of the LOCATION code "AB-CDEF-GH" is actually "AB-CD-EF-G,H" , the first three sections are the same and for the GH section, the G is de SCSI ID and the H is the LUN. For adapters, only the AB-CD is mentioned in the location code. A location code is a representation of the path to the device, from drawer, slot, connector and port. - For an adapter it is sufficient to have the codes of the drawer and slot to
identify the adapter. The location code of an adapter takes the form of AB-CD. - Other devices needs more specification, like a specific disk on a specific SCSI bus. For other devices the format is AB-CD-EF-GH. The AB-CD part then indicates the adapter the device is connected on. - For SCSI devices we have a location code like AB-CD-EF-S,L where the S,L fields identifies the SCSI ID and LUN of the device. To lists all devices in the Predefined object class with column headers, use # lsdev -P -H To list the adapters that are in the Available state in the Customized Devices object class, use # lsdev -C -c adapter -S lsattr examples: ---------------This command gets the current attributes (-E flag) for a tape drive: # lsattr -El rmt0 mode yes block_size 1024 extfm no ret no .. ..
Use DEVICE BUFFERS during writes Block size (0=variable length) Use EXTENDED file marks RETENSION on tape change or reset
True True True True
(Ofcourse, the equivalent for the above command is for example # lsattr -l rmt0 -E ) To list the default values for that tape device (-D flag), use # lsattr -l -D rmt0 This command gets the attributes for a network adapter: # lsattr -E -l ent1 busmem 0x3cfec00 busintr 7 .. ..
Bus memory address Bus interrupt level
False False
To list only a certain attribute (-a flag), use the command as in the following example: # lsattr -l -E scsi0 -a bus_intr_lvl bus_intr_lvl 14 Bus interrupt level False # lsattr -El tty0 -a speed speed 9600 BAUD rate true
You -D -E the -F -R -a
must specify one of the following flags with the lsattr command: Displays default values. Displays effective values (valid only for customized devices specified with -l flag). Format Specifies the user-defined format. Displays the range of legal values. Displays for that attribute
lscfg examples: --------------Example 1: This command gets the Vital Product Data for the tape drive rmt0: # lscfg -vl rmt0 Manufacturer...............EXABYTE Machine Type and Model.....IBM-20GB Device Specific(Z1)........38zA Serial Number..............60089837 .. .. -l Name Displays device information for the named device. -p Displays the platform-specific device information. This flag only applies to AIX 4.2.1 or later. -v Displays the VPD found in the Customized VPD object class. Also, on AIX 4.2.1 or later, displays platform specific VPD when used with the -p flag. -s Displays the device description on a separate line from the name and location. # lscfg -vp | grep -p 'Platform Firmware:' # lscfg -vp | grep -p Platform sample output: Platform Firmware: ROM Level.(alterable).......3R040602 Version.....................RS6K System Info Specific.(YL)...U1.18-P1-H2/Y2 Physical Location: U1.18-P1-H2/Y2 The ROM Level denotes the firmware/microcode level Platform Firmware: ROM Level ............. RH020930 Version ................RS6K .. Example 2: The following command shows details about the Fiber Channel cards:
# lscfg �vl fcs*
(fcs0 for example, is the parent of fsci0)
Adding a device: ---------------Adding a device with cfmgr: --------------------------To add a device you can run cfgmgr, or shutdown the system, attach the new device and boot the system. There are also many smitty screens to accomplish the task of adding a new device. Adding a device with mkdev: --------------------------Also the mkdev command can be used as in the following example: # mkdev -c tape -s scsi -t scsd -p scsi0 -w 5,0 where -c Class of the device -s Subclass of the device -t Type of the device. This is a specific attribute for the device -p The parent adapter of the device. You have to specify the logical name. -w You have to know the SCSI ID that you are goiing to assign to the new device. If it's non SCSI, you have to know the port number on the adapter. -a Specifies the device attribute-value pair The mkdev command also creates the ODM entries for the device and loads the device driver. The following command configures a new disk and ensures that it is available as a physical volume. This example adds a 2.2GB disk with a scsi ID of 6 and a LUN of 0 to the scsi3 SCSI bus. # mkdev -c disk -s scsi -t 2200mb -p scsi3 -w 6,0 -a pv=yes This example adds a terminal: # mkdev -c tty -t tty -s rd232 -p sa1 -w 0 -a login=enable -a term=ibm3151 tty0 Available Changing a device with chdev: ----------------------------Suppose you have just added a new disk. Suppose the cfgmgr has run and detected the disk. Now you run
# lspv hdisk1 OR hdisk1
none
none
0005264d2
none
The first field identifies the system-assigned name of the disk. The second field displays the "physical volume id" PVID. If that is not shown, you can use chdev: # chdev -l hdisk2 -a pv=yes Removing a device with rmdev: ----------------------------Examples: # lsdev -Cc tape rmt0 Available 10-60-00-5,0 # rmdev -l rmt0 rmt0 Defined
SCSI 8mm Tape Drive # -l indicates using the logical device name
The status have shifted from Available to Defined. # lsdev -Cc tape rmt0 Defined 10-60-00-5,0
SCSI 8mm Tape Drive
If you really want to remove it from the system, use the -d flag as well # rmdev -l rmt0 -d To unconfigure the childeren of PCI bus pci1 and all devices under them, while retaining their device definition in the Customized Devices Object Class. # rmdev -p pci1 rmt0 Defined hdisk1 Defined scsi1 Defined ent0 Defined
The special device sys0: -----------------------In AIX 5.x we have a special device named sys0 that is used to manage some kernel parameters. The way to change these values is by using smitty, the chdev command or WSM. Example. To change the maxusersprocesses parameter, you can for example use the Web-based System Manager. You can also use the chdev command: #chdev -l sys0 -a maxuproc=50
sys0 changed Note: In Solaris, to change kernel parameters, you have to edit /etc/system. Device drivers: --------------Device drivers are located in /usr/lib/drivers directory.
============================ 31. filesystem commands AIX: ============================ 31.1 The Logical Volume Manager LVM: ==================================== In AIX, it's common to use a Logical Volume Manager LVM to cross the boundaries posed by traditional disk management. Traditionally, a filesystem was on a single disk or on a single partition. Changing a partionion size was a difficult task. With a LVM, we can create logical volumes which can span several disks. The LVM has been a feature of the AIX operating system since version 3, and it is installed automatically with the Operating System. LVM commands in AIX: -------------------mkvg (or the mkvg4vp command in case of SAN vpath disks. See section 31.3) cplv rmlv mklvcopy extendvg reducevg getlvcb lspv lslv lsvg mirrorvg chpv migratepv exportvg, importvg varyonvg, varyoffvg And related commands: mkdev chdev rmdev lsdev Volume group: -------------
What a physical disk is, or a physical volume is, is evident. When you add a physical volume to a volume group, the physical volume is partitioned into contiguous equal-sized units of space called "physical partitions". A physical partition is the smallest unit of storage space allocation and is a contiguous space on a physical volume. The physical volume must now become part of a volume group. The disk must be in a available state and must have a "physical volume id" assigned to it. A volume group (VG) is an entity consisting of 1 to 32 physical volumes (of varying sizes and types). A "Big volume group" kan scale up to 128 devices. You create a volume group with the "mkvg" command. You add a physical volume to an existing volume group with the "extendvg" command, you make use of the changed size of a physical volume with the "chvg" command, and remove a physical volume from a volume group with the "reducevg" command. Some of the other commands that you use on volume groups include: list (lsvg), remove (exportvg), install (importvg), reorganize (reorgvg), synchronize (syncvg), make available for use (varyonvg), and make unavailable for use (varyoffvg). To create a VG, using local disks, use the "mkvg" command: mkvg -y -s Typical example: mkvg -y oravg -s 64 hdisk3 hdisk4 mkvg -y appsvg -s 32 hdisk2 mkvg -y datavg -s 64 hdisk3 mkvg -y appsvg -s 32 hdisk3 mkvg -y datavg -s 32 hdisk2 mkvg -y vge1corrap01 -s 64 hdisk2 In case you use the socalled SDD subsystem with vpath SAN storage, you should use the "mkvg4vp" command, which works similar (same flags) as the mkvg command.
Types of VG's: ============== There are 3 kinds of VG's: - Normal VG (AIX 5L) - Big VG (AIX 5L) - Scalable VG (as from AIX 5.3) Normal VG:
---------Number of disks 1 2 4 8 16 32
32512 16256 8128 4064 2032 1016
Max number of partitions/disk
Big VG: ------Number of disks 1 2 4 8 16 32 64 128
Max number of partitions/disk 130048 65024 32512 16256 8128 4064 2032 1016
VG Type Max PV's Max LV's Max PP's per VG --------------------------------------------------------------Normal 32 256 32512 Big 128 512 130048 Scalable 1024 4096 2097152 Physical Partition: =================== You can change the NUMBER of PPs in a VG, but you cannot change the SIZE of PPs afterwards. Defaults: - 4 MB partition size. It can be a multiple of that amount. The Max size is 1024 MB - The default is 1016 PPs per disk. You can increase the number of PPs in powers of 2 per PV, but the number of maximum disks per VG is decreased. #disks 32 16 8 4 2 1
max # of PPs / disk 1016 2032 4064 8128 16256 32512
In the case of a set of "normal" internal disks of, for example, 30G or 70G or so, common partition sizes are 64M or 128M. Logical Partition: ------------------
A LP maps to (at least) one PP, and is actually the smallest unit of allocatable space. Logical Volume: --------------Consists of LPs in a VG. A LV consists of LPs from actual PPs from one or more disks. |-----| |LP1 | ---> |-----| |LP2 | ---> |-----| |.. | |.. | |.. | |-----| |LPn | ---> |-----| |LPn+1| ---> |-----| Logical Volume
| ----| | PP1 | | ----| | PP2 | | ----| hdisk 1 (Physical Volume 1) |---- | |PPn | |---- | |PPn+1| |---- | hdisk2 (Physical Volume 2)
So, a VG is a collection of related PVs, but you know that actually LVs are created in the VG. For the applications, the LVs are the entities they work with. In AIX, a filesystem like "/data", corresponds to a LV. lspv Command -----------Purpose: Displays information about a physical volume within a volume group. lspv [ -L ] [ -l | -p | -M ] [ -n DescriptorPhysicalVolume] [ -v VolumeGroupID] PhysicalVolume -p: lists range, state, region, LV names, type and mount points # lspv # lspv hdisk3 # lspv -p hdisk3 # lspv hdisk0 hdisk1
00453267554 00465249766
rootvg rootvg
# lspv hdisk23 PHYSICAL VOLUME: hdisk23 VOLUME GROUP: PV IDENTIFIER: 00ccf45d564cfec0 VG IDENTIFIER 00ccf45d00004c0000000104564d2386 PV STATE: active
oravg
STALE PARTITIONS: PP SIZE: TOTAL PPs: FREE PPs: USED PPs: FREE DISTRIBUTION: USED DISTRIBUTION: # lspv -p hdisk23: PP RANGE 1-22 23-190 191-379 380-568 569-600 601-700 701-757 758-947
hdisk23
# lspv -p hdisk0: PP RANGE 1-1 2-48 49-51 52-52 53-108 109-116 117-215 216-216 217-217 218-222 223-320 .. ..
hdisk0
STATE used used used used used used free free
STATE used free used used used used used used used used used
0 256 megabyte(s) 947 (242432 megabytes) 247 (63232 megabytes) 700 (179200 megabytes) 00..00..00..57..190 190..189..189..132..00
ALLOCATABLE: LOGICAL VOLUMES: VG DESCRIPTORS: HOT SPARE:
yes 3 1 no
REGION outer edge outer edge outer middle center inner middle inner middle inner middle inner edge
LV NAME u01 u02 u01 u01 u02 u03
TYPE jfs2 jfs2 jfs2 jfs2 jfs2 jfs2
MOUNT POINT /u01 /u02 /u01 /u01 /u02 /u03
REGION outer edge outer edge outer edge outer edge outer edge outer middle outer middel center center center center
LV NAME hd5
TYPE boot
MOUNT POINT N/A
hd9var hd2 hd6 hd6 hd2 hd8 hd4 hd2 hd4
jfs jfs paging paging jfs jfslog jfs jfs jfs
/var /usr N/A N/A /usr N/A / /usr /
Note that in this example the Logical Volumes corresponds to the filesystems in the following way: hd4= /, hd5=boot, hd6=paging, hd2=/usr, hd3=/tmp, hd9var=/var lslv Command -----------Purpose: Displays information about a logical volume. To Display Logical Volume Information lslv [ -L ] [ -l| -m ] [ -nPhysicalVolume ] LogicalVolume To Display Logical Volume Allocation Map lslv [ -L ] [ -nPhysicalVolume ] -pPhysicalVolume [ LogicalVolume ] # lslv -l lv06 lv06:/backups
PV hdisk3
COPIES 512:000:000
IN BAND 100%
DISTRIBUTION 000:218:218:076:000
# lslv lv06 LOGICAL VOLUME: lv06 VOLUME GROUP: backupvg LV IDENTIFIER: 00c8132e00004c0000000106ef70cec2.2 PERMISSION: read/write VG STATE: active/complete LV STATE: opened/syncd TYPE: jfs WRITE VERIFY: off MAX LPs: 512 PP SIZE: 64 megabyte(s) COPIES: 1 SCHED POLICY: parallel LPs: 512 PPs: 512 STALE PPs: 0 BB POLICY: relocatable INTER-POLICY: minimum RELOCATABLE: yes INTRA-POLICY: middle UPPER BOUND: 32 MOUNT POINT: /backups LABEL: /backups MIRROR WRITE CONSISTENCY: on/ACTIVE EACH LP COPY ON A SEPARATE PV ?: yes Serialize IO ?: NO # lslv FREE FREE FREE FREE FREE FREE FREE FREE FREE .. ..
-p hdisk3 FREE FREE FREE FREE FREE FREE FREE FREE FREE FREE FREE FREE FREE FREE FREE FREE FREE FREE
FREE FREE FREE FREE FREE FREE FREE FREE FREE
FREE FREE FREE FREE FREE FREE FREE FREE FREE
FREE FREE FREE FREE FREE FREE FREE FREE FREE
FREE FREE FREE FREE FREE FREE FREE FREE FREE
FREE FREE FREE FREE FREE FREE FREE FREE FREE
FREE FREE FREE FREE FREE FREE FREE FREE FREE
FREE FREE FREE FREE FREE FREE FREE FREE FREE
Also, you can list LVs per VG by running, for example:
1-10 11-20 21-30 31-40 41-50 51-60 61-70 71-80 81-90
# lsvg -l backupvg backupvg: LV NAME loglv02 lv06
TYPE jfslog jfs
LPs 1 512
PPs 1 512
PVs 1 1
LV STATE open/syncd open/syncd
MOUNT POINT N/A /backups
# lsvg -l splvg splvg: LV NAME loglv01 lv04 lv00 lv07
TYPE jfslog jfs jfs jfs
LPs 1 240 384 256
PPs 1 240 384 256
PVs 1 1 1 1
LV STATE open/syncd open/syncd open/syncd open/syncd
MOUNT POINT N/A /data /spl /apps
For a complete storage system, this could yield in for example: -redovg: LV NAME redo1lv redo2lv loglv03
TYPE jfs2 jfs2 jfs2log
LPs 42 1401 1
PPs 42 1401 1
PVs 3 3 1
LV STATE open/syncd open/syncd open/syncd
MOUNT POINT /u05 /u04 N/A
-db2vg: LV NAME db2lv loglv00 -oravg: LV NAME u01 u02 u03 logfs -rootvg: LV NAME hd5 hd6 hd8 hd4 hd2 hd9var hd3 hd1 hd10opt fslv00 fslv01 paging00 sysdump1 oralv fslv03
TYPE jfs2 jfs2log
LPs 600 1
PPs 600 1
PVs 2 1
LV STATE open/syncd open/syncd
MOUNT POINT /db2_database N/A
TYPE jfs2 jfs2 jfs2 jfs2log
LPs 800 400 200 2
PPs 800 400 200 2
PVs 2 2 2 1
LV STATE open/syncd open/syncd open/syncd open/syncd
MOUNT POINT /u01 /u02 /u03 N/A
TYPE boot paging jfs2log jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 jfs2 paging sysdump jfs2 jfs2
LPs 1 36 1 8 24 9 11 10 2 1 2 32 80 100 63
PPs 2 72 2 16 48 18 22 20 4 2 4 32 80 100 63
PVs 2 2 2 3 2 3 3 2 2 2 3 1 1 1 2
LV STATE closed/syncd open/syncd open/syncd open/syncd open/syncd open/syncd open/syncd open/syncd open/syncd open/syncd open/syncd open/syncd open/syncd open/syncd open/syncd
MOUNT POINT N/A N/A N/A / /usr /var /tmp /home /opt /XmRec /tmp/m2 N/A N/A /opt/app/oracle /bmc_home
And you can list the LVs by PV by running # lspv -l hdiskn lsvg Command: -------------o -p VG_name -l VG_name
Shows only the active volume groups. Shows all the PVs that belong to the vg_name Shows all the LVs that belong to the vg_name
Examples: # lsvg rootvg informixvg oravg # lsvg -o rootvg oravg # lsvg oravg VOLUME GROUP: oravg 00ccf45d00004c0000000104564d2386 VG STATE: active VG PERMISSION: read/write MAX LVs: 256
VG IDENTIFIER: PP SIZE: TOTAL PPs: FREE PPs:
256 megabyte(s) 1894 (484864 megabytes) 492 (125952 megabytes)
LVs: 4 OPEN LVs: 4 TOTAL PVs: 2 STALE PVs: 0 ACTIVE PVs: 2 MAX PPs per PV: 1016 LTG size: 128 kilobyte(s) HOT SPARE: no
USED PPs: QUORUM: VG DESCRIPTORS: STALE PPs: AUTO ON: MAX PVs: AUTO SYNC: BB POLICY:
# lsvg -p informixvg informixvg PV_NAME PV STATE hdisk3 active hdisk4 active
TOTAL PPs 542 542
FREE PPs 462 447
LPs 1 24 1 4 76 4 6 20
PVs 1 1 1 1 1 1 1 1
# lsvg -l rootvg LV NAME TYPE hd5 boot hd6 paging hd8 jfslog hd4 jfs hd2 jfs hd9var jfs hd3 jfs paging00 paging .. ..
PPs 1 24 1 4 76 4 6 20
1402 (358912 megabytes) 2 3 0 yes 32 no relocatable
FREE DISTRIBUTION 109..28..108..108..109 109..13..108..108..109 LV STATE closed/syncd open/syncd open/syncd open/synced open/synced open/synced open/synced open/synced
MOUNT POINT N/A N/A N/A / /usr /var /tmp N/A
Suppose we have 70GB disk=70000MB 1016 partitions=> 63 MB per PP extendvg command: ----------------extendvg VGName hdiskNumber # extendvg newvg hdisk23 How to Add a Disk to a Volume Group? extendvg
VolumeGroupName
hdisk0 hdisk1 ... hdiskn
reducevg command: ----------------To remove a PV from a VG: # reducevg myvg hdisk23 To remove a VG: Suppose we have a VG informixvg with 2 PV, hdisk3 and hdisk4: # reducevg -d informixvg hdisk4 When you delete the last disk from the VG, the VG is also removed.
# reducevg -d informix hdisk3 varyonvg and varyoffvg commands: -------------------------------When you activate a VG for use, all its resident filesystems are mounted by default if they have the flag mount=true in the /etc/filesystems file. # varyonvg apachevg # varyoffvg apachevg To use this command, you must be sure that none of the logical volumes are opened, that is, in use. mkvg command: ------------You can create a new VG by using "smitty mkvg" or by using the mkvg command. Use the following command, where s "partition_size" sets the number of megabytes in each physical partition where the partition_size is expressed in units of megabytes from 1 through 1024. The size variable must be equal to a power of 2 (for example 1, 2, 4, 8). The default value is 4. mkvg -y -s As with physical volumes, volume groups can be created and removed and their characteristics can be modified. Before a new volume group can be added to the system, one or more physical volumes not used in other volume groups, and in an available state, must exist on the system. The following example shows the use of the mkvg command to create a volume group myvg using the physical volumes hdisk1 and hdisk5. # mkvg -y myvg -d 10 -s 8 hdisk1 hdisk5 # mkvg -y oravg -d 10 -s 64 hdisk1
mklv command: ------------To create a LV, you can use the smitty command "smitty mklv" or just use the mklv command by itself. The mklv command creates a new logical volume within the VolumeGroup. For example,
all file systems must be on separate logical volumes. The mklv command allocates the number of logical partitions to the new logical volume. If you specify one or more physical volumes with the PhysicalVolume parameter, only those physical volumes are available for allocating physical partitions; otherwise, all the physical volumes within the volume group are available. The default settings provide the most commonly used characteristics, but use flags to tailor the logical volume to the requirements of your system. Once a logical volume is created, its characteristics can be changed with the chlv command. When you create a LV, you also specify the number of LP�s, and how a LP maps to PP�s. Later, you can create one filesystem per LV. Examples The following example creates a LV "lv05" on the VG "splvg", with two copies (2 PPs) of each LP. In this case, we are mirroring a LP to two PP's. Also, 200 PP's are specified. If a PP is 128 MB is size, the total amount of space of one "mirror" is 25600 MB. # mklv -y lv05 -c 2 splvg 200 The following example shows the use of mklv command to create a new LV newlv in the rootvg and it will have 10 LP�s and each LP consists of 2 physical partitions. # mklv -y newlv -c 2 rootvg 10 To make a logical volume in volume group vg02 with one logical partition and a total of two copies of the data, enter: # mklv -c 2 vg02 1 To make a logical volume in volume group vg03 with nine logical partitions and a total of three copies spread across a maximum of two physical volumes, and whose allocation policy is not strict, enter: # mklv -c 3 -u 2 -s n vg03 9 To make a logical volume in vg04 with five logical partitions allocated across the center sections of the physical volumes when possible, with no bad-block relocation, and whose type is paging, enter: # mklv -a c -t paging -b n vg04 5 To make a logical volume in vg03 with 15 logical partitions chosen from physical volumes hdisk5, hdisk6, and hdisk9, enter:
# mklv vg03 15 hdisk5 hdisk6 hdisk9 To make a striped logical volume in vg05 with a stripe size of 64K across 3 physical volumes and 12 logical partitions, enter: # mklv -u 3 -S 64K vg05 12 To make a striped logical volume in vg05 with a stripe size of 8K across hdisk1, hdisk2, and hdisk3 and 12 logical partitions, enter: # mklv -S 8K vg05 12 hdisk1 hdisk2 hdisk3 The following example uses a "map file /tmp/mymap1" which list which PPs are to be used in creating a LV: # mklv -t jfs -y lv06 -m /tmp/mymap1 rootvg 10 The setting The setting that copies The default
Strict=y means that each copy of the LP is placed on a different PV. Strict=n means are not restricted to different PVs. is strict.
# mklv -y lv13 -c 2 failovervg 150 # crfs -v jfs -d lv13 -m /backups2 -a bf=true Another simple example using local disks: # mkvg -y appsvg -s 32 hdisk2 # mkvg -y datavg -s 32 hdisk3 # mklv -y testlv -c 1 appsvg 10 # mklv -y backuplv -c 1 datavg 10 # crfs -v jfs -d testlv -m /test -a bf=true # crfs -v jfs -d backuplv -m /backup -a bf=true mklv mklv crfs crfs
-y -y -v -v
testlv1 -c 1 appsvg 10 testlv2 -c 1 datavg 10 jfs -d testlv1 -m /test1 -a bf=true jfs -d testlv2 -m /test2 -a bf=true
mklv mklv crfs crfs
-y -y -v -v
testlv1 -c 1 vgp0corddap01 10 testlv2 -c 1 vgp0corddad01 10 jfs -d testlv1 -m /test1 -a bf=true jfs -d testlv2 -m /test2 -a bf=true
rmlv command: ------------# rmlv newlv Warning, all data on logical volume newlv will be destroyed. rmlv: Do you wish to continue? y(es) n(o) y #
extendlv command: ----------------The following example shows the use of the extentlv command to add 3 more LP's to the LP newlv: # extendlv newlv 3 cplv command: ------------The following command copies the contents of LV oldlv to a new LV called newlv: # cplv -v myvg -y newlv oldlv To copy to an existing LV: # cplv -e existinglv oldlv Purpose Copies the contents of a logical volume to a new logical volume. Syntax To Copy to a New Logical Volume cplv [ -vg VolumeGroup ] [ -lv NewLogicalVolume | -prefix Prefix ] SourceLogicalVolume To Copy to an Existing Logical Volume cplv [ -f ] SourceLogicalVolume DestinationLogicalVolume cplv -e DestinationLogicalVolume [-f] SourceLogicalVolume -e: specifies that the DestinationLogicalVolume already exists. -f: no user confirmation -y: specifies the name to use for the NewLogicalVolume, instead of a system generated name. Description Attention: Do not copy from a larger logical volume containing data to a smaller one. Doing so results in a corrupted file system because some data is not copied. The cplv command copies the contents of SourceLogicalVolume to a new or existing logical volume. The SourceLogicalVolume parameter can be a logical volume name or a logical volume ID. The cplv command creates a new logical volume with a system-generated name by using the default syntax. The system-generated name is displayed. Note: The cplv command can not copy logical volumes which are in the open state, including logical volumes that are being used as backing devices for virtual storage. Flags -f Copies to an existing logical volume without requesting user confirmation. -lv NewLogicalVolume Specifies the name to use, in place of a system-generated name,
for the new logical volume. Logical volume names must be unique systemwide names, and can range from 1 to 15 characters. -prefix Prefix Specifies a prefix to use in building a system-generated name for the new logical volume. The prefix must be less than or equal to 13 characters. A name cannot be a name already used by another device. -vg VolumeGroup Specifies the volume group where the new logical volume resides. If this is not specified, the new logical volume resides in the same volume group as the SourceLogicalVolume. Examples To copy the contents of logical volume fslv03 to a new logical volume, type: # cplv fslv03 The new logical volume is created, placed in the same volume group as fslv03, and named by the system. To copy the contents of logical volume fslv03 to a new logical volume in volume group vg02, type: #cplv -vg vg02 fslv03 The new logical volume is created, named, and added to volume group vg02. #To copy the contents of logical volume lv02 to a smaller, existing logical volume, lvtest, without requiring user confirmation, type: cplv -f lv02 lvtest Errors: ------0516-746 cplv: Destination logical volume must have type set to copy chlv -t copy lvprj ========================================================================== CASES of usage of cplv command: CASE 1: ------TITLE
: Procedure for moving a filesystem between disks that are in different volume groups using the cplv command. OS LEVEL : AIX 4.x DATE : 25/11/99 VERSION : 1.0 ---------------------------------------------------------------------------In the following example, an RS6000 has 1 one disk with rootvg on, and has just had a second disk installed. The second disk needs a volume group creating on it and a data filesystem transferring to the new disk. Ensure that you have a full system backup befor you start.
lspv hdisk0 hdisk1
00009922faf79f0d None
rootvg None
df -k Filesystem /dev/hd4 /dev/hd2 /dev/hd9var /dev/hd3 /dev/hd1 /dev/lv00 /dev/ftplv /dev/lv01
1024-blocks 8192 380928 32768 28672 53248 200704 102400 114688
Free %Used 1228 86% 40984 90% 20952 37% 1644 95% 51284 4% 110324 46% 94528 8% 58240 50%
Iused %Iused Mounted on 1647 41% / 11014 12% /usr 236 3% /var 166 3% /tmp 95 1% /home 1869 4% /home/john 32 1% /home/ftp 59 1% /usr2
In this example the /usr2 filesystem needs to be moved to the new disk drive, freeing up space in the root volume group. 1, Create a data volume group on the new disk (hdisk1), the command below will create a volume group called datavg on hdisk1 with a PP size of 32 Meg:mkvg -s 32 -y datavg hdisk1 2, Create a jfslog logical volume on the new volume group :mklv -y datalog -t jfslog datavg 1 3, Initialise the jfslog :logform /dev/datalog logform: destroy /dev/datalog (y)?y 4, Umount the filesystem that is being copied :umount /usr2 5, Copy the /usr2 logical volume (lv01) to a new logical volume (lv11) on the new volume group :cplv -y lv11 -v datavg lv01 cplv: Logical volume lv01 successfully copied to lv11 . 6, Change the /usr2 filesystem to use the new (/dev/lv11) logical volume and not the old (/dev/lv01) logical volume :chfs -a dev=/dev/lv11 /usr2 7, Change the /usr2 filesystem to use the jfslog on the new volume group (/dev/datalog) :-
chfs -a log=/dev/datalog /usr2 8, Mount the filesystem :mount /usr2 df -k Filesystem /dev/hd4 /dev/hd2 /dev/hd9var /dev/hd3 /dev/hd1 /dev/lv00 /dev/ftplv /dev/lv11
1024-blocks 8192 380928 32768 28672 53248 200704 102400 114688
Free %Used 1220 86% 40984 90% 20952 37% 1644 95% 51284 4% 110324 46% 94528 8% 58240 50%
Iused %Iused Mounted on 1649 41% / 11014 12% /usr 236 3% /var 166 3% /tmp 95 1% /home 1869 4% /home/john 32 1% /home/ftp 59 1% /usr2
9, Once the filesystem has been checked out, the old logical volume can be removed :rmfs /dev/lv01 Warning, all data contained on logical volume lv01 will be destroyed. rmlv: Do you wish to continue? y(es) n(o)? y rmlv: Logical volume lv01 is removed. If you wish to copy further filesystems repeat parts 4 to 9. ========================================================================== CASE 2: ------Doel: ----Een "move" van het /prj filesystem (met Websphere in /prj/was) op rootvg, naar een nieuw (groter en beter) volume group "wasvg". Het huidige /prj op rootvg, correspondeerd met de LV "prjlv". De nieuw te maken /prj op wasvg, correspondeerd met de LV "lvprj". ROOTVG WASVG --------------------------|/usr (hd2) | | | |.. | | | |/prj (prjlv)|----------->|/prj (lvprj) | |.. | | | -------------------------hdisk0,hdisk1 hdisk12,hdisk13 opm: /prj bevat "/prj/was", en dat is Websphere. Hier maken we geen gebruik van een backup tape. Gebruik het cplv command
umount /prj chfs -m /prj_old /prj + mkvg -y wasvg -d 10 -s 128 hdisk12 hdisk13
-- maak VG aan
+ mklv -y lvprj -c 2 wasvg 400
-- maak LV aan
+ mklv -y waslog -t jfslog wasvg 1
-- maak een jfslog
+ logform /dev/waslog
-- init de log
cplv -e lvprj prjlv chfs -a dev=/dev/lvprj /prj_old
--
chfs -a log=/dev/waslog /prj_old chfs -m /prj /prj_old mount /prj ========================================================================== migratepv command: -----------------Use the following command to move PPs from hdisk1 to hdisk6 and hdisk7 (all PVs must be in 1 VG) # migratepv hdisk1 hdisk6 hdisk7 Use the following command to move PPs in LV lv02 from hdisk1 to hdisk6 # migratepv -l lv02 hdisk1 hdisk6 chvg command: ------------This example multiplies by 2 the number of PPs: # chvg -t2 datavg chpv command: ------------The chpv command changes the state of the physical volume in a volume group by setting allocation permission to either allow or not allow allocation and by setting the availability to either available or removed. This command can also be used to clear the boot record for the given physical volume. Characteristics for a physical volume remain in effect unless explicitly changed with the corresponding flag. Examples To close physical volume hdisk03, enter:
# chpv -v r hdisk03 The physical volume is closed to logical input and output until the -v a flag is used. To open physical volume hdisk03, enter: # chpv -v a hdisk03 The physical volume is now open for logical input and output. To stop the allocation of physical partitions to physical volume hdisk03, enter: # chpv -a n hdisk03 No physical partitions can be allocated until the -a y flag is used. To clear the boot record of a physical volume hdisk3, enter: # chpv -c hdisk3
How to synchronize stale partitions in a VG?: --------------------------------------------the syncvg command: syncvg Command Purpose Synchronizes logical volume copies that are not current. Syntax syncvg [ -f ] [ -i ] [ -H ] [ -P NumParallelLps ] { -l | -p | -v } Name ... Description The syncvg command synchronizes the physical partitions, which are copies of the original physical partition, that are not current. The syncvg command can be used with logical volumes, physical volumes, or volume groups, with the Name parameter representing the logical volume name, physical volume name, or volume group name. The synchronization process can be time consuming, depending on the hardware characteristics and the amount of data. When the -f flag is used, a good physical copy is chosen and propagated to all other copies of the logical partition, whether or not they are stale. Using this flag is necessary in cases where the logical volume does not have the mirror write consistency recovery. Unless disabled, the copies within a volume group are synchronized automatically when the volume group is activated by the varyonvg command. Note: For the sycnvg command to be successful, at least one good copy of the logical
volume should be accessible, and the physical volumes that contains this copy should be in ACTIVE state. If the -f option is used, the above condition applies to all mirror copies. If the -P option is not specified, syncvg will check for the NUM_PARALLEL_LPS environment variable. The value of NUM_PARALLEL_LPS will be used to set the number of logical partitions to be synchronized in parallel. Examples To synchronize the copies on physical volumes hdisk04 and hdisk05, enter: # syncvg -p hdisk04 hdisk05 To synchronize the copies on volume groups vg04 and vg05, enter: # syncvg -v vg04 vg05
How to Mirror a Logical Volume? : -------------------------------mklvcopy LogicalVolumeName Numberofcopies syncvg VolumeGroupName To add a copy for LV lv01 on disk hdisk7: # mklvcopy lv01 2 hdisk7 Identifying hotspots: lvmstat command: -------------------------------------The lvmstat command display statistics values since the previous lvmstat command. # lvmstat -v rootvg -e # lvmstat -v rootvg -C # lvmstat -v rootvg Logical Volume hd8 paging01 .. ..
iocnt 4 0
KB_read 0 0
KB_wrtn 0 0
Kbps 0.00 0.00
31.2 Mirroring a VG: ==================== LVM provide a disk mirroring facility at the LV level. Mirroring is the association of 2 or 3 PP's with each LP in a LV. Use the "mklv", or the "mklvcopy", or the "mirrorvg" command. The mklv command allows you to select one or two additional copies for each logical volume. example:
To make a logical volume in volume group vg03 with nine logical partitions and a total of three copies spread across a maximum of two physical volumes, and whose allocation policy is not strict, enter: mklv -c 3 -u 2 -s n vg03 9 Mirroring can also be added to an existing LV using the mklvcopy command. The mirrorvg command mirrors all the LV's on a given VG. Examples: - To triply mirror a VG, run # mirrorvg -c 3 myvg - To get default mirroring of the rootvg, run # mirrorvg rootvg # # #
To replace a failed disk in a mirrored VG, run unmirrorvg workvg hdisk7 reducevg workvg hdisk7 rmdev -l hdisk7 -d
Now replace the failed disk with a new one and name it hdisk7 # extendvg workvg hdisk7 # mirrorvg workvg mirrorvg command: ----------------mirrorvg Command Purpose Mirrors all the logical volumes that exist on a given volume group. This command only applies to AIX 4.2.1 or later. Syntax mirrorvg [ -S | -s ] [ -Q ] [ -c Copies] [ -m ] VolumeGroup [ PhysicalVolume ... ]
Description The mirrorvg command takes all the logical volumes on a given volume group and mirrors those logical volumes. This same functionality may also be accomplished manually if you execute the mklvcopy command for each individual logical volume in a volume group. As with mklvcopy, the target physical drives to be mirrored with data must already be members of the volume group. To add disks to a volume group, run the extendvg command. By default, mirrorvg attempts to mirror the logical volumes onto any of the disks in a volume group. If you wish to control which drives are used for mirroring, you must include the
list of disks in the input parameters, PhysicalVolume. Mirror strictness is enforced. Additionally, mirrorvg mirrors the logical volumes, using the default settings of the logical volume being mirrored. If you wish to violate mirror strictness or affect the policy by which the mirror is created, you must execute the mirroring of all logical volumes manually with the mklvcopy command. When mirrorvg is executed, the default behavior of the command requires that the synchronization of the mirrors must complete before the command returns to the user. If you wish to avoid the delay, use the -S or -s option. Additionally, the default value of 2 copies is always used. To specify a value other than 2, use the -c option. Note: To use this command, you must either have root user authority or be a member of the system group. Attention: The mirrorvg command may take a significant amount of time before completing because of complex error checking, the amount of logical volumes to mirror in a volume group, and the time is takes to synchronize the new mirrored logical volumes. You can use the Volumes application in Web-based System Manager (wsm) to change volume characteristics. You could also use the System Management Interface Tool (SMIT) smit mirrorvg fast path to run this command. Flags -c Copies Specifies the minimum number of copies that each logical volume must have after the mirrorvg command has finished executing. It may be possible, through the independent use of mklvcopy, that some logical volumes may have more than the minimum number specified after the mirrorvg command has executed. Minimum value is 2 and 3 is the maximum value. A value of 1 is ignored. -m exact map Allows mirroring of logical volumes in the exact physical partition order that the original copy is ordered. This option requires you to specify a PhysicalVolume(s) where the exact map copy should be placed. If the space is insufficient for an exact mapping, then the command will fail. You should add new drives or pick a different set of drives that will satisfy an exact logical volume mapping of the entire volume group. The designated disks must be equal to or exceed the size of the drives which are to be exactly mirrored, regardless of if the entire disk is used. Also, if any logical volume to be mirrored is already mirrored, this command will fail.
-Q Quorum Keep By default in mirrorvg, when a volume group's contents becomes mirrored, volume group quorum is disabled. If the user wishes to keep the volume group quorum requirement after mirroring is complete, this option should be used in the command. For later quorum changes, refer to the chvg command. -S Background Sync Returns the mirrorvg command immediately and starts a background syncvg of the volume group. With this option, it is not obvious when the mirrors have completely finished their synchronization. However, as portions of the mirrors become synchronized, they are immediately used by the operating system in mirror usage. -s Disable Sync Returns the mirrorvg command immediately without performing any type of mirror synchronization. If this option is used, the mirror may exist for a logical volume but is not used by the operating system until it has been synchronized with the syncvg command. The following is a description of rootvg: - rootvg mirroring When the rootvg mirroring has completed, you must perform three additional tasks: bosboot, bootlist, and reboot. The bosboot command is required to customize the bootrec of the newly mirrored drive. The bootlist command needs to be performed to instruct the system which disk and order you prefer the mirrored boot process to start. Finally, the default of this command is for Quorum to be turned off. For this to take effect on a rootvg volume group, the system must be rebooted. - non-rootvg mirroring When this volume group has been mirrored, the default command causes Quorum to deactivated. The user must close all open logical volumes, execute varyoffvg and then varyonvg on the volume group for the system to understand that quorum is or is not needed for the volume group. If you do not revaryon the volume group, mirror will still work correctly. However, any quorum changes will not have taken effect. rootvg and non-rootvg mirroring The system dump devices, primary and secondary, should not be mirrored. In some systems, the paging device and the dump device are the same device. However, most users want the paging device mirrored. When mirrorvg detects that a dump device and the paging device are the same, the logical volume will be mirrored automatically. If mirrorvg detects that the dump and paging device are different logical volumes, the paging device is automatically mirrored, but the dump logical volume is not. The dump device can be queried and modified with the sysdumpdev command.
Remark: ------Run bosboot to initialize all boot records and devices by executing the following command: bosboot -a -d /dev/hdisk? hdisk? is the first hdisk listed under the PV heading after the command lslv -l hd5 has executed. Secondary, you need to understant that the mirroring under AIX it's at the logical volume level. The mirrorvg command is a hight level command that use "mklvcopy" command. So, all LV created before runing the mirrorvg command are keep synchronised, but if you add a new LV after runing mirrorvg, you need to mirror it manualy using "mklvcopy" . Remark: ------lresynclv
Mirroring the rootvg: --------------------Method 1: --------Howto mirror an AIX rootvg The following steps will guide you trough the mirroring of an AIX rootvg. This info is valid for AIX 4.3.3, AIX 5.1, AIX 5.2 and AIX 5.3. Make sure you have an empty disk, in this example its hdisk1 Add the disk to the vg via # extendvg rootvg hdisk1 Mirror the vg via: # mirrorvg -s rootvg Now synchronize the new copies you created: # syncvg -v rootvg As we want to be able to boot from different disks, we need to use bosboot: # bosboot -a As hd5 is mirrored there is no need to do it for each disk. Now, update the bootlist: # bootlist -m normal hdisk1 hdisk0 # bootlist -m service hdisk1 hdisk0
When mirrorvg is executed, the default behavior of the command requires that the synchronization of the mirrors must complete before the command returns to the user. If you wish to avoid the delay, use the -S or -s option. Additionally, the default value of 2 copies is always used. To specify a value other than 2, use the -c option. Method 2: --------------------------------------------------------------------------------------# Add the new disk, say its hdisk5, to rootvg extendvg rootvg hdisk5 # If you use one mirror disk, be sure that a quorum is not required for varyon: chvg -Qn rootvg # Add the mirrors for all rootvg LV's: mklvcopy mklvcopy mklvcopy mklvcopy mklvcopy mklvcopy mklvcopy mklvcopy mklvcopy mklvcopy
hd1 2 hdisk5 hd2 2 hdisk5 hd3 2 hdisk5 hd4 2 hdisk5 hd5 2 hdisk5 hd6 2 hdisk5 hd8 2 hdisk5 hd9var 2 hdisk5 hd10opt 2 hdisk5 prjlv 2 hdisk5
#If you have other LV's in your rootvg, be sure to create copies for them as well !! -----------------------------------------------------------------------------# lspv -l hdisk0 hd5 prjlv hd6 fwdump hd8 hd4 hd2 hd9var hd3 hd1 hd10opt
1 256 59 5 1 26 45 10 22 8 24
1 256 59 5 1 26 45 10 22 8 24
01..00..00..00..00 108..44..38..50..16 00..59..00..00..00 00..05..00..00..00 00..00..01..00..00 00..00..02..24..00 00..00..37..08..00 00..00..02..08..00 00..00..04..10..08 00..00..08..00..00 00..00..16..08..00
N/A /prj N/A /var/adm/ras/platform N/A / /usr /var /tmp /home /opt
Method 3: --------In the following example, an RS6000 has 3 disks, 2 of which have the AIX filesystems mirrored on. The boolist contains both hdisk0 and hdisk1. There are no other logical volumes in rootvg other than the AIX system
logical volumes. hdisk0 has failed and need replacing, both hdisk0 and hdisk1 are in "Hot Swap" carriers and therefore the machine does not need shutting down. lspv hdisk0 hdisk1 hdisk2
00522d5f22e3b29d 00522d5f90e66fd2 00522df586d454c3
rootvg rootvg datavg
lsvg -l rootvg rootvg: LV NAME hd6 hd5 hd8 hd4 hd2 hd9var hd3 hd1
TYPE paging boot jfslog jfs jfs jfs jfs jfs
LPs 4 1 1 1 12 1 2 1
PPs 8 2 2 2 24 2 4 2
PVs 2 2 2 2 2 2 2 2
LV STATE open/syncd closed/syncd open/syncd open/syncd open/syncd open/syncd open/syncd open/syncd
MOUNT POINT N/A N/A N/A / /usr /var /tmp /home
1, Reduce the logical volume copies from both disks to hdisk1 only :rmlvcopy rmlvcopy rmlvcopy rmlvcopy rmlvcopy rmlvcopy rmlvcopy rmlvcopy
hd6 1 hdisk0 hd5 1 hdisk0 hd8 1 hdisk0 hd4 1 hdisk0 hd2 1 hdisk0 hd9var 1 hdisk0 hd3 1 hdisk0 hd1 1 hdisk0
2, Check that no logical volumes are left on hdisk0 :lspv -p hdisk0 hdisk0: PP RANGE 1-101 102-201 202-301 302-401 402-501
STATE free free free free free
REGION outer edge outer middle center inner middle inner edge
LV ID
TYPE
MOUNT POINT
3, Remove the volume group from hdisk0 reducevg -df rootvg hdisk0 4, Recreate the boot logical volume on hdisk1, and reset bootlist:bosboot -a -d /dev/hdisk1 bootlist -m normal rmt0 cd0 hdisk1 5, Check that everything has been removed from hdisk0 :-
lspv hdisk0 hdisk1 hdisk2
00522d5f22e3b29d 00522d5f90e66fd2 00522df586d454c3
None rootvg datavg
6, Delete hdisk0 :rmdev -l hdisk0 -d 7, Remove the failed hard drive and replace with a new hard drive. 8, Configure the new disk drive :cfgmgr 9, Check new hard drive is present :lspv 10, Include the new hdisk in root volume group :extendvg rootvg hdisk?
(where hdisk? is the new hard disk)
11, Re-create the mirror :mirrorvg rootvg hdisk?
(where hdisk? is the new hard disk)
12, Syncronise the mirror :syncvg -v rootvg 13, Reset the bootlist :bootlist -m normal rmt0 cd0 hdisk0 hdisk1 14, Turn off Quorum checking on rootvg :chvg -Q n rootvg Method 4: --------Howto mirror an AIX rootvg The following steps will guide you trough the mirroring of an AIX rootvg. This info is valid for AIX 4.3.3, AIX 5.1, AIX 5.2 and AIX 5.3. Make sure you have an empty disk, in this example its hdisk1 Add the disk to the vg via "extendvg rootvg hdisk1 Mirror the vg via: "mirrorvg rootvg" Adapt the bootlist to add the current disk, the system will then fail to hdisk1 is hdisk0 fails during startup do bootlist -o -m normal this will list currently 1 disk, in this exmaple hdisk0 do bootlist -m normal hdisk0 hdisk1 Run a bosboot on both new disks, this will install all software needed for boot on
the disk bosboot -ad hdisk0 bosboot -ad hdisk1 Method 5: --------Although the steps to mirror volume groups between HP and AIX are incredibly similar, there are enough differences to send me through hoops if/when I ever have to do that. Therefore, the following checklist: 1. Mirror the logical volumes: If you don't care what disks the lvs get mirrored to, execute mirrorvg rootvg Otherwise: for lv in $(lsvg -l rootvg | grep -i open/syncd | \ grep -v dumplv | awk '{print $1}') do mklvcopy ${lv} 1 ${disk} done 2. Change the quorum checking if you did not use mirrorvg: chvg -Q n rootvg 3. Run bosboot on the new drive to copy boot files to it: bosboot ${disk} 4. Update the bootlist with the new drive: bootlist -m normal hdisk0 hdisk1 5. Reboot the system to enable the new quorum checking parameter Method 6: --------Audience: System Administrators Date: September 25, 2002 Mirroring "rootvg" protects the operating system from a disk failure. Mirroring "rootvg" requires a couple extra steps compared to other volume groups. The mirrored rootvg disk must be bootable *and* in the bootlist. Otherwise, if the primary disk fails, you'll continue to
run, but you won't be able to reboot. In brief, the procedure to mirror rootvg on hdisk0 to hdisk1 is 1. Add hdisk1 to rootvg: extendvg rootvg hdisk1 2. Mirror rootvg to hdisk1: mirrorvg rootvg hdisk1 (or smitty mirrorvg) 3. Create boot images on hdisk1: bosboot -ad /dev/hdisk1 4. Add hdisk1 to the bootlist: bootlist -m normal hdisk0 hdisk1 5. Reboot to disable quorum checking on rootvg. The mirrorvg turns off quorum by default, but the system needs to be rebooted for it to take effect. For more information, and a comprehensive procedure see the man page for mirrorvg and
Example using mklvcopy: ----------------------mklvcopy [ -a Position ] [ -e Range ] [ -k ] [ -m MapFile ] [ -s Strict ] [ -u UpperBound ] LogicalVolume Copies [ PhysicalVolume... ] Add a copy of LV "lv01" on disk hdisk7: # mklvcopy lv01 2 hdisk7 The mklvcopy command increases the number of copies in each logical partition in LogicalVolume. This is accomplished by increasing the total number of physical partitions for each logical partition to the number represented by Copies. The LogicalVolume parameter can be a logical volume name or logical volume ID. You can request that the physical partitions for the new copies be allocated on specific physical volumes (within the volume group) with the PhysicalVolume parameter; otherwise, all the physical volumes within the volume group are available for allocation. The logical volume modified with this command uses the Copies parameter as its new copy characteristic. The data in the new copies are not synchronized until one of the following occurs: the -k option is used, the volume group is activated by the varyonvg command, or
the volume group or logical volume is synchronized explicitly by the syncvg command. Individual logical partitions are always updated as they are written to. The default allocation policy is to use minimum numbering of physical volumes per logical volume copy, to place the physical partitions belong to a copy as contiguously as possible, and then to place the physical partitions in the desired region specified by the -a flag. Also, by default, each copy of a logical partition is placed on a separate physical volume.
Using smitty: ------------# smit mklv or # smit mklvcopy Using "smit mklv" you can create a new LV and at the same time tell the system to create a mirror (2 or 3 copies) of each LP and which PV's are involved. Using "smit mklvcopy" you can add mirrors to an existing LV.
31.3 Filesystems in AIX: ======================== After a VG is created, you can create filesystems. You can use smitty or the crfs and mkfs command. File systems are confined to a single logical volume. The journaled file system (JFS) and the enhanced journaled file system (JFS2) are built into the base operating system. Both file system types link their file and directory data to the structure used by the AIX Logical Volume Manager for storage and retrieval. A difference is that JFS2 is designed to accommodate a 64-bit kernel and larger files. Run lsfs -v jfs2 to determine if your system uses JFS2 file systems. This command returns no output if it finds only standard file systems. crfs: ----crfs -v VfsType { -g VolumeGroup | -d Device } [ -l LogPartitions ] -m MountPoint [ -n NodeName ] [ -u MountGroup ] [ -A { yes | no } ] [ -p {ro | rw } ]
[ -a Attribute= Value ... ] [ -t { yes | no } ]
The crfs command creates a file system on a logical volume within a previously created volume group. A new logical volume is created for the file system unless the name of an existing logical volume is specified using the -d. An entry for the file system is put into the /etc/filesystems file. crfs -v jfs -g(vg) -m(mount point) -a size=(size Will create a logical volume on the volume group the logical volume. All at the size stated. Will /etc/filesystems and will create the mount point
of fs) -A yes and create the file system on add entry into directory if it does not exist.
- To make a JFS on the rootvg volume group with nondefault fragment size and nondefault nbpi, enter: # crfs -v jfs -g rootvg -m /test -a size=32768 -a frag=512 -a nbpi=1024 This command creates the /test file system on the rootvg volume group with a fragment size of 512 bytes, a number of bytes per i-node (nbpi) ratio of 1024, and an initial size of 16MB (512 * 32768). - To make a JFS on the rootvg volume group with nondefault fragment size and nondefault nbpi, enter: # crfs -v jfs -g rootvg -m /test -a size=16M -a frag=512 -a nbpi=1024 This command creates the /test file system on the rootvg volume group with a fragment size of 512 bytes, a number of bytes per i-node (nbpi) ratio of 1024, and an initial size of 16MB. - To create a JFS2 file system which can support NFS4 ACLs, type: # crfs -v jfs2 -g rootvg -m /test -a size=1G -a ea=v2 - This command creates the /test JFS2 file system on the rootvg volume group with an initial size of 1 gigabyte. The file system will store extended attributes using the v2 format. # crfs -v jfs -g backupvg -m /backups -a size=32G -a bf=true # crfs -v jfs -g oravg -m /filetransfer -a size=4G -a bf=true Extended example: ----------------The following command creates a JFS filesystem on a previously created LV "lv05". In this example, suppose the LV was created in the following way: # mklv -y lv05 -c 2 splvg 200 In this case, it is clear that we mirror each LP to 2 PP's (because of the -c 2). Now to create a filesystem on lv05, we can use the command # crfs -v jfs -d lv05 -m /spl -a bf=true Note that we did not mentioned the size of the filesystem. This is because we use
a previously defined LV with a known size. Notes: 1. The option -a bf=true allows large files [ > 2Gb]; 2. Specifying -m / (like for example "/data") will create the entry in /etc/filesystems for you Some more examples: ------------------Commands to create VG's: mkvg oravg -d 10 -s 128 hdisk2 hdisk4 mkvg splvg -d 10 -s 128 hdisk3 hdisk5 mkvg softwvg -d 10 -s 128 hdisk6 mkvg backupvg -d 10 -s 128 hdisk7 Set of Create Logical Volume and Filesystem commands: # crfs -v jfs -g -m -a size=xG -a bf=true or # mklv -y -c 2 No_Of_PPs # crfs -v jfs -d -m -a bf=true # # # #
mklv crfs mklv crfs
-y -v -y -v
lv05 -c 2 splvg 300 jfs -d lv05 -m /spl -a bf=true lv06 -c 2 splvg 100 jfs -d lv06 -m /u04 -a bf=true
# # # # # #
mklv mklv mklv crfs crfs crfs
-y -y -y -v -v -v
lv02 -c 2 oravg 200 lv03 -c 2 oravg 200 lv04 -c 2 oravg 200 jfs -d lv02 -m /u01 -a bf=true jfs -d lv03 -m /u02 -a bf=true jfs -d lv04 -m /u03 -a bf=true
# # # # #
crfs crfs crfs crfs crfs
-v -v -v -v -v
jfs jfs jfs jfs jfs
-g -g -g -g -g
backupvg -m /backups -a size=33G -a bf=true backupvg -m /data -a size=33G -a bf=true softwvg -m /apps -a size=16G -a bf=true softwvg -m /software -a size=33G -a bf=true softwvg -m /u05 -a size=12G -a bf=true
mkfs: ----The mkfs command makes a new file system on a specified device. The mkfs command initializes the volume label, file system label, and startup block. The Device parameter specifies a block device name, raw device name, or file system name. If the parameter
specifies a file system name, the mkfs command uses this name to obtain the following parameters from the applicable stanza in the /etc/filesystems file, unless these parameters are entered with the mkfs command. - To specify the volume and file system name for a new file system, type: # mkfs -lworks -vvol001 /dev/hd3 This command creates an empty file system on the /dev/hd3 device, giving it the volume serial number vol001 and file system name works. The new file system occupies the entire device. The file system has a default fragment size (4096 bytes) and a default nbpi ratio (4096). - To create a file system with nondefault attributes, type: # mkfs -s 8192 -o nbpi=2048,frag=512 /dev/lv01 This command creates an empty 4 MB file system on the /dev/lv01 device with 512byte fragments and 1 i-node for each 2048 bytes. -To create a large file enabled file system, type: # mkfs -V jfs -o nbpi=131072,bf=true,ag=64 /dev/lv01 This creates a large file enabled JFS file system with an allocation group size of 64 megabytes and 1 inode for every 131072 bytes of disk. The size of the file system will be the size of the logical volume lv01. - To create a file system with nondefault attributes, type: # mkfs -s 4M -o nbpi=2048, frag=512 /dev/lv01 This command creates an empty 4 MB file system on the /dev/lv01 device with 512byte fragments and one i-node for each 2048 bytes. - To create a JFS2 file system which can support NFS4 ACLs, type: # mkfs -V jfs2 -o ea=v2 /dev/lv01 This command creates an empty file system on the /dev/lv01 device with v2 format for extended attributes. chfs command: ------------- Example 1: How do I change the size of a filesystem? To increase /usr filesystem size by 1000000 512-byte blocks, type: # chfs -a size=+1000000 /usr - Example 2: To split off a copy of a mirrored file system and mount it read-only for use as an online backup, enter: # chfs -a splitcopy=/backup -a copy=2 /testfs This mount a read-only copy of /testfs at /backup.
- Example 3: To change the mount point of a file system, enter: # chfs -m /test2 /test This command changes the mount point of a file system from /test to /test2. - Eaxample 4: # chfs -a size=+20G /data/udb/eidwha2/eddwha2/DATA03 - Example 5: chfs -a size=+5M /opt
would do it this way: 1) chfs -m old_filename new_filename 2) umount old_filename 3) mount new_filename To stop or kill access to a fs, use: fuser -xuc /scratch
lsfs command: ------------Displays the characteristics of file systems. Syntax lsfs [ -q ] [ -c | -l ] [ -a | -v VfsType | -u MountGroup| [FileSystem...] ] Description The lsfs command displays characteristics of file systems, such as mount points, automatic mounts, permissions, and file system size. The FileSystem parameter reports on a specific file system. The following subsets can be queried for a listing of characteristics: All All All One
file systems file systems of a certain mount group file systems of a certain virtual file system type or more individual file systems
The lsfs command displays additional Journaled File System (JFS) or Enhanced Journaled File System (JFS2) characteristics if the -q flag is specified. To show all file systems in the /etc/filesystems file, enter: #lsfs To show all file systems of vfs type jfs, enter: #lsfs -v jfs
To show the file system size, the fragment size, the compression algorithm (if any), and the number of bytes per i-node as recorded in the superblock of the root file system, enter: #lsfs -q /
31.4 SAN connection via SDD, and related commands: ================================================== If you use advanced storage on AIX, the workings on disks and volume groups are a bit different from the traditional ways, using local disks, as described above. You can use SDD or SDDPCM Multipath IO. This section describes SDD. See section 31.5 for SDDPCM. Overview of the Subsystem device driver: ---------------------------------------The IBM System Storage Multipath Device Driver SDD provides multipath configuration environment support for a host system that is attached to storage devices. It provides: -Enhanced data availability -Automatic path failover and recovery to an alternate path -Dynamic load balancing of multiple paths -Concurrent microcode upgrade. The IBM System Storage Multipath Subsystem Device Driver Path Control Module SDDPCM provides AIX MPIO support. Its a loadable module. During the configuration of supported devices, SDDPCM is loaded and becomes part of the AIX MPIO Fibre Channel protocol device driver. The AIX MPIO-capable device driver with the SDDPCM module provides the same functions that SDD provides. Note that before attempting to exploit the Virtual shared disk support for the Subsystem device driver, you must read IBM Subsystem Device Driver Installation and User's Guide. An SDD implementation is available for AIX, Solaris, HP-UX, some Linux distro's, Windows 200x. An impression about the architecture on AIX can be seen in the following figure: ------------------------------| Host System | | ------------- | | |FC 0 | | FC 1| | | ------------- | ------------------------------| |
| | ---------------------------------ESS | --------------| | |port 0| |port 1| | | -------- \ /-------| | | \ / | | | | \/ | | | | / \ | | | -----------/ \---------- | | |Cluster 1| |Cluster 2|| | ---------------------| | | | | | | | | | | | | | | | | | | | | | O--|--|--|-------| | | | | | lun0| | | | | | | | O--|--|---------| | | | | lun1| | | | | | O--|-----------| | | | lun2| | | | O--------------| | | lun3 | --------------------------------DPO (Data Path Optimizer) was renamed by IBM a couple years ago- and became SDD (Subsystem Device Driver). When redundant paths are configured to ESS logical units, and the SDD is installed and configured, the AIX(R) lspv command shows multiple hdisks as well as a new construct called a vpath. The hdisks and vpaths represent the same logical unit. You will need to use the lsvpcfg command to get more information. Each SDD vpath device represents a unique physical device on the storage server. Each physical device is presented to the operating system as an operating system disk device. So, essentially, a vpath device acts like a disk. You will see later on that a hdisk is actually a "path" to a LUN, that can be reached either by fscsi0 or fscsi1. Also you will see that a vpath represents the LUN. SDD does not support multipathing to a bootdevice. Support for VIO: ---------------Starting from SDD version 1.6.2.0, a unique ID attribute is added to SDD vpath devices, in order to support AIX5.3 VIO future features. AIX device configure methods have been changed in both AIX52 TL8 and AIX53 TL4 for this support. Examples: --------For example, after issuing lspv, you see output similar to this:
# lspv hdisk0 hdisk1 hdisk18 hdisk19 hdisk20 hdisk21 hdisk22 hdisk23 hdisk24 vpath0 vpath1 vpath2 vpath3
000047690001d59d 000047694d8ce8b6 000047694caaba22 000047694caadf9a none none 000047694cab2963 none none none none 000047694cab0b35 000047694cab1d27
rootvg None None None None None None None None None None gpfs1scsivg gpfs1scsivg
After issuing lsvpcfg, you see output similar to this: # lsvpcfg vpath0 (Avail ) 502FCA01 = hdisk18 (Avail pv ) vpath1 (Avail ) 503FCA01 = hdisk19 (Avail pv ) vpath2 (Avail pv gpfs1scsivg) 407FCA01 = hdisk20 (Avail ) hdisk24 (Avail ) The examples above illustrate some important points: - vpath0 consists of a single path (hdisk18) and therefore will not provide failover protection. Also, hdisk18 is defined to AIX as a physical volume (pv flag) and has a PVID, as you can see from the output of the lspv command. Likewise for vpath1. - vpath2 has two paths (hdisk20 and hdisk24) and has a volume group defined on it. Notice that with the lspv command, hdisk20 and hdisk24 look like newly installed disks with no PVIDs. The lsvpcfg command had to be used to determine that hdisk20 and hdisk24 make up vpath2, which has a PVID. Warning: so be very carefull not to use a hdisk for a "local" VG, if its already used for a vpath. Other Example: -------------# lspv hdisk0 hdisk1 -hdisk2 -hdisk3 vpath0 vpath1 -hdisk4 vpath2 -hdisk5 -hdisk6 -hdisk7
00c49e8c8053fe86 00c49e8c841a74d5 none none 00c49e8c94c02c15 00c49e8c94c050d4 none 00c49e8c2806dc22 none none none
rootvg rootvg None None datavg appsvg None appsvg None None None
active active active active active
# lsvpcfg vpath0 (Avail pv datavg) 75BAFX1006C = hdisk2 (Avail ) hdisk5 (Avail ) vpath1 (Avail pv appsvg) 75BAFX1017B = hdisk3 (Avail ) hdisk6 (Avail ) vpath2 (Avail pv appsvg) 75BAFX10329 = hdisk4 (Avail ) hdisk7 (Avail ) # datapath query adapter Active Adapters :2 Adpt# 0 1
Name fscsi0 fscsi1
State NORMAL NORMAL
Mode ACTIVE ACTIVE
Select 12611291 13375287
Errors 0 0
Paths 3 3
Active 3 3
# datapath query device Total Devices : 3 DEV#: 0 DEVICE NAME: vpath0 TYPE: 2107900 POLICY: Optimized is vpath0 SERIAL: 75BAFX1006C ========================================================================== Path# Adapter/Hard Disk State Mode Select Errors 0 fscsi0/hdisk2 OPEN NORMAL 12561763 0 1 fscsi1/hdisk5 OPEN NORMAL 13324883 0
# this
DEV#: 1 DEVICE NAME: vpath1 TYPE: 2107900 POLICY: Optimized SERIAL: 75BAFX1017B ========================================================================== Path# Adapter/Hard Disk State Mode Select Errors 0 fscsi0/hdisk3 OPEN NORMAL 28024 0 1 fscsi1/hdisk6 OPEN NORMAL 28847 0 DEV#: 2 DEVICE NAME: vpath2 TYPE: 2107900 POLICY: Optimized SERIAL: 75BAFX10329 ========================================================================== Path# Adapter/Hard Disk State Mode Select Errors 0 fscsi0/hdisk4 OPEN NORMAL 21672 0 1 fscsi1/hdisk7 OPEN NORMAL 21712 0 # lsattr -El vpath0 active_hdisk hdisk2/75BAFX1006C/fscsi0 active_hdisk hdisk5/75BAFX1006C/fscsi1 policy df pvid 00c49e8c94c02c150000000000000000 serial_number 75BAFX1006C
Active hdisk Active hdisk Scheduling Policy Physical volume identifier LUN serial number
# lsdev -Cc adapter ent0 Available 04-08 10/100/1000 Base-TX PCI-X Adapter (14106902) ent1 Available 06-08 10/100/1000 Base-TX PCI-X Adapter (14106902) fcs0 Available 05-08 FC Adapter
False False True False False
fcs1 Available 07-08 FC Adapter sa0 Available LPAR Virtual Serial Adapter sisscsia0 Available 03-08 PCI-X Ultra320 SCSI Adapter # lsattr -El fcs0 bus_intr_lvl 131193 bus_io_addr 0xcfc00 bus_mem_addr 0xc0040000 init_link al intr_priority 3 lg_term_dma 0x800000 max_xfer_size 0x100000 num_cmd_elems 200 pref_alpa 0x1 sw_fc_class 2 # lscfg -lv fcs0 fcs0
Bus interrupt level False Bus I/O address False Bus memory address False INIT Link flags True Interrupt priority False Long term DMA True Maximum Transfer Size True Maximum number of COMMANDS to queue to the adapter True Preferred AL_PA True FC Class for Fabric True
U7879.001.DQDKCPR-P1-C2-T1
FC Adapter
Part Number.................03N6441 EC Level....................A Serial Number...............1D54508045 Manufacturer................001D Feature Code................280B FRU Number.................. 03N6441 Device Specific.(ZM)........3 Network Address.............10000000C94F91CD ROS Level and ID............0288193D Device Specific.(Z0)........1001206D Device Specific.(Z1)........00000000 Device Specific.(Z2)........00000000 Device Specific.(Z3)........03000909 Device Specific.(Z4)........FF801412 Device Specific.(Z5)........0288193D Device Specific.(Z6)........0683193D Device Specific.(Z7)........0783193D Device Specific.(Z8)........20000000C94F91CD Device Specific.(Z9)........TS1.90X13 Device Specific.(ZA)........T1D1.90X13 Device Specific.(ZB)........T2D1.90X13 Device Specific.(YL)........U7879.001.DQDKCPR-P1-C2-T1 # lsdev -Cc adapter -F 'name parent' ent0 pci4 ent1 pci6 fcs0 pci5 fcs1 pci7 sa0 sisscsia0 pci3 # lsdev -Cc disk -F 'name location' hdisk0 03-08-00-3,0 hdisk1 03-08-00-5,0 hdisk2 05-08-01 ------------------------>|
hdisk3 hdisk4 hdisk5 hdisk6 hdisk7 vpath0 vpath1 vpath2
05-08-01 ------------------------>| 05-08-01 ------------------------>| 07-08-01 | 07-08-01 | 07-08-01 | | | | | | # lsdev -Cc driver -F 'name location' | dpo | fcnet0 05-08-02 | fcnet1 07-08-02 | fscsi0 05-08-01 > 8. Reboot. > > > If you can tell me how to make this procedure more nearly correct, I'd > greatly appreciate it. Note 2: ------thread Q + A: > > I need a quick refresher here. > ESS storage. SDD is installed. on > the fly, or does HA need to be I > can't quite remember if I have
I've got a HACMP (4.4) cluster with SAN- attached Can I add volumes to one of these volume groups down? It's been awhile since I have done this and to jump through any hoops. Thanks for the help.
Should be relatively easy with no downtime required. 1) acquire the new disks on primary node (where the VG is in service) with: cfgmgr -Svl fcs0 - repeat this for all fcs adapters in system 2) convert hdisks to vpaths, note use the smit screens for this because the commands have changed from version to version. 3) add vpaths to VG with: extendvg4vp vgname vpath# 4) create LVs/filesystems on the vpaths. 5) break VG/scsi locks so that other systems can see the disks with: varyonvg -b -u vgname 6) perform steps 1 & 2 for all failover nodes in the cluster. 7) refresh the VG definitions on all the failover nodes with: importvg -L vgname vpath# 8) reestablish disk locks on service node with: varyonvg vgname 9) add new filesystems to HA configuration. 10) synchronise HA resources to the cluster. Note 3: ------From IBM Doc SC30-4131-00: hd2vp and vp2hd SDD provides two conversion scripts, hd2vp and vp2hd. The hd2vp script converts a volume group from supported storage device hdisks to SDD vpath devices, and the vp2hd script converts a volume group from SDD vpath devices to supported storage device hdisks. Use the vp2hd program when you want to configure your applications back
to original supported storage device hdisks, or when you want to remove SDD from your AIX host system. The syntax for these conversion scripts is as follows: hd2vp vgname vp2hd vgname vgname Specifies the volume group name to be converted. Note 4: ------thread Q: Hi There, I want to add a vpath to running hacmp cluster with HACMP 5.1 on AIX 5.2 with Rotating Resource Group. If anyone has done it before then can provide a step by step procedure for this. Do i need to stop and start HACMP for this? A: On Vg active node : #extendvg4vp vg00 vpath10 vpath11 #smitty chfs ( Increase the f/s as required ) #varyonvg -bu vg00 ( this is to un-lock the vg) On Secondary node where vg is not active : # cfgmgr -vl fscsi0 ( fscsi1 and fcs0 and fcs1 ) Found new vpaths # chdev -l vpath10 -a pv=yes ( for vpath11 also ) # lsvg vg00|grep path ( just note down any one vpath which is from this o/p-for e.g vpath0 ) # importvg vg00 vpath0 Once its fine...go to Primary Node # varyonvg vg00 ( Locking the VG ) Regards Note 5: ------> HI, > Is there a way to know dependencies between devices. > For example, > hdisk2 is attached to fscsi0 which in turn is attached to fcs0 > I have found nothing in lsdev's man > Do I have to look in the odm directly
> I need this in order to improve a script This is a good question and the lsdev man page should be burned in front of the building where they develop and document AIX in Austin, TX, for not answering it for you. After all, you bothered to read the damn thing; why didn't it tell you? $ /usr/sbin/lsdev -Cc adapter -F 'name parent' ppa0 isa0 sa0 isa0 sa1 isa0 sa2 isa0 siokma0 isa0 fda0 isa0 scsi0 pci0 ent0 pci0 cxpa0 pci0 ent1 pci0 mga0 pci1 ent2 pci1 scsi1 pci2 sioka0 siokma0 sioma0 siokma0 ent3 pci0 There's also the lsparent command. Regards, Actually, I have the same question as Frederic and you have not quite answered it. Sure, lsdev can tell you that "hdisk5" is matched to "fcs0" . . . but what tells you that "fcs0" in turn matches to "fscsi0"? And if "hdisk126" matches to adapter "fchan1", how do I determine what that matches to? I've checked all of the various lsxxxx commands but can't find this bit of info. ONCE AGAIN the answer pops up just moments after announcing to the world that "there's no way to do that" and "I've looked everywhere and tried everything". Herewith the output from the necessary commands, with extraneous lines removed: # lsdev -C -c disk -F 'name location' hdisk0 11-08-00-2,0 hdisk1 11-08-00-4,0 hdisk2 3A-08-01 hdisk3 3A-08-01 hdisk4 27-08-01 hdisk5 27-08-01 # lsdev -C -c driver -F 'name location' fscsi0 27-08-01 fscsi1 3A-08-01 # lsdev -C -c adapter -F 'name location' scsi0 11-08
scsi1 11-09 fcs0 27-08 mg20 2D-08 fcs1 3A-08 # Obviously it is a simply matter to match disk to adapter to driver by the location of each object. After that I can easily sprintf(pathname, "/dev/%s", driver); fp = open(pathname, O_RDONLY | O_NDELAY); ioctl(fp, SCIOINQU, &info); to get the scsi inquiry buffer. Note 6: ------thread Q: where to fidnd a guide for the adapter (described blinkging/lighting)
all its states, LED
Adapter is cabled by SAN guys, they double checked it and when I run: rmdev -Rl fcs0 cfgmgr -l fcs0 lsattr -El fscsi0 -l attach I don't see "switch" but "none". thx in advance. A: Did you check SAN Switch Zoning? Regards, Do something like: rmdev -Rdl fscsi0 rmdev -dl fcnet0 rmdev -l fcs0 cfgmgr -l fcs0 rmdev -Rdl fscsi0 rmdev -Rdl fscsi1 rmdev -l fcs1 This way, the FC adapter re-negociates an FC fabric logon. HTH,
I had already done something similiar but it didn't helped: # lsslot -c slot|grep fcs0 U787B.001.DNWFFM5-P1-C4 Logical I/O Slot pci4 fcs0 # rmdev -dl pci4 -R fcnet0 deleted fscsi0 deleted fcs0 deleted pci4 deleted # cfgmgr Method error (/usr/lib/methods/cfgefscsi -l fscsi0 ): 0514-061 Cannot find a child device. # lsattr -El fscsi0 -a attach attach none How this adapter is CONNECTED False the second FC is connected ok: # lsattr -El fscsi1 -a attach attach switch How this adapter is CONNECTED False # thx anyway, I will ask my SAN team to check cables once more. Note 7: ------thread hdisk and vpath correspondance for IBM SAN (shark) Description Correspondance between phsical disks: 4 hdisk = 1 vpath = 1 physical disk To remove all vpaths run the command: # rmdev -dl dpo -R To remove all fibre channel disks (2 cards in this example): # rmdev -dl fscsi0 -R # rmdev -dl fscsi1 -R To recreate the hdisks run the command: # cfgmgr -vl fcs0 # cfgmgr -vl fcs1 To recreate the vpaths run the command: # cfallvpath To delete a device run this command: # rmdev -l fcs1 -d Example
rmdev -dl dpo -R ; rmdev -dl fscsi0 -R ; cfgmgr -vl fcs0 ; cfallvpath Note 8: ------Technote (FAQ) Problem When non-root AIX users issue SDD datapath commands, the "No device file found" message results. Cause AIX SDD does not distinguish between file not found and invalid permissions. Solution Login as the root user or "su" to root user and re-execute command in order to obtain the desired SDD datapath command output. Note 9: ------(thread ibm site) Question: Hi, I have an AIX 5.3 server running with 2 FCs. One on a DS8300 and one on a DS4300. On the server, i have a filesystems that is mounted and active (hdisks are from the DS8300). I can access it fine, write, delete etc... Yet, when i do a "datapath query adapter" i get the following : # datapath query adapter Active Adapters :1 Adpt# Name State Mode Select Errors Paths Active 0 fscsi0 NORMAL ACTIVE 4111177 0 32 0 I would expect to see my 32 paths Active. I checked another server that has a similar configuration (though it only has 1 FC) and i can see 32 Paths, 32 Active... Is it because of the other FC being connected to a DS4300? Answer: Hi. The reason is that the vpaths are not part of a varied on volume group. If you do a 'datapath query device' you should find all the paths will be state=closed. If the vpaths are being used by a volume group, do a varyonvg xxxx. Then display the datapath and the paths should be active.
Question: Hi. THanks, but as i mentionned in my original post, the VG is varied on and the FS is mounted. I ran the datapath command after i i varyonvg bkpvg and mount /backup. I then dumped a DB within the FS, deleted and everything else works...yet datapath query adapter shows no Active paths...weird... Question: Hi. What version of SDD? What does 'datapath query device' say? Answer: Version of SDD is 1.6.0.5 And a datapath query device shows : ... DEV#: 14 DEVICE NAME: vpath14 TYPE: 2107900 POLICY: Optimized SERIAL: 75AYYV111B7 =========================================================================== Path# Adapter/Hard Disk State Mode Select Errors 0 fscsi0/hdisk40 CLOSE NORMAL 147989 0 1 fscsi0/hdisk23 CLOSE NORMAL 0 0 DEV#: 15 DEVICE NAME: vpath15 TYPE: 2107900 POLICY: Optimized SERIAL: 75AYYV111B8 =========================================================================== Path# Adapter/Hard Disk State Mode Select Errors 0 fscsi0/hdisk41 CLOSE NORMAL 155256 0 1 fscsi0/hdisk24 CLOSE NORMAL 0 0 yet, as i mentionned, my FS /backup is mounted and accessible... Note 10: -------thread Q: Hi All, I am having problems on a p570 on which there are 3 HBA cards. 2 of the HBAs are connected via a SAN switch to an ESS 800. It appears only one of the "paths" to the ESS 800 is working As I only have one set of view of the disks on the ESS.
Running cfgmgr on the adapter gives the following error. I have tried removing fscsi0 then unconfiguring fcs0, Then reconfiguring fcs0 but I still get the same error. Any ideas? Is there some command/utility I can run to verify The state of ths HBA? Thank you. bash-3.00# cfgmgr -l fcs0 Method error (/usr/lib/methods/cfgefscsi -l fscsi0 ): 0514-061 Cannot find a child device. bash-3.00# 0514-061 Cannot find a child device A: HI I have had the same problem using HDS SAN devices. AT that time I did not have the corect version off the device driver for the fiber cards in P570. For aix 5.2 devices.pci.df1000fa >= 5.2.0.40 For aix 5.3 devices.pci.df1000f7 >= 5.3.0.10 /HGA Note 11: -------Greetings: The "0514-061 Cannot find a child device" is common when the FC card is either not attached to a FC device, or if it is attached, then I would look at the polarity of the cable ie. (tx -> rx and rx -> tx) NOT (tx -> tx and rx -> rx) cfgmgr is attempting to configure the FC device it is connected to (child device) but is unable to see it. In this context, device would be some sort of FC endpoint, not just a switch or director. I would make sure the FC card has connectivity to a FC device, not just the fabric and re-run cfgmgr. -=Patrick="Vincent D'Antonio, III" on 02/19/2003 01:51:24 PM Please respond to IBM AIX Discussion List
To:
[email protected] cc: (bcc: Patrick Bigelbach/DSS) Subject Re: Cannot cfgmgr on a new FC Put in your OS cd in the cdrom drive and run: cfgmgr -vi /dev/cd0 this should load any filesets you need for the adapter if they are not already there. You should the adapter in lsdev -Cc adapter | grep fs. HTH Vince -----Original Message----From: IBM AIX Discussion List [mailto:
[email protected]] On Behalf Of Calderon, Linda Sent: Wednesday, February 19, 2003 10:12 AM To:
[email protected] Subject: Cannot cfgmgr on a new FC I am trying to connect a new HBA on a P660 to a switch for a SAN. This HBA has not been used previously, newly cabled etc. I issued the following commands and receive the following errors: * rmdev -Rdl fsc1 0514-519 The following device was not found in the customized device configuration database: name 'fcs1' * cfgmgr 0514-061 Cannot find a child device Looking for ideas as to root cause. Note 12: -------thread Q: Hi All AIXers, I am trying to add some vpath to Current Volume Group (which is on vpath)and i am getting this error Method Error (/usr/lib/methods/chgvpath): 0514-047 Cannot access a device 0516-1182 extendvg open failure on vpath3 0516-792 extendvg: Unable to estend a Volume Group Do anybody have any idea about this error. I never seen this error before. Thanks
A: James, If you're adding a vpath to a volume group that has other vpaths, you will need to use extendvg4vp instead of extendvg. Hope this helps! Note 13: -------On Vg active node : #extendvg4vp vg00 vpath10 vpath11 #smitty chfs ( Increase the f/s as required ) #varyonvg -bu vg00 ( this is to un-lock the vg) On Secondary node where vg is not active : # cfgmgr -vl fscsi0 ( fscsi1 and fcs0 and fcs1 ) Found new vpaths # chdev -l vpath10 -a pv=yes ( for vpath11 also ) # lsvg vg00|grep path ( just note down any one vpath which is from this o/p-for e.g vpath0 ) # importvg vg00 vpath0 Once its fine...go to Primary Node # varyonvg vg00 ( Locking the VG ) Regards Note 14: -------thread How to add a a new PV into an existing concurrent mounted VG. The PMR action plan suggests: -
stop of the resource group varyoffvg dummyvg varyonvg -nc dummyvg extendvg4vp dummyvg vpath0 start of the resource group
as a backup action - restart of the cluster - extendvg4vp dummyvg vpath0 - start of the resource group After a spech with the Country IBM referent we modify the action plan in:
- stop of the cluster - varyoffvg dummyvg - varyonvg dummyvg dummyvg should remain Enhanced Concurrent Capable, but I mount it in normal mode to do the extentions - extendvg4vp dummyvg vpath0 - importvg -L dummyvg disk on the other node of the cluster - varyoffvg dummyvg - cluster verification & syncro - start of the cluster Anyway before applying original one, but with works, with someothers with others return the
the modified action plan I try to follow the unpredictable return codes. With some vpaths halfworks (update the VGDA, but not the odm), original error.
In my opinion there is an high probability that the cause is in gsclvmd... So, a bit disappointed, I applied the modified plan. All works and the extendvg4vp enlarged the dummyvg... My machines are too downlevel and very full of lacks :-( After that my curiosity pulls me to try the next step: mirrorvg -s -c 2 dummyvg vpath0 vpath1 0516-1509 : VGDA corruption: physical partition info for this LV is invalid. 0516-842 : Unable to make logical partition copies for logical volume. 0516-1199 mirrorvg: Failed to create logical partition copies for logical volume dummylv. 0516-1200 mirrorvg: Failed to mirror the volume group Now, IBM support is working for analyze this new issue...... Regards. Note 15: cfgmgr method errors: -----------------------------1: == APAR status Closed as program error. Error description Users of the 64bit kernel may observe an error when cfgmgr is invoked at runtime in the cfgsisscsi or cfgsisioa config methods. Following is an example: # cfgmgr Method error (/usr/lib/methods/cfgsisscsi -l sisscsia0 ): 0514-061 Cannot find a child device. The error occurs in the cfgsisscsi or cfgsisioa routines
which automatically update the microcode on the adapter if it is found to be at a level lower than the minimum supported microcode level. If the adapter was previously unconfigured, the adapter will remain in the Defined state. A system reboot should make it Available. APAR information APAR number IY48873 Reported component name AIX 5L POWER V5 Reported component ID 5765E6200 Reported release 520 Status CLOSED PER PE NoPE HIPER NoHIPER Submitted date 2003-09-19 Closed date 2003-09-19 Last modified date 2003-10-24 Note 16: cfgmgr method errors: -----------------------------Q: cfgmgr error-- devices are reported twice Asked by kuntal_acharyy... on 11/28/2005 6:15:00 AM I have an IBM DS4400 with two EXP 700s expansion units connected to a pSeries 650 with AIX 5.1.I have created two logical drives in the storage unit.When i run "cfgmgr" to recognise the new raw physical volume each disk is reported twice. hdisk4 hdisk5 hdisk6 hdisk7
Available Available Available Available
1n-08-01 1n-08-01 11-08-01 11-08-01
1742 1742 1742 1742
(700) (700) (700) (700)
Disk Disk Disk Disk
Array Array Array Array
Device Device Device Device
There is an error message while running cfgmgr: Method error (/etc/methods/cfgfdar -l dar0 ): 0514-002 Cannot initialize the ODM. cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed. devices.scsi What may have cause the problem ? How ca I solve this problem? Any advice is truly welcome. A: hi, I had met the same problem just as yours. 3 LPARs(AIX 5300-02) on a p570 connect FastT600(Ds4300) with 2 HBA cards each, using SAN fibre switch. 2 of the LPARs reported hdisk twice, and 1 of them
reported normally. And I found that the HBA cards on the normal one are in the PCI Slots belong to different BUSs, and the HBA cards on unnormal ones are in the same BUSs. Then I changed HBA cards to different BUSs' slots, deleted all the dar dac and HBA cards in the system, and cfgmgr at last. The problem got solved. I guess there must be some thing wrong with the BUS design. Some one told me that he solved the problem by install the last patch (AIX 5300-03). So my advice is that you should chang the HBA cards to differet slots, clear the system and cfgmgr. Or maybe update your AIX with the last patch. Just try and tell me the result. Good luck! Note 17: cfgmgr method errors:
[email protected] (Ed) wrote in message news:... > I deleted a scsi device from my 4.3.3 configuration with the following > command: > rmdev -l scsi2 -dR > > The device is a dual channel ultra scsi 3 card. I deleted it to try > to resolve some performance problems with a drawer connected to the > device. Incidentally, scsi3 which is the other side of the dual > channel card, is working fine. > > When I try to reconfigure the device with: > cfgmgr -v -lscsi2 > > I get the following error: > > Method error (/usr/lib/methods/cfgncr_scsi -l scsi2 ): > 0514-034 The following attributes do not have valid values: > > Any thoughts on how to fix it? For the timebeing I can't reboot the > machine. Would a reboot be able to resolve the problem if there is no > other solution? > > Thanks! > -- Ed #>> Ed, what you probably should do is run the cfgmgr comand without the device name behind it. Because you deleted the scsi device with the options -dR you also removed any child devices. try this: cfgmgr -v Note 18: cfgmgr method errors: ------------------------------
Q: Hi... Does someone know what to do with an SDD driver which can't detect vpaths from an ESS F20 but hdisks are already available on AIX? showvpath, cfgvpath, datapath query commands don't display or found anything By the way, rebooting the system didn't help I accept any suggestions. Regards Luis A. Rojas A: Thank you all for your suggestions I solve the problem using the hd2vp command which converts the logical hdisk to its related vpath. And Wal? !.. vpaths suddenly were recognized by cfgvpath command. I don't know why this happened, but, everything is OK now. To those people with similar problems, please check these following commands: dpovgfix, hd2vp, vp2hd Best Regards
Note 19: fget_config: --------------------how to show the current state and volume (hdisk) ownership in a IBM DS4000 Description The fget_config command shows the current state and volume (hdisk) ownership. To display controllers and hdisks that are associated with a specified DS4000 (dar): # fget_config To display the state of each controller in a DS4000 array, and the current path that is being used for I/O for each hdisk: # fget_config -A Example fget_config -A
Note 20: -------Q: dpovgfix, hd2vp, vp2hd Asked by RandallGoff on 1/23/2007 9:38:00 AM What filesets do dpovgfix, hd2vp and vp2hd belong to. I installed my sdd driver and can see everything but can't find these commands. A: They are part of your SDD drivers. You probably installed the devices.xxx filesets. Did you also install the host attachment script... the ibm2105 filesets? Note 21: -------thread Q: Hi I have several AIX LPARS running on SVC controlled disks. Right now i have SDD SW 1.6.1.2. After configuration i have some vpath devices that can be managed using the datapath command. Now in a recent training of SVC i was asked to install the new SDDPCM driver in order to get some of the benefits of this SW driver. SDDPCM does not use the concept of vpath anymore, instead a hdisk device object is created. This object has definitions and attributes in ODM files. Recently i had to change a faulty HBA under SDD drivers. I was able to: 1- datapath query device: in order to check hdisk devices belonging to the faulty adaptr. 2- datapath query adapter: in order to check the faulty adapter. 3- datapath set adapter XX offline: in order to put the faulty HAB offline. 4- datapath remove adapter XX 5- Used the diag Hot Plug option to remove the PCI-x HBA and install a new one. Configured the system and modified the corresponden zone. How to do the same with SDDPCM even when there's no concept of vpath anymore. Thanks in advanced A: Hello , You can do the same with sddpcm , either using the MPIO commands or smitty screens , smitty devices ---> MPIO devices there you can list paths , remove paths , adapters.
IN the SDD user guide there is a complete section describing what you can do , but same functions you use for the vpath , you can use for sddpcm. Here is the link for the latest user guide http://www-1.ibm.com/support/docview.wss?rsP3&con text=ST52G7&dc=DA490&dc=DA4A30&dc=DA480&dc=D700&dc =DA410&dc=DA4A20&dc=DA460&dc=DA470&dc=DA400&uid=ss g1 S7000303&loc=en_US&cs=utf8&lang=en Note 22: -------thread Q: Greetings: Has anyone encountered the 0516-1182 ( mkvg: Open Failure on vpath ) or 0516-826 ( mkvg: Unable to create volume group ) errors while trying to create a new volume group ? I attempted to create a new volume group using a couple of newly added vpath devices and received those errors. Any help will be greatly appreciated. Thanks in advance. Jay. A: Hi If using vpath devices then you can confirm that you can open any given device by running: datapath query device and confirm there's no error in the HBA communications. Also you can review the errpt reports in order to look for VPATH OPEN messages. You can also use the lquerypr command in order to check for SCSI reservations in the SAN box previously set by another host (in case of a cluster). Hope this helps Example lquerypr output # lquerypr -Vh /dev/hdisk12 connection type: fscsi1 open dev: /dev/hdisk12
Attempt to read reservation key... Attempt to read registration keys... Read Keys parameter Generation : 52 Additional Length: 32 Key0 : c8ca9d09 Key1 : c8ca9d09 Key2 : c8cabd09 Key3 : c8cabd09 Reserve Key provided by current host = c8cabd09 Not reserved.
Note 23: -------thread Q: All, I'm in the process of preparing for our upcoming disaster recovery exercise which is happening in a few weeks. Our plan is to create one big volume group, instead of a bunch of little ones like we have in our production environment, to try and save some time. My question is, is there a way to script using a for/next loop to assign each hdisk/vpath when creating a new volume group instead of going into smit and assigning them one by one by hand? The hdisks will be sequential and will probably be over a hundred in number so you can imagine how tedious this will be. Also, this will need to be bigvg enabled. Any of you scripters out there have any suggestions? Thanks for your help in advance! A: Create the VG >mkvg -B -y datavg vpathN Extend it for i in `lspv | grep vpath | grep None | awk '{print #1}'` do extendvg datavg $i done That would assign all unused vpaths to the VG. BTW Use the vpath and not the hdisk. You could add a count into it to limit the number of disks you assign. Note 24:
-------thread Q: Is anyone aware of a problem if i do a cfgmgr -vl dp0 and once the vpaths are made it shows as vpathxx none None and then i add the vpath to VG #extendvg VGname vpathxx Does this create a problem ? A: it sound like the vpath is showing correctly after cfgmgr so thats OK. But you need to use extendvg4vp and not just extendvg Do a 'smitty vg' and choose 'Add a Data Path Volume to a Volume Group' Once its added to a VG then it will show more info in lspv
Note 25: cfgmgr Method error (/usr/sbin/fcppcmmap > /etc/essmap.out): --------------------------------------------------------------------Method error (/usr/sbin/fcppcmmap > /etc/essmap.out): 0514-001 System error:
Note 26: mkpath, lspath commands: --------------------------------Examples mkpath: --To define and configure an already defined path between scsi0 and the hdisk1 device at SCSI ID 5 and LUN 0 (i.e., connection 5,0), enter: # mkpath -l hdisk1 -p scsi0 -w 5,0 The system displays a message similar to the following: path available --To configure an already defined path from 'fscsi0' to fiber channel disk 'hdisk1', the command would be: # mkpath -l hdisk1 -p fscsi0
The message would look similar to: path available --To only add to the Customized Paths object class a path definition between scsi0 and the hdisk1 disk device at SCSI ID 5 and LUN 0, enter: # mkpath -d -l hdisk1 -p scsi0 -w 5,0 The system displays a message similar to the following: path defined Examples lspath: lspath displays information about paths to an MultiPath I/O (MPIO) capable device. Examples of displaying path status: -- To display the status of all paths to hdisk1 with column headers, enter: # lspath -H -l hdisk1 The system will display a message similar to the following: status device parent enabled hdisk1 scsi0 disabled hdisk1 scsi1 missing hdisk1 scsi2 -- To display, without column headers, the set of paths whose operational status is disabled, enter: # lspath -s disabled The system will display a message similar to the following: disabled hdisk1 scsi1 disabled hdisk2 scsi1 disabled hdisk23 scsi8 disabled hdisk25 scsi8 --To display the set of paths whose operational status is failed, enter: # lspath -s failed The system will display a message similar to the following: failed hdisk1 scsi1 failed hdisk2 scsi1 failed hdisk23 scsi8 failed hdisk25 scsi8 -- To display in a user-specified format, without column headers, the set of paths to hdisk1 whose path status is available enter: # lspath -l hdisk1 -s available -F"connection:parent:path_status:status" The system will display a message similar to the following: 5,0:scsi0:available:enabled 6,0:scsi1:available:disabled Note that this output shows both the path status and the operational status of the device.
The path status simply indicates whether the path is configured or not. The operational status indicates how the path is being used with respect to path selection processing in the device driver. Only paths with a path status of available also have an operational status. If a path is not currently configured into the device driver, it does not have an operational status. Examples of displaying path attributes: --If the target device is a SCSI disk, to display all attributes for the path to parent scsi0 at connection 5,0, use the command: # lspath -AHE -l hdisk10 -p scsi0 -w "5,0" The system will display a message similar to the following: attribute value description user_settable weight 1 Order of path failover selection true Note 26: About FastT and DS Storage: -----------------------------------IBM TotalStorage� FAStT has been renamed IBM TotalStorage DS4000 series DS4100 formerly FAStT100 DS4300 formerly FAStT600 DS4300 Turbo formerly FAStT600 Turbo DS4400 formerly FAStT700 DS4500 formerly FAStT900 Note 27: from GPFS FAQ: ----------------------Q20: What's the difference between using an ESS with or without SDD or SDDPCM installed on the host? A20: The use of SDD or SDDPCM gives the AIX host the ability to access multiple paths to a single LUN within an ESS. This ability to access a single LUN on multiple paths allows for a higher degree of data availability in the event of a path failure. Data can continue to be accessed within the ESS as long as there is at least one available path. Without one of these installed, you will lose access to the LUN in the event of a path failure. However, your choice of whether to use SDD or SDDPCM impacts your ability to use single-node quourm: Single-node quorum is not supported if SDD is installed. Single-node quorum is support if SDDPCM is installed. To determine the GPFS disk support guidelines for SDD and SDDPCM for your cluster
type, see Q3: What disk support guidelines must be followed when running GPFS in an sp cluster type? Q6: What disk support guidelines must be followed when running GPFS in an rpd cluster type? Q9:What are the disk support guidelines that must be followed when running GPFS in an hacmp cluster type Note 28: changing attributes of a fcs0 device: ---------------------------------------------Examples: # chdev -l fscsi0 -a fc_err_recov=fast_fail # chdev -l fscsi0 -a dyntrk=yes Display attributes: # lsattr -El fscsi0 attach dyntrk fc_err_recov scsi_id sw_fc_class
switch no fast_fail 0x741113 3
How this adapter is CONNECTED False Dynamic Tracking of FC Devices True FC Fabric Event Error RECOVERY Policy True Adapter SCSI ID False FC Class for Fabric True
Note 29: Flash alerts: ---------------------IBM Flash Alert on AIX migration with vpaths: --------------------------------------------http://www1.ibm.com/support/docview.wss?rs=540&context=ST52G7&uid=ssg1S1002295&loc=en_US&cs= utf-8&lang=en All hdisks and vpath devices must be removed from host system before upgrading to SDD host attachment script 32.6.100.21 and above. All MPIO hdisks must be removed from host system before upgrading to SDDPCM host attachment script 33.6.100.9. Flash (Alert) Abstract When upgrading from SDDPCM host attachment script devices.fcp.disk.ibm2105.mpio.rte version 33.6.100.8 or below to 33.6.100.9, all SDDPCM MPIO hdisks must be removed from the AIX host system before the upgrade. When upgrading from SDD host attachment script ibm2105.rte version 32.6.100.18 or below to 32.6.100.21 or later, all AIX hdisks and SDD vpath devices must be removed from the AIX host system before the upgrade.
Content Please note that this document contains the following sections: Problem description, symptoms, and information SDD/host attachment upgrade procedures Recovery procedures should the ODM become corrupted Recovery procedures should the associations become corrupted Procedures for upgrading if rootvg is on an ESS disk - Problem description, symptoms, and information: Starting with SDDPCM host attachment script devices.fcp.disk.ibm2105.mpio.rte version 33.6.100.9 and SDD host attachment script ibm2105.rte version 32.6.100.21, ESS FCP devices are configured as "IBM MPIO FC 2105" for MPIO devices, and "IBM FC 2105" for ESS devices. This information can be seen in the "lsdev -Cc disk" output. Prior to these host attachment script versions, ESS FCP devices were configured as "IBM MPIO FC 2105XXX" for MPIO devices and "IBM FC 2105XXX" for ESS devices, where 'XXX' is the ESS device module, such as F20 or 800. If a host system is upgraded without removing all of the hdisks first, then the AIX host system ODM will be corrupted. Additionally, if all he hdisks are removed without removing all SDD vpath devices, then the associations between an SDD vpath device and its hdisks may be corrupted because the hdisk's device minor number may change after reconfiguration. The ODM corruption may look something like the following in the "lsdev -Cc disk" output: # lsdev -Cc disk lsdev: 0514-521 Cannot find information in the predefined configuration database for the customized device hdisk1. lsdev: 0514-521 Cannot find information in the predefined configuration database for the customized device hdisk2. lsdev: 0514-521 Cannot find information in the predefined configuration database for the customized device hdisk3. lsdev: 0514-521 Cannot find information in the predefined configuration database for the customized device hdisk4. lsdev: 0514-521 Cannot find information in the predefined configuration database for the customized device hdisk5. lsdev: 0514-521 Cannot find information in the predefined configuration database for the customized device hdisk6. lsdev: 0514-521 Cannot find information in the predefined configuration database for the customized device hdisk7. lsdev: 0514-521 Cannot find information in the predefined configuration database for the customized device hdisk8. hdisk0 Available 10-60-00-8,0 16 Bit SCSI Disk Drive hdisk1 Available 20-60-01 N/A hdisk2 Available 20-60-01 N/A hdisk3 Available 20-60-01 N/A hdisk4 Available 20-60-01 N/A hdisk5 Available 20-60-01 N/A hdisk6 Available 20-60-01 N/A
device device device device device device device device
hdisk7 Available 20-60-01 N/A hdisk8 Available 20-60-01 N/A - SDD/host attachment upgrade procedures: In order to prevent ODM corruption and vpath/hdisk association corruption, all hdisks and SDD vpath devices must be removed prior to the upgrade. The following procedure should be used when you want to upgrade: -
AIX OS only* Host attachment + AIX OS* SDD + AIX OS* Host attachment + SDD Host attachment only SDD + Host attachment + AIX OS*
* Upgrading the AIX OS will always require you to install the SDD which corresponds to the new AIX OS level. To upgrade SDD only, follow the procedure in the SDD User's Guide. 1. Ensure rootvg is on local scsi disks. If this is not possible, see "Procedures for upgrading if rootvg is on an ESS disk" below. 2. Stop all applications running on SDD Volume Groups/File Systems. 3. Unmount all File Systems of SDD volume group. 4. Varyoff all SDD volume groups. 5. If upgrading OS, save output of lspv command to remember pvids of VGs. 6. If upgrading OS, export volume groups with exportvg. 7. Remove SDD vpath devices with rmdev command. 8. Remove 2105 hdisk devices with rmdev command. 9. If upgrading OS, run 'stopsrc -s sddsrv' to stop sddsrv daemon. 10. If upgrading OS, uninstall SDD. 11. If required, upgrade ibm2105.rte. The recommended version is 32.6.100.18 if support for ESS model 750 is not needed. Version 32.6.100.21 is required to support ESS model 750. 12. If upgrading OS, migrate AIX OS level. 13. If OS upgraded, boot to new AIX level with no disk groups online except rootvg, which is on local scsi disks. /* reboot will automatically start at the end of migration */ 14. If OS upgraded, install SDD for the new OS level. Otherwise, if required, upgrade SDD. 15. If OS not upgraded, configure hdisks with the 'cfgmgr -vl fcsX' command. 16. Configure SDD vpath devices by running 'cfallvpath'. 17. If OS upgraded, use lspv command to find out one physical volume which has a pvid matching the previous SDD VG's pv. Example: =================================================== Previous lspv output (from step 4): hdisk0 000bc67da3945d3c None hdisk1 000bc67d531c699f rootvg active hdisk2 none None hdisk3 none None hdisk4 none None hdisk5 none None
hdisk6 none None hdisk7 none None hdisk8 none None hdisk9 none None hdisk10 none None hdisk11 none None hdisk12 none None hdisk13 none None hdisk14 none None hdisk15 none None hdisk16 none None hdisk17 none None hdisk18 none None hdisk19 none None hdisk20 none None hdisk21 none None vpath0 000bc67d318fb8ea SDDVG0 vpath1 000bc67d318fde50 SDDVG1 vpath2 000bc67d318ffbb0 SDDVG2 vpath3 000bc67d319018f3 SDDVG3 vpath4 000bc67d319035b2 SDDVG4 Current lspv output (from this step): hdisk0 000bc67da3945d3c None hdisk1 000bc67d531c699f rootvg active hdisk2 000bc67d318fb8ea None hdisk3 000bc67d318fde50 None hdisk4 000bc67d318ffbb0 None hdisk5 000bc67d319018f3 None hdisk6 000bc67d319035b2 None hdisk7 000bc67d318fb8ea None hdisk8 000bc67d318fde50 None hdisk9 000bc67d318ffbb0 None hdisk10 000bc67d319018f3 None hdisk11 000bc67d319035b2 None hdisk12 000bc67d318fb8ea None hdisk13 000bc67d318fde50 None hdisk14 000bc67d318ffbb0 None hdisk15 000bc67d319018f3 None hdisk16 000bc67d319035b2 None hdisk17 000bc67d318fb8ea None hdisk18 000bc67d318fde50 None hdisk19 000bc67d318ffbb0 None hdisk20 000bc67d319018f3 None hdisk21 000bc67d319035b2 None vpath0 none None vpath1 none None vpath2 none None vpath3 none None vpath4 none None In this case, hdisk2, hdisk7, hdisk12, and hdisk17 from the current lspv output has the pvid which matches the pvid of SDDVG0 from the previous lspv output. So, use either hdisk2, hdisk7, hdisk12, or hdisk17 to import the volume group with the name SDDVG0 18. Run hd2vp on all SDD volume groups. 19. Vary on all SDD volume groups. 20. Mount all file system back.
- Recovery procedures should the ODM become corrupted: If the host system's ODM is already corrupted as a result of upgrading without removing the hdisks, please contact IBM Customer Support at 1-800-IBM-SERV to request a script to fix the corrupted ODM. - Recovery procedures should the associations become corrupted: If vpath/hdisk association corruption has occurred because hdisks were removed without removing SDD vpath devices, all SDD vpath devices must be removed and reconfigured in order to correct this corrupted association. - Procedures for upgrading if rootvg is on an ESS disk: If rootvg is on an ESS device and cannot be moved to local scsi disks, all hdisks cannot be removed prior to the upgrade. In this case, the following procedure should be used to upgrade the SDD host attachment script to version 32.6.100.21 or later: . Contact IBM Customer Support at 1-800-IBM-SERV to request a script to fix the corrupted ODM referenced above. . Without removing ESS hdisks, use smitty to upgrade the SDD host attachment script on the host system. . Immediately run the script to fix the corrupted ODM on the host system. . Run bosboot on the host system. . Reboot the host system so that the hdisks can be configured with the new ODM attributes. . Return to the "SDD/host attachment upgrade procedures" above and follow the appropriate upgrade steps now that the SDD host attachment script upgrade is complete. This issue only occurs when upgrading to devices.fcp.disk.ibm2105.mpio.rte version 33.6.100.9 and SDD host attachment script ibm2105.rte version 32.6.100.21 and above.
IBM Flash Alert: SDD 1.6.2.0 requires minimum AIX code levels; possible 0514-035 error: -------------------------------------------------------------------------------------Flash (Alert) Abstract SDD 1.6.2.0 requires minimum AIX code levels. Not upgrading to correct AIX version and level can result in 0514-035 error when attempting removal of dpo or vpath device Content Starting from SDD version 1.6.2.0, a unique ID attribute is added to SDD vpath devices, in order to support AIX5.3 VIO future features. AIX device configure methods have been changed in both AIX52 TL8 and
AIX53 TL4 for this support. Following are the requirements for this version of SDD with: AIX5.2 and AIX5.3: AIX52 TL8 & above with PTF U804193 (IY76991) AIX53 TL4 & above with PTF U804397 (IY76997) Please view 1.6.2.0 readme for further details If upgraded to SDD 1.6.2.0 and above without first upgrading AIX to the levels listed above the following error will be experienced when attempting to remove any vpath devices using the: # rmdev -dl dpo -R or the # rmdev -dl vpathX command. Method error (/usr/lib/methods/ucfgdevice): 0514-035 Cannot perform the requested function because of missing predefined information in the device configuration database. Solution: 1) Upgrade AIX to correct level and ptf, or 2) Contact SDD support at 1-800-IBM-SERV for steps to clean up ODM to allow for downgrading the SDD level from 1.6.2.0, if unable to upgrade AIX to a newer technology level.
Note 30: -------Suppose the following happens: # rmdev -dRl fcs0 fcnet0 deleted fscsi0 deleted fcs0 deleted # cfgmgr Method error (/usr/lib/methods/cfgefscsi -l fscsi0 ): 0514-061 Cannot find a child device. root@n5114l02:/root# adapter checked with several commands connection with san seems impossible. root@n5114l02:/root#lsattr -El fscsi0 attach none How this adapter is CONNECTED False dyntrk no Dynamic Tracking of FC Devices True fc_err_recov delayed_fail FC Fabric Event Error RECOVERY Policy True scsi_id Adapter SCSI ID False sw_fc_class 3 FC Class for Fabric True
Note 31: -------IY83872: AFTER CHVG -T, VG IS IN INCONSISTENT STATE A fix is available Obtain fix for this APAR
APAR status Closed as program error. Error description #--------------------------------------------------chvg -t renumber pvs that have pv numbers greater than maxpvs with the new factor. chvg -t is only updating the new pv_num in lvmrec and not updating the VGDA. chvg -t leaves the vg is inconsistent state and any changes to vg may get unpredictable results like a system crash. Local fix Problem summary #--------------------------------------------------chvg -t renumber pvs that have pv numbers greater than maxpvs with the new factor. chvg -t is only updating the new pv_num in lvmrec and not updating the VGDA. chvg -t leaves the vg is inconsistent state and any changes to vg may get unpredictable results like a system crash. Problem conclusion Fix chvg -t to update the VGDA with the new pv number. Add a check in hd_kextendlv to make sure that the pvol we are trying to access is not null. Temporary fix Comments APAR information APAR number IY83872 Reported component name AIX 5.3 Reported component ID 5765G0300 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER Submitted date 2006-04-11 Closed date 2006-04-11 Last modified date 2006-05-03 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Publications Referenced Fix information Fixed component name AIX 5.3 Fixed component ID 5765G0300
Applicable component levels R530 PSY U805071 UP06/05/03 I 1000
31.6 Other filesystem commands: =============================== df command: ----------df Command Purpose Reports information about space on file systems. This document describes the AIX� df command as well as the System V version of df. Syntax df [ [ -P ] | [ -I | -M | -i | -t | -v ] ] [ -k ] [ -m ] [ -g ] [ -s ] [FileSystem ... | File... ] Description The df command displays information about total space and available space on a file system. The FileSystem parameter specifies the name of the device on which the file system resides, the directory on which the file system is mounted, or the relative path name of a file system. The File parameter specifies a file or a directory that is not a mount point. If the File parameter is specified, the df command displays information for the file system on which the file or directory resides. If you do not specify the FileSystem or File parameter, the df command displays information for all currently mounted file systems. File system statistics are displayed in units of 512-byte blocks by default. The df command gets file system space statistics from the statfs system call. However, specifying the -s flag gets the statistics from the virtual file system (VFS) specific file system helper. If you do not specify arguments with the -s flag and the helper fails to get the statistics, the statfs system call statistics are used. Under certain exceptional conditions, such as when a file system is being modified while the df command is running, the statistics displayed by the df command might not be accurate. Note: Some remote file systems, such as the Network File System (NFS), do not provide
all the information that the df command needs. The df command prints blanks for statistics that the server does not provide. flags: -g Displays statistics in units of GB blocks. The output values for the file system statistics would be in floating point numbers as value of each unit in bytes is significantly high. -i Displays the number of free and used i-nodes for the file system; this output is the default when the specified file system is mounted. -I Displays information on the total number of blocks, the used space, the free space, the percentage of used space, and the mount point for the file system. -k Displays statistics in units of 1024-byte blocks. -m Displays statistics in units of MB blocks. The output values for the file system statistics would be in floating point numbers as value of each unit in bytes is significantly high. -M Displays the mount point information for the file system in the second column. -P Displays information on the file system in POSIX portable format. -s Gets file system statistics from the VFS specific file system helper instead of the statfs system call. Any arguments given when using the -s flag must be a JFS or Enhanced JFS filesystem mount point or device. The filesystem must also be listed in /etc/filesystems. -t Includes figures for total allocated space in the output. -v Displays all information for the specified file system. examples: To display information about all mounted file systems, enter: df If your system has the /, /usr, /site, and /usr/venus file systems mounted, the output from the df command resembles the following: Filesystem 512-blocks Free /dev/hd0 19368 9976 /dev/hd1 24212 4808 /dev/hd2 9744 9352 /dev/hd3 3868 3856
%Used 48% 80% 4% 0%
Iused 4714 5031 1900 986
%Iused 5% 19% 4% 0%
Mounted on / /usr /site /usr/venus
To display information about /test file system in 1024-byte blocks, enter: df -k /test Filesystem 1024 blocks Free %Used Iused %Iused Mounted on /dev/lv11 16384 15824 4% 18 1% /tmp/ravi1 This displays the file system statistics in 1024-byte disk blocks. To display information about /test file system in MB blocks, enter: df -m /test Filesystem MB blocks Free %Used Iused %Iused Mounted on /dev/lv11 16.00 15.46 4% 18 1% /tmp/ravi1 This displays file system statistics in MB disk blocks rounded off to nearest 2nd decimal digit.
To display information about the /test file system in GB blocks, enter: df -g /test Filesystem GB blocks Free %Used Iused %Iused Mounted on /dev/lv11 0.02 0.02 0% 18 1% /tmp/ravi1 This displays file system statistics in GB disk blocks rounded off to nearest 2nd decimal digit. To display available space on the file system in which your current directory resides, enter: cd/ df . The output from this command resembles the following: Device 512-blocks /dev/hd4 19368
free 9976
%used 48%
iused 4714
%iused 5%
Mounted on /
The defragfs command: --------------------defragfs Command Purpose Increases a file system's contiguous free space. Syntax defragfs [ -q | -r | -s] { Device | FileSystem } Description The defragfs command increases a file system's contiguous free space by reorganizing allocations to be contiguous rather than scattered across the disk. The file system to be defragmented can be specified with the Device variable, which is the path name of the logical volume (for example, /dev/hd4). It can also be specified with the FileSystem variable, which is the mount point in the /etc/filesystems file. The defragfs command is intended for fragmented and compressed file systems. However, you can use the defragfs command to increase contiguous free space in nonfragmented file systems. You must mount the file system read-write for this command to run successfully. Using the -q flag, the -r flag or the -s flag generates a fragmentation report. These flags do not alter the file system. The defragfs command is slow against a JFS2 file system with a snapshot due to the amount of data that must be copied into snapshot storage object. The defragfs command issues a warning message if there are snapshots. The snapshot command can be used to delete the snapshots and then used again to create a new snapshot after the defragfs command completes.
Flags -q Reports the current state of the file system. -r Reports the current state of the file system and the state that would result if the defragfs command is run without either the -q, -r or -s flag. -s Reports the fragmentation in the file system. This option causes defragfs to pass through meta data in the file system which may result in degraded performance. Output On a JFS filesystem, the definitions for the messages reported by the defragfs command are as follows: Number of free fragments The number of free fragments in the file system. Number of allocated fragments The number of allocated fragments in the file system. Number of free spaces shorter than a block The number of free spaces within the file system that are shorter than a block. A free space is a set of contiguous fragments that are not allocated. Number of free fragments in short free spaces The total number of fragments in all the short free spaces. A short free space is one that is shorter than a block. Number of fragments moved The total number of fragments moved. Number of logical blocks moved The total number of logical blocks moved. Number of allocation attempts The number of times free fragments were reallocated. Number of exact matches The number of times the fragments that are moved would fit exactly in some free space. Total number of fragments The total number of fragments in the file system. Number of fragments that may be migrated The number of fragments that may be moved during defragmentation. FileSystem filesystem is n percent fragmented Shows to what extent the file system is fragmented in percentage. On a JFS2 filesystem the definitions for the messages reported by the defragfs command are as follows: Total allocation groups The number of allocation groups in the file system. Allocation groups divide the space on a file system into chunks. Allocation groups allow JFS2 resource allocation policies to use well known methods for achieving good I/O performance. Allocation groups defragmented The number of allocation groups that were defragmented. Allocation groups skipped - entirely free The number of allocation groups that were skipped because they were entirely free. Allocation groups skipped - too few free blocks The number of allocation groups that were skipped because there were too few free blocks in them for reallocation. Allocation groups skipped - contains a large contiguous free space The number of allocation groups that were skipped because they contained a large contiguous free space which is not worth defragmenting. Allocation groups are candidates for defragmenting
The number of allocation groups that are fit for defragmenting. Average number of free runs in candidate allocation groups The average number of free runs per allocation group, for allocation groups that are found fit for defragmentation. A free run is a contiguous set of blocks which are not allocated. Total number of blocks The total number of blocks in the file system. Number of blocks that may be migrated The number of blocks that may be moved during defragmentation. FileSystem filesystem is n percent fragmented Shows to what extent the file system is fragmented in percentage. Examples: To defragment the /data1 file system located on the /dev/lv00 logical volume, enter: defragfs /data1 To defragment the /data1 file system by specifying its mount point, enter: defragfs /data1 To generate a report on the /data1 file system that indicates its current status as well as its status after being defragmented, enter: defragfs -r /data1 To generate a report on the fragmentation in the /data1 file system, enter: defragfs -s /data1 The fsck command: ----------------Purpose Checks file system consistency and interactively repairs the file system. Syntax fsck [ -n ] [ -p ] [ -y ] [ -dBlockNumber ] [ -f ] [ -ii-NodeNumber ] [ -o Options ] [ -tFile ] [ -V VfsName ] [ FileSystem1 - FileSystem2 ... ] Description Attention: Always run the fsck command on file systems after a system malfunction. Corrective actions may result in some loss of data. The default action for each consistency correction is to wait for the operator to enter yes or no. If you do not have write permission for an affected file system, the fsck command defaults to a no response in spite of your actual response. Notes: The fsck command does not make corrections to a mounted file system. The fsck command can be run on a mounted file system for reasons other than repairs. However, inaccurate error messages may be returned when the file system is mounted. The fsck command checks and interactively repairs inconsistent file systems. You should run this command
before mounting any file system. You must be able to read the device file on which the file system resides (for example, the /dev/hd0 device). Normally, the file system is consistent, and the fsck command merely reports on the number of files, used blocks, and free blocks in the file system. If the file system is inconsistent, the fsck command displays information about the inconsistencies found and prompts you for permission to repair them. The fsck command is conservative in its repair efforts and tries to avoid actions that might result in the loss of valid data. In certain cases, however, the fsck command recommends the destruction of a damaged file. If you do not allow the fsck command to perform the necessary repairs, an inconsistent file system may result. Mounting an inconsistent file system may result in a system crash. If a JFS2 file system has snapshots, the fsck command will attempt to preserve them. If this action fails, the snapshots cannot be guaranteed to contain all of the before-images from the snapped file system. The fsck command will delete the snapshots and the snapshot logical volumes. If you do not specify a file system with the FileSystem parameter, the fsck command checks all file systems listed in the /etc/filesystems file for which the check attribute is set to True. You can enable this type of checking by adding a line in the stanza, as follows: check=true You can also perform checks on multiple file systems by grouping the file systems in the /etc/filesystems file. To do so, change the check attribute in the /etc/filesystems file as follows: check=Number The Number parameter tells the fsck command which group contains a particular file system. File systems that use a common log device should be placed in the same group. File systems are checked, one at a time, in group order, and then in the order that they are listed in the /etc/filesystems file. All check=true file systems are in group 1. The fsck command attempts to check the root file system before any other file system regardless of the order specified on the command line or in the /etc/filesystems file. The fsck command checks for the following inconsistencies: -Blocks or fragments allocated to multiple files. -i-nodes containing block or fragment numbers that overlap. -i-nodes containing block or fragment numbers out of range. -Discrepancies between the number of directory references to a file and the link count of the file. -Illegally allocated blocks or fragments. -i-nodes containing block or fragment numbers that are marked free in the disk map. -i-nodes containing corrupt block or fragment numbers. -A fragment that is not the last disk address in an i-node. This check does not
apply to compressed file systems. -Files larger than 32KB containing a fragment. This check does not apply to compressed file systems. -Size checks: Incorrect number of blocks. Directory size not a multiple of 512 bytes. These checks do not apply to compressed file systems. -Directory checks: Directory entry containing an i-node number marked free in the i-node map. i-node number out of range. Dot (.) link missing or not pointing to itself. Dot dot (..) link missing or not pointing to the parent directory. Files that are not referenced or directories that are not reachable. -Inconsistent disk map. -Inconsistent i-node map. -Orphaned files and directories (those that cannot be reached) are, if you allow it, reconnected by placing them in the lost+found subdirectory in the root directory of the file system. The name assigned is the i-node number. If you do not allow the fsck command to reattach an orphaned file, it requests permission to destroy the file. In addition to its messages, the fsck command records the outcome of its checks and repairs through its exit value. This exit value can be any sum of the following conditions: 0 All checked file systems are now okay. 2 The fsck command was interrupted before it could complete checks or repairs. 4 The fsck command changed the file system; the user must restart the system immediately. 8 The file system contains unrepaired damage. When the system is booted from a disk, the boot process explicitly runs the fsck command, specified with the -f and -p flags on the /, /usr, /var, and /tmp file systems. If the fsck command is unsuccessful on any of these file systems, the system does not boot. Booting from removable media and performing maintenance work will then be required before such a system will boot. If the fsck command successfully runs on /, /usr, /var, and /tmp, normal system initialization continues. During normal system initialization, the fsck command specified with the -f and -p flags runs from the /etc/rc file. This command sequence checks all file systems in which the check attribute is set to True (check=true). If the fsck command executed from the /etc/rc file is unable to guarantee the consistency of any file system, system initialization continues. However, the mount of any inconsistent file systems may fail. A mount failure may cause incomplete system initialization. Note: By default, the /, /usr, /var, and /tmp file systems have the check attribute set to False (check=false) in their /etc/filesystem stanzas. The attribute is set to False for the following reasons: The boot process explicitly runs the fsck command on the /, /usr, /var, and /tmp
file systems. The /, /usr, /var, and /tmp file systems are mounted when the /etc/rc file is executed. The fsck command will not modify a mounted file system. Furthermore, the fsck command run on a mounted file system produces unreliable results. You can use the File Systems application in Web-based System Manager (wsm) to change file system characteristics. You could also use the System Management Interface Tool (SMIT) smit fsck fast path to run this command. Flags -dBlockNumber Searches for references to a specified disk block. Whenever the fsck command encounters a file that contains a specified block, it displays the i-node number and all path names that refer to it. For JFS2 filesystems, the i-node numbers referencing the specified block will be displayed but not their path names." -f Performs a fast check. Under normal circumstances, the only file systems likely to be affected by halting the system without shutting down properly are those that are mounted when the system stops. The -f flag prompts the fsck command not to check file systems that were unmounted successfully. The fsck command determines this by inspecting the s_fmod flag in the file system superblock. This flag is set whenever a file system is mounted and cleared when it is unmounted successfully. If a file system is unmounted successfully, it is unlikely to have any problems. Because most file systems are unmounted successfully, not checking those file systems can reduce the checking time. -ii-NodeNumber Searches for references to a specified i-node. Whenever the fsck command encounters a directory reference to a specified i-node, it displays the full path name of the reference. -n Assumes a no response to all questions asked by the fsck command; does not open the specified file system for writing. -o Options Passes comma-separated options to the fsck command. The following options are currently supported for JFS (these options are obsolete for newer file systems and can be ignored): mountable Causes the fsck command to exit with success, returning a value of 0, if the file system in question is mountable (clean). If the file system is not mountable, the fsck command exits returning with a value of 8. mytype Causes the fsck command to exit with success (0) if the file system in question is of the same type as either specified in the /etc/filesystems file or by the -V flag on the command line. Otherwise, 8 is returned. For example, fsck -o mytype -V jfs / exits with a value of 0 if / (the root file system) is a journaled file system. -p Does not display messages about minor problems but fixes them automatically. This flag does not grant the wholesale license that the -y flag does and is useful
for performing automatic checks when the system is started normally. You should use this flag as part of the system startup procedures, whenever the system is being run automatically. If the primary superblock is corrupt, the secondary superblock is verified and copied to the primary superblock. -tFile Specifies a File parameter as a scratch file on a file system other than the one being checked, if the fsck command cannot obtain enough memory to keep its tables. If you do not specify the -t flag and the fsck command needs a scratch file, it prompts you for the name of the scratch file. However, if you have specified the -p flag, the fsck command is unsuccessful. If the scratch file is not a special file, it is removed when the fsck command ends. -V VfsName Uses the description of the virtual file system specified by the VFSName variable for the file system instead of using the /etc/filesystems file to determine the description. If the -V VfsName flag is not specified on the command line, the /etc/filesystems file is checked and the vfs=Attribute of the matching stanza is assumed to be the correct file system type. -y Assumes a yes response to all questions asked by the fsck command. This flag lets the fsck command take any action it considers necessary. Use this flag only on severely damaged file systems. Examples To check all the default file systems, enter: fsck This command checks all the file systems marked check=true in the /etc/filesystems file. This form of the fsck command asks you for permission before making any changes to a file system. To fix minor problems with the default file systems automatically, enter: fsck -p To check a specific file system, enter: fsck /dev/hd1 This command checks the unmounted file system located on the /dev/hd1 device.
31.6 DESCRIPTOR AREA'S: ----------------------- 1. VOLUME GROUP DESCRIPTOR AREA, VGDA Global to the VG: The VGDA, located at the beginning of each physical volume, contains information that describes all the LV's and all the PV's that belong to the VG of which that PV is a member. The VGDA makes a VG selfdescribing. An AIX System can read the VGDA on a disk, and from that, can determine what PV's and LV's are part of this VG. There are one or two copies per disk. - 2. VOLUME GROUP STATUS AREA, VGSA Tracks the state of mirrorred copies. The VGSA contains state information about physical partitions and physical volumes.
For example, the VGSA knows if one PV in a VG is unavailable. Each PV has at least one VGDA/VGSA. The number of VGDA's contained on a single disk varies according to the number of disks in the VG. - 3. LOGICAL VOLUME CONTROL BLOCK, LVCB Contains LV attributes (policies, number of copies). The LVCB is located at the start of every LV. It contains information about the logical volume. You can however, use the mklv command with the -T option, to request that the LVCB will not be stored in the beginning of the LV. With Scalable VG's, LVCM info is no longer stored in the first user block of any LV. All relevant LVCM info is kept in the VGDA.
31.7 The lqueryvg command: -------------------------The lqueryvg command reads the VGDA from a specified disk in a VG. Example: # lqueryvg -p hdisk1 -At # lqueryvg -Atp hdisk0 -p: which PV -A: show all available information -t: show descriptive tags Example: #lqueryvg -Atp hdisk0 Max LVs: 256 PP Size: 25 Free PPs: 468 LV count: 20 PV count: 2 Total VGDAs: 3 Conc Allowed: 0 MAX PPs per PV 1016 MAX PVs: 32 Conc Autovaryo 0 Varied on Conc 0 Logical: 00c665ed00004c0000000112b7408848.1 00c665ed00004c0000000112b7408848.2 00c665ed00004c0000000112b7408848.3 00c665ed00004c0000000112b7408848.4 00c665ed00004c0000000112b7408848.5 00c665ed00004c0000000112b7408848.6 00c665ed00004c0000000112b7408848.7 00c665ed00004c0000000112b7408848.8 00c665ed00004c0000000112b7408848.9
hd5 1 hd6 1 hd8 1 hd4 1 hd2 1 hd9var 1 hd3 1 hd1 1 hd10opt 1
Physical: Total PPs: LTG size: HOT SPARE: AUTO SYNC: VG PERMISSION: SNAPSHOT VG: IS_PRIMARY VG: PSNFSTPP: VARYON MODE: VG Type: Max PPs:
00c665ed00004c0000000112b7408848.10 hd7 1 00c665ed00004c0000000112b7408848.11 hd7x 1 00c665ed00004c0000000112b7408848.12 beheerlv 1 00c665ed00004c0000000112b7408848.13 varperflv 1 00c665ed00004c0000000112b7408848.14 loglv00 1 00c665ed00004c0000000112b7408848.15 db2_server_v8 1 00c665ed00004c0000000112b7408848.16 db2_var_v8 1 00c665ed00004c0000000112b7408848.17 db2_admin_v8 1 00c665ed00004c0000000112b7408848.18 db2_adminlog_v8 1 00c665ed00004c0000000112b7408848.19 db2_dasscr_v8 1 00c665ed00004c0000000112b7408848.20 db2_Fixpak10 1 00c665edb74079bc 2 0 00c665edb7f2987a 1 0 1022 128 0 0 0 0 0 4352 0 0 32512
31.8 The lquerypv command: -------------------------------How do I find out what the maximum supported logical track group (LTG) size of my hard disk? You can use the lquerypv command with the -M flag. The output gives the LTG size in KB. For instance, the LTG size for hdisk0 in the following example is 256 KB. /usr/sbin/lquerypv -M hdisk0 256 -----run lquerypv -h core 6b0 to find the executable (probably man, but man may have called something else in the background) then run dbx path_/to_/executable core and run the subcommand
dbx> where and paste the stack output, should be able to find it from there. also paste the level of fileset you are on for the executable lslpp -w /path_/to_/executable -> this will give fileset_name lslpp -l fileset_name ------Wie l�sst sich ein Storage Lock auf einer SAN-Disk brechen? Endlich die ersehnte SAN-Disk bekommen und dann das, es l�sst sich keine Volume Group darauf anlegen. # mkvg -f vpath100 gibt einen I/O Error. Was tun? H�chstwahrscheinlich befindet sich noch ein Lock auf der SAN-Disk. Dies l�sst sich mit dem Befehl # lquerypv -ch /dev/vpath100 aufbrechen und die Volume Group kann angelegt werden. ------# lquerypv -h /dev/hdisk9 80 10 00000080 00001155 583CD4B0 00000000 00000000 # lquerypv 00000000 00000010 00000020 00000030 00000040 00000050 00000060 00000070 00000080 00000090 000000A0 000000B0 000000C0 000000D0 000000E0 000000F0
-h /dev/hdisk1 C9C2D4C1 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00C665ED B7F2987A 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
|...UX43 ls -l /dev|grep 43, 000b is 11 --> look for 43, 11 Date: Wed, 29 Dec 2004 11:06:27 +0000 To:
[email protected] Q: Subject Re: error concerning filesystem [Virus checked] Hi Holger, A small query...how did you arrive at this figure of 43 from the error code. The decimal value of B is 11 but I could not understand the 2*16.. can you please exp this....
A: The major/minor numbers (002B 000B) are in hex: hex abcd = a*16^3+b*16^2+c*16^1+d therefore hex 002B=0*16^3+0*16^2+2*16^1+11=2*16+11 Note 3: AIX superblock issues: ------------------------------- Hint 1 for AIX: -- --------------thread: Use this command in case the superblock is corrupted. This will restore the BACKUP COPY of the superblock to the CURRENT copy. # dd count=1 bs=4k skip=31 seek=1 if=/dev/hd4 of=/dev/hd4 # fsck /dev/hd4 2>&1 | tee /tmp/fsck.errors Note: fuser Identifies processes using a file or file system # fuser -u /dev/hd3 Sample output: /dev/hd3: 2964(root) 6615c(root) 8465(casado) 11290(bonner) -- Hint 2 for AIX: -- --------------http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix .howtos/doc/howto/HT_baseadmn_badmagnumber.htm Fixing a corrupted magic number in the file system superblock If the superblock of a file system is damaged, the file system cannot be accessed. You can fix a corrupted magic number in the file system superblock. Most damage to the superblock cannot be repaired. The following procedure describes how to repair a superblock in a JFS file system when the problem is caused by a corrupted magic number. If the primary superblock is corrupted in a JFS2 file system, use the fsck command to automatically copy the secondary superblock and repair the primary superblock. In the following scenario, assume /home/myfs is a JFS file system on the physical volume /dev/lv02. The information in this how-to was tested using AIX� 5.2. If you are using a different version or level of AIX, the results you obtain might vary significantly.
1. Unmount the /home/myfs file system, which you suspect might be damaged, using the following command: # umount /home/myfs 2. To confirm damage to the file system, run the fsck command against the file system. For example: # fsck -p /dev/lv02 If the problem is damage to the superblock, the fsck command returns one of the following messages: fsck: Not an AIXV5 file system OR Not a recognized filesystem type 3. With root authority, use the od command to display the superblock for the file system, as shown in the following example: # od -x -N 64 /dev/lv02 +0x1000 Where the -x flag displays output in hexadecimal format and the -N flag instructs the system to format no more than 64 input bytes from the offset parameter (+), which specifies the point in the file where the file output begins. The following is an example output: 0001000 0001010 0001020 0001030 0001040
1234 0001 3300 0000
0234 8000 0000 0001
0000 1000 000a 0000
0000 0000 0003 0200
0000 2f6c 0100 0000
4000 7633 0000 2000
0000 0000 2f28 0000
000a 6c76 0383 0000
In the preceding output, note the corrupted magic value at 0x1000 (1234 0234). If all defaults were taken when the file system was created, the magic number should be 0x43218765. If any defaults were overridden, the magic number should be 0x65872143. 4. Use the od command to check the secondary superblock for a correct magic number. An example command and its output follows: # od -x -N 64 /dev/lv02 +0x1f000 001f000 001f010 001f020 001f030 001f040
6587 0001 3300 0000
2143 8000 0000 0001
0000 1000 000a 0000
0000 0000 0003 0200
0000 2f6c 0100 0000
4000 7633 0000 2000
0000 0000 2f28 0000
000a 6c76 0383 0000
Note the correct magic value at 0x1f000. 5. Copy the secondary superblock to the primary superblock. An example command and output follows:
# dd count=1 bs=4k skip=31 seek=1 if=/dev/lv02 of=/dev/lv02 dd: 1+0 records in. dd: 1+0 records out. Use the fsck command to clean up inconsistent files caused by using the secondary superblock. For example: # fsck /dev/lv02 2>&1 | tee /tmp/fsck.errs For more information The fsck and od command descriptions in AIX 5L Version 5.3 Commands Reference, Volume 4 AIX Logical Volume Manager from A to Z: Introduction and Concepts, an IBM Redbook AIX Logical Volume Manager from A to Z: Troubleshooting and Commands, an IBM Redbook "Boot Problems" in Problem Solving and Troubleshooting in AIX 5L, an IBM Redbook
Note 4: Linux superblock issues: -------------------------------1. DAMAGED SUPERBLOCK If a filesystem check fails and returns the error message �Damaged Superblock� you're lost . . . . . . . or not ? Well, not really, the damaged �superblock� can be restored from a backup. There are several backups stored on the harddisk. But let me first have a go at explaining what a �superblock�is. A superblock is located at position 0 of every partition, contains vital information about the filesystem and is needed at a fielsystem check. The information stored in the superblock are about what sort of fiesystem is used, the I-Node counts, block counts, free blocks and I-Nodes, the numer of times the filesystem was mounted, date of the last filesystem check and the first I-Node where / is located. Thus, a damaged superblock means that the filesystem check will fail. Our luck is that there are backups of the superblock located on several positions and we can restore them with a simple command. The usual ( and only ) 294912. ( 8193 in many only on older systems, You can check this out
positions are: 8193, 32768, 98304, 163840, 229376 and cases 32768 is the most current position for the first backup ) and have a lot more info about a particular partition you
have on your HD by: CODE # dumpe2fs /dev/hda5 You will see that the primary superblock is located at position 0, and the first backup on position 32768. O.K. let�s get serious now, suppose you get a �Damaged Superblock� error message at filesystem check ( after a power failure ) and you get a root-prompt in a recovery console, then you give the command: CODE # e2fsck -b 32768 /dev/hda5 don�t try this on a mounted filesystem It will then check the filesystem with the information stored in that backup superblock and if the check was successful it will restore the backup to position 0. Now imagine the backup at position 32768 was damaged too . . . then you just try again with the backup stored at position 98304, and 163840, and 229376 etc. etc. until you find an undamaged backup ( there are five backups so if at least one of those five is okay it�s bingo ! ) So next time don�t panic . . just get the paper where you printed out this Tip and give the magic command CODE # e2fsck -b 32768 /dev/hda5
32.6 Undelete programs: ======================= Note 1: AIX and JFS ------------------/***************************************************************************** * rsb.c - Read Super Block. Allows a jfs superblock to be dumped, inode * table to be listed or specific inodes data pointers to be chased and * dumped to standard out (undelete). * * Phil Gibbs - Trinem Consulting (
[email protected]) ****************************************************************************/ #include #include #include #include #include #include #include #include
#define FOUR_MB #define THIRTY_TWO_KB extern extern extern extern
(1024*1024*4) (1024*32)
int optind; int Optopt; int Opterr; char *optarg;
void PrintSep() { int k=80; while (k) { putchar('-'); k--; } putchar('\n'); } char *UserName(uid_t uid) { char replystr[10]; struct passwd *res; res=getpwuid(uid); if (res->pw_name[0]) { return res->pw_name; } else { sprintf(replystr,"%d",uid); return replystr; } } char *GroupName(gid_t gid) { struct group *res; res=getgrgid(gid); return res->gr_name; } ulong NumberOfInodes(struct superblock *sb) { ulong MaxInodes; ulong TotalFrags; if (sb->s_version==fsv3pvers) { TotalFrags=(sb->s_fsize*512)/sb->s_fragsize; MaxInodes=(TotalFrags/sb->s_agsize)*sb->s_iagsize; } else {
MaxInodes=(sb->s_fsize*512)/sb->s_bsize; } return MaxInodes; } void AnalyseSuperBlock(struct superblock *sb) { ulong TotalFrags; PrintSep(); printf("SuperBlock Details:\n-------------------\n"); printf("File system size: %ld x 512 bytes (%ld Mb)\n", sb->s_fsize, (sb->s_fsize*512)/(1024*1024)); printf("Block size: %d bytes\n",sb->s_bsize); printf("Flags: "); switch (sb->s_fmod) { case (char)FM_CLEAN: break; case (char)FM_MOUNT: printf("mounted "); break; case (char)FM_MDIRTY: printf("mounted dirty "); break; case (char)FM_LOGREDO: printf("log redo failed "); break; default: printf("Unknown flag "); break; } if (sb->s_ronly) printf("(read-only)"); printf("\n"); printf("Last SB update at: %s",ctime(&(sb->s_time))); printf("Version: %s\n", sb->s_version?"1 - fsv3pvers":"0 - fsv3vers"); printf("\n"); if (sb->s_version==fsv3pvers) { TotalFrags=(sb->s_fsize*512)/sb->s_fragsize; printf("Fragment size: %5d ",sb->s_fragsize); printf("inodes per alloc: %8d\n",sb->s_iagsize); printf("Frags per alloc: %5d ",sb->s_agsize); printf("Total Fragments: %8d\n",TotalFrags); printf("Total Alloc Grps: %5d ", TotalFrags/sb->s_agsize); printf("Max inodes: %8ld\n",NumberOfInodes(sb)); } else { printf("Total Alloc Grps: %5d ", (sb->s_fsize*512)/sb->s_agsize); printf("inodes per alloc: %8d\n",sb->s_agsize); printf("Max inodes: %8ld\n",NumberOfInodes(sb)); }
PrintSep(); } void ReadInode( FILE *in, ulong StartInum, struct dinode *inode, ulong InodesPerAllocBlock, ulong AllocBlockSize) { off_t SeekPoint; long BlockNumber; int OffsetInBlock; static struct dinode I_NODES[PAGESIZE/DILENGTH]; ulong AllocBlock; ulong inum; static off_t LastSeekPoint=-1; AllocBlock=(StartInum/InodesPerAllocBlock); BlockNumber=(StartInum-(AllocBlock*InodesPerAllocBlock))/ (PAGESIZE/DILENGTH); OffsetInBlock=(StartInum-(AllocBlock*InodesPerAllocBlock))(BlockNumber*(PAGESIZE/DILENGTH)); SeekPoint=(AllocBlock)? (BlockNumber*PAGESIZE)+(AllocBlock*AllocBlockSize): (BlockNumber*PAGESIZE)+(INODES_B*PAGESIZE); if (SeekPoint!=LastSeekPoint) { sync(); fseek(in,SeekPoint,SEEK_SET); fread(I_NODES,PAGESIZE,1,in); LastSeekPoint=SeekPoint; } *inode=I_NODES[OffsetInBlock]; } void DumpInodeContents( FILE ulong ulong ulong ulong { struct dinode ulong char ulong int int ulong int ReadInode(
long inode, *in, InodesPerAllocBlock, AllocBlockSize, Mask, Multiplier) DiskInode; SeekPoint; Buffer[4096]; FileSize; k; BytesToRead; *DiskPointers; NumPtrs;
in, inode, &DiskInode, InodesPerAllocBlock, AllocBlockSize); FileSize=DiskInode.di_size;
if (FileSize>FOUR_MB) { /* Double indirect mapping */ } else if (FileSize>THIRTY_TWO_KB) { /* Indirect mapping */ SeekPoint=DiskInode.di_rindirect & Mask; SeekPoint=SeekPoint*Multiplier; DiskPointers=(ulong *)malloc(1024*sizeof(ulong)); fseek(in,SeekPoint,SEEK_SET); fread(DiskPointers,1024*sizeof(ulong),1,in); NumPtrs=1024; } else { /* Direct Mapping */ DiskPointers=&(DiskInode.di_rdaddr[0]); NumPtrs=8; } for (k=0;ksizeof(Buffer))?sizeof(Buffer):FileSize; fseek(in,SeekPoint,SEEK_SET); fread(Buffer,BytesToRead,1,in); FileSize=FileSize-BytesToRead; write(1,Buffer,BytesToRead);
} void DumpInodeList( ulong ulong ulong { long struct dinode struct tm
FILE *in, MaxInodes, InodesPerAllocBlock, AllocBlockSize) inode; DiskInode; *TimeStruct;
printf(" Inode Links User Group Size ModDate\n"); printf("-------- ----- -------- -------- --------------\n"); for (inode=0;inodetm_mday, TimeStruct->tm_mon, TimeStruct->tm_year+1900); }
}
} void ExitWithUsageMessage() { fprintf(stderr,"USAGE: rsb [-i inode] [-d] [-s] \n"); exit(1); } main(int argc,char **argv) { FILE *in; struct superblock SuperBlock; short Valid; long inode=0; struct dinode DiskInode; ulong AllocBlockSize; ulong InodesPerAllocBlock; ulong MaxInodes; ulong Mask; ulong Multiplier; int option; int DumpSuperBlockFlag=0; int DumpFlag=0; while ((option=getopt(argc,argv,"i:ds")) != EOF) { switch(option) { case 'i': /* Inode specified */ inode=atol(optarg); break; case 'd': /* Dump flag */ DumpFlag=1; break; case 's': /* List Superblock flag */ DumpSuperBlockFlag=1; break; default: break; } } if (strlen(argv[optind])) in=fopen(argv[optind],"r"); else ExitWithUsageMessage(); if (in)
{ fseek(in,SUPER_B*PAGESIZE,SEEK_SET); fread(&SuperBlock,sizeof(SuperBlock),1,in); switch (SuperBlock.s_version) { case fsv3pvers: Valid=!strncmp(SuperBlock.s_magic,fsv3pmagic,4); InodesPerAllocBlock=SuperBlock.s_iagsize; AllocBlockSize= SuperBlock.s_fragsize*SuperBlock.s_agsize; Multiplier=SuperBlock.s_fragsize; Mask=0x3ffffff; break; case fsv3vers: Valid=!strncmp(SuperBlock.s_magic,fsv3magic,4); InodesPerAllocBlock=SuperBlock.s_agsize; AllocBlockSize=SuperBlock.s_agsize*PAGESIZE; Multiplier=SuperBlock.s_bsize; Mask=0xfffffff; break; default: Valid=0; break; } if (Valid) { if (DumpSuperBlockFlag==1) { AnalyseSuperBlock(&SuperBlock); } MaxInodes=NumberOfInodes(&SuperBlock); if (DumpFlag==1) { if (inode) DumpInodeContents(inode,in,InodesPerAllocBlock,AllocBlockSize,Mask,Multiplier); else
}
DumpInodeList(in,MaxInodes,InodesPerAllocBlock,AllocBlockSize); } } else { fprintf(stderr,"Superblock - bad magic number\n"); exit(1); } } else { fprintf(stderr,"couldn't open "); perror(argv[optind]); exit(1); }
Note 2: Undelete a text file on most unixes (no garantee): ---------------------------------------------------------Works mainly on Linux Distro's Using grep (traditional UNIX way) to recover files Use following grep syntax: # grep -b �search-text� /dev/partition > file.txt OR # grep -a -B[size before] -A[size after] �text� /dev/[your_partition] > file.txt Where, -i : Ignore case distinctions in both the PATTERN and the input files i.e. match both uppercase and lowercase character. -a : Process a binary file as if it were text -B Print number lines/size of leading context before matching lines. -A: Print number lines/size of trailing context after matching lines. To recover text file starting with �nixCraft� word on /dev/sda1 you can try following command: # grep -i -a -B10 -A100 'nixCraft' /dev/sda1 > file.txt Next use vi to see file.txt. This method is ONLY useful if deleted file is text file. If you are using ext2 file system, try out recover command. . Note 3: ------For AIX there are undelete tools: http://www.compunix.com/ Note 4: lsof and Linux: ----------------------Bring back deleted files with lsof By Michael Stutz on November 16, 2006 (8:00:00 AM) Briefly, a file as it appears somewhere on a Linux filesystem is actually just a link to an inode, which contains all of the file's properties, such as permissions and ownership, as well as the addresses of the data blocks where the file's content is stored on disk. When you rm a file, you're removing the link that points to its inode, but not the inode itself; other processes (such as your audio player) might still have it open. It's only after they're through and all links are removed that an inode and the data blocks it pointed to are made available for writing. This delay is your key to a quick and happy recovery: if a process still has the file open, the data's there somewhere, even though according to the directory listing the file already appears to be gone. This is where the Linux process pseudo-filesystem, the /proc directory, comes into play. Every process on
the system has a directory here with its name on it, inside of which lies many things -including an fd ("file descriptor") subdirectory containing links to all files that the process has open. Even if a file has been removed from the filesystem, a copy of the data will be right here: /proc/process id/fd/file descriptor To know where to go, you need to get the id of the process that has the file open, and the file descriptor. These you get with lsof, whose name means "list open files." (It actually does a whole lot more than this and is so useful that almost every system has it installed. If yours isn't one of them, you can grab the latest version straight from its author.) Once you get that information from lsof, you can just copy the data out of /proc and call it a day. This whole thing is best demonstrated with a live example. First, create a text file that you can delete and then bring back: $ man lsof | col -b > myfile Then have a look at the contents of the file that you just created: $ less myfile You should see a plaintext version of lsof's huge man page looking out at you, courtesy of less. Now press Ctrl-Z to suspend less. Back at a shell prompt make sure your file is still there: $ ls -l myfile -rw-r--r-- 1 jimbo jimbo 114383 Oct 31 16:14 myfile $ stat myfile File: `myfile' Size: 114383 Blocks: 232 IO Block: 4096 regular file Device: 341h/833d Inode: 1276722 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1010/ jimbo) Gid: ( 1010/ jimbo) Access: 2006-10-31 16:15:08.423715488 -0400 Modify: 2006-10-31 16:14:52.684417746 -0400 Change: 2006-10-31 16:14:52.684417746 -0400 Yup, it's there all right. OK, go ahead and oops it: $ rm myfile $ ls -l myfile ls: myfile: No such file or directory $ stat myfile stat: cannot stat `myfile': No such file or directory $ It's gone. At this point, you must not allow the process still using the file to exit, because once that happens,
the file will really be gone and your troubles will intensify. Your background less process in this walkthrough isn't going anywhere (unless you kill the process or exit the shell), but if this were a video or sound file that you were playing, the first thing to do at the point where you realize you deleted the file would be to immediately pause the application playback, or otherwise freeze the process, so that it doesn't eventually stop playing the file and exit. Now to bring the file back. First see what lsof has to say about it: $ lsof | grep myfile less 4158 jimbo 4r REG 3,65 114383 1276722 /home/jimbo/myfile (deleted) The first column gives you the name of the command associated with the process, the second column is the process id, and the number in the fourth column is the file descriptor (the "r" means that it's a regular file). Now you know that process 4158 still has the file open, and you know the file descriptor, 4. That's everything you have to know to copy it out of /proc. You might think that using the -a flag with cp is the right thing to do here, since you're restoring the file -but it's actually important that you don't do that. Otherwise, instead of copying the literal data contained in the file, you'll be copying a now-broken symbolic link to the file as it once was listed in its original directory: $ ls -l /proc/4158/fd/4 lr-x------ 1 jimbo jimbo 64 Oct 31 16:18 /proc/4158/fd/4 -> /home/jimbo/myfile (deleted) $ cp -a /proc/4158/fd/4 myfile.wrong $ ls -l myfile.wrong lrwxr-xr-x 1 jimbo jimbo 24 Oct 31 16:22 myfile.wrong -> /home/jimbo/myfile (deleted) $ file myfile.wrong myfile.wrong: broken symbolic link to `/home/jimbo/myfile (deleted)' $ file /proc/4158/fd/4 /proc/4158/fd/4: broken symbolic link to `/home/jimbo/myfile (deleted)' So instead of all that, just a plain old cp will do the trick: $ cp /proc/4158/fd/4 myfile.saved And finally, verify that you've done good: $ ls -l myfile.saved -rw-r--r-- 1 jimbo jimbo 114383 Oct 31 16:25 myfile.saved $ man lsof | col -b > myfile.new $ cmp myfile.saved myfile.new No complaints from cmp -- your restoration is the real deal. Incidentally, there are a lot of useful things you can do with lsof in addition to rescuing lost files.
32.7 Some notes about disks on x86 systems: MBR and Partition Bootsector: ========================================================================= The following applies to PC's and x86 based Servers. There are two sectors on the disk that are critical to starting the computer: - Master Boot Record - Partition Boot Sector The MBR is created when you create the first partition on the harddisk. The location is always cylinder 0, head 0 and sector 1. The MBR contains the Partition Table for the disk and a small amount of executable code. On x86 machines, this executable code examines the Partition Table and identifies the system partition. The code then finds the system partition's starting location on the disk, and loads an copy of its Partition Boot Sector into memory. If you would take a look at the MBR, you would find: The first 446 bytes in the sector is the MBR. After that, you would see the Partition Table, a 64 byte structure. Each table entry is 16 bytes long, the first byte being the Boot Indicator field. This tells the code which partition is bootable. The Partition Boot Sector, has its own "layout" depending on the type of system. 32.8 How to get LUN ID's: ========================= # lscfg -vl hdiskx # lsattr -El hdiskx ZD110L05 600507680190014DC000000000000304 ZD110L08 600507680190014DC000000000000305 ZD111L05 600507680190014DC000000000000306 ZD111L08 600507680190014DC000000000000307
33. Filesystems in Linux: =========================
33.1 Disks: ----------Linux on x86 systems, have the following (storage) devices: -- Entire harddisks are listed as devices without numbers, such as "/dev/hda" or "/dev/sda". - IDE: /dev/hda /dev/hdb /dev/hdc /dev/hdd
is is is is
the the the the
primary IDE master drive, primary IDE slave drive, secondary IDE master, secondary IDE slave,
- SCSI: /dev/sda1 etc..
is the first SCSI interface and 1st device id number
-- Partitions on a disk are referred to with a number such as /dev/hda1 Floppydrive: /dev/fd0 # mount -t auto /dev/fd0 /mnt/floppy # mount -t vfat /dev/fd0 /mnt/floppy # mount /dev/fd0 /mnt/floppy Zipdrive: # insmod ppa # load the module # mount -t vfat /dev/sda /mnt/zip 33.2 Filesystems: ----------------Linux supports a huge number of filesystems, including FAT, JFS, NTFS etc.. But for the "native" filesystems, we take a look at the following FS's: - ReiserFS A journaled filesystem - Ext2 The most popular filesystem for years. But it does not use a log/jounal, so gradually it becomes less important. - Ext3 Very related to Ext2, but this one supports journaling. An Ext2 filesystem can easily be upgraded to Ext3. 33.3 Adding a disk in Linux: ----------------------------
Suppose you have SCSI card on with a disk is attached. The disk as a whole would be refferred to as "/dev/sda" and the first partition would be referred to as "/dev/sda1". But we have a new disk here. If you cannot find the device files /dev/sda in /dev, you might create it with the /dev/MAKEDEV script: # cd /dev # ./MAKEDEV sda The disk is now ready to be partitioned. In this example, we plan to create 3 partitions, including a swap partition. # fdisk /dev/sda The number of cylinders for this disk is set to .. (.. more output..) Command: The fdisk program is interactive; pressing m displays a list of all its commands. Command: new Command action e extended p primary partition (1-4): 1 (.. more output..) Command: print Device /dev/sda1
Boot
Start 1
End 255
Blocks 2048256
Id 83
System Linux
So we have created our first partition. We now create the swap partition: Command: new Command action e extended p primary partition (1-4): 2 (.. more output..) Command: type Partition number (1-4): 2 Hex code: 82 # which is a Linix swap partition Changed system type of partition 2 to 82 (Linux swap) The third partition can be created in a similar way. We now would like to see a listing of our partitions Command: print Device /dev/sda1 /dev/sda2 /dev/sda3
Boot
Start 1 256 512
End 255 511 5721
Now, save the label to the disk:
Blocks 2048256 2056320 41849325
Id 83 82 83
System Linux Swap Linux
Command: write (.. more output..) Ofcourse, we now would like to create the filesystems and the swap. If you want to use the Ext2 filesystem on partition one, use the following command: # mke2fs /dev/sda1 2048256
( or # mkfs -t ext2 -b 4096 /dev/sda1 )
Lets check the filesystem with fsck: # fsck -f /dev/sda1 A new filesystem can be mounted as soon as the mount point is created. # mkdir /bkroot # mount /dev/sda1 /bkroot Lets now create the swap space: # mkswap -c /dev/sda2 2056320 and activate it using the command: # swapon /dev/sda2 See also section 34.3 for administering swap space on Linux.
Notes about Linux and LVM: ========================== Note 1: ======= -What is RAID and LVM -Initial setup of a RAID-5 array -Initial setup of LVM on top of RAID -Handling a Drive Failure -Common Glitches -Other Useful Resources -Expanding an Array/Filesytem --------------------------------------------------------------------------------What is RAID and LVM RAID is usually defined as Redundant Array of Inexpensive disks. It is normally used to spread data among several physical hard drives with enough redundancy that should any drive fail the data will still be intact. Once created a RAID array appears to be one device which can be used pretty much like a regular partition. There are several kinds of RAID but I will only refer to the two most common here. The first is RAID-1 which is also known as mirroring. With RAID-1 it's basically
done with two essentially identical drives, each with a complete set of data. The second, the one I will mostly refer to in this guide is RAID-5 which is set up using three or more drives with the data spread in a way that any one drive failing will not result in data loss. The Red Hat website has a great overview of the RAID Levels. There is one limitation with Linux Software RAID that a /boot parition can only reside on a RAID-1 array. Linux supports both several hardware RAID devices but also software RAID which allows you to use any IDE or SCSI drives as the physical devices. In all cases I'll refer to software RAID. LVM stands for Logical Volume Manager and is a way of grouping drives and/or partition in a way where instead of dealing with hard and fast physical partitions the data is managed in a virtual basis where the virtual partitions can be resized. The Red Hat website has a great overview of the Logical Volume Manager. There is one limitation that a LVM cannot be used for the /boot. -------------------------------------------------------------------------------Initial set of a RAID-5 array I recommend you experiment with setting up and managing RAID and LVM systems before using it on an important filesystem. One way I was able to do it was to take old hard drive and create a bunch of partitions on it (8 or so should be enough) and try combining them into RAID arrays. In my testing I created two RAID-5 arrays each with 3 partitions. You can then manually fail and hot remove the partitions from the array and then add them back to see how the recovery process works. You'll get a warning about the partitions sharing a physical disc but you can ignore that since it's only for experimentation. In my case I have two systems with RAID arrays, one with two 73G SCSI drives running RAID-1 (mirroring) and my other test system is configured with three 120G IDE drives running RAID-5. In most cases I will refer to my RAID-5 configuration as that will be more typical. I have an extra IDE controller in my system to allow me to support the use of more than 4 IDE devices which caused a very odd drive assignment. The order doesn't seem to bother the Linux kernel so it doesn't bother me. My basic configuration is as follows: hda hdb hde hdf hdg
120G drive 120G drive 60G boot drive not on RAID array 120G drive CD-ROM drive
The first step is to create the physical partitions on each drive that will be
part of the RAID array. In my case I want to use each 120G drive in the array in it's entirety. All the drives are partitioned identically so for example, this is how hda is partitioned: Disk /dev/hda: 120.0 GB, 120034123776 bytes 16 heads, 63 sectors/track, 232581 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot /dev/hda1 *
Start 1
End 232581
Blocks 117220792+
Id fd
System Linux raid autodetect
So now with all three drives with a partitioned with id fd Linux raid autodetect you can go ahead and combine the paritions into a RAID array: # /sbin/mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 \ /dev/hdb1 /dev/hda1 /dev/hdf1 Wow, that was easy. That created a special device /dev/md0 which can be used instead of a physical parition. You can check on the status of that RAID array with the mdadm command: # /sbin/mdadm --detail /dev/md0 Version : 00.90.01 Creation Time : Wed May 11 20:00:18 2005 Raid Level : raid5 Array Size : 234436352 (223.58 GiB 240.06 GB) Device Size : 117218176 (111.79 GiB 120.03 GB) Raid Devices : 3 Total Devices : 3 Preferred Minor : 0 Persistence : Superblock is persistent Update Time State Active Devices Working Devices Failed Devices Spare Devices
: : : : : :
Fri Jun 10 04:13:11 2005 clean 3 3 0 0
Layout : left-symmetric Chunk Size : 64K UUID : 36161bdd:a9018a79:60e0757a:e27bb7ca Events : 0.10670 Number 0 1 2
Major 3 3 33
Minor 1 65 65
RaidDevice 0 1 2
State active sync active sync active sync
/dev/hda1 /dev/hdb1 /dev/hdf1
The important lines to see are the State line which should say clean otherwise there might be a problem. At the bottom you should make sure that the State column always says active sync which says each device is actively in the array. You could potentially have a spare device that's on-hand should any drive should fail.
If you have a spare you'll see it listed as such here. One thing you'll see above if you're paying attention is the fact that the size of the array is 240G but I have three 120G drives as part of the array. That's because the extra space is used as extra parity data that is needed to survive the failure of one of the drives. -------------------------------------------------------------------------------- Initial set of LVM on top of RAID Now that we have /dev/md0 device you can create a Logical Volume on top of it. Why would you want to do that? If I were to build an ext3 filesystem on top of the RAID device and someday wanted to increase it's capacity I wouldn't be able to do that without backing up the data, building a new RAID array and restoring my data. Using LVM allows me to expand (or contract) the size of the filesystem without disturbing the existing data. Anyway, here are the steps to then add this RAID array to the LVM system. The first command pvcreate will "initialize a disk or parition for use by LVM". The second command vgcreate will then create the Volume Group, in my case I called it lvm-raid: # pvcreate /dev/md0 # vgcreate lvm-raid /dev/md0 The default value for the physical extent size can be too low for a large RAID array. In those cases you'll need to specify the -s option with a larger than default physical extent size. The default is only 4MB as of the version in Fedora Core 5. For example, to successfully create a 550G RAID array a size of 2G works well: # vgcreate -s 2G Ok, you've created a blank receptacle but now you have to tell how many Physical Extents from the physical device (/dev/md0 in this case) will be allocated to this Volume Group. In my case I wanted all the data from /dev/md0 to be allocated to this Volume Group. If later I wanted to add additional space I would create a new RAID array and add that physical device to this Volume Group. To find out how many PEs are available to me use the vgdisplay command to find out how many are available and now I can create a Logical Volume using all (or some) of the space in the Volume Group. In my case I call the Logical Volume lvm0. # vgdisplay lvm-raid . . Free PE / Size
57235 / 223.57 GB
# lvcreate -l 57235 lvm-raid -n lvm0 In the end you will have a device you can use very much like a plain 'ol parition
called /dev/lvm-raid/lvm0. You can now check on the status of the Logical Volume with the lvdisplay command. The device can then be used to to create a filesystem on. # lvdisplay /dev/lvm-raid/lvm0 --- Logical volume --LV Name /dev/lvm-raid/lvm0 VG Name lvm-raid LV UUID FFX673-dGlX-tsEL-6UXl-1hLs-6b3Y-rkO9O2 LV Write Access read/write LV Status available # open 1 LV Size 223.57 GB Current LE 57235 Segments 1 Allocation inherit Read ahead sectors 0 Block device 253:2 # mkfs.ext3 /dev/lvm-raid/lvm0 . . # mount /dev/lvm-raid/lvm0 /mnt # df -h /mnt Filesystem Size Used Avail Use% Mounted on /dev/mapper/lvm--raid-lvm0 224G 93M 224G 1% /mnt -------------------------------------------------------------------------------- Handling a Drive Failure As everything eventually does break (some sooner than others) a drive in the array will fail. It is a very good idea to run smartd on all drives in your array (and probably ALL drives period) to be notified of a failure or a pending failure as soon as possible. You can also manually fail a partition, meaning to take it out of the RAID array, with the following command: # /sbin/mdadm /dev/md0 -f /dev/hdb1 mdadm: set /dev/hdb1 faulty in /dev/md0 Once the system has determined a drive has failed or is otherwise missing (you can shut down and pull out a drive and reboot to similate a drive failure or use the command to manually fail a drive above it will show something like this in mdadm: # /sbin/mdadm --detail /dev/md0 Update Time : Wed Jun 15 11:30:59 2005 State : clean, degraded Active Devices : 2 Working Devices : 2 Failed Devices : 1 Spare Devices : 0 .
. Number 0 1 2
Major 3 0 33
Minor 1 0 65
RaidDevice 0 2
State active sync removed active sync
/dev/hda1 /dev/hdf1
You'll notice in this case I had /dev/hdb fail. I replaced it with a new drive with the same capacity and was able to add it back to the array. The first step is to partition the new drive just like when first creating the array. Then you can simply add the partition back to the array and watch the status as the data is rebuilt onto the newly replace drive. # /sbin/mdadm /dev/md0 -a /dev/hdb1 # /sbin/mdadm --detail /dev/md0 Update Time : Wed Jun 15 12:11:23 2005 State : clean, degraded, recovering Active Devices : 2 Working Devices : 3 Failed Devices : 0 Spare Devices : 1 Layout : left-symmetric Chunk Size : 64K Rebuild Status : 2% complete . . During the rebuild process the system performance may be somewhat impacted but the data should remain in-tact. -------------------------------------------------------------------------------- Expanding an Array/Filesytem The answer to how to expand a RAID-5 array is very simple: You can't. I'm used to working with a NetApp Filer where you plug in a drive, type a simple command and that drive was added to the existing RAID array, no muss, no fuss. While you can't add space to a RAID5 array directly in Linux you CAN add space to an existing Logical Volume and then expand the ext3 filesytem on top of it. That's the main reason you want to run LVM on top of RAID. Before you start it's probably a good idea to back up your data just in case something goes wrong. Assuming you want your data to be protected from a drive failing you'll need to create another RAID array per the instructions above. In my case I called it /dev/md1 so after partitioning I can create the array: # /sbin/mdadm --create --verbose /dev/md1 --level=5 --raid-devices=3 \ /dev/hde1 /dev/hdg1 /dev/hdh1 # /sbin/mdadm --detail /dev/md1 The next couple steps will add the space from the new RAID array to the space available to be used by Logical Volumes. You then check to see how many Physical Extents you have and add them to the
Logical Volume you're using. Remember that since you can have multiple Logical Volumes on top of a physical RAID array you need to do this extra step. # vgextend lvm-raid /dev/md1 # vgdisplay lvm-raid . . . Alloc PE / Size 57235 / 223.57 GB Free PE / Size 57235 / 223.57 GB # lvextend -l 57235 lvm-raid -n lvm0 There, you now have a much larger Logical Volume which is using space on two separate RAID arrays. You're not done yet, you now have to extend your filesystem to make use of all that new space. Fortunately this is easy on FC4 and RHEL4 since there is a command to expand a ext3 filesytem without even unmounting it! Be patient, expanding the file system takes a while. # lvdisplay /dev/lvm-raid/lvm0 . . LV Size 447.14 GB . # df /raid-array Filesystem 1K-blocks Used /dev/mapper/lvm--raid-lvm0 230755476 40901348 # ext2online /dev/lvm-raid1/lvm0 447g Get yourself a sandwich # df /raid-array Filesystem 1K-blocks Used /dev/mapper/lvm--raid-lvm0 461510952 40901348
Available Use% Mounted on 178132400
19% /raid-array
Available Use% Mounted on 40887876
9% /raid-array
Congrats, you now have more space. Now go fill it with something.
Note 2: ======= Creating a LVM in Linux I am sure anybody who have used windows (2000 and above) have come across the term dynamic disks. Linux/Unix also have its own dynamic disk management called LVM. What is an LVM ? LVM stands for Logical Disk Manager which is the fundamental way to manage UNIX/Linux storage systems in a scalable manner. An LVM abstracts disk devices into pools of storage space called Volume Groups. These volume groups are in turn subdivided into virtual disks called Logical
Volumes. The logical volumes may be used just like regular disks with filesystem created on them and mounted in the Unix/Linux filesystem tree. The logical volumes can span multiple disks. Even though a lot of companies have implemented their own LVM's for *nixes, the one created by Open Software Foundation (OSF) was integrated into many Unix systems which serves as a base for the Linux implementation of LVM. Note: Sun Solaris ships with LVM from Veritas which is substantially different from the OSF implementation. Benefits of Logical Volume Management LVM created in conjunction with RAID can provide fault tolerance coupled with scalability and easy disk management. Create a logical volume and filesystem which spans multiple disks. By creating virtual pools of space, an administrator can create dozens of small filesystems for different projects and add space to them as needed without (much) disruption. When a project ends, he can remove the space a nd put it back into the pool of free space. Note : Before you move to implement LVM's in linux, make sure your kernel is 2.4 and above. Or else you will have to recompile your kernel from source to include support for LVM. LVM Creation To create a LVM, we follow a three step process. Step One : We need to select the physical storage resources that are going to be used for LVM. Typically, these are standard partitions but can also be Linux software RAID volumes that we've created. In LVM terminology, these storage resources are called "physical volumes" (eg: /dev/hda1, /dev/hda2 ... etc). Our first step in setting up LVM involves properly initializing these partitions so that they can be recognized by the LVM system. This involves setting the correct partition type (usually using the fdisk command, and entering the type of partition as 'Linux LVM' - 0x8e ) if we're adding a physical partition; and then running the pvcreate command. # pvcreate /dev/hda1 /dev/hda2 /dev/hda3 # pvscan The above step creates a physical volume from 3 partitions which I want to initialize for inclusion in a volume group. Step Two : Creating a volume group. You can think of a volume group as a pool of storage that consists of one or more physical volumes. While LVM is running, we can add physical volumes to the volume group or even remove them.
First initialize the /etc/lvmtab and /etc/lvmtab.d files by running the following command: # vgscan Now you can create a volume group and assign one or more physical volumes to the volume group. # vgcreate my_vol_grp /dev/hda1 /dev/hda2 Behind the scenes, the LVM system allocates storage in equal-sized "chunks", called extents. We can specify the particular extent size to use at volume group creation time. The size of an extent defaults to 4Mb, which is perfect for most uses.You can use the -s flag to change the size of the extent. The extent affects the minimum size of changes which can be made to a logical volume in the volume group, and the maximum size of logical and physical volumes in the volume group. A logical volume can contain at most 65534 extents, so the default extent size (4 MB) limits the volume to about 256 GB; a size of 1 TB would require extents of atleast 16 MB. So to accomodate a 1 TB size, the above command can be rewriten as : # vgcreate -s 16M my_vol_grp /dev/hda1 /dev/hda2 You can check the result of your work at this stage by entering the command: # vgdisplay This command displays the total physical extends in a volume group, size of each extent, the allocated size and so on. Step Three : This step involves the creation of one or more "logical volumes" using our volume group storage pool. The logical volumes are created from volume groups, and may have arbitary names. The size of the new volume may be requested in either extents (-l switch) or in KB, MB, GB or TB ( -L switch) rounding up to whole extents. # lvcreate -l 50 -n my_logical_vol my_vol_grp The above command allocates 50 extents of space in my_vol_grp to the newly created my_logical_vol. The -n switch specifies the name of the logical volume we are creating. Now you can check if you got the desired results by using the command : # lvdisplay which shows the information of your newly created logical volume. Once a logical volume is created, we can go ahead and put a filesystem on it, mount it, and start using the volume to store our files. For creating a filesystem, we do the following:
# mke2fs -j /dev/my_vol_grp/my_logical_vol The -j signifies journaling support for the ext3 filesystem we are creating. Mount the newly created file system : # mount /dev/my_vol_grp/my_logical_vol /data Also do not forget to append the corresponding line in the /etc/fstab file: #File: /etc/fstab /dev/my_vol_grp/my_logical_vol /data ext3 defaults 0 0 Now you can start using the newly created logical volume accessable at /data mount point. Next : Resizing Logical Volumes Some more on Linux LVM commands: Linux vgcreate command: ======================= Linux / Unix Command: vgcreate Command Library NAME vgcreate - create a volume group SYNOPSIS vgcreate [-A|--autobackup {y|n}] [-d|--debug] [-h|--help] [-l|--maxlogicalvolumes MaxLogicalVolumes] [-p|--maxphysicalvolumes MaxPhysicalVolumes] [-s|--physicalextentsize PhysicalExtentSize[kKmMgGtT]] [-v|--verbose] [--version] VolumeGroupName PhysicalVolumePath [PhysicalVolumePath...] DESCRIPTION vgcreate creates a new volume group called VolumeGroupName using the block special device PhysicalVolumePath previously configured for LVM with pvcreate(8). OPTIONS -A, --autobackup {y|n} Controls automatic backup of VG metadata after the change (see vgcfgbackup(8)). Default is yes. -d, --debug Enables additional debugging output (if compiled with DEBUG). -h, --help Print a usage message on standard output and exit successfully. -l, --maxlogicalvolumes MaxLogicalVolumes Sets the maximum possible logical volume count. More logical volumes can't be created in this volume group. Absolute maximum is 256. -p, --maxphysicalvolumes MaxPhysicalVolumes Sets the maximum possible physical volume count. More physical volumes can't be included in this volume group. Absolute maximum is 256. -s, --physicalextentsize PhysicalExtentSize[kKmMgGtT] Sets the physical extent size on physical volumes of this volume group. A size suffix
(k for kilobytes up to t for terabytes) is optional, megabytes is the default if no suffix is present. Values can be from 8 KB to 16 GB in powers of 2. The default of 4 MB causes maximum LV sizes of ~256GB because as many as ~64k extents are supported per LV. In case larger maximum LV sizes are needed (later), you need to set the PE size to a larger value as well. Later changes of the PE size in an existing VG are not supported. -v, --verbose Display verbose runtime information about vgcreate's activities. --version Display tool and IOP version and exit successfully. EXAMPLES To create a volume group named test_vg using physical volumes /dev/hdk1, /dev/hdl1, and /dev/hdm1 with default physical extent size of 4MB: # vgcreate test_vg /dev/sd[k-m]1 To create a volume group named test_vg using physical volumes /dev/hdk1, and /dev/hdl1 with default physical extent size of 4MB: # vgcreate test_vg /dev/sdk1 /dev/sdl1 NOTE: If you are using devfs it is essential to use the full devfs name of the device rather than the symlinked name in /dev. so: the above could be # vgcreate test_vg /dev/scsi/host1/bus0/target[1-3]/lun0/part1
Linux vgextend command: ======================= Linux / Unix Command: vgextend Command Library NAME vgextend - add physical volumes to a volume group SYNOPSIS vgextend [-A|--autobackup{y|n}] [-d|--debug] [-h|--help] [-v|--verbose] VolumeGroupName PhysicalVolumePath [PhysicalVolumePath...] DESCRIPTION vgextend allows you to add one or more initialized physical volumes ( see pvcreate(8) ) to an existing volume group to extend it in size. OPTIONS -A, --autobackup y/n
Controls automatic backup of VG metadata after the change ( see vgcfgbackup(8) ). Default is yes. -d, --debug Enables additional debugging output (if compiled with DEBUG). -h, --help Print a usage message on standard output and exit successfully. -v, --verbose Gives verbose runtime information about lvextend's activities. Examples # vgextend vg00 /dev/sda4 /dev/sdn1 tries to extend the existing volume group "vg00" by the new physical volumes (see pvcreate(8) ) "/dev/sdn1" and /dev/sda4". Linux pvcreate command: ======================= Linux / Unix Command: pvcreate Command Library NAME pvcreate - initialize a disk or partition for use by LVM SYNOPSIS pvcreate [-d|--debug] [-f[f]|--force [--force]] [-y|--yes] [-h|--help] [-v|-verbose] [-V|--version] PhysicalVolume [PhysicalVolume...] DESCRIPTION pvcreate initializes PhysicalVolume for later use by the Logical Volume Manager (LVM). Each PhysicalVolume can be a disk partition, whole disk, meta device, or loopback file. For DOS disk partitions, the partition id must be set to 0x8e using fdisk(8), cfdisk(8), or a equivalent. For whole disk devices only the partition table must be erased, which will effectively destroy all data on that disk. This can be done by zeroing the first sector with: # dd if=/dev/zero of=PhysicalVolume bs=512 count=1 Continue with vgcreate(8) to create a new volume group on PhysicalVolume, or vgextend(8) to add PhysicalVolume to an existing volume group. OPTIONS -d, --debug Enables additional debugging output (if compiled with DEBUG). -f, --force Force the creation without any confirmation. You can not recreate (reinitialize) a physical volume belonging to an existing volume group. In an emergency you can override this behaviour with -ff. In no case case can you
initialize an active physical volume with this command. -s, --size Overrides the size of the physical volume which is normally retrieved. Useful in rare case where this value is wrong. More useful to fake large physical volumes of up to 2 Terabyes - 1 Kilobyte on smaller devices for testing purposes only where no real access to data in created logical volumes is needed. If you wish to create the supported maximum, use "pvcreate -s 2147483647k PhysicalVolume [PhysicalVolume ...]". All other LVM tools will use this size with the exception of lvmdiskscan(8) -y, --yes Answer yes to all questions. -h, --help Print a usage message on standard output and exit successfully. -v, --verbose Gives verbose runtime information about pvcreate's activities. -V, --version Print the version number on standard output and exit successfully. Example Initialize partition #4 on the third SCSI disk and the entire fifth SCSI disk for later use by LVM: # pvcreate /dev/sdc4 /dev/sde
34. SWAP space: =============== 34.1 Solaris: -------------- View swap space: -- ---------------The /usr/sbib/swap utility provides a method of adding, deleting, and monitoring the system swap areas used by the memory manager. # swap -l The -l option can be used to list swap space. The system displays information like: swapfile dev swaplo blocks free /dev/dsk/c0t0d0s3 136,3 16 302384 302384 path : the pathname for the swaparea. In this example the pathname is swapfile. dev : the major/minor device number is in decimal if it's a block special device; zeroes otherwise swaplo: the offset in 512 byte blocks where usable swapspace begins blocks: size in 512 byte blocks. The swaplen value can be adjusted as a kernel parameter. free : free 512 byte blocks.
The swap -l command does not include physical memory in it's calculation of swap space. # swap -s The -s option can be used to list a summary of the system's virtual swap space. total: 31760k bytes allocated + 5952k reserved = 37712k used, 202928k available These numbers are in 1024 byte blocks. -- Add swap area's: -- ---------------There are 2 methods available for adding more swap to your system. (1) create a secondary swap partition: (2) create a swapfile in an existing UFS file system (1) Creating a secondary swap partition requires additional unused diskspace. You must use the format coommand to create a new partition and filesystem on a disk. Suppose we have the /data directory currently on slice 5 and is 200MB in size. - free up the /data directory (save the contents to another location ) - unmount /dev/dsk/c0t0d0s5 - use format: Enter partition id tag (unassigned): swap Enter partition permission flags (wm): wu Enter new starting cil(3400): return Enter partition size: return Then label the disk as follows Partition> la Ready to label disk? y - Run the newfs command on that partition to create a fresh filesystem on slice 5 newfs /dev/rdsk/c0t0d0s5 - Make an entry to the /etc/vfstab file - Run the swapadd script to add the swap to your system as follows: /sbin/swapadd - verify that the swap has been added with swap -l (2) The other method to add more swap space is to use the mkfile and swap commands to designate a part of an existing UFS filesystem as a supplementary swap area. You can use it as a temporary solution, or as a solution for longer duration as well, but a swap file is just another file in the filesystem, so you cannot unmount that filesystem while the swapfile is in use. The following steps enable you to add more swap space without repartitioning a disk. - As root, use df -k to locate a suitable filesystem. Suppose /data looks allright for this purpose - Use the mkfile command to add a 50MB swapfile named swapfile in the /data partition. mkfile 50m /data/swapfile - use ls -l /data to verify that the file has been created. Notice that the sticky bit has automatically been set.
- Activate the swaparea with the swap command as follows: /usr/sbin/swap -a /data/swapfile - verify that the swap has been added with swap -l The system responds something like this: swapfile /dev/dsk/c0t0d0s3 /data/swapfile
dev 136,3 -
swaplo 16 16
blocks 302384 102384
free 302384 102384
If this will be a permanent swaparea, add an entry for the swapfile in the vfstab file. /data/swapfile - - swap - no -- Removing a swapfile: -- -------------------As root use the swap -d command to remove a swaparea is follows swap -d /dev/dsk/c0t0d0s5 swap -d /data/swapfile
for a swap partition for a swapfile
Use the swap -l command to verify that the swaparea is gone. Edit the /etc/vfstab file and delete the entry for the swapfile if neccessary. In case of a swapfile, just remove the file with rm /data/swapfile -- Creating a Temporary File System: -- --------------------------------Create a directory which will serve as the mount point for the TMPFS file system. There is no command such as newfs to create a TMPFS file system before mounting it. The TMPFS file system actually gets created in RAM when you execute the mount command and specify a filesystem type of TMPFS. The following example creates a new directory /export/data and mounts a TMPFS filesystem, limiting it to 25MB. mount -F tmpfs -o size=25m swap /export/data
34.2 AIX: --------The installation creates a default paging logical volume, hd6, on drive hdisk0, also referred as primary paging space. The reports from the "vmstat" and "topas" commands indicate the amount of paging space I/O that is taking place. Showing paging space: --------------------The lsps -a command provides a snapshot of the current utilization of each of the
paging spaces on the system, while the lsps -s command provides a summary of the total active paging space and its current utilization. # lsps -a Page Space Type paging00 lv hd6 lv
Physical Volume
Volume Group
Size
%Used
Active
Auto
hdisk1
rootvg
80MB
1
yes
yes
hdisk1
rootvg
256MB
1
yes
yes
The /etc/swapspaces file specifies the paging-space devices that are activated by the swapon -a command. A pagingspace is added to this file when its created by the mkps -a command, and removed from the file when rmps is used. Managing Paging space: ---------------------The following commands are used to manage paging space: chps lsps mkps rmps swapon swapoff
: : : : : :
changes the attributes of a paging space displays the characteristics of a paging space creates an additional paging space removes an inactive paging space activates a paging space deactivates one or more paging spaces
Show paging space usage: # lsps -a Increase paging space: # chps -s 32 hd6
32x32MB
where we increased the size of hd6 with 30 LP's. Reducing paging space: # chps -d 1 hd6 where we decreased the size of hd6 with 1 LP. mkps: ----To Add a Logical Volume for Additional Paging Space mkps [ -a ] [ -n ] [ -t lv ] -s LogicalPartitions VolumeGroup [ PhysicalVolume ] To create a paging space in volume group myvg that has four logical partitions and is activated immediately and at all subsequent system restarts, enter:
# mkps
-a
-n
-s 4 myvg
To create a paging space in rootvg on hdisk0 # mkps -a -n -s 30 rootvg hdisk0 rmps: ----Before AIX 5L: Active paging spaces cannot be removed. It must first be made inactive. Use the chps command so the paging space is not used on the next restart. After reboot, the paging space is inactive and can be removed with the rmps command. AIX 51 or later: Use the swapoff command to dynamically deactive the paging space, then use the rmps command. # swapoff /dev/paging03 # rmps paging03 chps: ----As from AIX 5L you can use the chps -d command, to decrease the size of a paging space, without having to deactive it, then reboot, then remove, and then recreate it with a smaller size. Decrease it with a number of LP's like: # chps -d 2 paging03 chps -a {y|n} paging00 : specifies that the paging space paging00 is active (y) or inactive (n) at subsequent system restarts. chps -s 10 paging02 : adds ten LPs to paging02 without rebooting. chps -d 5 paging01 : removes five LPs from paging01 without rebooting. chps -d 50 hd6 : removes fifty LPs from hd6 without rebooting. List the active paging spaces: -----------------------------# lsps -a
or lsps -s
# pg /etc/swapspaces hd6: dev=/dev/hd6 paging00
dev=/dev/paging00
34.3 Linux: ------------ Check the swapspace: # cat /proc/meminfo
# cat /proc/swaps # /sbin/swapon -s -- Creating swap space using a partition Create a partition of the proper size using fdisk. Format the partition, for example # mkswap -c /dev/hda4 Enable the swap, for example # swapon /dev/hd4 If you want the swap space enabled after boot, include the appropriate entry into /etc/fstab, for example /dev/hda4 swap swap defaults 0 0 If you need to disable the swap, you can do it with # swapoff /dev/hda4 -- Creating swap space using a swapfile Create a file with the size of your swapfile # dd if=/dev/zero of=/swapfile bs=1024 count=8192 Setup the file with the command # mkswap /swapfile 8192 Enable the swap with the command # swapon /swapfile When you are done using the swapfile, you can turn it off and remove with # swapoff /swapfile # rm /swapfile 34.4: Note about swap: ---------------------Page replacement in Linux 2.4 memory management Rik van Riel Conectiva Inc.
[email protected], http://www.surriel.com/ Abstract While the virtual memory management in Linux 2.2 has decent performance for many workloads, it suffers from a number of problems. The first part of this paper contains a description of how the Linux 2.2 VMM works and an analysis of why it has bad behaviour in some situations. The way in which a lot of this behaviour has been fixed in the Linux 2.4 kernel is described in the second part of the paper. Due to Linux 2.4 being in a code freeze period while these improvements were implemented, only known-good solutions have been integrated. A lot of the ideas used are derived from principles used in
other operating systems, mostly because we have certainty that they work and a good understanding of why, making them suitable for integration into the Linux codebase during a code freeze. --Linux 2.2 memory management The memory management in the Linux 2.2 kernel seems to be focussed on simplicity and low overhead. While this works pretty well in practice for most systems, it has some weak points left and simply falls apart under some scenarios. Memory in Linux is unified, that is all the physical memory is on the same free list and can be allocated to any of the following memory pools on demand. Most of these pools can grow and shrink on demand. Typically most of a system's memory will be allocated to the data pages of processes and the page and buffer caches. The slab cache: this is the kernel's dynamically allocated heap storage. This memory is unswappable, but once all objects within one (usually page-sized) area are unused, that area can be reclaimed. The page cache: this cache is used to cache file data for both mmap() and read() and is indexed by (inode, index) pairs. No dirty data exists in this cache; whenever a program writes to a page, the dirty data is copied to the buffer cache, from where the data is written back to disk. The buffer cache: this cache is indexed by (block device, block number) tuples and is used to cache raw disk devices, inodes, directories and other filesystem metadata. It is also used to perform disk IO on behalf of the page cache and the other caches. For disk reads the pagecache bypasses this cache and for network filesystems it isn't used at all. The inode cache: this cache resides in the slab cache and contains information about cached files in the system. Linux 2.2 cannot shrink this cache, but because of its limited size it does need to reclaim individual entries. The dentry cache: this cache contains directory and name information in a filesystem-independent way and is used to lookup files and directories. This cache is dynamically grown and shrunk on demand. SYSV shared memory: the memory pool containing the SYSV shared memory segments is managed pretty much like the page cache, but has its own infrastructure for doing things. Process mapped virtual memory: this memory is administrated in the process page tables. Processes can have page cache or SYSV shared memory segments mapped, in which case those pages are managed in both the page tables and the data structures used for respectively the page cache or the shared memory code. --Linux 2.2 page replacement The page replacement of Linux 2.2 works as follows. When free memory drops below a certain threshold, the pageout daemon (kswapd) is woken up. The pageout daemon should usually be able to keep enough free memory, but if it isn't, user programs will end up calling the pageout code itself. The main pageout loop is in the function try_to_free_pages, which starts by freeing unused slabs from the kernel memory pool. After that, it calls the
following functions in a loop, asking each of them to scan a small part of their part of memory until enough memory has been freed. shrink_mmap is a classical clock algorithm, which loops over all physical pages, clearing referenced bits, queueing old dirty pages pages for IO and freeing old clean pages. The main disadvantage it has compared to a clock algorithm, however, is that it isn't able to free pages which are in use by a program or a shared memory segment. Those pages need to be unmapped by swap_out first. shm_swap scans the SYSV shared memory segments, swapping out those pages that haven't been referenced recently and which aren't mapped into any process. swap_out scans the virtual memory of all processes in the system, unmapping pages which haven't been referenced recently, starting swapout IO and placing those pages in the page cache. shrink_dcache_memory recaims entries from the VFS name cache. This is not directly reusable memory, but as soon as a whole page of these entries gets unused we can reclaim that page. Some balancing between these memory freeing function is achieved by calling them in a loop, starting of by asking each of these functions to scan a little bit of their memory, as each of these funnctions accepts a priority argument which tells them how big a percentage of their memory to scan. If not enough memory is freed in the first loop, the priority is increased and the functions are called again. The idea behind this scheme is that when one memory pool is heavily used, it will not give up its resources lightly and we'll automatically fall through to one of the other memory pools. However, this scheme relies on each of the memory pools to react in a similar way to the priority argument under different load conditions. This doesn't work out in practice because the memory pools just have fundamentally different properties to begin with. --Problems with the Linux 2.2 page replacement Balancing between evicting pages from the file cache, evicting unused process pages and evicting pages from shm segments. If memory pressure is "just right" shrink_mmap is always successful in freeing cache pages and a process which has been idle for a day is still in memory. This can even happen on a system with a fairly busy filesystem cache, but only with the right phase of moon. Simple NRU[Note] replacement cannot accurately identify the working incidentally accessed pages and can lead to extra page faults. This noticably for most workloads, but it makes a big difference in some can be fixed easily, mostly since the LFU replacement used in older is known to work.
set versus doesn't hurt workloads and Linux kernels
Due to the simple clock algorithm in shrink_mmap, sometimes clean, accessed pages can get evicted before dirty, old pages. With a relatively small file cache that mostly consists of dirty data, eg unpacking a tarball, it is possible for the dirty pages to evict the (clean) metadata buffers that are needed to write the dirty data to disk. A few other corner cases with amusing variations on this theme are bound to exist. The system reacts badly to variable VM load or to load spikes after a period of no VM activity. Since kswapd, the pageout daemon, only scans when the system is low on memory, the system can end up in a state where some pages have referenced bits from the last 5 seconds, while other pages have referenced bits from 20 minutes
ago. This means that on a load spike the system has no clue which are the right pages to evict from memory, this can lead to a swapping storm, where the wrong pages are evicted and almost immediately afterwards faulted back in, leading to the pageout of another random page, etc... Under very heavy loads, NRU replacement of pages simply doesn't cut it. More careful and better balanced pageout eviction and flushing is called for. With the fragility of the Linux 2.2 pageout framework this goal doesn't really seem achievable. The facts that shrink_mmap is a simple clock algorithm and relies on other functions to make process-mapped pages freeable makes it fairly unpredictable. Add to that the balancing loop in try_to_free_pages and you get a VM subsystem which is extremely sensitive to minute changes in the code and a fragile beast at its best when it comes to maintenance or (shudder) tweaking. --Changes in Linux 2.4 For Linux 2.4 a substantial development effort has gone into things like making the VM subsystem fully fine-grained for SMP systems and supporting machines with more than 1GB of RAM. Changes to the pageout code were done only in the last phase of development and are, because of that, somewhat conservative in nature and only employ known-good methods to deal with the problems that happened in the page replacement of the Linux 2.2 kernel. Before we get to the page replacement changes, however, first a short overview of the other changes in the 2.4 VM: More fine-grained SMP locking. The scalability of the VM subsystem has improved a lot for workloads where multiple CPUs are reading or writing the same file simultaneously; for example web or ftp server workloads. This has no real influence on the page replacement code. Unification of the buffer cache and the page cache. While in Linux 2.2 the page cache used the buffer cache to write back its data, needing an extra copy of the data and doubling memory requirements for some write loads, in Linux 2.4 dirty page cache pages are simply added in both the buffer and the page cache. The system does disk IO directly to and from the page cache page. That the buffer cache is still maintained separately for filesystem metadata and the caching of raw block devices. Note that the cache was already unified for reads in Linux 2.2, Linux 2.4 just completes the unification. Support for systems with up to 64GB of RAM (on x86). The Linux kernel previously had all physical memory directly mapped in the kernel's virtual address space, which limited the amount of supported memory to slightly under 1GB. For Linux 2.4 the kernel also supports additional memory (so called "high memory" or highmem), which can not be used for kernel data structures but only for page cache and user process memory. To do IO on these pages they are temporarily mapped into kernel virtual memory and the data is copied to or from a bounce buffer in "low memory". At the same time the memory zone for ISA DMA (0 - 16 MB physical address range) has also been split out into a separate page zone. This means larger x86 systems end up with 3 memory zones, which all need their free memory balanced so we can continue allocating kernel data structures and ISA DMA buffers. The memory zones logic is generalised enough to also work for NUMA systems. The SYSV shared memory code has been removed and replaced with a simple memory filesystem which uses the page cache for all its functions. It supports both POSIX SHM and SYSV SHM semantics and can also be used as a swappable memory filesystem (tmpfs).
Since the changes to the page replacement code took place after all these changes and in the (one and a half year long) code freeze period of the Linux 2.4 kernel, the changes have been kept fairly conservative. On the other hand, we have tried to fix as many of the Linux 2.2 page replacement problems as possible. Here is a short overview of the page replacement changes: they'll be described in more detail below. Page aging, which was present in the Linux 1.2 and 2.0 kernels and in FreeBSD has been reintroduced into the VM. However, a few small changes have been made to avoid some artifacts of virtual page based aging. To avoid the eviction of "wrong" pages due to interactions from page aging and page flushing, the page aging and flushing has been separated. There are active and inactive page lists. Page flushing has been optimised to avoid too much interference by writeout IO on the more time-critical disk read IO. Controlled background page aging during periods of little or no VM activity in order to keep the system in a state where it can easily deal with load spikes. Streaming IO is detected; we do early eviction on the pages that have already been used and reward the IO stream with more agressive readahead. --Linux 2.4 page replacement changes in detail The development of the page replacement changes in Linux 2.4 has been influenced by two main factors. Firstly the bad behaviours of Linux 2.2 page replacement had to be fixed, using only known-good strategies because the development of Linux 2.4 had already entered the "code freeze" state. Secondly the page replacement had to be more predictable and easier to understand than Linux 2.2 because tuning the page replacement in Linux 2.2 was deserving of the proverbial label "subtle and quick to upset". This means that only VM ideas that are well understood and have little interactions with the rest of the system were integrated. Lots of ideas were taken from other freely available operating systems and literature. --Page aging Page aging was the first easy step in making the bad border-case behaviour from Linux 2.2 go away, it works reasonably well in Linux 1.2, Linux 2.0 and FreeBSD. Page aging allows us to make a much finer distinction between pages we want to keep in memory and pages we want to swap out than the NRU aging in Linux 2.2. Page aging in these OSes works as follows: for each physical page we keep a counter (called age in Linux, or act_count in FreeBSD) that indicates how desirable it is to keep this page in memory. When scanning through memory for pages to evict, we increase the page age (adding a constant) whenever we find that the page was accessed and we decrease the page age (substracting a constant) whenever we find that the page wasn't accessed. When the page age (or act_count) reaches zero, the page is a candidate for eviction. However, in some situations the LFU[Note] page aging of Linux 2.0 is known to have too much CPU overhead and adjust to changes in system load too slowly. Furthermore, research[Smaragdis, Kaplan, Wilson] has shown that recency of access is a more important criteria for page replacement than frequency. These two problems are solved by doing exponential decline of the page age (divide by two instead of substracting a constant) whenever we find a page that wasn't accessed, resulting in page replacement which is closer to LRU[Note] than LFU.
This reduces the CPU overhead of page aging drastically in some cases; however, no noticable change in swap behaviour has been observed. Another artifact comes from the virtual address scanning. In Linux 1.2 and 2.0 the system reduces the page age of a page whenever it sees that the page hasn't been accessed from the page table which it is currently scanning, completely ignoring the fact that the page could have been accessed from other page tables. This can put a severe penalty on heavily shared pages, for example the C library. This problem is fixed by simply not doing "downwards" aging from the virtual page scans, but only from the physical-page based scanning of the active list. If we encounter pages which are not referenced, present in the page tables but not on the active list, we simply follow the swapout path to add this page to the swap cache and the active list so we'll be able to lower the page age of this page and swap it out as soon as the page age reaches zero. --Multiple page lists The bad interactions between page aging and page flushing, where referenced clean pages were freed before old dirty pages, is fixed by keeping the pages which are candidates for eviction separated from the pages we want to keep in memory (page age zero vs. nonzero). We separate the pages out by putting them on various page lists and having separate algorithms deal with each list. Pages which are not (yet) candidate for eviction are in process page tables, on the active list or both. Page aging as described above happens on these pages, with the function refill_inactive() balancing between scanning the page tables and scanning the active list. When the page age on a page reaches zero, due to a combination of pageout scanning and the page not being actively used, the page is moved to the inactive_dirty list. Pages on this list are not mapped in the page tables of any process and are, or can become, reclaimable. Pages on this list are handled by the function page_launder(), which flushes the dirty pages to disk and moves the clean pages to the inactive_clean list. Unlike the active and inactive_dirty lists, the inactive_clean list isn't global but per memory zone. The pages on these lists can be immediately reused by the page allocation code and count as free pages. These pages can also still be faulted back into where it came from, since the data is still there. In BSD this would be called the "cache" queue. --Dynamically sized inactive list Since we do page aging to select which pages to evict, having a very large statically sized inactive list (like FreeBSD has) doesn't seem to make much sense. In fact, it would cancel out some of the effects of doing the page aging in the first place: why spend much effort selecting which pages to evict[Dillon] when you keep as much as 33% of your swappable pages on the inactive list? Why do careful page aging when 33% of your pages end up as candidates for eviction at the same priority and you've effectively undone the aging for those 33% of pages which are candidates for eviction? On the other hand, having lots of inactive pages to choose from when doing page eviction means you have more chances of avoiding writeout IO or doing better IO clustering. It also gives you more of a "buffer" to deal with allocations due to page faults, etc. Both a large and a small target size for the inactive page list have their benefits. In Linux 2.4 we have chosen for a middle ground by letting the system
dynamically vary the size of the inactive list depending on VM activity, with an artificial upper limit to make sure the system always preserves some aging information. Linux 2.4 keeps a floating average of the amount of pages evicted per second and sets the target for the inactive list and the free list combined to the free target plus this average number of page steals per second. Not only does this second give us enough time to do all kinds of page flushing optimisations, it also is small enough to keep page age distribution within the system intact, allowing us to make good choices on which pages to evict and which pages to keep. --Optimised page flushing Writing out pages from the inactive_dirty list as we encounter them can cause a system to totally destroy read performance because of the extra disk seeks done. A better solution is to delay writeout of dirty pages and let these dirty pages accumulate until we can do better IO clustering so that these pages can be written out to disk with less disk seeks and less interference with read performance. Due to the development of the page replacement changes happening in the code freeze, the system currently has a rather simple implementation of what's present in FreeBSD 4.2. As long as there are enough clean inactive pages around, we keep moving those to the inactive_clean list and never bother with syncing out the dirty pages. Note that this catches both clean pages and pages which have been written to disk by the update daemon (which commits filesystem data to disk periodically). This means that under loads where data is seldom written we can avoid writing out dirty inactive pages most of the time, giving us much better latencies in freeing pages and letting streaming reads continue without the disk head moving away to write out data all the time. Only under loads where lots of pages are being dirtied quickly does the system suffer a bit from syncing out dirty data irregularly. Another alternative would have been the strategy used in FreeBSD 4.3, where dirty pages get to stay in the inactive list longer than clean pages but are synced out before the clean pages are exhausted. This strategy gives more consistent pageout IO in FreeBSD during heavy write loads. However, a big factor causing the irregularities in pageout writes using the simpler strategy above may well be caused because of the huge inactive list target in FreeBSD (33It is not at all clear what this more complicated strategy would do when used on the dynamically sized inactive list on Linux 2.4, because of this Linux 2.4 uses the better understood strategy of evicting clean inactive pages first and only after those are gone start syncing the dirty ones. --Background page aging On many systems the normal operating mode is that after a period of relative activity a sudden load spike comes in and the system has to deal with that as gracefully as possible. Linux 2.2 has the problem that, with the lack of an inactive page list, it is not clear at all which pages should be evicted when a sudden demand for memory kicks in. Linux 2.4 is better in this respect, with the reclaim candidates neatly separated out on the inactive list. However, the inactive list could have any random size the moment VM pressure drops off. We'd like get the system in a more predictable state while the VM pressure is low. In order to achieve this, Linux 2.4 does background scanning of the pages, trying to get a sane amount of pages on the inactive list, but without scanning agressively so only truly idle pages will end up on the inactive list and the scanning overhead stays small.
--Drop behind Streaming IO doesn't just have readahead, but also its natural complement: drop behind. After the program doing the streaming IO is done with a page, we depress its priority heavily so it will be a prime candidate for eviction. Not only does this protect the working set of running processes from being quickly evicted by streaming IO, but it also prevents the streaming IO from competing with the pageouts and pageins of the other running processes, which reduces the number of disk seeks and allows the streaming IO to proceed at a faster speed. Currently readahead and drop-behind only work for read() and write(); mmap()ed files and swap-backed anonymous memory aren't supported yet. --Conclusions Since the Linux 2.4 kernel's VM subsystem is still being tuned heavily, it is too early to come with conclusive figures on performance. However, initial results seem to indicate that Linux 2.4 generally has better performance than Linux 2.2 on the same hardware. Reports from users indicate that performance on typical desktop machines has improved a lot, even though the tuning of the new VM has only just begun. Throughput figures for server machines seem to be better too, but that could also be attributed to the fact that the unification of the page cache and the buffer cache is complete. One big difference between the VM in Linux 2.4 and the VM in Linux 2.2 is that the new VM is far less sensitive to subtle changes. While in Linux 2.2 a subtle change in the page flushing logic could upset page replacement, in Linux 2.4 it is possible to tweak the various aspects of the VM with predictable results and little to no side-effects in the rest of the VM. The solid performance and relative insensitivity to subtle changes in the environment can be taken as a sign that the Linux 2.4 VM is not just a set of simple fixes for the problems experienced in Linux 2.2, but also a good base for future development. Remaining issues The Linux 2.4 VM mainly contains easy to implement and obvious to verify solutions for some of the known problems Linux 2.2 suffers from. A number of issues are either too subtle to implement during the code freeze or will have too much impact on the code. The complete list of TODO items can be found on the Linux-MM page[Linux-MM]; here are the most important ones: Low memory deadlock prevention: with the arrival of journaling and delayedallocation filesystems it is possible that the system will need to allocate memory in order to free memory; more precisely, to write out data so memory can become freeable. To remove the possibility for deadlock, we need to limit the number of outstanding transactions to a safe number, possibly letting each of the page flushing functions indicate how much memory it may need and doing bookkeeping of these values. Note that the same problem occurs with swap over network. Load control: no matter how good we can get the page replacement code, there will always be a point where the system ends up thrashing to death. Implementing a simple load control system, where processes get suspended in round-robin fashion when the paging load gets too high, can keep the system alive under heavy overload and allow the system to get enough work done to bring itself back to a sane state.
RSS limits and guarantees: in some situations it is desirable to control the amount of physical memory a process can consume (the resident set size, or RSS). With the virtual address based page scanning of Linux' VM subsystem it is trivial to implement RSS ulimits and minimal RSS guarantees. Both help to protect processes under heavy load and allow the system administrator to better control the use of memory resources. VM balancing: in Linux 2.4, the balancing between the eviction of cache pages, swap-backed anonymous memory and the inode and dentry caches is essentially the same as in Linux 2.2. While this seems to work well for most cases there are some possible scenarios where a few of the caches push the other users out of memory, leading to suboptimal system performance. It may be worthwhile to look into improving the balancing algorithm to achieve better performance in "non-standard" situations. Unified readahead: currently readahead and drop-behind only works for read() and write(). Ideally they should work for mmap()ed files and anonymous memory too. Having the same set of algorithms for both read()/write(), mmap() and swap-backed anonymous memory will simplify the code and make performance improvements in the readahead and drop-behind code immediately available to all of the system. AIX swap notes: --------------Note 1: ------Q: Hi All, I'm seeing an interesting paging behavior (paging out to paging space when I don't think it should) on our AIX 5.3 TL3CSP system. First the system particulars: AIX 5.3 TL3 with CSP HACMP v5.2 Oracle 10g 28GB memory 8GB paging space EMC LUNs for Oracle data. CIO used for Oracle data. Virtual memory tuned as such vmo -p -o maxclient%=50 vmo -p -o maxperm%=50 vmo -p -o 'lru_file_repage=0' vmo -p -o 'minperm%=3' So, given that configuration, it is my understanding that AIX, when under memory pressure, will steal memory from the file cache instead of paging process memory out to the paging space (lru_file_repage = 0). Now, this system works for the most part like I understand it should. Via nmon, I
can watch it stealing memory from the FileSystemCache (numclient values decrease) when the box gets under memory pressure. However, every once in a while when under memory pressure, I can see that the system starts writing to the paging space when there is plenty of FileSystemCache available to steal from. Below is a snapshot from the nmon 'm'emory switch: nmon.jpg You can see here that I've got 1.7GB paged out, while numclient is at 21%. So, my question is, why does AIX page out when under memory pressure instead of stealing from the FileSystemCache memory like I want it to? A: Look at the Paging to/from the Paging Space - its zero. Once info is in the paging space its left there until the space is needed for something else. So at this point the server isn't actually paging. It Has paged in the past however. Note 2: -----AIX will always try to use 100% of real memory--> AIX will use the amount of memory solicited by your processes. The remaining capacity will be used as filesystem cache. You can change the minimum and maximum amounts of memory used to cache files with vmtune (vmo for 5.2+), and it is advised to do so if your�re running databases with data on raw devices (since the db engine usually has its own cache algorithm, and AIX can�t cache data on raw devices). The values to modify are minperm, maxperm, minclient and maxpin (use at you own risk!!!). Paging space use will be very low: 5% is about right--> A paging space so little used seems to be oversized. In general, the paging space should be under 40%, and the size must be determined accordingly to the application running (i.e. 4X the physical memory size for oracle). In AIX 5L a paging space can be reduced without rebooting. Anyway, AIX always uses some paging space, even keeping copies of the data on memory and on disk, as a �predictive� paging. Look in topas for the values �comp mem� (proceses) and �non comp mem� (filesystem cache) to see the distribution of the memory usage. Nmon can show you the top proceses by memory usage, along with many other statistics. There are several tools which can give you a more detailed picture of how memory is being used. "svmon" is very comprehensive. Tools such as topas and nmon will also give you a bit more information. Note 3: -------
Memory utilization on AIX systems typically runs around 100%. This is often a source of concern. However, high memory utilization in AIX does not imply the system is out of memory. By design, AIX leaves files it has accessed in memory. This significantly improves performance when AIX reaccesses these files because they can be reread directly from memory, not disk*. When AIX needs memory, it discards files using a "least used" algorithm. This generates no I/O and has almost no performance impact under normal circumstances. Sustained paging activity is the best indication of low memory. Paging activity can be monitored using the "vmstat" command. If the "page-in" (PI) and "page-out" (PO) columns show non-zero values over "long" periods of time, then the system is short on memory. (All systems will show occasional paging, which is not a concern.) Memory requirements for applications can be empirically determined using the AIX "rmss"command. The "rmss" command is a test tool that dynamically reduces usable memory. The onset of paging indicates an application's minimum memory requirement. Finally, the "svmon" command can be used to list how much memory is used each process. The interpretation of the svmon output requires some expertise. See the AIX documentation for details.
================================================================== 35 Volume group, logical volumes, and filesystem commands in HPUX: ================================================================== 35.1 Filesystems in HPUX: ------------------------HFS : used at HP-UX < v. 10 VxFS: used at HP-UX >= v. 10 Ofcourse, CDFS (cdroms), and other filesystem types, are supported. HP-UX's implementation of a journaled file system, also known as JFS, is based on the version from VERITAS Software Inc. called VxFS. Up through the 10.0 release of HP-UX, HFS has been the only available locally mounted read/write file system. Beginning at 10.01, you also have the option of using VxFS. (Note, however, that VxFS cannot be used as the root file system.) As compared to HFS, VxFS allows much shorter recovery times in the event of system failure. It is also particularly useful in environments that require high performance or deal with large
volumes of data. This is because the unit of file storage, called an extent, can be multiple blocks, allowing considerably faster I/O than with HFS. It also provides for minimal downtime by allowing online backup and administration � that is, unmounting the file system will not be necessary for certain tasks. You may not want to configure VxFS, though, on a system with limited memory because VxFS memory requirements are considerably larger than that for HFS. Basic VxFS functionality is included with the HP-UX operating system software. Additional enhancements to VxFS are available as a separately orderable product called HP "OnlineJFS", product number B5117AA (Series 700) and B3928AA (Series 800). 35.2 How to create a filesystem in HP-UX: an outline. ------------------------------------------------------ Task 1. Estimate the Size Required for the Logical Volume -- Task 2. Determine If Sufficient Disk Space Is Available for the Logical Volume within Its Volume Group Use the vgdisplay command to calculate this information. vgdisplay will output data on one or more volume groups, including the physical extent size (under PE Size (Mbytes)) and the number of available physical extents (under Free PE). By multiplying these two figures together, you will get the number of megabytes available within the volume group. See vgdisplay(1M) for more information. -- Task 3. Add a Disk to a Volume Group If Necessary If there is not enough space within a volume group, you will need to add a disk to a volume group. To add a disk to an existing volume group, use pvcreate(1M) and vgextend(1M). You can also add a disk by creating a new volume group with pvcreate(1M) and vgcreate(1M). -- Task 4. Create the Logical Volume Use lvcreate to create a logical volume of a certain size in the above volume group. See lvcreate(1M) for details. Use lvcreate as in the following example: Create a logical volume of size 100 MB in volume group /dev/vg03: # lvcreate -L 100 /dev/vg03 -- Task 5. Create the New File System Create a file system using the newfs command. Note the use of the character device file. For example: # newfs -F hfs /dev/vg02/rlvol1
If you do not use the -F FStype option, by default, newfs creates a file system based on the content of your /etc/fstab file. If there is no entry for the file system in /etc/fstab, then the file system type is determined from the file /etc/default/fs. For information on additional options, see newfs(1M). $ cat /etc/default/fs LOCAL=vxfs For HFS, you can explicitly specify that newfs create a file system that allows short file names or long file names by using either the -S or -L option. By default, these names will as short or long as those allowed by the root file system. Short file names are 14 characters maximum. Long file names allow up to 255 characters. Generally, you use long file names to gain flexibility in naming files. Also, files created on other systems that use long file names can be moved to your system without being renamed. When creating a VxFS file system, file names will automatically be long. After creating a filesystem, you need to mount it to make it accesible, for example like: -- Task 6. mount the new local file system: Choose an empty directory to serve as the mount point for the file system. Use the mkdir command to create the directory if it does not currently exist. For example, enter: # mkdir /test Mount the file system using the mount command. Use the block device file name that contains the file system. You will need to enter this name as an argument to the mount command. For example, enter # mount /dev/vg01/lvol1 /test Note: The newfs command is a "friendly" front-end to the mkfs command (see mkfs(1M)). The newfs command calculates the appropriate parameters and then builds the file system by invoking the mkfs command.
35.3 HP-UX LVM commands: ======================== -- vgdisplay:
-- ---------Displays information about volume groups. Examples: # vgdisplay # vgdisplay -v vgdatadir -- pvdisplay: -- ---------Display information about physical volumes within LVM volume group. EXAMPLES Display the status and characteristics of a physical volume: # pvdisplay /dev/dsk/c1t0d0 Display the status, characteristics, and allocation map of a physical volume: # pvdisplay -v /dev/dsk/c2t0d0 # pvdisplay /dev/dsk/c102t9d3 --- Physical volumes --PV Name PV Name VG Name PV Status Allocatable VGDA Cur LV PE Size (Mbytes) Total PE Free PE Allocated PE Stale PE IO Timeout (Seconds) Autoswitch
/dev/dsk/c43t9d3 /dev/dsk/c102t9d3 Alternate Link /dev/vgora_e1atlas_data available yes 2 2 4 1668 102 1566 0 default On
-- lvdisplay: -- ---------Displays information about logical volumes. Examples: # lvdisplay lvora_p0gencfg_apps # lvdisplay -v lvora_p0gencfg_apps # lvdisplay -v /dev/vg00/lvol2 # lvdisplay /dev/vgora_e0etea_data/lvora_e0etea_data --- Logical volumes --LV Name /dev/vgora_e0etea_data/lvora_e0etea_data VG Name /dev/vgora_e0etea_data LV Permission read/write
LV Status Mirror copies Consistency Recovery Schedule LV Size (Mbytes) Current LE Allocated PE Stripes Stripe Size (Kbytes) Bad block Allocation IO Timeout (Seconds)
available/syncd 1 MWC parallel 17020 4255 8510 0 0 on strict default
-- vgchange: -- --------Set volume group availability. This command activates or deactivates one or more volume groups as specified by the -a option, namely y or n. Activate a volume group: # vgchange -a y /dev/vg03 Deactivate a volume group: # vgchange -a n /dev/vg03
-- vgcreate: -- --------/usr/sbin/vgcreate [-f] [-A autobackup] [-x extensibility] [-e max_pe] [-l max_lv] [-p max_pv] [-s pe_size] [-g pvg_name] vg_name pv_path ... The vgcreate command creates a new volume group. vg_name is a symbolic name for the volume group and must be used in all references to it. vg_name is the path to a directory entry under /dev that must contain a character special file named group. Except for the group entry, the vg_name directory should be empty. The vg_name directory and the group file have to be created by the user (see lvm(7)). vgcreate leaves the volume group in an active state. EXAMPLES 1. Create a volume group named /dev/vg00 containing two physical volumes with extent size set to 2 Mbytes. If directory /dev/vg00 exists with the character special file group, the volume group is created: # vgcreate -s 2 /dev/vg00 /dev/dsk/c1d0s2 /dev/dskc2d0s2
2. Create a volume group named /dev/vg01 that can contain a maximum of three logical volumes, with extent size set to 8 Mbytes: # vgcreate -l 3 -s 8 /dev/vg01 /dev/dsk/c4d0s2 3. Create a volume group named /dev/vg00 and a physical volume group named PVG0 with two physical volumes: # vgcreate -g PVG0 /dev/vg00 /dev/dsk/c1d0s2 /dev/dsk/c2d0s2 3. Create a volume group named /dev/vg00 containing two physical volumes with extent size set to 2 MB, from scratch. First, create the directory /dev/vg00 with the character special file called group. mkdir /dev/vg00 mknod /dev/vg00/group c 64 0x030000 The minor number for the group file should be unique among all the volume groups on the system. It has the format 0xNN0000, where NN runs from 00 to ff. The maximum value of NN is controlled by the kernel tunable parameter maxvgs. Initialize the disks using pvcreate(1M). pvcreate /dev/rdsk/c1t0d0 pvcreate /dev/rdsk/c1t2d0 Create the volume group. vgcreate -s 2 /dev/vg00 /dev/dsk/c1t0d0 /dev/dsk/c1t2d0 Note About the "dsk" and "rdsk" notation: ----------------------------------------Physical volumes are identified by their device file names, for example /dev/dsk/cntndn /dev/rdsk/cntndn Note that each disk has a block device file and a character or raw device file, the latter identified by the r. Which name you use depends on what task you are doing with the disk. In the notation above, the first name represents the block device file while the second is the raw device file. -- Use a physical volume's raw device file for these two tasks only: -> When creating a physical volume. Here, you use the device file for the disk. For example, this might be /dev/rdsk/c3t2d0 if the disk were at card instance 3, target address 2, and device number 0. (The absence of a section number beginning with s indicates you are referring to
the entire disk.) -> When restoring your volume group configuration. For all other tasks, use the block device file. For example, when you add a physical volume to a volume group, you use the disk's block device file for the disk, such as /dev/dsk/c5t3d0.
-- vgextend: -- --------Extends a volume group by adding physical volumes to it. Examples: Add physical volumes /dev/dsk/c1d0s2 and /dev/dsk/c2d0s2 to volume group /dev/vg03: # vgextend /dev/vg03 /dev/dsk/c1d0s2 /dev/dsk/c2d0s2 # vgextend vg01 /dev/dsk/c0t4d0 -- pvcreate: -- --------Creates physical volume for use in a volume group. Examples: # pvcreate -f /dev/rdsk/c1d0s2 # ioscan -fnC disk # pvcreate -f /dev/rdsk/c0t1d0 -- lvcreate: -- --------Create logical volume in LVM volume group The lvcreate command creates a new logical volume within the volume group specified by vg_name. Up to 255 logical volumes can be created in one volume group SYNOPSIS /etc/lvcreate [-d schedule] {-l logical_extents_number | -L logical_volume_size} [-m mirror_copies] [-n lv_path] [-p permission] [-r relocate] [-s strict] [-C contiguous] [-M mirror_write_cache] [-c vol_group_name Examples: Create a logical volume in volume group /dev/vg02: # lvcreate /dev/vg02
Create a logical volume in volume group /dev/vg03 with nonstrict allocation policy: # lvcreate -s n /dev/vg03 Create a logical volume of size 100 MB in volume group /dev/vg03: # lvcreate -L 100 /dev/vg03 Create a logical volume of size 90 MB striped across 3 disks with a stripe size of 64 KB: # lvcreate -L 90 -i 3 -I 64 /dev/vg03 -- fstyp: -- -----Determines file system type. SYNOPSIS /usr/sbin/fstyp [-v] special The fstyp command allows the user to determine the file system type of a mounted or unmounted file system. special represents a device special file (for example: /dev/dsk/c1t6d0). The file system type is determined by reading the superblock of the supplied special file. If the superblock is read successfully, the command prints the file system type identifier on the standard output and exits with an exit status of 0. If the type of the file system cannot be identified, the error message unknown_fstyp (no matches) is printed and the exit status is 1. Exit status 2 is not currently returned, but is reserved for the situation where the file system matches more than one file system type. Any other error will cause exit status 3 to be returned. The file system type is determined by reading the superblock of the supplied special file. Examples: Find the type of the file system on a disk, /dev/dsk/c1t6d0: # fstyp /dev/dsk/c1t6d0 Find the type of the file system on a logical volume, /dev/vg00/lvol6: # fstyp /dev/vg00/lvol6 Find the file system type for a particular device file and also information about its super block: # fstyp -v /dev/dsk/c1t6d0
-- mkboot: -- ------mkboot is used to install or update boot programs on the specified device file. The position on device at which boot programs are installed depends on the disk layout of the device. mkboot examines device to discover the current layout and uses this as the default. If the disk is uninitialized, the default is LVM layout on PA-RISC and Whole Disk on Itanium(R)-based systems. The default can be overridden by the -l, -H, or -W options. Boot programs are stored in the boot which is similar to a file system. For a device to be bootable, the LIF the ISL (the initial system loader) and HPUX in addition, the device is an LVM physical volume, the LABEL
area in Logical Interchange Format (LIF), volume on that device must contain at least (the HP-UX bootstrap utility) LIF files. If, file must be present (see lvlnboot(1M) ).
For the VERITAS Volume Manager (VxVM) layout on the Itanium-based system architecture, the only relevant LIF file is the LABEL file. All other LIF files are ignored. VxVM uses the LABEL file when the system boots to determine the location of the root, stand, swap, and dump volumes. EXAMPLES Install default boot programs on the specified disk, treating it as an LVM disk: # mkboot -l /dev/dsk/c0t5d0 Use the existing layout, and install only SYSLIB and ODE files and preserve the EST file on the disk: # mkboot -i SYSLIB -i ODE -p EST /dev/rdsk/c0t5d0 Install only the SYSLIB file and retain the ODE file on the disk. Use the Whole Disk layout. Use the file /tmp/bootlf to get the boot programs rather than the default. (The -i ODE option will be ignored): # mkboot -b /tmp/bootlf -i SYSLIB -i ODE -p ODE -W /dev/rdsk/c0t5d0 Install EFI utilities to the EFI partition on an Itanium-based system, treating it as an LVM or VxVM disk: # mkboot -e -l /dev/dsk/c3t1d0 Create AUTO file with the string autofile command on a device. If the device is on an Itanium-based system, the file is created as /EFI/HPUX/AUTO in the EFI partition. If the device is on a PA-RISC system, the file is created as a LIF file in the boot area. # mkboot -a "autofile command" /dev/dsk/c2t0d0
-- bdf: -- ---Report number of free disk blocks. bdf prints out the amount of free disk space available on the specified filesystem (/dev/dsk/c0d0s0, for example) or on the file system in which the specified file ($HOME, for example) is contained. If no file system is specified, the free space on all of the normally mounted file systems is printed. The reported numbers are in kilobytes. Examples: # bdf oranh300:/home/se1223>bdf | more Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol3 434176 165632 266504 38% / /dev/vg00/lvol1 298928 52272 216760 19% /stand /dev/vg00/lvol8 2097152 1584488 508928 76% /var /dev/vg00/lvol11 524288 2440 490421 0% /var/tmp /dev/vg00/lvucmd 81920 1208 75671 2% /var/opt/universal /dev/vg00/lvol9 1048576 791925 240664 77% /var/adm /dev/vg00/lvol10 2064384 47386 1890941 2% /var/adm/crash /dev/vg00/lvol7 1548288 1262792 283320 82% /usr /dev/vg00/vsaunixlv 311296 185096 118339 61% /usr/local/vsaunix /dev/vg00/lvol4 1867776 5264 1849784 0% /tmp /dev/vg00/lvol6 1187840 757456 427064 64% /opt /dev/vg00/lvol5 262144 34784 225632 13% /home /dev/vg00/lvbeheer 131072 79046 48833 62% /beheer /dev/vg00/lvbeheertmp 655360 65296 553190 11% /beheer/tmp /dev/vg00/lvbeheerlog 524288 99374 398407 20% /beheer/log /dev/vg00/lvbeheerhistlog .. .. # bdf /tmp Filesystem /dev/vg00/lvol4
kbytes 1867776
used avail %used Mounted on 5264 1849784 0% /tmp
-- lvextend: -- --------Increase number of physical extents allocated to a logical volume. /etc/lvextend {-l logical_extents_number | -L logical_volume_size | -m mirror_copies} lv_path [physical_volume_path ... | physical_vol_group_name...]
lvextend increases the number of mirrored copies or the size of the lv_path parameter. The change is determined according to which command options are specified. WARNINGS The -m option cannot be used on HP-IB devices. EXAMPLES - Increase the number of the logical extents of a logical volume to one hundred: # lvextend -l 100 /dev/vg01/lvol3 - Increase the logical volume size to 400 Mbytes: # lvextend -L 400 /dev/vg01/lvol4 Allocate two mirrors (that is, three copies) for each logical extent of a logical volume: # lvextend -m 2 /dev/vg01/lvol5
-- extendfs: -- --------Extend file system size. /etc/extendfs [-q] [-v] [-s size] special If the original hfs filesystem image created on special does not make use of all of the available space, extendfs can be used to increase the capacity of an hfs filesystem by updating the filesystem structure to include the extra space. The command-line parameter special specifies the character device special file of either a logical volume or a disk partition. If special refers to a mounted filesystem, special must be un-mounted before extendfs can be run (see mount(1M)). The root filesystem cannot be extended using the extendfs command because the root filesystem is always mounted, and extendfs only works on unmounted filesystems. EXAMPLES To increase the capacity of a filesystem created on a logical volume, enter: # umount /dev/vg00/lvol1 # lvextend -L larger_size /dev/vg00/lvol1 # extendfs /dev/vg00/rlvol1 -- fsadm: -- ------
EXAMPLES Convert a HFS file system from a nolargefiles file system to a largefiles file system: # fsadm -F hfs -o largefiles /dev/vg02/lvol1 Display HFS relevant file system statistics: # fsadm -F hfs /dev/vg02/lvol1 -- diskinfo: -- --------diskinfo - describe characteristics of a disk device SYNOPSIS /etc/diskinfo [-b|-v] character_devicefile DESCRIPTION diskinfo determines whether the character special file named by character_devicefile is associated with a SCSI, CS/80, or Subset/80 disk drive; if so, diskinfo summarizes the disk's characteristics. Example: # diskinfo /dev/rdsk/c31t1d3 SCSI describe of /dev/rdsk/c31t1d3: vendor: IBM product id: 2105800 type: direct access size: 13671904 Kbytes bytes per sector: 512
35.4 Notes and further examples: ================================ Examples: More on how to create a filesystem on HP-UX: -----------------------------------------------------Example 1: ---------Here we repeat the essentials of section 35.2: Task 1. Estimate the Size Required for the Logical Volume Task 2. Determine If Sufficient Disk Space Is Available for the Logical Volume within Its Volume Group Task 3. Add a Disk to a Volume Group If Necessary Task 4. Create the Logical Volume
Use lvcreate to create a logical volume of a certain size in the above volume group. See lvcreate(1M) for details. Use lvcreate as in the following example: Create a logical volume of size 100 MB in volume group /dev/vg03: # lvcreate -L 100 /dev/vg03 -- Task 5. Create the New File System Create a file system using the newfs command. Note the use of the character device file. For example: # newfs -F hfs /dev/vg02/rlvol1 -- Task 6. mount the new local file system: Choose an empty directory to serve as the mount point for the file system. Use the mkdir command to create the directory if it does not currently exist. For example, enter: # mkdir /test Mount the file system using the mount command. Use the block device file name that contains the file system. You will need to enter this name as an argument to the mount command. For example, enter # mount /dev/vg01/lvol1 /test
Example 2: ---------This is an example of creating volume group vg01 & logical volume/partion data. Prepare for logical volume creation: root:/> mkdir /dev/vg01 root:/> mknod /dev/vg01/group c 64 0x010000 root:/> pvcreate -f /dev/rdsk/c0t5d0 Physical volume "/dev/rdsk/c0t5d0" has been successfully created. root:/> vgcreate vg01 /dev/dsk/c0t5d0 Volume group "/dev/vg01" has been successfully created. Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf root:/> vgdisplay -v vg01 root:/> lvcreate -L 100 -n data vg01 Logical volume "/dev/vg01/data" has been successfully created with character device "/dev/vg01/rdata". Create HFS file system
root:/> newfs -F hfs /dev/vg01/rdata Create Journal or Veritas file system root:/> newfs -F vxfs /dev/vg02/rdata
[email protected] Example 3: ---------To create a VxFS file system 12288 sectors in size on VxVM volume, enter: # mkfs -F vxfs /dev/vx/rdsk/diskgroup/volume 12288 To use mkfs to create a VxFS file system on /dev/rdsk/c0t6d0: # mkfs -F vxfs /dev/rdsk/c0t6d0 1024 To use mkfs to determine the command that was used to create the VxFS file system on /dev/rdsk/c0t6d0: # mkfs -F vxfs -m /dev/rdsk/c0t6d0 To create a VxFS file system on /dev/vgqa/lvol1, with a Version 4 disk layout and largefiles capability: # mkfs -F vxfs -o version=4,largefiles /dev/vgqa/lvol1 http://www.docs.hp.com/en/B2355-90672/index.html Example 4: ---------Example: Creating a Logical Volume Using HP-UX Commands To create a logical volume: Select one or more disks. ioscan(1M) shows the disks attached to the system and their device file names. Initialize each disk as an LVM disk by using the pvcreate command. For example, enter # pvcreate /dev/rdsk/c0t0d0 Note that using pvcreate will result in the loss of any existing data currently on the physical volume. You use the character device file for the disk. Once a disk is initialized, it is called a physical volume. - Pool the physical volumes into a volume group. To complete this step: Create a directory for the volume group. For example:
# mkdir /dev/vgnn Create a device file named group in the above directory with the mknod command. # mknod /dev/vgnn/group c 64 0xNN0000 The c following the device file name specifies that group is a character device file. The 64 is the major number for the group device file; it will always be 64. The 0xNN0000 is the minor number for the group file in hexadecimal. Note that each particular NN must be a unique number across all volume groups. For more information on mknod, see mknod(1M); for more information on major numbers and minor numbers, see Configuring HP-UX for Peripherals. Create the volume group specifying each physical volume to be included using vgcreate. For example: # vgcreate /dev/vgnn /dev/dsk/c0t0d0 Use the block device file to include each disk in your volume group. You can assign all the physical volumes to the volume group with one command. No physical volume can already be part of an existing volume group. Once you have created a volume group, you can now create a logical volume using lvcreate. For example: # lvcreate /dev/vgnn Using the above command creates the logical volume /dev/vgnn/lvoln with LVM automatically assigning the n in lvoln. When LVM creates the logical volume, it creates the block and character device files and places them in the directory /dev/vgnn.
VxFS can, theoretically, support files up to two terabytes in size because file system structures are no longer in fixed locations (see Chapter 2 �Disk Layout�). The maximum size tested and supported on HP-UX 11.x systems is one terabyte. Large files are files larger than two gigabytes in size. NOTE: Be careful when enabling large file capability. Applications and utilities such as backup may experience problems if they are not aware of large files. Creating a File System with Large Files You can create a file system with large file capability by entering the following command:
# mkfs -F vxfs -o largefiles special_device size Specifying largefiles sets the largefiles flag, which allows the file system to hold files up to one terabyte in size. Conversely, the default nolargefiles option clears the flag and limits files being created to a size of two gigabytes or less: # mkfs -F vxfs -o nolargefiles special_device size
Notes: -----Note 1: Create a System Mirror Disk: -----------------------------------This note describes how to configure LVM mirroring of a system disk. In this example the HP server is STSRV1, the primary boot device is SCSI=6 (/dev/dsk/c2t6d0) and the alternative mirrored bootdevice is SCSI=5 (/dev/dsk/c2t5d0). The following commands will do the trick: # # # # #
ioscan -fnC disk pvcreate -Bf /dev/rdsk/c2t5d0 mkboot -l /dev/rdsk/c2t5d0 mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c2t5d0 vgextend /dev/vg00 /dev/dsk/c2t5d0
# > > > >
for P in 1 2 3 4 5 6 7 8 9 10 do lvextend -m 1 /dev/vg00/lvol$P /dev/dsk/c2t5d0 sleep 1 done
Note 2: Create a System Mirror Disk: -----------------------------------# ioscan -fnC disk Class I H/W Path Driver S/W State H/W Type Description ===================================================================== disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE HP 73.4GMAN3735MC /dev/dsk/c1t2d0 /dev/rdsk/c1t2d0 disk 1 0/0/2/0.2.0 sdisk CLAIMED DEVICE HP 73.4GATLAS10K3_73_SCA /dev/dsk/c2t2d0 /dev/rdsk/c2t2d0 Note: c1t2d0 is the boot disk and c2t2d0 is the mirrored disk. 1) Initialize the disk and make it bootable pvcreate -B /dev/rdsk/c2t2d0 Note: the -B parameter tells pvcreate that this will be a bootable disk. 2) Add the physical volume to the volume group
vgextend /dev/vg00 /dev/dsk/c2t2d0 3) Use mkboot to place the boot utilities in the boot area and add the AUTO file. mkboot /dev/dsk/c2t2d0 mkboot -a "hpux -lq" /dev/rdsk/c2t2d0 4) Use mkboot to update the AUTO file on the primary boot disk. mkboot -a "hpux -lq" /dev/rdsk/c1t2d0 5) Mirror the stand, lvextend lvextend lvextend
root -m 1 -m 1 -m 1
and swap logical volumes /dev/vg00/lvol1 /dev/vg00/lvol2 /dev/vg00/lvol3
Note: LVM will resynchronize the new mirror copies. Repeat the lvextend for lvextend -m lvextend -m lvextend -m lvextend -m lvextend -m
all other logical volumes on the boot mirror. 1 /dev/vg00/lvol4 1 /dev/vg00/lvol5 1 /dev/vg00/lvol6 1 /dev/vg00/lvol7 1 /dev/vg00/lvol8
6) Modify your alternate boot path to point to the mirror copy of the boot disk. Note: Use the Hardware path for your new boot disk. setboot -a 0/0/2/0.2.0
Note 3: Increase a filesystem in HP-UX: --------------------------------------Example 1: ---------In this example, you would need to increase the file system size of /var by 10 MB, which actually needs to be rounded up to 12 MB. Increase /var Follow these steps to increase the size limit of /var. - Determine if any space is available for the /dev/vg00: # /sbin/vgdisplay /dev/vg00 The Free PE indicates the number of 4 MB extents available, in this case 79 (equivalent to 316 MB). - Change to single user state: /sbin/shutdown This allows /var to be unmounted.
- View mounted volumes: # /sbin/mount You see a display similar to the following: / on /dev/vg00/lvol1 defaults on Sat Mar 8 23:19:19 1997 /var on /dev/vg00/lvol7 defaults on Sat Mar 8 23:19:28 1997 # Determine which logical volume maps to /var. In this example, it is /dev/vg00/lvol7 - Unmount /var: # /sbin/umount /var This is required for the next step, because extendfs can only work on unmounted volumes. If you get a "device busy" error at this point, reboot the system and log on in single-user mode before continuing. - Extend the size of the logical volume: # /sbin/lvextend -L new_size_in_MB /dev/vg00/lvol7 For example, to make this volume 332 MB: # /sbin/lvextend -L 332 /dev/vg00/lvol7 To extend the file system size to the logical volume size: # /sbin/extendfs /dev/vg00/rlvol7 Mount /var: # /sbin/mount /var Go back to the regular init state: init 3 or init 4, or reboot. Example 2: ---------To increase the capacity of a file system created on a logical volume, enter: # umount /dev/vg00/lvol1 # lvextend -L larger_size /dev/vg00/lvol1 # extendfs -F hfs /dev/vg00/rlvol1 -- For operation like mkfs or extendfs, you should use raw device interface. # mount /dev/vg00/lvol1 mount_directory Example 3: --------->
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Date: 12/14/99 Document description: Extending /var, /usr, /tmp without Online JFS Document id: KBRC00000204 You may provide feedback on this document Extending /var, /usr, /tmp without Online JFS DocId: KBRC00000204 Updated: 12/14/99 1:14:29 PM PROBLEM Since /var, /usr, /tmp (and sometimes /opt) are always in use by the operating system, they cannot be unmounted with the umount command. In order to extend these filesystems, the system must be in single user mode. RESOLUTION This example will show how to extend /usr to 400MB without Online JFS 1.. Backup the filesystem before extending 2.. Display disk information on the logical volume lvdisplay -v /dev/vg00/lvol4 | more a.. Make sure this is enough Free PE's to increase this filesystem. b.. Make sure that allocation is NOT strict/contiguous. 3.. Reboot the machine shutdown -r now 4.. When prompted, press "ESC" to interrupt the boot. 5.. Boot from the primary device and invoke ISL interaction. bo pri isl NOTE: If prompted to interact with ISL, respond "y" 6.. Boot into single user mode hpux -is NOTE:Nothing will be mounted. 7.. Extend the logical volume that holds the filesystem. /sbin/lvextend -L 400 /dev/vg00/lvol4
> > 8.. Extend the file system. > > /sbin/extendfs -F hfs /dev/vg00/rlvol4 > > NOTE: The use of the character device. > > > 9.. Ensure the filesystem now reports to be the new size > > bdf > > > 10.. Reboot the system to its normal running state. > > shutdown -r now > > > The only thing is that you have to have contiguous lvols to do that. The best way is to do an Ignite make_tape_recovery -i for vg00 and then resize it when you recreate it. If you have vg00 on a seperate disk then it is real easy, the backup can run in the background, and the restore interactive will take about 2.5 hours for a 9GB root disk, you can make the lvols any size you want and it also puts it back in place in order so you save space. Example 4: ---------The right way to extend a file system with "OnLine jfs" is using the command "fsadm". For example, if you want to extend the fs /mk2/toto in the /dev/vgmk2/lvtoto in from 50Mbytes to 60 you must extend de logical volume # lvextend -L 60 /dev/vgmk2/lvtoto Now use fsadm ( I supose you have vxfs, if you are using hfs is not possible to increase on-line, or at least I don't know how ). # fsadm -F vxfs -b 61440 /mk2/toto You will have your fs increased on line ... be carefull if your fs is 100% occupied the comand fsadm will fail, you need some free space on the file system ( it depends on the fs type, size etc ..). In general, Online jfs should be increased in the following way: lvextend -L ???? /dev/vg??/lvol?? fsadm -F vxfs -b ????? / oranh300:/home/se1223>cat /etc/inittab | grep enab vxen::bootwait:/sbin/fs/vxfs/vxenablef -a Note 4:
------Extend OnlineJFS licenses on next D&ST servers: aavnh400 oranh503 oranh603 orazh500 orazh601 orazh602 commands are: swagentd -r swinstall -x mount_all_filesystems=false -x enforce_dependencies=true -s hpdepot.ao.nl.abnamro.com:/beheer/depot/OnlineJFS_License OnlineJFS swagentd -k
HP-UX errors: Error 23 filetable overflow: -----------------------------------------Error: 23 is a infamous error, as shown in this thread: thread: Doc ID: Note:1018306.102 Problem Description: ==================== You are backing up your database and are getting the following errors: HP-UX Error 23: file table overflow RMAN-569 file not found LEM-00031 file not found LEM-00033 lempgfm couldn't open message file RMAN indicates that Recovery Manager is complete, however the database and the catalog are not resync'd. Problem Explanation: ==================== Recovery Manager cannot find or open the message file. Search Words: ============= Recovery Manager, LEM-33, LEM-31, RMAN-00569, message file, lempgfm, error 23, HPUX error 23, HP-UX error 23 Solution Description: ===================== You may need to increase the value of the unix kernel parameter 'nfile'. Solution Explanation: ===================== 'nfile' needs to have a value in the thousands for a database server. If this parameter is < 1000, increase it to something like 5000 or greater. If there is enough memory on your system, this parameter can be set to values > 30000.
35.5 Some important filesystem related kernel params: =====================================================
nfile: -----nfile defines the maximum number of files that can be open simultaneously, systemwide, at any given time. Acceptable Values: Minimum 14 Maximum Memory limited Default ((16*(Nproc+16+MaxUsers)/10)+32+2*(Npty+Nstrpty) Specify integer value or use integer formula expression. For more information, see Specifying Parameter Values. Description nfile defines the maximum number files that can be open at any one time, systemwide. It is the number of slots in the file descriptor table. Be generous with this number because the required memory is minimal, and not having enough slots restricts system processing capacity. Related Parameters and System Factors The value used for nfile must be sufficient to service the number of users and processes allowed by the combination of nproc, maxusers, npty , and nstrpty. Every process uses at least three file descriptors per process (standard input, standard output, and standard error). Every process has two pipes per process (one per side), each of which requires a pty. Stream pipes also use s treams ptys which are limited by nstrpty.
35.6 HP-UX kernel parameters: ============================= Take especially notice of the parameters nfile, nflocks, ninodes, nprocs. They determine how many open files, open locks, simultaneous processes are possible *system-wide*. Too low values may result in HP-UX errors when dealing with larger databases, huge App Servers and the like. Entering Values: Use the kcweb web interface or the kmtune command to view and change values. kcweb is described in the kcweb(1M) manpage and in the program's help topics. You can run kcweb from the command line or from the System Administration Manager (SAM); see sam(1M). You run kmtune from
the command line; see kmtune(1M) for details.
Accounting acctresume Resume accounting when free space on the file system where accounting log files reside rises above acctresume plus minfree percent of total usable file system size. Manpage: acctsuspend(5). Accounting acctsuspend Suspend accounting when free space on the file system where accounting log files reside drops below acctsuspend plus minfree percent of total usable file system size. Manpage: acctsuspend(5). Asynchronous I/O aio_listio_max Maximum number of POSIX asynchronous I/O operations allowed in a single lio_listio() call. Manpage: aio_listio_max(5). Asynchronous I/O aio_max_ops System-wide maximum number of POSIX asynchronous I/O operations allowed at one time. Manpage: aio_max_ops(5). Asynchronous I/O aio_physmem_pct Maximum percentage of total system memory that can be locked for use in POSIX asynchronous I/O operations. Manpage: aio_physmem_pct(5). Asynchronous I/O aio_prio_delta_max Maximum priority offset (slowdown factor) allowed in a POSIX asynchronous I/O control block (aiocb). Manpage: aio_prio_delta_max(5). Memory Paging allocate_fs_swapmap Enable or disable preallocation of file system swap space when swapon() is called as opposed to allocating swap space when malloc() is called. Enabling allocation reduces risk of insufficient swap space and is used primarily where high availability is important. Manpage: allocate_fs_swapmap(5). Kernel Crash Dump alwaysdump Select which classes of system memory pages are to be dumped if a kernel panic occurs. Manpage: alwaysdump(5). Spinlock Pool bufcache_hash_locks Buffer-cache spinlock pool. NO MANPAGE. File System: Buffer bufpages Number of 4 KB pages in file system static buffer cache. Manpage: bufpages(5). Spinlock Pool
chanq_hash_locks Channel queue spinlock pool. Manpage: chanq_hash_locks(5). IPC: Share core_addshmem_read Flag to include readable shared memory in a process core dump. Manpage: core_addshmem_read(5). IPC: Share core_addshmem_write Flag to include read/write shared memory in a process core dump. Manpage: core_addshmem_write(5). Miscellaneous: Links create_fastlinks Create fast symbolic links using a newer, more efficient format to improve access speed by reducing disk block accesses during path name look-up sequences. Manpage: create_fastlinks(5). File System: Buffer dbc_max_pct Maximum percentage of memory for dynamic buffer cache. Manpage: dbc_max_pct(5). File System: Buffer dbc_min_pct Minimum percentage of memory for dynamic buffer cache. Manpage: dbc_min_pct(5). Miscellaneous: Disk I/O default_disk_ir Immediate reporting for disk writes; whether a write() returns immediately after the data is placed in the disk's write buffer or waits until the data is physically stored on the disk media. Manpage: default_disk_ir(5). File System: Buffer disksort_seconds Maximum wait time for disk requests. NO MANPAGE. Miscellaneous: Disk I/O dma32_pool_size Amount of memory to set aside for 32-bit DMA (bytes). Manpage: dma32_pool_size(5). Spinlock Pool dnlc_hash_locks Number of locks for directory cache synchronization. NO MANPAGE. Kernel Crash Dump dontdump Select which classes of system memory pages are not to be dumped if a kernel panic occurs. Manpage: dontdump(5). Miscellaneous: Clock dst Enable/disable daylight savings time. Manpage: timezone(5). Miscellaneous: IDS enable_idds Flag to enable the IDDS daemon, which gathers data for IDS/9000. Manpage:
enable_idds(5). Miscellaneous: Memory eqmemsize Number of pages of memory to be reserved for equivalently mapped memory, used mostly for DMA transfers. Manpage: eqmemsize(5). ProcessMgmt: Process executable_stack Allows or denies program execution on the stack. Manpage: executable_stack(5). File System: Write fs_async Enable/disable asynchronous writes of file system data structures to disk. Manpage: fs_async(5). Spinlock Pool ftable_hash_locks File table spinlock pool. NO MANPAGE. Spinlock Pool hdlpreg_hash_locks Set the size of the pregion spinlock pool. Manpage: hdlpreg_hash_locks(5). File System: Read hfs_max_ra_blocks The maximum number of read-ahead blocks that the kernel may have outstanding for a single HFS file system. Manpage: hfs_max_ra_blocks(5). File System: Read hfs_max_revra_blocks The maximum number of reverse read-ahead blocks that the kernel may have outstanding for a single HFS file system. Manpage: hfs_max_revra_blocks(5). File System: Read hfs_ra_per_disk The amount of HFS file system read-ahead per disk drive, in KB. Manpage: hfs_ra_per_disk(5). File System: Read hfs_revra_per_disk The amount of memory (in KB) for HFS reverse read-ahead operations, per disk drive. Manpage: hfs_revra_per_disk(5). File System: Read hp_hfs_mtra_enabled Enable or disable HFS multithreaded read-ahead. NO MANPAGE. Kernel Crash Dump initmodmax Maximum size of the dump table of dynamically loaded kernel modules. Manpage: initmodmax(5). Spinlock Pool io_ports_hash_locks I/O port spinlock pool. NO MANPAGE. Miscellaneous: Queue ksi_alloc_max Maximum number of system-wide queued signals that can be allocated. Manpage:
ksi_alloc_max(5). Miscellaneous: Queue ksi_send_max Maximum number of queued signals that a process can send and have pending at one or more receivers. Manpage: ksi_send_max(5). ProcessMgmt: Memory maxdsiz Maximum process data storage segment space that can be used for statics and strings, as well as dynamic data space allocated by sbrk() and malloc() (32-bit processes). Manpage: maxdsiz(5). ProcessMgmt: Memory maxdsiz_64bit Maximum process data storage segment space that can be used for statics and strings, as well as dynamic data space allocated by sbrk() and malloc() (64-bit processes). Manpage: maxdsiz(5). File System: Open/Lock maxfiles Soft limit on how many files a single process can have opened or locked at any given time. Manpage: maxfiles(5). File System: Open/Lock maxfiles_lim Hard limit on how many files a single process can have opened or locked at any given time. Manpage: maxfiles_lim(5). ProcessMgmt: Memory maxrsessiz Maximum size (in bytes) of the RSE stack for any user process on the IPF platform. Manpage: maxrsessiz(5). ProcessMgmt: Memory maxrsessiz_64bit Maximum size (in bytes) of the RSE stack for any user process on the IPF platform. Manpage: maxrsessiz(5). ProcessMgmt: Memory maxssiz Maximum dynamic storage segment (DSS) space used for stack space (32-bit processes). Manpage: maxssiz(5). ProcessMgmt: Memory maxssiz_64bit Maximum dynamic storage segment (DSS) space used for stack space (64-bit processes). Manpage: maxssiz(5). ProcessMgmt: Memory maxtsiz Maximum allowable process text segment size, used by unchanging executable-code (32-bit processes). Manpage: maxtsiz(5). ProcessMgmt: Memory maxtsiz_64bit Maximum allowable process text segment size, used by unchanging executable-code (64-bit processes). Manpage: maxtsiz(5).
ProcessMgmt: Process maxuprc Maximum number of processes that any single user can have running at the same time, including login shells, user interface processes, running programs and child processes, I/O processes, etc. If a user is using multiple, simultaneous logins under the same login name (user ID) as is common in X Window, CDE, or Motif environments, all processes are combined, even though they may belong to separate process groups. Processes that detach from their parent process group, where that is possible, are not counted after they detach (line printer spooler jobs, certain specialized applications, etc.). Manpage: maxuprc(5). Miscellaneous: Users maxusers Maximum number of users expected to be logged in on the system at one time; used by other system parameters to allocate system resources. Manpage: maxusers(5). File System: LVM maxvgs Maximum number of volume groups configured by the Logical Volume Manager on the system. Manpage: maxvgs(5). Accounting max_acct_file_size Maximum size of the accounting file. Manpage: max_acct_file_size(5). Asynchronous I/O max_async_ports System-wide maximum number of ports to the asynchronous disk I/O driver that processes can have open at any given time. Manpage: max_async_ports(5). Memory Paging max_mem_window Maximum number of group-private 32-bit shared memory windows. Manpage: max_mem_window(5). ProcessMgmt: Threads max_thread_proc Maximum number of threads that any single process can create and have running at the same time. Manpage: max_thread_proc(5). IPC: Message mesg Enable or disable IPC messages at system boot time. Manpage: mesg(5). Kernel Crash Dump modstrmax Maximum size, in bytes, of the savecrash kernel module table that contains module names and their locations in the file system. Manpage: modstrmax(5). IPC: Message msgmap Size of free-space resource map for allocating shared memory space for messages. Manpage: msgmap(5). IPC: Message msgmax System-wide maximum size (in bytes) for individual messages. Manpage: msgmax(5).
IPC: Message msgmnb Maximum combined size (in bytes) of all messages that can be queued simultaneously in a message queue. Manpage: msgmnb(5). IPC: Message msgmni Maximum number of message queues allowed on the system at any given time. Manpage: msgmni(5). IPC: Message msgseg Maximum number of message segments that can exist on the system. Manpage: msgseg(5). IPC: Message msgssz Message segment size in bytes. Manpage: msgssz(5). IPC: Message msgtql Maximum number of messages that can exist on the system at any given time. Manpage: msgtql(5). File System: Buffer nbuf System-wide number of static file system buffer and cache buffer headers. Manpage: nbuf(5). Miscellaneous: CD ncdnode Maximum number of entries in the vnode table and therefore the maximum number of open CD-ROM file system nodes that can be in memory. Manpage: ncdnode(5). Miscellaneous: Terminal nclist Maximum number of cblocks available for data transfers through tty and pty devices. Manpage: nclist(5). File System: Open/Lock ncsize Inode space needed for directory name lookup cache (DNLC). NO MANPAGE. File System: Open/Lock nfile Maximum number of files that can be open simultaneously on the system at any given time. Manpage: nfile(5). File System: Open/Lock nflocks Maximum combined number of file locks that are available system-wide to all processes at one time. Manpage: nflocks(5). File System: Open/Lock ninode Maximum number of open inodes that can be in memory. Manpage: ninode(5).
ProcessMgmt: Threads nkthread Maximum number of kernel threads allowed on the system at the same time. Manpage: nkthread(5). ProcessMgmt: Process nproc Defines the maximum number of processes that can be running simultaneously on the entire system, including remote execution processes initiated by other systems via remsh or other networking commands. Manpage: nproc(5). Miscellaneous: Terminal npty Maximum number of pseudo-tty entries allowed on the system at any one time. Manpage: npty(5). Streams NSTREVENT Maximum number of outstanding streams bufcalls that are allowed to exist at any given time on the system. This number should be equal to or greater than the maximum bufcalls that can be generated by the combined total modules pushed onto any given stream, and serves to limit run-away bufcalls. Manpage: nstrevent(5). Miscellaneous: Terminal nstrpty System-wide maximum number of streams-based pseudo-ttys that are allowed on the system. Manpage: nstrpty(5). Streams nstrpty System-wide maximum number of streams-based pseudo-ttys that are allowed on the system. Manpage: nstrpty(5). Streams NSTRPUSH Maximum number of streams modules that are allowed to exist in any single stream at any one time on the system. This provides a mechanism for preventing a software defect from attempting to push too many modules onto a stream, but it is not intended as adequate protection against malicious use of streams. Manpage: nstrpush(5). Streams NSTRSCHED Maximum number of streams scheduler daemons that are allowed to run at any given time on the system. This value is related to the number of processors installed in the system. Manpage: nstrsched(5). Miscellaneous: Terminal nstrtel Number of telnet session device files that are available on the system. Manpage: nstrtel(5). Memory Paging nswapdev Maximum number of devices, system-wide, that can be used for device swap. Set to match actual system configuration. Manpage: nswapdev(5). Memory Paging
nswapfs Maximum number of mounted file systems, system-wide, that can be used for file system swap. Set to match actual system configuration. Manpage: nswapfs(5). Miscellaneous: Memory nsysmap Number of entries in the kernel dynamic memory virtual address space resource map (32-bit processes). Manpage: nsysmap(5). Miscellaneous: Memory nsysmap64 Number of entries in the kernel dynamic memory virtual address space resource map (64-bit processes). Manpage: nsysmap(5). Miscellaneous: Disk I/O o_sync_is_o_dsync Specifies whether an open() or fcntl() with the O_SYNC flag set can be converted to the same call with the O_DSYNC flag instead. This controls whether the function can return before updating the file access. NO MANPAGE. ProcessMgmt: Memory pa_maxssiz_32bit Maximum size (in bytes) of the stack for a user process running under the PA-RISC emulator on IPF. Manpage: pa_maxssiz(5). ProcessMgmt: Memory pa_maxssiz_64bit Maximum size (in bytes) of the stack for a user process running under the PA-RISC emulator on IPF. Manpage: pa_maxssiz(5). Spinlock Pool pfdat_hash_locks Pfdat spinlock pool. Manpage: pfdat_hash_locks(5). Miscellaneous: Disk I/O physical_io_buffers Total buffers for physical I/O operations. Manpage: physical_io_buffers(5). Spinlock Pool region_hash_locks Process-region spinlock pool. Manpage: region_hash_locks(5). Memory Paging remote_nfs_swap Enable or disable swap to mounted remote NFS file system. Used on cluster clients for swapping to NFS-mounted server file systems. Manpage: remote_nfs_swap(5). Miscellaneous: Schedule rtsched_numpri Number of distinct real-time interrupt scheduling priority levels are available on the system. Manpage: rtsched_numpri(5). Miscellaneous: Terminal scroll_lines Defines the number of lines that can be scrolled on the internal terminal emulator (ITE) system console. Manpage: scroll_lines(5). File System: SCSI
scsi_maxphys Maximum record size for the SCSI I/O subsystem, in bytes. Manpage: scsi_maxphys(5). File System: SCSI scsi_max_qdepth Maximum number of SCSI commands queued up for SCSI devices. Manpage: scsi_max_qdepth(5). ProcessMgmt: Process secure_sid_scripts Controls whether setuid and setgid bits on scripts are honored. Manpage: secure_sid_scripts(5). IPC: Semaphore sema Enable or disable IPC semaphores at system boot time. Manpage: sema(5). IPC: Semaphore semaem Maximum value by which a semaphore can be changed in a semaphore �undo� operation. Manpage: semaem(5). IPC: Semaphore semmni Maximum number of sets of IPC semaphores allowed on the system at any one time. Manpage: semmni(5). IPC: Semaphore semmns Maximum number of individual IPC semaphores available to system users, systemwide. Manpage: semmns(5). IPC: Semaphore semmnu Maximum number of processes that can have undo operations pending on any given IPC semaphore on the system. Manpage: semmnu(5). IPC: Semaphore semmsl Maximum number of individual System V IPC semaphores per semaphore identifier. Manpage: semmsl(5). IPC: Semaphore semume Maximum number of IPC semaphores that a given process can have undo operations pending on. Manpage: semume(5). IPC: Semaphore semvmx Maximum value any given IPC semaphore is allowed to reach (prevents undetected overflow conditions). Manpage: semvmx(5). Miscellaneous: Web sendfile_max The amount of buffer cache that can be used by the sendfile() system call on HPUX web servers. Manpage: sendfile_max(5).
IPC: Share shmem Enable or disable shared memory at system boot time. Manpage: shmem(5). IPC: Share shmmax Maximum allowable shared memory segment size (in bytes). Manpage: shmmax(5). IPC: Share shmmni Maximum number of shared memory segments allowed on the system at any given time. Manpage: shmmni(5). IPC: Share shmseg Maximum number of shared memory segments that can be attached simultaneously to any given process. Manpage: shmseg(5). Streams STRCTLSZ Maximum number of control bytes allowed in the control portion of any streams message on the system. Manpage: strctlsz(5). Streams streampipes Force all pipes to be streams-based. Manpage: streampipes(5). Streams STRMSGSZ Maximum number of bytes that can be placed in the data portion of any streams message on the system. Manpage: strmsgsz(5). File System: SCSI st_ats_enabled Flag whether to reserve a tape device on open. Manpage: st_ats_enabled(5). File System: SCSI st_fail_overruns SCSI tape read resulting in data overrun causes failure. Manpage: st_fail_overruns(5). File System: SCSI st_large_recs Enable large record support for SCSI tape. Manpage: st_large_recs(5). Memory Paging swapmem_on Enable or disable pseudo-swap allocation. This allows systems with large installed memory to allocate memory space as well as disk swap space for virtual memory use instead of restricting availability to defined disk swap area. Manpage: swapmem_on(5). Memory Paging swchunk Amount of space allocated for each chunk of swap area. Chunks are allocated from device to device by the kernel. Changing this parameter requires extensive knowledge of system internals. Without such knowledge, do not change this parameter from the normal default value. Manpage: swchunk(5).
Spinlock Pool sysv_hash_locks System V interprocess communication spinlock pool. Manpage: sysv_hash_locks(5). Miscellaneous: Network tcphashsz TCP hash table size, in bytes. Manpage: tcphashsz(5). ProcessMgmt: CPU timeslice Maximum time a process can use the CPU until it is made available to the next process having the same process execution priority. This feature also prevents runaway processes from causing system lock-up. Manpage: timeslice(5). Miscellaneous: Clock timezone The offset between the local time zone and Coordinated Universal Time (UTC), often called Greenwich Mean Time or GMT. Manpage: timezone(5). Miscellaneous: Memory unlockable_mem Amount of system memory to be reserved for system overhead and virtual memory management, that cannot be locked by user processes. Manpage: unlockable_mem(5). Spinlock Pool vnode_cd_hash_locks Vnode clean/dirty spinlock pool. NO MANPAGE. Spinlock Pool vnode_hash_locks Vnode spinlock pool. NO MANPAGE. Memory Paging: Size vps_ceiling Maximum system-selected page size (in KB) if the user does not specify a page size. Manpage: vps_ceiling(5). Memory Paging: Size vps_chatr_ceiling Maximum page size a user can specify with the chatr command in a program. Manpage: vps_chatr_ceiling(5). Memory Paging: Size vps_pagesize Minimum user page size (in KB) if no page size is specified using chatr. Manpage: vps_pagesize(5). File System: Journaled vxfs_max_ra_kbytes Maximum amount of read-ahead data, in KB, that the kernel may have outstanding for a single VxFS file system. Manpage: vxfs_max_ra_kbytes(5). File System: Read vxfs_max_ra_kbytes Maximum amount of read-ahead data, in KB, that the kernel may have outstanding for a single VxFS file system. Manpage: vxfs_max_ra_kbytes(5).
File System: Journaled vxfs_ra_per_disk Maximum amount of VxFS file system read-ahead per disk, in KB. Manpage: vxfs_ra_per_disk(5). File System: Read vxfs_ra_per_disk Maximum amount of VxFS file system read-ahead per disk, in KB. Manpage: vxfs_ra_per_disk(5). File System: Journaled vx_fancyra_enable Enable or disable VxFS file system read-ahead. NO MANPAGE. File System: Journaled vx_maxlink Number of subdirectories created within a directory. NO MANPAGE. File System: Journaled vx_ncsize Memory space reserved for VxFS directory path name cache. Manpage: vx_ncsize(5). File System: Journaled vx_ninode Number of entries in the VxFS inode table. NO MANPAGE
36. Some remarks about VI: ========================== Before you run vi: -----------------If you've connected to a central UCS computer to use vi, first tell that host about your communications software (e.g., NCSA Telnet). At IUB, your software will typically emulate a VT-100 terminal. To find out what shell program you use, type: echo $SHELL Then if you use ksh, bash, or sh, type: TERM=vt100; export TERM If you use csh or tcsh, type: set term = vt100 You can automate this task by adding the appropriate command to your default command shell's configuration file. Using vi modes: ---------------
Vi has three "modes": edit, insert, and colon. - Edit mode (press Esc) Vi enters edit mode by default when it starts up. Edit mode allows you to move the cursor and edit the text buffer. - Insert mode (press i) Insert mode "drops" the cursor at a specific point in the buffer, allowing you to insert text. To enter insert mode, position the cursor where you want to place text and press i. If you make a typing mistake, press ESC to return to edit mode and then reposition the cursor at the error, and press i to get back to insert mode. - Colon mode (press : with a command) You enter colon mode from edit mode by typing a colon followed by a command. Some useful commands are: :w :w newname :r :r oldname :q! :wq :e filename :e #
Write buffer to the current filename. Write buffer to file newname. Read the current filename into the buffer. Read the file oldname into the buffer. Quit vi without saving buffer. Write buffer to current filename and quit vi. Close current buffer and edit (open) filename. Close current buffer and edit (open) previous file.
Search and Replace: ------------------Replace: Same as with sed, Replace OLD with NEW: ESC, First occurrence on current line: Globally (all) on current line: Between two lines #,#: Every occurrence in file:
:s/OLD/NEW :s/OLD/NEW/g :#,#s/OLD/NEW/g :%s/OLD/NEW/g
The VI editor has two kinds of searches: string and character. For a string search, the / and ? commands are used. When you start these commands, the command just typed will be shown on the bottom line, where you type the particular string to look for. These two commands differ only in the direction where the search takes place. The / command searches forwards (downwards) in the file, while the ? command searches backwards (upwards) in the file. The n and N commands repeat the previous search command in the same or opposite direction, respectively. Some characters have special meanings to VI, so they must be preceded by a backslash (\) to be included as part of the search expression.
36. ulimit: =========== limit, ulimit, unlimit - set or get limitations on the to the current shell and its descendents. /usr/bin/ulimit Example 1:
system resources available
Limiting the stack size
To limit the stack size to 512 kilobytes: example% ulimit -s 512 example% ulimit -a time(seconds) unlimited file(blocks) 100 data(kbytes) 523256 stack(kbytes) 512 coredump(blocks) 200 nofiles(descriptors) 64 memory(kbytes) unlimited ULIMIT - Sets the file size limit for the login. Units are disk blocks. Default is zero (no limit). Be sure to specify even numbers, as the ULIMIT variable accepts a number of 512byte blocks. $ $ $ $
ulimit -a # Display limits for your session under sh or ksh limit # Display limits for your session under csh or tcsh ulimit -c SIZE_IN_BLOCKS # Limit core size under sh or ksh limit coredumpsize SIZE_IN_KB # Limit core size under csh or tcsh
If you see a core file lying around, just type "file core" to get some details about it. Example: $ file core core:ELF-64 core file - PA-RISC 2.0 from 'sqlplus' - received SIGABRT Run the Unix process debugger to obtain more information about where and why the process abended. This information is normally requested by Oracle Support for in-depth analysis of the problem. Some example: Solaris: $ gdb $ORACLE_HOME/bin/sqlplus core bt # backtrace of all stack frames quit HP-UX, Solaris, etc: $ adb $ORACLE_HOME/bin/sqlplus core $c $q Sequent: $ debug -c core $ORACLE_HOME/bin/sqlplus debug> stack
debug> quit AIX: Purpose Sets or reports user resource limits. Syntax ulimit [ -H ] [ -S ] [ -a ] [ -c ] [ -d ] [ [ Limit ]
-f ] [ -m ] [ -n ] [ -s ] [ -t ]
Description The ulimit command sets or reports user process resource limits, as defined in the /etc/security/limits file. This file contains these default limits: fsize = 2097151 core = 2097151 cpu = -1 data = 262144 rss = 65536 stack = 65536 nofiles = 2000 These values are used as default settings when a new user is added to the system. The values are set with the mkuser command when the user is added to the system, or changed with the chuser command. Limits are categorized as either soft or hard. With the ulimit command, you can change your soft limits, up to the maximum set by the hard limits. You must have root user authority to change resource hard limits. Many systems do not contain one or more of these limits. The limit for a specified resource is set when the Limit parameter is specified. The value of the Limit parameter can be a number in the unit specified with each resource, or the value unlimited. To set the specific ulimit to unlimited, use the word unlimited Note: Setting the default limits in the /etc/security/limits file sets system wide limits, not just limits taken on by a user when that user is created. The current resource limit is printed when you omit the Limit parameter. The soft limit is printed unless you specify the -H flag. When you specify more than one resource, the limit name and unit is printed before the value. If no option is given, the -f flag is assumed. Since the ulimit command affects the current shell environment, it is provided as a shell regular built-in command. If this command is called in a separate command execution environment, it does not affect the file size limit of the caller's environment. This would be the case in the following examples:
nohup ulimit -f 10000 env ulimit 10000 Once a hard limit has been decreased by a process, it cannot be increased without root privilege, even to revert to the original limit. For more information about user and system resource limits, refer to the getrlimit, setrlimit, or vlimit subroutine in AIX 5L Version 5.2 Technical Reference: Base Operating System and Extensions Volume 1. Flags -a Lists all of the current resource limits. -c Specifies the size of core dumps, in number of 512-byte blocks. -d Specifies the size of the data area, in number of K bytes. -f Sets the file size limit in blocks when the Limit parameter is used, or reports the file size limit if no parameter is specified. The -f flag is the default. -H Specifies that the hard limit for the given resource is set. If you have root user authority, you can increase the hard limit. Anyone can decrease it. -m Specifies the size of physical memory, in number of K bytes. -n Specifies the limit on the number of file descriptors a process may have. -s Specifies the stack size, in number of K bytes. -S Specifies that the soft limit for the given resource is set. A soft limit can be increased up to the value of the hard limit. If neither the -H nor -S flags are specified, the limit applies to both. -t Specifies the number of seconds to be used by each process. You can check the current ulimit settings using the ulimit -a command, and at least the following three commands should be run, as the user account that will launch Java: ulimit -m unlimited ulimit -d unlimited ulimit -f unlimited
===================================== 37. RAM disks: ===================================== 37.1 AIX: ========= Example: -------# mkramdisk SIZE /dev/rramdiskxx # mkfs -V jfs /dev/ramdiskxx
# mount -V jfs -o nointegrity /dev/ramdiskxx /whatever_mountpoint mkramdisk Command: -----------------Purpose Creates a RAM disk using a portion of RAM that is accessed through normal reads and writes. Syntax mkramdisk [ -u ] size[ M | G ] Description The mkramdisk command is shipped as part of bos.rte.filesystems, which allows the user to create a RAM disk. Upon successful execution of the mkramdisk command, a new RAM disk is created, a new entry added to /dev, the name of the new RAM disk is written to standard output, and the command exits with a value of 0. If the creation of the RAM disk fails, the command prints an internalized error message, and the command will exit with a nonzero value. The size can be specified in terms of MB or GB. By default, it is in 512 byte blocks. A suffix of M will be used to specify size in megabytes and G to specify size in gigabytes. The names of the RAM disks are in the form of /dev/rramdiskx where x is the logical RAM disk number (0 through 63). The mkramdisk command also creates block special device entries (for example, /dev/ramdisk5) although use of the block device interface is discouraged because it adds overhead. The device special files in /dev are owned by root with a mode of 600. However, the mode, owner, and group ID can be changed using normal system commands. Up to 64 RAM disks can be created. Note: The size of a RAM disk cannot be changed after it is created. The mkramdisk command is responsible for generating a major number, loading the ram disk kernel extension, configuring the kernel extension, creating a ram disk, and creating the device special files in /dev. Once the device special files are created, they can be used just like any other device special files through normal open, read, write, and close system calls. RAM disks can be removed by using the rmramdisk command. RAM disks are also removed when the machine is rebooted. By default, RAM disk pages are pinned. Use the -u flag to create RAM disk pages that are not pinned. Flags -u Specifies that the ram disk that is created will not be pinned. By default, the ram disk will be pinned.
Parameters size Indicates the amount of RAM (in 512 byte increments) to use for the new RAM disk. For example, typing: # mkramdisk 1 creates a RAM disk that uses 512 bytes of RAM. To create a RAM disk that uses approximately 20 MB of RAM, type: # mkramdisk 40000 Exit Status The following exit values are returned: 0 Successful completion. >0 An error occurred. Examples: To create a new ram disk using a default 512-byte block size, and the size is 500 MBs (1048576 * 512), enter: # mkramdisk 1048576 /dev/rramdisk0 The /dev/rramdisk0 ramdisk is created. To create a new ramdisk with a size of 500 Megabytes, enter: # mkramdisk 500M /dev/rramdisk0 The /dev/rramdisk0 ramdisk is created. Note that the ramdisk has the same size as example 1 above. To create a new ram disk with a 2-Gigabyte size, enter: # mkramdisk 2G /dev/rramdisk0 To set up a RAM disk that is approximately 20 MB in size and create a JFS file system on that RAM disk, enter the following: # # # # #
mkramdisk 40000 ls -l /dev | grep ram mkfs -V jfs /dev/ramdiskx mkdir /ramdisk0 mount -V jfs -o nointegrity /dev/ramdiskx /ramdiskx
where x is the logical RAM disk number. Note: If using file system on a RAM disk, the RAM disk must be pinned.
37.2 Linux: =========== Redhat: It is very easy to use a ramdisk. First of all, the default installation of RedHat >= 6.0 comes with ramdisk support. All you have to do is format a ramdisk and then mount it to a directory. To find out all the ramdisks you have available, do a "ls -al /dev/ram*". This gives you the preset ramdisks available to your liking. These ramdisks don't actually grab memory until you use them somehow (like formatting them). Here is a very simple example of how to use a ramdisk. # create a mount point: mkdir /tmp/ramdisk0 # create a filesystem: mke2fs /dev/ram0 # mount the ramdisk: mount /dev/ram0 /tmp/ramdisk0 Those three commands will make a directory for the ramdisk , format the ramdisk (create a filesystem), and mount the ramdisk to the directory "/tmp/ramdisk0". Now you can treat that directory as a pretend partition! Go ahead and use it like any other directory or as any other partition. If the formatting of the ramdisk faild then you might have no support for ramdisk compiled into the Kernel. The Kernel configuration option for ramdisk is CONFIG_BLK_DEV_RAM . The default size of the ramdisk is 4Mb=4096 blocks. You saw what ramdisk size you got while you were running mke2fs. mke2fs /dev/ram0 should have produced a message like this: mke2fs 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09 Linux ext2 filesystem format Filesystem label= 1024 inodes, 4096 blocks 204 blocks (4.98%) reserved for the super user First data block=1 Block size=1024 (log=0) Fragment size=1024 (log=0) 1 block group 8192 blocks per group, 8192 fragments per group 1024 inodes per group Running df -k /dev/ram0 tells you how much of that you can really use (The filesystem takes also some space): >df -k /dev/ram0 Filesystem 1k-blocks /dev/ram0 3963
Used Available Use% Mounted on 13 3746 0% /tmp/ramdisk0
What are some catches? Well, when the computer reboots, it gets wiped. Don't put any data there that isn't copied somewhere else. If you make changes to that directory, and you need to keep
the changes, figure out some way to back them up. - Changing the size of the ramdisks To use a ram disk you either need to have ramdisk support compiled into the Kernel or you need to compile it as loadable module. The Kernel configuration option is CONFIG_BLK_DEV_RAM . Compiling the ramdisk a loadable module has the advantage that you can decide at load time what the size of your ramdisks should be. Okay, first the hard way. Add this line to your lilo.conf file: ramdisk_size=10000 (or ramdisk=10000 for old kernels) and it will make the default ramdisks 10 megs after you type the "lilo" command and reboot the computer. Here is an example of my /etc/lilo.conf file. boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 image=/boot/vmlinuz label=linux root=/dev/hda2 read-only ramdisk_size=10000 Actually, I got a little over 9 megs of usable space as the filesystem takes also a little space. When you compile ramdisk support as loadable module then you can decide at load time what the size should be. This is done either with an option line in the /etc/conf.modules file: options rd rd_size=10000 or as a command line parameter to ismod: insmod rd rd_size=10000 Here is an example which shows how to use the module: Unmount the ramdisk mounted in the previous chapter, umount /tmp/ramdisk0 . Unload the module (it was automatically loaded in the previous chapter), rmmod rd Load the ramdisk module and set the size to 20Mb, insmod rd rd_size=20000 create a file system, mke2fs /dev/ram0 mount the ramdisk, mount /dev/ram0 /tmp/ramdisk0 - Example of how to use a RamDisk for a webserver. Okay, here is an example of how to use 3 ramdisks for a webserver. Let us say you are 99% confident that your default installation of Apache for RedHat 6.0 won't use more than 9 megs for its cgi-scripts, html, and icons. Here is how to install one. First, issue this command to move the real copy of the document root directory of your webserver to a different place. Also, make the directories to mount the ramdisks . mv /home/httpd/ /home/httpd_real
mkdir mkdir mkdir mkdir
/home/httpd /home/httpd/cgi-bin /home/httpd/html /home/httpd/icons
Then, add these commands to the start procedure in your /etc/rc.d/init.d/httpd.init (or where ever the httpd gets started on your system): ### Make the /sbin/mkfs -t ext2 /sbin/mkfs -t ext2 /sbin/mkfs -t ext2
ramdisk partitions /dev/ram0 /dev/ram1 /dev/ram2
### Mount the ramdisks to their appropriate places mount /dev/ram0 /home/httpd/cgi-bin mount /dev/ram1 /home/httpd/icons mount /dev/ram2 /home/httpd/html ### Copying real directory to ramdisks (the ### data on the ramdisks is lost after a reboot) tar -C /home/httpd_real -c . | tar -C /home/httpd -x ### After this you can start the web-server.
37.3 Solaris: ============= Note 1: ------Solaris 9 and higher: use the ramdiskadm command: Quick example: Example: Creating a 2MB Ramdisk Named mydisk # ramdiskadm -a mydisk 2m /dev/ramdisk/mydisk Example: Listing All Ramdisks # ramdiskadm Block Device /dev/ramdisk/miniroot /dev/ramdisk/certfs /dev/ramdisk/mydisk
Size 134217728 1048576 2097152
Removable No No Yes
-- The ramdiskadm command: NAME ramdiskadm� administer ramdisk pseudo device SYNOPSIS
/usr/sbin/ramdiskadm -a name size [g | m | k | b] /usr/sbin/ramdiskadm -d name /usr/sbin/ramdiskadm DESCRIPTION The ramdiskadm command administers ramdisk(7D), the ramdisk driver. Use ramdiskadm to create a new named ramdisk device, delete an existing named ramdisk, or list information about exisiting ramdisks. Ramdisks created using ramdiskadm are not persistent across reboots. OPTIONS The following options are supported: -a name size Create a ramdisk named name of size size and its corresponding block and character device nodes. name must be composed only of the characters a-z, A-Z, 0-9, _ (underbar), and (hyphen), but it must not begin with a hyphen. It must be no more than 32 characters long. Ramdisk names must be unique. The size can be a decimal number, or, when prefixed with 0x, a hexadecimal number, and can specify the size in bytes (no suffix), 512-byte blocks (suffix b), kilobytes (suffix k), megabytes (suffix m) or gigabytes (suffix g). The size of the ramdisk actually created might be larger than that specified, depending on the hardware implementation. If the named ramdisk is successfully created, its block device path is printed on standard out. -d name Delete an existing ramdisk of the name name. This command succeeds only when the named ramdisk is not open. The associated memory is freed and the device nodes are removed. You can delete only ramdisks created using ramdiskadm. It is not possible to delete a ramdisk that was created during the boot process. Without options, ramdiskadm lists any existing ramdisks, their sizes (in decimal), and whether they can be removed by ramdiskadm (see the description of the -d option, above). Note 2: ------thread: In Solaris =< version 8, its a bit of a pain. This is what i asked:
Is there anyone who could tell me how to make a ram disk in Solaris 8? I have a Sun Sparc Box running Solaris 8, and I want to use some of it's memory to mount a new file-system Thanks in advance, The solution: As many mentioned i could use tmpfs, lik this: mkdir /ramdisk mount -F tmpfs -o size=500m swap /ramdisk However this is not a true ramdisk (it really uses VM, not RAM, and the size is an upper limit, not a reservation) This is what Solaris provides.
====================== 38. Software Packages: ====================== 38.1 Software Packages on Solaris: ================================== This section deals about software packages for Solaris. A software package is a collection of files and directories in a defined format. It describes a software application such as manual pages and line printer support. Solaris 8 has about 80 packages that total about 900MB. A Solaris software package is the standard way to deliver bundeld and unbundled software. Packages are administered by using the package administration commands, and are generally identified by a SUNWxxx naming convention. Software packages are grouped into software clusters, which are logical collections of software packages. Some clusters contain just 1 or 2 packages, while another may contain more packages. Installing Software Packages: ----------------------------Solaris provides the tools for adding and removing software from a system: -- pkgadd: -- ------pkgadd [-nv] [-a admin] [-d device] [[-M]-R root_path] [-r response] [-V fs_file] [pkginst...] pkgadd -s spool [-d device] [pkginst...]
-a admin Define an installation administration file, admin, to be used in place of the default administration file. The token none overrides the use of any admin file, and thus forces interaction with the user. Unless a full path name is given, pkgadd first looks in the current working directory for the administration file. If the specified administration file is not in the current working directory, pkgadd looks in the /var/sadm/install/admin directory for the administration file. -d device Install or copy a package from device. device can be a full path name to a directory or the identifiers for tape, floppy disk, or removable disk (for example, /var/tmp or /floppy/floppy_name ). It can also be a device alias (for example, /floppy/floppy0). pkgadd transfers the contents of a software package from the distribution medium or directory to install it onto the system. Used without the -d option, pkgadd looks in the default spool directory for the package (var/spool//pkg). Used with the -s option, it writes the package to a spool directory instead of installing it. Example 1: # pkgadd -d /cdrom/cdrom0/s0/Solaris_2.6 Example 2: # pkgadd -d /tmp/signed_pppd The following packages are available: 1 SUNWpppd Solaris PPP Device Drivers (sparc) 11.10.0,REV=2003.05.08.12.24 Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: all Enter keystore password: Example 3: # pkgadd -d http://install/signed-video.pkg ## Downloading... ..............25%..............50%..............75%..............100% ## Download Complete Example 4: # pkgadd -d . DISsci /opt/DISsci
The command will create a new directory structure in
Example 5: Spooling the packages to a spool directory #pkgadd -d /cdrom/sol_8_sparc/s0/Solaris_8/Product -s /var/spool/pkg SUNWaudio Example 6:
# pkgadd -d /cdrom/cdrom0/s0/Solaris_9/Product SUNWpl5u . . . Installation of was successful. # pkgchk -v SUNWpl5u /usr /usr/bin /usr/bin/perl /usr/perl5 /usr/perl5/5.00503 Example 7: Suppose you need to install something that's called the UUCP packages. First Check that the UUCP packages maybe already been installed: # pkginfo | grep UUCP Check that the following are installed: system system
SUNWbnur SUNWbnuu
Networking UUCP Utilities, (Root) Networking UUCP Utilities, (Usr)
If this command just returns with a prompt, the packages aren't installed. Use pkgadd to install them as follows: For Intel (x86) Solaris 8: Insert the CD marked "Solaris 8 Intel Platform Edition Software CD 2 of 2" and type: # pkgadd -d /cdrom/sol_8_ia_2/Solaris_8/Product SUNWbnur # pkgadd -d /cdrom/sol_8_ia_2/Solaris_8/Product SUNWbnuu Other package related commands: -------------------------------
pkgrm pkgchk pkginfo pkgask pkgparam
Displays a package parameter values. # pkgparam -d /cdrom/cdrom0/s0/Solaris_2.8/Product SUNWvolr SUNW_PKGTYPE The system responds with the location where the application will be stored. - admintool - Solaris Product Registry To startup the Solaris Product Registry to view, install or uninstall software, use the command /usr/bin/prodreg
Installing Patches: ------------------#patchadd #patchrm patchadd service] patchadd service]
[-d] [-u] [-B backout_dir] [-C net_install_image| -R client_root_path| -S patch [-d] [-u] [-B backout_dir] [-C net_install_image| -R client_root_path| -S -M patch_dir| patch_id... | patch_dir patch_list patchadd [-C net_install_image| -R client_root_path| -S service] -p Examples: Example 1: Show the patches on your system: # showrev -p shows all patches applied to a system # patchadd -p same as above # pkgparam PATCHLIST shows all patches applied to the package identified by Example 2: # patchadd /var/spool/patch/104945-02 # patchadd -R /export/root/client1 /var/spool/patch/104945-02 # patchadd -M /var/spool/patch 104945-02 104946-02 102345-02 # patchadd -M /var/spool/patch patchlist # patchadd -M /var/spool/patch -R /export/root/client1 -B /export/backoutrepository 104945-02 104946-02 102345-02 The /var/sadm/install/contents file: -----------------------------------The /var/sadm/install/contents file is the file which Solaris uses to keep track of all the files installed on a system, and their corresponding packages. Every file installed on a Solaris OS using the pkgadd command has an entry in the database of installed files /var/sadm/install/contents. The contents is a textfile that contains one line per installed file.
38.2 Software Packages on AIX: ============================== Installing software, filesets, packages, lpp: --------------------------------------------Similar to Solaris, AIX5L also has a specific terminology related to installable software. There are 4 basic package concepts in AIX5L: fileset, package, LPP, and bundle. - Fileset: A fileset is the smallest individually installable unit. It's a collection of files that provide a specific
function. For example, the "bos.net.tcp.client" is a fileset in the "bos.net" package. - Package: A package contains a group of filesets with a common function, This is a single installable image, for example "bos.net". - LPP: This is a complete software product collection, including all the packages and filesets required. LPP's are separately orderable products that will run on the AIX operating system, for example BOS, DB2, CICS, ADSM and so on. -- AIX verifying correct installation: # lppchk # lppchk -v # lppchk -l
Fileset version consistency check File link verification
P521:/apps $lppchk -l lppchk: No link found from /etc/security/mkuser.sys to /usr/lib/security/mkuser.sys. lppchk: No link found from /etc/security/mkuser.default to /usr/lib/security/mkuser.default.
-- AIX installing maintenance levels and fixes: 1. download the fix from IBM website http://techsupport.services.ibm.com/server/support?view=pSeries 2. uncompress and untar the software archive 3. type smitty update_all Install a fix with instfix: --------------------------P521:/apps $instfix Usage: instfix [-T [-M platform]] [-s string] [ -k keyword | -f file ] [-d device] [-S] [-p | [-i [-c] [-q] [-t type] [-v] [-F]]] [-a] Function: Installs or queries filesets associated with keywords or fixes. -a Display the symptom text (can be combined with -i, -k, or -f). -c Colon-separated output for use with -i. Output includes keyword name, fileset name, required level, installed level, status, and abstract. Status values are < (down level), = (correct level), + (superseded), and ! (not installed). -d Input device (required for all but -i and -a). -F Returns failure unless all filesets associated with the fix are installed.
-f Input file containing keywords or fixes. Use '-' for standard input. The -T option produces a suitable input file format for -f. -i Use with -k or -f option to display whether specified fixes or keywords are installed. Installation is not attempted. If neither -k nor -f is specified, all known fixes are displayed. -k Install filesets for a keyword or fix. -M Use with -T option to display information for fixes present on the media that have to do with the platform specified. -p Use with -k or -f to print filesets associated with keywords. Installation is not attempted when -p is used. -q Quiet option for use with -i. If -c is specified, no heading is displayed. Otherwise, no output is displayed. -S Suppress multi-volume processing. -s Search for and display fixes on media containing a specified string. -T Display fix information for complete fixes present on the media. -t Use with -i option to limit search to a given type. Currently valid types are 'f' (fix) and 'p' (preventive maintenance). -v Verbose option for use with -i. Gives information about each fileset associated with a fix or keyword. to the environment provided.
Another option is to use the instfix command. Any fix can have a single fileset or multiple filesets that comprise that fix. Fix information is organized in the Table of Contents (TOC) on the installation media. After a fix is installed, fix information is kept on the system in a fix database. instfix [ -T ] [ -s String ] [ -S ] [ -k Keyword | -f File ] [ -p ] [ -d Device ] [ -i [ -c ] [ -q ] [ -t Type ] [ -v ] [ -F ] ] [ -a ] Examples: - If you want to install only a specific fix, use # instfix -k -d , for example # instfix -k IX75893 -d /dev/cd0 # instfix -k IX75893 -d . # instfix -k IY63533 -d . - To list fixes that are on a CD-ROM in /dev/cd0, enter # instfix -T -d /dev/cd0 IX75893 - To determine if for example APAR IX75893 is installed on the system, enter # instfix -ik IX75893 Not all filesets for IX75893 were found. You will always be able to determine if an APAR is installed on your system using the command instfix -ivk APAR_NUMBER , whereas installed PTFs are not trackable. - How to determine if all filesets of a ML are installed? P521:/apps $instfix -i | grep ML All filesets for 5.2.0.0_AIX_ML were found. All filesets for 5200-01_AIX_ML were found.
All All All All All All All All
filesets filesets filesets filesets filesets filesets filesets filesets
for for for for for for for for
5200-02_AIX_ML 5200-03_AIX_ML 5200-04_AIX_ML 5200-05_AIX_ML 5200-06_AIX_ML 5200-07_AIX_ML 5200-08_AIX_ML 5200-09_AIX_ML
were were were were were were were were
found. found. found. found. found. found. found. found.
The command "instfix -i | grep ML" is essentially the same as "instfix -i -tp". - To detect incomplete AIX maintaince levels: # instfix -i |grep ML Not all filesets for 4.3.1.0_AIX_ML were found. Not all filesets for 4.3.2.0_AIX_ML were found. All filesets for 4.3.1.0_AIX_ML were found. Not all filesets for 4.3.2.0_AIX_ML were found. Not all filesets for 4.3.3.0_AIX_ML were found. Not all filesets for 4330-02_AIX_ML were found. All filesets for 4320-02_AIX_ML were found. Not all filesets for 4330-03_AIX_ML were found. .. .. You can also use smitty: # smitty instfix Update Software by Fix (APAR) Type or select a value for the entry field. Press Enter AFTER making all desired changes. [Entry Fields] * INPUT device / directory for software +
[]
The lslpp command: -----------------Purpose Lists installed software products. Syntax lslpp { -d | -E | -f | -h | -i | -l | -L | -p } ] [ -a] [ -c] [ -J ] [ -q ] [ -I ] [ -O { [ r ] [ s ] [ u ] } ] [ [ FilesetName ... | FixID ... | all ] lslpp -w [ -c ] [ -q ] [ -O { [ r ] [ s ] [ u ] } ] [ FileName ... | all ] lslpp -L -c [ -v] lslpp -S [A|O]
lslpp -e Description The lslpp command displays information about installed filesets or fileset updates. The FilesetName parameter is the name of a software product. The FixID (also known as PTF or program temporary fix ID) parameter specifies the identifier of an update to a formatted fileset. When only the -l (lowercase L) flag is entered, the lslpp command displays the latest installed level of the fileset specified for formatted filesets. The base level fileset is displayed for formatted filesets. When the -a flag is entered along with the -l flag, the lslpp command displays information about all installed filesets for the FilesetName specified. The -I (uppercase i) flag combined with the -l (lowercase L) flag specifies that the output from the lslpp command should be limited to base level filesets.
-a Displays additional ("all") information when combined with other flags. (Not valid with -f, only valid with -B when combined with -h) -B Permits PTF ID input. (Not valid with -L) -c Colon-separated output. (Includes all deinstallable levels of software if -Lc) -d Dependents (filesets for which this is a requisite). -E License Agreements. -S Lists Automatically and Optionally installed filesets. -e Lists all efixes on the system. -f Files that belong to this fileset. -h History information. -I Limits listings to base level filesets (no updates displayed). -i Product Identification information (requested per fileset). -J Use list as the output format. (Valid with -l and -L) -L Lists fileset names, latest level, states, and descriptions. (Consolidates usr, root and share part information.) -l Lists fileset names, latest level, states, and descriptions. (Separates usr, root and share part information.) -O Data comes from [r] root and/or [s] share and/or [u] usr. (Not valid with -L) -p Requisites of installed filesets. -q Quiet (no column headers). -v Lists additional information from vendor database. (Valid with -Lc only) -w Lists the fileset that owns this file. One of the following mutually exclusive flags: d,f,h,i,L,l,p,w,E,S,e must be specified. P521:/apps $ To display information about installed filesets, you can use the lslpp command. If you need to check whether certain filesets have been installed, use the lslpp command as in the following example:
# lslpp -h bos.adt.include bos.adt.l1b bos.adt.l1bm \ bos.net.ncs 1for_ls.compat 1for_ls.base In the above example, we check whether those filesets have been installed. lslpp options: -l: -h: -p: -d: -f: -w:
Displays the name, level, state and description of the fileset. Displays the installation and update history for the fileset. Displays requisite information for the fileset. Displays dependent information for the fileset. Displays the filenames added to the system during installation of the fileset. Lists the fileset that owns a file or files.
Examples: - To display the name, level of the bos.adt.include fileset, use zd57l09 # lslpp -l bos.adt.include Fileset Level State Description ---------------------------------------------------------------------------Path: /usr/lib/objrepos bos.adt.include 5.2.0.95 COMMITTED Base Application Development Include Files - To display all files in the inventory database which include vmstat, use # lslpp -w "*vmstat*" File Fileset Type ---------------------------------------------------------------------------/usr/sbin/lvmstat bos.rte.lvm File /usr/share/man/info/EN_US/a_doc_lib/cmds/aixcmds6/vmstat.htm infocenter.man.EN_US.commands File /usr/share/man/info/EN_US/a_doc_lib/cmds/aixcmds3/lvmstat.htm infocenter.man.EN_US.commands File /usr/bin/vmstat bos.acct File /usr/bin/vmstat64 bos.acct File /usr/es/sbin/cluster/OEM/VxVM40/cllsvxvmstat cluster.es.server.utils File The same for trying to find out what contains the make command: # lslpp -w "*make*" /usr/bin/makedev /usr/ccs/bin/make /usr/bin/make /usr/bin/makekey /usr/ccs/bin/makekey
bos.txt.tfs bos.adt.base bos.adt.base bos.adt.base bos.adt.base
File File Symlink Symlink File
- To list the installation state for the most recent level of installed filesets for all of the bos.rte filesets, use # lslpp -l "bos.rte.*" # lslpp -l | grep bos.rte
So, "lslpp -l" shows all of the filesets - To display the names of the files added to the system during installation of the bos.perf.perfstat fileset, use # lslpp -f "*perf*" - To check whether some certain filesets have been installed, like in the following example: # lslpp -h bos.adt.include bos.adt.lib bos.adt.l1bm \ bos.net.ncs 1for_ls.compat 1for_ls.base - To check you have the SDD driver on your system: # lslpp -L devices.sdd.* - To check the Java filesets on your system: # lslpp -l | grep Java /root:>lslpp -l | grep Java Java131.rte.bin 1.3.1.16 Java131.rte.lib 1.3.1.16
idebug.rte.hpj idebug.rte.jre idebug.rte.olt.Java
9.2.5.0 9.2.5.0 9.2.5.0
COMMITTED COMMITTED
COMMITTED COMMITTED COMMITTED
Java Runtime Environment Java Runtime Environment Java-based build tool. JavaBeans(TM) (EJB(TM)). Javadocs Java(TM) technology-based Web Java(TM) technology-based Web Javadocs High-Performance Java Runtime Java Runtime Environment Object Level Trace Java
# lslpp -l | grep Java13_64 # lslpp -l | grep App
X11.adt.bitmaps X11.adt.ext X11.adt.imake X11.adt.include X11.adt.lib X11.adt.motif X11.apps.aixterm X11.apps.clients
5.2.0.0 5.2.0.30 5.2.0.0 5.2.0.10 5.2.0.40 5.2.0.0 5.2.0.30 5.2.0.0
COMMITTED COMMITTED COMMITTED COMMITTED COMMITTED COMMITTED COMMITTED COMMITTED
X11.apps.msmit
5.2.0.50
COMMITTED
5.2.0.40 5.2.0.0 5.2.0.0 X11.msg.en_US.apps.config 5.2.0.0
COMMITTED COMMITTED COMMITTED COMMITTED
X11.apps.xdm X11.apps.xterm
Application Server Dynamic WebSphere Application Server. for WebSphere Application the WebSphere Application Application Profile, and AIXwindows Application AIXwindows Application AIXwindows Application AIXwindows Application AIXwindows Application AIXwindows Application AIXwindows aixterm Application AIXwindows Client Applications Applications AIXwindows msmit Application Configuration Applications Applications AIXwindows xdm Application AIXwindows xterm Application AIXwindows Client Application AIXwindows Config Application
bos.adt.base bos.adt.debug bos.adt.graphics bos.adt.include bos.adt.lib bos.adt.libm bos.adt.sccs bos.adt.syscalls bos.adt.utils bos.net.tcp.adt
5.2.0.50 5.2.0.50 5.2.0.40 5.2.0.53 5.2.0.50 5.2.0.50 5.2.0.0 5.2.0.50 5.2.0.50 5.2.0.40
COMMITTED COMMITTED COMMITTED COMMITTED COMMITTED COMMITTED COMMITTED COMMITTED COMMITTED COMMITTED
6.0.0.0 5.2.0.0
COMMITTED COMMITTED
xlC.adt.include bos.adt.data
Base Application Development Base Application Development Base Application Development Base Application Development Base Application Development Base Application Development SCCS Application Development System Calls Application Base Application Development TCP/IP Application Toolkit Application Runtime C Set ++ Application Base Application Development
Removing a fix: --------------On AIX you can use either the installp -r command, or use the smitty reject fast path Smitty fastpaths: ------------------ AIX software maintenance: # smitty maintain_software From here you can commit or reject installed software. You can also copy the filesets from the installation media to a directory on disk. The default directory for doing this is /usr/sys/inst.images -- Install new software: # smitty install_update # smitty install_latest -- To commit software: # smitty install_commit -- To reject software: # smitty install_reject -- To remove installed and commited software: # smitty install_remove -- To see what fixes are installed on your system: # smitty show_apar_stat -- To install individual fix: # smitty instfix or # smitty update_by_fix -- To install all filesets: # smitty update_all
-- To view already installed software: # smitty list_installed
The AIX installp command: ------------------------installp Command Purpose Installs available software products in a compatible installation package. Syntax To Install with Apply Only or with Apply and Commit installp [ -a | -ac [ -N ] ] [ -eLogFile ] [ -V Number ] [ -dDevice ] [ -b ] [ -S ] [ -B ] [ -D ] [ -I ] [ -p ] [ -Q ] [ -q ] [ -v ] [ -X ] [ -F | -g ] [ -O { [ r ] [ s ] [ u ] } ] [ -tSaveDirectory ] [ -w ] [ -zBlockSize ] { FilesetName [ Level ]... | -f ListFile | all } To Commit Applied Updates installp -c [ -eLogFile ] [ -VNumber ] [ -b ] [ -g ] [ -p ] [ -v ] [ -X ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -f ListFile | all } To Reject Applied Updates installp -r [ -eLogFile ] [ -VNumber ] [ -b ] [ -g ] [ -p ] [ -v ] [ -X ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -f ListFile } To Deinstall (Remove) Installed Software installp -u [ -eLogFile ] [ -VNumber ] [ -b ] [ -g ] [ -p ] [ -v ] [ -X ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -f ListFile } To Clean Up a Failed Installation: installp -C [ -b ] [ -eLogFile ] To List All Installable Software on Media installp { -l | -L } [ -eLogFile ] [ -d Device ] [ -B ] [ -I ] [ -q ] [ -zBlockSize ] [ -O { [ s ] [ u ] } ] To List All Customer-Reported Problems Fixed with Software or Display All Supplemental Information installp { -A|-i } [ -eLogFile ] [ -dDevice ] [ -B ] [ -I ] [ -q ] [ -z BlockSize ] [ -O { [ s ] [ u ] } ] { FilesetName [ Level ]... | -f ListFile | all } To List Installed Updates That Are Applied But Not Committed installp -s [ -eLogFile ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -fListFile | all } fileset is the lowest installable base unit. For example, bos.net.tcp.client 4.1.0.0 is a fileset. A fileset update is an update with a different fix ID or maintenance level. For example, bos.net.tcp.client 4.1.0.2 and bos.net.tcp.client 4.1.1.0 are both fileset updates for bos.net.tcp.client 4.1.0.0. When a base level (fileset) is installed on the system, it is automatically
committed. You can remove a fileset regardless of the state (committed, broken, committed with applied updates, committed with committed updates, etc.). When a fileset update is applied to the system, the update is installed. The current version of that software, at the time of the installation, is saved in a special save directory on the disk so that later you can return to that version if desired. Once a new version of a software product has been applied to the system, that version becomes the currently active version of the software. Updates that have been applied to the system can be either committed or rejected at a later time. The installp -s command can be used to get a list of applied updates that can be committed or rejected. When updates are committed with the -c flag, the user is making a commitment to that version of the software product, and the saved files from all previous versions of the software product are removed from the system, thereby making it impossible to return to a previous version of the software product. Software can be committed at the time of installation by using the -ac flags. Note that committing already applied updates does not change the currently active version of a software product. It merely removes saved files for previous versions of the software product. Examples: To install all filesets within the bos.net software package in /usr/sys/inst.images directory in the applied state, enter # installp -avX -d/usr/sys/inst.images bos.net To commit all updates, enter # installp -cgX all To list the software that is on your CDROM, enter # installp -L -d /dev/cd0 A record of the installp output can be found in the /var/adm/sw/installp.summary # cat /var/adm/sw/installp.summary Used to cleanup after a failed lpp install/update: # installp -C Commits all applied LPPs or PTFs: # installp -c -g -X all Lists the table of contents for the install/update media and saves it into a file named /tmp/toc.list # installp -q -d/dev/rmt1.1 -l > /tmp/toc.list Lists the lpps that have been applied but not yet committed or rejected:
# installp -s [P521]root@ol116u106:installp -s 0503-459 installp: No filesets were found in the Software Vital Product Database in the APPLIED state.
The AIX geninstall command: --------------------------A generic installer that installs software products of various packaging formats. For example, installp, RPM, and ISMP. With the geninstall command, you can list and install packages from media that contains installation images packaged in any of the listed formats. The geninstall and gencopy commands recognize the non-installp installation formats and either call the appropriate installers or copy the images, respectively. Beginning in AIX 5L, you can not only install installp formatted packages, but also RPM and Install Shield Mutli-Platform (ISMP) formatted packages. Use the Web-based System Manager, SMIT, or the geninstall command to install and uninstall these types of packages. The geninstall command is designed to detect the format type of a specified package and run the appropriate install command. Syntax geninstall -d Media [ -I installpFlags ] [ -E | -T ] [ -t ResponseFileLocation ] [-e LogFile] [ -p ] [ -F ] [ -Y ] [ -Z ] [ -D ] { -f File | Install_List ] | all} OR geninstall -u [-e LogFile] [ -E | -T ] [ -t ResponseFileLocation ] [ -D ] {-f File | Uninstall_List...} OR geninstall -L -d Media [-e LogFile] [ -D ] Description Accepts all current installp flags and passes them on to installp. Some flags (for example, -L) are overloaded to mean list all products on the media. Flags that don't make sense for ISMP packaged products are ignored. This allows programs (like NIM) to continue to always send in installp flags to geninstall, but only the flags that make sense are used. The geninstall command provides an easy way to see what modifications have been made to the configuration files
listed in /etc/check_config.files. When these files have been changed during a geninstall installation or update operation, the differences between the old and new files will be recorded in the /var/adm/ras/config.diff. If /etc/check_config.files requests that the old file be saved, the old file can be found in the /var/adm/config directory. The /etc/check_config.files file can be edited and can be used to specify whether old configuration files that have been changed should be saved (indicated by s) or deleted (indicated by d), and has the following format: d /etc/inittab A summary of the geninstall command's install activity is kept at /var/adm/sw/geninstall.summary. This file contains colon-separated lists of filesets installed by installp and components installed by ISMP. This is used mainly to provide summary information for silent installs. Note: Refer to the README.ISMP file in the /usr/lpp/bos directory to learn more about ISMP-packaged installations and using response files. Examples: - To install all the products on a CD media that is in drive cd0, type: # geninstall -d /dev/cd0 all If ISMP images are present on the media, a graphical interface is presented. Any installp or RPM images are installed without prompting, unless the installp images are spread out over multiple CDs. - If you using the geninstall command to install RPM or ISMP packages, use the prefix type to designate to the geninstall command the type of package you are installing. In AIX 5L, the package prefix types are the following: I: installp format R: RPM format J: ISMP format For example, to install the cdrecord RPM package and the bos.games installp package, type the following: # geninstall -d/dev/cd0 R:cdrecord I:bos.games The geninstall command detects that the cdrecord package is an RPM package type and runs the rpm command to install cdrecord. The geninstall command then detects that bos.games is an installp package type and runs the installp command to install bos.games. The process for uninstallation is
similar to the installation process.
Fixdist: -------There is a tool named fixdist you can use to download fixes from IBM. Maintenance levels: =================== Notes: Note 1: ------Current versions of AIX5L are 5200-04, 05, 06, 07 04: V5.2 with the 5200-04 Recommended Maintenance Package APAR IY56722 plus APAR IY60347 � 05: V5.2 with the 5200-05 Recommended Maintenance Package Note 2: Go from 5200-00 to 5200-05: ----------------------------------Use this package to update to 5200-05 (ML 05) an AIX 5.2.0 system whose current ML is 5200-00 (i.e. base level) or higher. (Nota: ML 05 notably brings the fileset bos.mp.5.2.0.54) AIX 5200-05 maintenance package: AIX 5200-05 maintenance package Recommended maintenance for AIX 5.2.0 This package, 5200-05, updates AIX 5.2 from base level (no maintenance level) to maintenance level 05 (5200-05). This package is a recommended maintenance package for AIX 5.2. IBM recommends that customers install the latest available maintenace package for their AIX release. To determine if AIX 5200-05 is already installed on your system, run the following command: oslevel -r General description This package contains code corrections for the AIX operating system and many related subsystems. Unless otherwise stated, this package is released for all languages. For additional information, refer to the Package information Download and install instructions
Package Released Size (Bytes) Checksum 520005.tar.gz (See Note) 01/20/05 750,314,420 2116147779 Additional space needed to extract the filesets 1,034,141,696 Note: IBM recommends that you create a separate file system for /usr/sys/inst.images to prevent the expansion of the /usr file system. More information Click on the package name above. Put the package (a tar.gz file) in /usr/sys/inst.images Extract the filesets from the package. cd /usr/sys/inst.images gzip -d -c 520005.tar.gz | tar -xvf Back up your system. Install the package by creating a table of contents for install to use. Then update the install subsystem itself. Run SMIT to complete the installation. # inutoc /usr/sys/inst.images # installp -acgXd /usr/sys/inst.images bos.rte.install # smit update_all Reboot your system. This maintenance package replaces critical operating system code. Installation Tips * You will need to be logged in as 'root' to perform the installation of this package. * Creating a system backup is recommended before starting the installation procedure. Refer to the mksysb command in the AIX 5.2 Commands Reference manual for additional information. * The latest AIX 5.2 installation hints and tips are available from the eServer Subscription Services web site at: https://techsupport.services.ibm.com/server/pseries.subscriptionSvcs These tips contain important information that should be reviewed before installing this update. Installation To install selected updates from this package, use the command: smit update_by_fix To install all updates from this package that apply to installed filesets on your system, use the command: smit update_all It is highly recommended that you apply all updates from this package.
After successful installation, a system reboot is required for this update to take effect. Note 2: Go from 5200-04 to 5200-05: ----------------------------------AIX 5200(04)-05 maintenance package Recommended maintenance for AIX 5.2.0 This package, 5200(04)-05, updates AIX 5.2 from maintenance level 04 (5200-04) to maintenance level 05 (5200-05). This package is a recommended maintenance package for AIX 5.2. IBM recommends that customers install the latest available maintenace package for their AIX release. To determine if AIX 5200-05 is already installed on your system, run the following command: oslevel -r General description This package contains code corrections for the AIX operating system and many related subsystems. Unless otherwise stated, this package is released for all languages. For additional information, refer to the Package information Download and install instructions Package Released Size (Bytes) Checksum 520405.tar.gz (See Note) 01/20/05 637,751,943 3712904912 Additional space needed to extract the filesets 856,494,080 Note: IBM recommends that you create a separate file system for /usr/sys/inst.images to prevent the expansion of the /usr file system. More information Click on the package name above. Put the package (a tar.gz file) in /usr/sys/inst.images Extract the filesets from the package. cd /usr/sys/inst.images gzip -d -c 520405.tar.gz | tar -xvf Back up your system. Install the package by creating a table of contents for install to use. Then update the install subsystem itself. Run SMIT to complete the installation. # inutoc /usr/sys/inst.images # installp -acgXd /usr/sys/inst.images bos.rte.install # smit update_all Reboot your system. This maintenance package replaces critical operating system code.
Note 3: Go from 5200-05 to 5200-07: ----------------------------------Always run the inutoc command to ensure the installation subsystem will recognize the new fix packages you download. This command creates a new .toc file for the fix package. Run the inutoc command in the same directory where you downloaded the package filesets. For example, if you downloaded the filesets to /usr/sys/inst.images, run the following command: # inutoc /usr/sys/inst.images - For selected updates To install selected updates from this package, use the following command: # smit update_by_fix - For all updates To install all updates from this package that apply to the installed filesets on your system, use the following command: # smit update_all It is highly recommended that you apply all updates from this package. Reboot the system. A reboot is required for this update to take effect. -First do the bos.rte.install # installp -acgYqXd /software/ML07 bos.rte.install # inutoc /software/ML07 # smitty update_all
Note 4: About the /usr/sys/inst.images fs: -----------------------------------------Create a LV # crfs -v jfs -a bf=true -dXXX##instlv -m/usr/sys/inst.images -Ayes -prw -tno -a nbpi=4096 -a ag=64 # mount /usr/sys/inst.images
Note 5: About the inutoc command: --------------------------------inutoc Command Purpose Creates a .toc file for directories that have backup format file install images. This command is used by the installp command and the install scripts. Syntax inutoc [ Directory ] Description The inutoc command creates the .toc file in Directory. If a .toc file already exists, it is recreated with new information. The default installation image Directory is /usr/sys/inst.images. The inutoc command adds table of contents entries in the .toc file for every installation image in Directory. The installp command and the bffcreate command call this command automatically upon the creation or use of an installation image in a directory without a .toc file. Examples To create the .toc file for the /usr/sys/inst.images directory, enter: # inutoc To create a .toc file for the /tmp/images directory, enter: # inutoc /tmp/images Note 6: About the bffcreate command: -----------------------------------bffcreate Command Purpose Creates installation image files in backup format. Syntax bffcreate [ -q ] [ -S ] [ -U ] [ -v ] [ -X ] [ -d Device ] [ -t SaveDir ] [ -w Directory ] [ -M Platform ] { [ -l | -L ] | -c [ -s LogFile ] | Package [Level ] ... | -f ListFile | all } Description The bffcreate command creates an installation image file in backup file format (bff) to support software installation operations. The bffcreate command creates an installation image file from an installation image file on the specified installation media. Also, it automatically creates an installation image file from hyptertext images (such as those on the operating system documentation CD-ROMs). The installp command can use the newly created installation file to install software onto the system. The file is created in backup format and saved to the directory specified by SaveDir. The .toc file in
the directory specified by the SaveDir parameter is updated to include an entry for the image file. The bffcreate command determines the bff name according to this information: Neutral Packages POWER-based platform
package.v.r.m.f.platform.installtype Packages package.v.r.m.f.installtype
Image Type Target bff Name Installation image for the POWER-based platform package.v.r.m.f.I Installation image for Neutral package.v.r.m.f.N.I 3.1 update for the POWER-based platform package.v.r.m.f.service# 3.2 update for the POWER-based platform package.v.r.m.f.ptf 4.X** or later updates for the POWER-based platform package.part.v.r.m.f.U Update image for Neutral package.v.r.m.f.N.U ** 4.X or later updates contain one package only. In addition, AIX Version 4 and later updates do not contain ptf IDs. package = the name of the software package as described by the PackageName parameter v.r.m.f = version.release.modification.fix, the level associated with the software package. The PackageName is usually not the same as the fileset name. ptf = program temporary fix ID (also known as FixID) The installation image file name has the form Package.Level.I. The Package is the name of the software package, as described for the Package Name parameter. Level has the format of v.r.m.f, where v = version, r = release, m = modification, f = fix. The I extension means that the image is an installation image rather than an update image. Update image files containing an AIX 3.1 formatted update have a service number extension following the level. The Servicenum parameter can be up to 4 digits in length. One example is xlccmp.3.1.5.0.1234. Update image files containing an AIX 3.2 formatted update have a ptf extension following the level. One example is bosnet.3.2.0.0.U412345. AIX Version 4 and later update image file names begin with the fileset name, not the PackageName. They also have U extensions to indicate that they are indeed update image files, not installation images. One example of an update image file is bos.rte.install.4.3.2.0.U. The all keyword indicates that installation image files are created for every installable software package on the device. You can extract a single update image with the AIX Version 4 and later bffcreate command. Then you must specify the fileset name and the v.r.m.f. parameter. As in example 3 in the Examples section,
the PackageName parameter must be the entire fileset name, bos.net.tcp.client, not just bos.net. Attention: Be careful when selecting the target directory for the extracted images, especially if that directory already contains installable images. If a fileset at a particular level exists as both an installation image and as an update image in the same directory, unexpected installation results can occur. In cases like this, installp selects the image it finds first in the table of contents (.toc) file. The image it selects may not be the one you intended and unexpected requisite failures can result. As a rule of thumb, you should extract maintenance levels to clean directories. Examples To create an installation image file from the bos.net software package on the tape in the /dev/rmt0 tape drive and use /var/tmp as the working directory, type: # bffcreate -d /dev/rmt0.1 -w /var/tmp bos.net To create an installation image file from the package software package on the diskette in the /dev/rfd0 diskette drive and print the name of the installation image file without being prompted, type: # bffcreate -q -v package To create a single update image file from the bos.net.tcp.client software package on the CD in /dev/cd0, type: # bffcreate -d /dev/cd0 bos.net.tcp.client 4.2.2.1 To list the packages on the CD in /dev/cd0, type: # bffcreate -l -d /dev/cd0 To create installation and/or update images from a CD in /dev/cd0 by specifying a list of PackageNames and Levels in a ListFile called my MyListFile, type: # bffcreate -d /dev/cd0 -f MyListFile To create installation or update images of all software packages on the CD-ROM media for the current platform, type: # bffcreate -d /dev/cd0 all To list fileset information for the bos.games software package from a particular device, type: # bffcreate -d /usr/sys/inst.images/bos.games -l To list all the Neutral software packages on the CD-ROM media, type: # bffcreate -d /dev/cd0 -MN -l
38.3 Software Packages on Linux: ================================ 38.3.1 RPM packages on Linux (1):
--------------------------------Note 1: ------First we show a few simple examples: - Examples getting software info from your system: # rpm -q kernel kernel-2.4.7-10 # rpm -q glibc glibc-2.2.4-19.3 # rpm -q gcc gcc-2.96-98 Show everything: # rpm -qa - Examples installing rpm packages: # rpm -Uvh libpng-1.2.2-22.i386.rpm # rpm -Uvh gnome-libs-1.4.1.2.90-40.i386.rpm # rpm -Uvh oracleasm-support-2.0.0-1.i386.rpm \ oracleasm-lib-2.0.0-1.i386.rpm \ oracleasm-2.6.9-5.0.5-ELsmp-2.0.0-1.i686.rpm # rpm -Uvh /mnt/cdrom/RedHat/RPMS/tripwire*.rpm Note: the U switch really means starting an Upgrade, but if nothing is there, an installation will take place. Note 2: ------What is RPM? RPM is the RPM Package Manager. It is an open packaging system available anyone to use. It allows users to take source code for new software and package it into and binary form such that binaries can be easily installed and tracked and source can be easily. It also maintains a database of all packages and their files that can be verifying packages and querying for information about files and/or packages.
for source rebuilt used for
Red Hat, Inc. encourages other distribution vendors to take the time to look at RPM and use it for their own distributions. RPM is quite flexible and easy to use, though it provides the base
for a very extensive system. It is also completely open and available, though we would appreciate bug reports and fixes. Permission is granted to use and distribute RPM royalty free under the GPL. More complete documentation is available on RPM in the book by Ed Bailey, Maximum RPM. That book is available for download or purchase at www.redhat.com. RPM is a core component of many Linux distributions, such as Red Hat Enterprise Linux, the Fedora Project, SUSE Linux Enterprise, openSUSE, CentOS, Mandriva Linux, and many others. It is also used on many other operating systems as well, and the RPM format is part of the Linux Standard Base. Acquiring RPM The best way to get RPM is to install Red Hat Linux. If you don't want to do that, you can still get and use RPM. It can be acquired from ftp.redhat.com. RPM Requirements RPM itself should build on basically any Unix-like system. It has been built and used on Tru64 Unix, AIX, Solaris, SunOS, and basically all flavors of Linux. To build RPMs from source, you also need everything normally required to build a package, like gcc, make, etc. In its simplest form, RPM can be used to install packages: # rpm -i foobar-1.0-1.i386.rpm The next simplest command is to uninstall a package: # rpm -e foobar One of the more complex but highly useful commands allows you to install packages via FTP. If you are connected to the net and want to install a new package, all you need to do is specify the file with a valid URL, like so: # rpm -i ftp://ftp.redhat.com/pub/redhat/rh-2.0-beta/RPMS/foobar-1.0-1.i386.rpm Please note, that RPM will now query and/or install via FTP. While these are simple commands, rpm can be used in a multitude of ways. To see which options are available in your version of RPM, type: # rpm --help You can find more details on what those options do in the RPM man page, found by typing:
# man rpm RPM is a very useful tool and, as you can see, has several options. The best way to make sense of them is to look at some examples. I covered simple install/uninstall above, so here are some more examples: Let's say you delete some files by accident, but you aren't sure what you deleted. If you want to verify your entire system and see what might be missing, you would do: # rpm -Va Let's say you run across a file that you don't recognize. To find out which package owns it, you would do: # rpm -qf /usr/X11R6/bin/xjewel The output would be sometime like: xjewel-1.6-1 You find a new koules RPM, but you don't know what it is. To find out some information on it, do: # rpm -qpi koules-1.2-2.i386.rpm The output would be: Name : Version : Release : Install date: Group : Size : Summary : Description :
koules Distribution: Red Hat Linux Colgate 1.2 Vendor: Red Hat Software 2 Build Date: Mon Sep 02 11:59:12 1996 (none) Build Host: porky.redhat.com Games Source RPM: koules-1.2-2.src.rpm 614939 SVGAlib action game with multiplayer, network, and sound support
This arcade-style game is novel in conception and excellent in execution. No shooting, no blood, no guts, no gore. The play is simple, but you still must develop skill to play. This version uses SVGAlib to run on a graphics console. Now you want to see what files the koules RPM installs. You would do: # rpm -qpl koules-1.2-2.i386.rpm The output is: /usr/doc/koules /usr/doc/koules/ANNOUNCE /usr/doc/koules/BUGS /usr/doc/koules/COMPILE.OS2 /usr/doc/koules/COPYING /usr/doc/koules/Card /usr/doc/koules/ChangeLog /usr/doc/koules/INSTALLATION /usr/doc/koules/Icon.xpm
/usr/doc/koules/Icon2.xpm /usr/doc/koules/Koules.FAQ /usr/doc/koules/Koules.xpm /usr/doc/koules/README /usr/doc/koules/TODO /usr/games/koules /usr/games/koules.svga /usr/games/koules.tcl /usr/man/man6/koules.svga.6 SYNOPSIS QUERYING AND VERIFYING PACKAGES: rpm {-q|--query} [select-options] [query-options] rpm {-V|--verify} [select-options] [verify-options] rpm --import PUBKEY ... rpm {-K|--checksig} [--nosignature] [--nodigest] PACKAGE_FILE ... INSTALLING, UPGRADING, AND REMOVING PACKAGES: rpm {-i|--install} [install-options] PACKAGE_FILE ... rpm {-U|--upgrade} [install-options] PACKAGE_FILE ... rpm {-F|--freshen} [install-options] PACKAGE_FILE ... rpm {-e|--erase} [--allmatches] [--nodeps] [--noscripts] [--notriggers] [--repackage] [--test] PACKAGE_NAME ... MISCELLANEOUS: rpm {--initdb|--rebuilddb} rpm {--addsign|--resign} PACKAGE_FILE ... rpm {--querytags|--showrc} rpm {--setperms|--setugids} PACKAGE_NAME ...
Note 3: ------NAME rpm - RPM Package Manager SYNOPSIS QUERYING AND VERIFYING PACKAGES: rpm {-q|--query} [select-options] [query-options] rpm {-V|--verify} [select-options] [verify-options] rpm --import PUBKEY ... rpm {-K|--checksig} [--nosignature] [--nodigest] PACKAGE_FILE ... INSTALLING, UPGRADING, AND REMOVING PACKAGES: rpm {-i|--install} [install-options] PACKAGE_FILE ... rpm {-U|--upgrade} [install-options] PACKAGE_FILE ... rpm {-F|--freshen} [install-options] PACKAGE_FILE ... rpm {-e|--erase} [--allmatches] [--nodeps] [--noscripts]
[--notriggers] [--repackage] [--test] PACKAGE_NAME ... MISCELLANEOUS: rpm {--initdb|--rebuilddb} rpm {--addsign|--resign} PACKAGE_FILE ... rpm {--querytags|--showrc} rpm {--setperms|--setugids} PACKAGE_NAME ... select-options [PACKAGE_NAME] [-a,--all] [-f,--file FILE] [-g,--group GROUP] {-p,--package PACKAGE_FILE] [--fileid MD5] [--hdrid SHA1] [--pkgid MD5] [--tid TID] [--querybynumber HDRNUM] [--triggeredby PACKAGE_NAME] [--whatprovides CAPABILITY] [--whatrequires CAPABILITY] query-options [--changelog] [-c,--configfiles] [-d,--docfiles] [--dump] [--filesbypkg] [-i,--info] [--last] [-l,--list] [--provides] [--qf,--queryformat QUERYFMT] [-R,--requires] [--scripts] [-s,--state] [--triggers,--triggerscripts] verify-options [--nodeps] [--nofiles] [--noscripts] [--nodigest] [--nosignature] [--nolinkto] [--nomd5] [--nosize] [--nouser] [--nogroup] [--nomtime] [--nomode] [--nordev] install-options [--aid] [--allfiles] [--badreloc] [--excludepath OLDPATH] [--excludedocs] [--force] [-h,--hash] [--ignoresize] [--ignorearch] [--ignoreos] [--includedocs] [--justdb] [--nodeps] [--nodigest] [--nosignature] [--nosuggest] [--noorder] [--noscripts] [--notriggers] [--oldpackage] [--percent] [--prefix NEWPATH] [--relocate OLDPATH=NEWPATH] [--repackage] [--replacefiles] [--replacepkgs] [--test] DESCRIPTION rpm is a powerful Package Manager, which can be used to build, install, query, verify, update, and erase individual software packages. A package consists of an archive of files and metadata used to install and erase the archive files. The meta-data includes helper scripts, file attributes, and descriptive information about the package. Packages come in two varieties: binary packages, used to encapsulate
software to be installed, and source packages, containing the source code and recipe necessary to produce binary packages. One of the following basic modes must be selected: Query, Verify, Signature Check, Install/Upgrade/Freshen, Uninstall, Initialize Database, Rebuild Database, Resign, Add Signature, Set Owners/Groups, Show Querytags, and Show Configuration. GENERAL OPTIONS These options can be used in all the different modes. -?, --help Print a longer usage message then normal. --version Print a single line containing the version number of rpm being used. --quiet Print as little as possible - normally only error messages will be displayed. -v Print verbose information - normally routine progress messages will be displayed. -vv Print lots of ugly debugging information. --rcfile FILELIST Each of the files in the colon separated FILELIST is read sequentially by rpm for configuration information. Only the first file in the list must exist, and tildes will be expanded to the value of $HOME. The default FILELIST is /usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc:~/.rpmrc. --pipe CMD Pipes the output of rpm to the command CMD. --dbpath DIRECTORY Use the database in DIRECTORY rathen than the default path /var/lib/rpm --root DIRECTORY Use the file system tree rooted at DIRECTORY for all operations. Note that this means the database within DIRECTORY will be used for dependency checks and any scriptlet(s) (e.g. %post if installing, or %prep if building, a package) will be run after a chroot(2) to DIRECTORY. INSTALL AND UPGRADE OPTIONS The general form of an rpm install command is rpm {-i|--install} [install-options] PACKAGE_FILE ... This installs a new package. The general form of an rpm upgrade command is rpm {-U|--upgrade} [install-options] PACKAGE_FILE ... This upgrades or installs the package currently installed to a newer version. This is the same as install, except all other version(s) of the package are removed after the new package is installed.
rpm {-F|--freshen} [install-options] PACKAGE_FILE ... This will upgrade packages, but only if an earlier version currently exists. The PACKAGE_FILE may be specified as an ftp or http URL, in which case the package will be downloaded before being installed. See FTP/HTTP OPTIONS for information on rpm's internal ftp and http client support. --aid Add suggested packages to the transaction set when needed. --allfiles Installs or upgrades all the missingok files in the package, regardless if they exist. --badreloc Used with --relocate, permit relocations on all file paths, not just those OLDPATH's included in the binary package relocation hint(s). --excludepath OLDPATH Don't install files whose name begins with OLDPATH. --excludedocs Don't install any files which are marked as documentation (which includes man pages and texinfo documents). --force Same as using --replacepkgs, --replacefiles, and --oldpackage. -h, --hash Print 50 hash marks as the package archive is unpacked. Use with -v|--verbose for a nicer display. --ignoresize Don't check mount file systems for sufficient disk space before installing this package. --ignorearch Allow installation or upgrading even if the architectures of the binary package and host don't match. --ignoreos Allow installation or upgrading even if the operating systems of the binary package and host don't match. --includedocs Install documentation files. This is the default behavior. --justdb Update only the database, not the filesystem. --nodigest Don't verify package or header digests when reading. --nosignature Don't verify package or header signatures when reading. --nodeps Don't do a dependency check before installing or upgrading a package. --nosuggest Don't suggest package(s) that provide a missing dependency. --noorder Don't reorder the packages for an install. The list of packages would normally be reordered to satisfy dependancies. --noscripts --nopre --nopost --nopreun --nopostun
Don't execute the scriptlet of the same name. The --noscripts option is equivalent to --nopre --nopost --nopreun --nopostun and turns off the execution of the corresponding %pre, %post, %preun, and %postun scriptlet(s). --notriggers --notriggerin --notriggerun --notriggerpostun Don't execute any trigger scriptlet of the named type. The --notriggers option is equivalent to --notriggerin --notriggerun --notriggerpostun and turns off execution of the corresponding %triggerin, %triggerun, and %triggerpostun scriptlet(s). --oldpackage Allow an upgrade to replace a newer package with an older one. --percent Print percentages as files are unpacked from the package archive. This is intended to make rpm easy to run from other tools. --prefix NEWPATH For relocateable binary packages, translate all file paths that start with the installation prefix in the package relocation hint(s) to NEWPATH. --relocate OLDPATH=NEWPATH For relocatable binary packages, translate all file paths that start with OLDPATH in the package relocation hint(s) to NEWPATH. This option can be used repeatedly if several OLDPATH's in the package are to be relocated. --repackage Re-package the files before erasing. The previously installed package will be named according to the macro %_repackage_name_fmt and will be created in the directory named by the macro %_repackage_dir (default value is /var/tmp). --replacefiles Install the packages even if they replace files from other, already installed, packages. --replacepkgs Install the packages even if some of them are already installed on this system. --test Do not install the package, simply check for and report potential conflicts. ERASE OPTIONS The general form of an rpm erase command is rpm {-e|--erase} [--allmatches] [--nodeps] [--noscripts] [--notriggers] [-repackage] [--test] PACKAGE_NAME ... The following options may also be used: --allmatches Remove all versions of the package which match PACKAGE_NAME. Normally an error is issued if PACKAGE_NAME matches multiple packages. --nodeps Don't check dependencies before uninstalling the packages. --noscripts --nopreun
--nopostun Don't execute the scriptlet of the same name. The --noscripts option during package erase is equivalent to --nopreun --nopostun and turns off the execution of the corresponding %preun, and %postun scriptlet(s). --notriggers --notriggerun --notriggerpostun Don't execute any trigger scriptlet of the named type. The --notriggers option is equivalent to --notriggerun --notriggerpostun and turns off execution of the corresponding %triggerun, and %triggerpostun scriptlet(s). --repackage Re-package the files before erasing. The previously installed package will be named according to the macro %_repackage_name_fmt and will be created in the directory named by the macro %_repackage_dir (default value is /var/tmp). --test Don't really uninstall anything, just go through the motions. Useful in conjunction with the -vv option for debugging. QUERY OPTIONS The general form of an rpm query command is rpm {-q|--query} [select-options] [query-options] You may specify the format that package information should be printed in. To do this, you use the --qf|--queryformat QUERYFMT option, followed by the QUERYFMT format string. Query formats are modifed versions of the standard printf(3) formatting. The format is made up of static strings (which may include standard C character escapes for newlines, tabs, and other special characters) and printf(3) type formatters. As rpm already knows the type to print, the type specifier must be omitted however, and replaced by the name of the header tag to be printed, enclosed by {} characters. Tag names are case insesitive, and the leading RPMTAG_ portion of the tag name may be omitted as well. Alternate output formats may be requested by following the tag with :typetag. Currently, the following types are supported: :armor Wrap a public key in ASCII armor. :base64 Encode binary data using base64. :date Use strftime(3) "%c" format. :day
Use strftime(3) "%a %b %d %Y" format. :depflags Format dependency flags. :fflags Format file flags. :hex Format in hexadecimal. :octal Format in octal. :perms Format file permissions. :shescape Escape single quotes for use in a script. :triggertype Display trigger suffix. For example, to print only the names of the packages queried, you could use %{NAME} as the format string. To print the packages name and distribution information in two columns, you could use %-30{NAME}%{DISTRIBUTION}. rpm will print a list of all of the tags it knows about when it is invoked with the -querytags argument. There are two subsets of options for querying: package selection, and information selection. PACKAGE SELECTION OPTIONS: PACKAGE_NAME Query installed package named PACKAGE_NAME. -a, --all Query all installed packages. -f, --file FILE Query package owning FILE. --fileid MD5 Query package that contains a given file identifier, i.e. the MD5 digest of the file contents. -g, --group GROUP Query packages with the group of GROUP. --hdrid SHA1 Query package that contains a given header identifier, i.e. the SHA1 digest of the immutable header region. -p, --package PACKAGE_FILE Query an (uninstalled) package PACKAGE_FILE. The PACKAGE_FILE may be specified as an ftp or http style URL, in which case the package header will be downloaded and queried. See FTP/HTTP OPTIONS for information on rpm's internal ftp and http client support. The PACKAGE_FILE argument(s), if not a binary package, will be interpreted as an ASCII package manifest. Comments are permitted, starting with a '#', and each line of a package manifest file may include white space seperated glob expressions, including URL's with remote glob expressions, that will be expanded to paths that are substituted in place of the package manifest as additional PACKAGE_FILE arguments to the query. --pkgid MD5 Query package that contains a given package identifier, i.e. the MD5 digest of the combined header and payload contents. --querybynumber HDRNUM Query the HDRNUMth database entry directly; this is useful only for debugging. --specfile SPECFILE Parse and query SPECFILE as if it were a package. Although not all the information (e.g. file lists) is available, this type of query permits rpm to be used to
extract information from spec files without having to write a specfile parser. --tid TID Query package(s) that have a given TID transaction identifier. A unix time stamp is currently used as a transaction identifier. All package(s) installed or erased within a single transaction have a common identifier. --triggeredby PACKAGE_NAME Query packages that are triggered by package(s) PACKAGE_NAME. --whatprovides CAPABILITY Query all packages that provide the CAPABILITY capability. --whatrequires CAPABILITY Query all packages that requires CAPABILITY for proper functioning. PACKAGE QUERY OPTIONS: --changelog Display change information for the package. -c, --configfiles List only configuration files (implies -l). -d, --docfiles List only documentation files (implies -l). --dump Dump file information as follows: path size mtime md5sum mode owner group isconfig isdoc rdev symlink This option must be used with at least one of -l, -c, -d. --filesbypkg List all the files in each selected package. -i, --info Display package information, including name, version, and description. This uses the --queryformat if one was specified. --last Orders the package listing by install time such that the latest packages are at the top. -l, --list List files in package. --provides List capabilities this package provides. -R, --requires List packages on which this package depends. --scripts List the package specific scriptlet(s) that are used as part of the installation and uninstallation processes. -s, --state Display the states of files in the package (implies -l). The state of each file is one of normal, not installed, or replaced. --triggers, --triggerscripts Display the trigger scripts, if any, which are contained in the package. VERIFY OPTIONS The general form of an rpm verify command is rpm {-V|--verify} [select-options] [verify-options] Verifying a package compares information about the installed files in the package
with information about the files taken from the package metadata stored in the rpm database. Among other things, verifying compares the size, MD5 sum, permissions, type, owner and group of each file. Any discrepencies are displayed. Files that were not installed from the package, for example, documentation files excluded on installation using the "--excludedocs" option, will be silently ignored. The package selection options are the same as for package querying (including package manifest files as arguments). Other options unique to verify mode are: --nodeps Don't verify dependencies of packages. --nodigest Don't verify package or header digests when reading. --nofiles Don't verify any attributes of package files. --noscripts Don't execute the %verifyscript scriptlet (if any). --nosignature Don't verify package or header signatures when reading. --nolinkto --nomd5 --nosize --nouser --nogroup --nomtime --nomode --nordev Don't verify the corresponding file attribute. The format of the output is a string of 8 characters, a possible attribute marker:
c d g l r
%config configuration file. %doc documentation file. %ghost file (i.e. the file contents are not included in the package payload). %license license file. %readme readme file.
from the package header, followed by the file name. Each of the 8 characters denotes the result of a comparison of attribute(s) of the file to the value of those attribute(s) recorded in the database. A single "." (period) means the test passed, while a single "?" (question mark) indicates the test could not be performed (e.g. file permissions prevent reading). Otherwise, the (mnemonically emBoldened) character denotes failure of the corresponding --verify test: S M 5 D L U G T
file Size differs Mode differs (includes permissions and file type) MD5 sum differs Device major/minor number mis-match readLink(2) path mis-match User ownership differs Group ownership differs mTime differs
DIGITAL SIGNATURE AND DIGEST VERIFICATION The general forms of rpm digital signature commands are
rpm --import PUBKEY ... rpm {--checksig} [--nosignature] [--nodigest] PACKAGE_FILE ... The --checksig option checks all the digests and signatures contained in PACKAGE_FILE to ensure the integrity and origin of the package. Note that signatures are now verified whenever a package is read, and --checksig is useful to verify all of the digests and signatures associated with a package. Digital signatures cannot be verified without a public key. An ascii armored public key can be added to the rpm database using --import. An imported public key is carried in a header, and key ring management is performed exactly like package management. For example, all currently imported public keys can be displayed by: rpm -qa gpg-pubkey* Details about a specific public key, when imported, can be displayed by querying. Here's information about the Red Hat GPG/DSA key: rpm -qi gpg-pubkey-db42a60e Finally, public keys can be erased after importing just like packages. Here's how to remove the Red Hat GPG/DSA key rpm -e gpg-pubkey-db42a60e SIGNING A PACKAGE rpm --addsign|--resign PACKAGE_FILE ... Both of the --addsign and --resign options generate and insert new signatures for each package PACKAGE_FILE given, replacing any existing signatures. There are two options for historical reasons, there is no difference in behavior currently. USING GPG TO SIGN PACKAGES In order to sign packages using GPG, rpm must be configured to run GPG and be able to find a key ring with the appropriate keys. By default, rpm uses the same conventions as GPG to find key rings, namely the $GNUPGHOME environment variable. If your key rings are not located where GPG expects them to be, you will need to configure the macro %_gpg_path to be the location of the GPG key rings to use. For compatibility with older versions of GPG, PGP, and rpm, only V3 OpenPGP signature packets should be configured. Either DSA or RSA verification algorithms can be used, but DSA is preferred. If you want to be able to sign packages you create yourself, you also need to create your own public and secret key pair (see the GPG manual). You will also need to configure the rpm macros %_signature The signature type. Right now only gpg and pgp are supported.
%_gpg_name The name of the "user" whose key you wish to use to sign your packages. For example, to be able to use GPG to sign packages as the user "John Doe " from the key rings located in /etc/rpm/.gpg using the executable /usr/bin/gpg you would include %_signature gpg %_gpg_path /etc/rpm/.gpg %_gpg_name John Doe %_gpgbin /usr/bin/gpg in a macro configuration file. Use /etc/rpm/macros for per-system configuration and ~/.rpmmacros for per-user configuration. REBUILD DATABASE OPTIONS The general form of an rpm rebuild database command is rpm {--initdb|--rebuilddb} [-v] [--dbpath DIRECTORY] [--root DIRECTORY] Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers. SHOWRC The command rpm --showrc shows the values rpm will use for all of the options are currently set in rpmrc and macros configuration file(s). FTP/HTTP OPTIONS rpm can act as an FTP and/or HTTP client so that packages can be queried or installed from the internet. Package files for install, upgrade, and query operations may be specified as an ftp or http style URL: ftp://USER:PASSWORD@HOST:PORT/path/to/package.rpm If the :PASSWORD portion is omitted, the password will be prompted for (once per user/hostname pair). If both the user and password are omitted, anonymous ftp is used. In all cases, passive (PASV) ftp transfers are performed. rpm allows the following options to be used with ftp URLs: --ftpproxy HOST The host HOST will be used as a proxy server for all ftp transfers, which allows users to ftp through firewall machines which use proxy systems. This option may also be specified by configuring the macro %_ftpproxy. --ftpport HOST The TCP PORT number to use for the ftp connection on the proxy ftp server instead of the default port. This option may also be specified by configuring the macro %_ftpport. rpm allows the following options to be used with http URLs:
--httpproxy HOST The host HOST will be used as a proxy server for all http transfers. This option may also be specified by configuring the macro %_httpproxy. --httpport PORT The TCP PORT number to use for the http connection on the proxy http server instead of the default port. This option may also be specified by configuring the macro %_httpport. LEGACY ISSUES Executing rpmbuild The build modes of rpm are now resident in the /usr/bin/rpmbuild executable. Although legacy compatibility provided by the popt aliases below has been adequate, the compatibility is not perfect; hence build mode compatibility through popt aliases is being removed from rpm. Install the rpmbuild package, and see rpmbuild(8) for documentation of all the rpm build modes previously documented here in rpm(8). Add the following lines to /etc/popt if you wish to continue invoking rpmbuild from the rpm command line: rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm rpm
exec exec exec exec exec exec exec exec exec exec exec exec exec exec exec exec exec exec exec exec exec
--bp --bc --bi --bl --ba --bb --bs --tp --tc --ti --tl --ta --tb --ts --rebuild --recompile --clean --rmsource --rmspec --target --short-circuit
rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb rpmb
-bp -bc -bi -bl -ba -bb -bs -tp -tc -ti -tl -ta -tb -ts --rebuild --recompile --clean --rmsource --rmspec --target --short-circuit
SEE ALSO popt(3), rpm2cpio(8), rpmbuild(8), http://www.rpm.org/ http://www.rpm.org/>
39. Simplified overview Kernel parameters Solaris, AIX, Linux: ==============================================================
Throughout this document, you can find many other examples of settings. This section is only a simplified overview. 39.1 Solaris: ------------The "/etc/system" file: Available for Solaris Operating Environment, the /etc/system file contains definitions for kernel configuration limits such as the maximum number of users allowed on the system at a time, the maximum number of processes per user, and the inter-process communication (IPC) limits on size and number of resources. These limits are important because they affect, for example, DB2, Oracle performance on a Solaris Operating Environment machine. Some examples: set set set set set set set set set .. ..
shmsys:shminfo_shmmax=4294967295 shmsys:shminfo_shmmin=1 shmsys:shminfo_shmmni=100 shmsys:shminfo_shmseg=10 semsys:seminfo_semmni=100 semsys:seminfo_semmsl=100 semsys:seminfo_semmns=2500 semsys:seminfo_semopm=100 semsys:seminfo_semvmx=32767
You can use, among others, the "ipcs" command and "adb" command to retrieve kernel parameters and mem info. Some remarks on Shared Memory and Semaphores: - Shared Memory Shared memory provides the fastest way for processes to pass large amounts of data to one another. As the name implies, shared memory refers to physical pages of memory that are shared by more than one process. Of particular interest is the "Intimate Shared Memory" facility, where the translation tables are shared as well as the memory. This enhances the effectiveness of the TLB (Translation Lookaside Buffer), which is a CPU-based cache of translation table information. Since the same information is used for several processes, available buffer space can be used much more efficiently. In addition, ISM-designated memory cannot be paged out, which can be used to keep frequently-used data and binaries in memory. Database applications are the heaviest users of shared memory. Vendor recommendations should be consulted when tuning the shared memory parameters.
Solaris 10 only uses the shmmax and shmmni parameters. (Other parameters are set dynamically within the Solaris 10 IPC model.) shmmax (max-shm-memory in Solaris 10+): This is the maximum size of a shared memory segment (ie the largest value that can be used by shmget). Its theoretical maximum value is 4294967295 (4GB), but practical considerations usually limit it to less than this. There is no reason not to tune this value as high as possible, since no kernel resources are allocated based on this parameter. Solaris 10 sets shmmax to 1/4 physical memory by default, vs 512k for previous versions. shmmin: This is the smallest possible shared memory segment size. The default is 1 byte; this parameter should probably not be tuned. shmmni (max-shm-ids in Solaris 10+): Maximum number of shared memory identifiers at any given time. This parameter is used by kernel memory allocation to determine how much size to put aside for shmid_ds structures. Each of these is 112 bytes and requires an additional 8 bytes for a mutex lock; if it is set too high, memory useage can be a problem. The maximum setting for this variable in Solaris 2.5.1 and 2.6 is 2147483648 (2GB), and the default is 100. For Solaris 10, the default is 128 and the maximum is MAXINT. shmseg: Maximum number of segments per process. It is usually set to shmmni, but it should always be less than 65535. Sun documentations suggests a maximum for this parameter of 32767 and a default of 8 for Solaris 2.5.1 and 2.6. - Semaphores Semaphores are a shareable resource that take on a non-negative integer value. They are manipulted by the P (wait) and V (signal) functions, which decrement and increment the semaphore, respectively. When a process needs a resource, a "wait" is issued and the semaphore is decremented. When the semaphore contains a value of zero, the resources are not available and the calling process spins or blocks (as appropriate) until resources are available. When a process releases a resource controlled by a semaphore, it increments the semaphore and the waiting processes are notified. Solaris 10 only uses the semmni, semmsl and semopm parameters. (Other parameters are dynamic within the Solaris 10 IPC model.) semmap: This sets the number of entries in the semaphore map. This should never be greater than semmni. If the number of semaphores per semaphore set used by the application is "n" then set semmap = ((semmni + n - 1)/n)+1 or more. Alternatively, we can set semmap to semmni x semmsl. An undersized semmap leads to "WARNING: rmfree map overflow" errors. The default setting is 10; the maximum for Solaris 2.6 is 2GB. The default for Solaris 9 was 25; Solaris 10 increased the default to 512. The limit is SHRT_MAX.
semmni (max-sem-ids in Solaris 10+): Maximum number of systemwide semaphore sets. Each control structure consumes 84 bytes. For Solaris 2.5.1-9, the default setting is 10; for Solaris 10, the default setting is 128. The maximum is 65535 semmns: Maximum number of semaphores in the system. Each structure uses 16 bytes. This parameter should be set to semmni x semmsl. The default is 60; the maximum is 2GB. semmnu: Maximum number of undo structures in the system. This should be set to semmni so that each control structure has an undo structure. The default is 30, the maximum is 2 GB. semmsl (max-sem-nsems in Solaris 10+): Maximum number of semaphores per semaphore set. The default is 25, the maximum is 65535. semopm (max-sem-ops in Solaris 10+): Maximum number of semaphore operations that can be performed in each semop call. The default in Solaris 2.5.1-9 is 10, the maximum is 2 GB. Solaris 10 increased the default to 512. semume: Maximum number of undo structures per process. This should be set to semopm times the number of processes that will be using semaphores at any one time. The default is 10; the maximum is 2 GB. semusz: Number of bytes required for semume undo structures. This should not be tuned; it is set to semume x (1 + sizeof(undo)). The default is 96; the maximum is 2 GB. semvmx: Maximum value of a semaphore. This should never exceed 32767 (default value) unless SEM_UNDO is never used. The default is 32767; the maximum is 65535. semaem: Maximum adjust-on-exit value. This should almost always be left alone. The default is 16384; the maximum is 32767.
39.2 Linux: ----------Kernel parameters used for system configuration are found in "/proc/sys/kernel", where you will find an individual file for each configuration parameter. Because these parameters have a direct effect on system performance and viability, you must have root access in order to modify them. Occasionally, a prerequisite to a package installation requires the modification of kernel parameters. Since each parameter file contains a single line of data consisting of either a text string or numeric values, it is often easy to modify a parameter by simply using the echo command: # echo 2048 > /proc/sys/kernel/msgmax The aforementioned command will set the value of the msgmax parameter to 2048. -- More on the proc File System: The Linux kernel has two primary functions: to control access to physical devices on the computer
and to schedule when and how processes interact with these devices. The /proc/ directory contains a hierarchy of special files which represent the current state of the kernel � allowing applications and users to peer into the kernel's view of the system. Within the /proc/ directory, one can find a wealth of information about the system hardware and any processes currently running. In addition, some of the files within the /proc/ directory tree can be manipulated by users and applications to communicate configuration changes to the kernel. Under Linux, all data are stored as files. Most users are familiar with the two primary types of files: text and binary. But the /proc/ directory contains another type of file called a virtual file. It is for this reason that /proc/ is often referred to as a virtual file system. These virtual files have unique qualities. Most of them are listed as zero bytes in size and yet when one is viewed, it can contain a large amount of information. In addition, most of the time and date settings on virtual files reflect the current time and date, indicative of the fact they constantly changing. Virtual files such as interrupts, /proc/meminfo, /proc/mounts, and /proc/partitions provide an up-to-the-moment glimpse of the system's hardware. Others, like /proc/filesystems and the /proc/sys/ directory provide system configuration information and interfaces. For organizational purposes, files containing information on a similar topic are grouped into virtual directories and sub-directories. For instance, /proc/ide/ contains information for all physical IDE devices. Likewise, process directories contain information about each running process on the system. By using the cat, more, or less commands on files within the /proc/ directory, you can immediately access an enormous amount of information about the system. For example, if you want to see what sort of CPU your computer has, type "cat /proc/cpuinfo" and you will see something similar to the following: processor : vendor_id : cpu family : model : model name : stepping : cpu MHz cache size : fdiv_bug : hlt_bug f00f_bug : coma_bug : fpu : fpu_exception
0 AuthenticAMD 5 9 AMD-K6(tm) 3D+ Processor 1 : 400.919 256 KB no : no no no yes : yes
cpuid level wp flags bogomips
: : : :
1 yes fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr 799.53
When viewing different virtual files in the /proc/ file system, you will notice some of the information is easily understandable while some is not human-readable. This is in part why utilities exist to pull data from virtual files and display it in a useful way. Some examples of such applications are lspci, apm, free, and top. As a general rule, most virtual files within the /proc/ directory are read only. However, some can be used to adjust settings in the kernel. This is especially true for files in the /proc/sys/ subdirectory. To change the value of a virtual file, use the echo command and a > symbol to redirect the new value to the file. For instance, to change your hostname on the fly, you can type: echo bob.subgenius.com > /proc/sys/kernel/hostname Other files act as binary or boolean switches. For instance, if you type cat /proc/sys/net/ipv4/ip_forward, you will see either a 0 or a 1. A 0 indicates the kernel is not forwarding network packets. By using the echo command to change the value of the ip_forward file to 1, you can immediately turn packet forwarding on. Another command used to alter settings in the /proc/sys/ subdirectory is /sbin/sysctl. -- sysctl: Linux also provides the sysctl command to modify kernel parameters at runtime. Sysctl uses parameter information stored in a file called /etc/sysctl.conf. If, for example, we wanted to change the value of the msgmax parameter as we did above, but this time using sysctl, the command would look like this: # sysctl -w kernel.msgmax=2048 - About the kernel: Finding the Kernel Locate the kernel image on your hard disk. It should be in the file /vmlinuz, or /vmlinux, or /boot/vmlinux In some installations, /vmlinuz is a soft link to the actual kernel, so you may need to track down the kernel by following the links. On Redhat 6.1 it is in "/boot/vmlinuz". To find the kernel being used look in "/etc/lilo.conf".
You can also type "uname -a" to see the kernel version. /proc/cmdline This file shows the parameters passed to the kernel at the time it is started. A sample /proc/cmdline file looks like this: ro root=/dev/hda2 This tell us the kernel is mounted read-only � signified by (ro) � off of the second partition on the first IDE device (/dev/hda2). - Kernel, memory tuning: Most about tuning memory en kernel params seem to do with the "/etc/sysctl.conf" file: In most distributions, the "/etc/sysctl.conf" determines the limits and/or behaviour of the kernel and memory. If you type "sysctl -a |more" you will see a long list of kernel parameters. You can use this sysctl program to modify these parameters, for example: # sysctl -w kernel.shmmax=100000000 # sysctl -w fs.file-max=65536 # echo "kernel.shmmax = 100000000" >> /etc/sysctl.conf Example configuration: setting kernel parameters before installing Oracle 10g: -----------------------------------------------------------------------------Most out of the box kernel parameters (of RHELS 3,4,5) are set correctly for Oracle except a few. You should have the following minimal configuration: net.ipv4.ip_local_port_range 1024 65000 kernel.sem 250 32000 100 128 kernel.shmmni 4096 kernel.shmall 2097152 kernel.shmmax 2147483648 fs.file-max 65536 You can check the most important parameters using the following command: # /sbin/sysctl -a | egrep 'sem|shm|file-max|ip_local' net.ipv4.ip_local_port_range = 1024 kernel.sem = 250 32000 100 128 kernel.shmmni = 4096 kernel.shmall = 2097152
65000
kernel.shmmax = 2147483648 fs.file-max = 65536 If some value should be changed, you can change the "/etc/sysctl.conf" file and run the "/sbin/sysctl -p" command to change the value immediately. Every time the system boots, the init program runs the /etc/rc.d/rc.sysinit script. This script contains a command to execute sysctl using /etc/sysctl.conf to dictate the values passed to the kernel. Any values added to /etc/sysctl.conf will take effect each time the system boots.
Example configuration: from: Installing Oracle 91 on Linux ----------------------------------------------------------For Linux, use the ipcs command to obtain a list of the system's current shared memory segments and semaphore sets, and their identification numbers and owner. Perform the following steps to modify the kernel parameters by using the /proc file system. Log in as the root user. Change to the /proc/sys/kernel directory. Review the current semaphore parameter values in the sem file by using the cat or more utility. For example, using the cat utility, enter the following command: # cat sem The output lists, in order, the values for the SEMMSL, SEMMNS, SEMOPM, and SEMMNI parameters. The following example shows how the output appears: 250 32000 32 128 In the preceding output example, 250 is the value of the SEMMSL parameter, 32000 is the value of the SEMMNS parameter, 32 is the value of the SEMOPM parameter, and 128 is the value of the SEMMNI parameter. Modify the parameter values by using the following command syntax: # echo SEMMSL_value SEMMNS_value SEMOPM_value SEMMNI_value > sem Replace the parameter variables with the values for your system in the order that they are entered in the preceding example. For example: # echo 100 32000 100 100 > sem Review the current shared memory parameters by using the cat or more utility. For example, using the cat utility, enter the following command:
# cat shared_memory_parameter In the preceding example, the variable shared_memory_parameter is either the SHMMAX or SHMMNI parameter. The parameter name must be entered in lowercase letters. Modify the shared memory parameter by using the echo utility. For example, to modify the SHMMAX parameter, enter the following command: # echo 2147483648 > shmmax Modify the shared memory parameter by using the echo utility. For example, to modify the SHMMNI parameter, enter the following command: # echo 4096 > shmmni Modify the shared memory parameter by using the echo utility. For example, to modify the SHMALL parameter, enter the following command: # echo 2097152 > shmall Write a script to initialize these values during system startup, and include the script in your system init files. See Also: Your system vendor's documentation for more information on script files and init files. Set the File Handles by using ulimit -n and /proc/sys/fs/file-max. # echo 65536 > /proc/sys/fs/file-max ulimit -n 65536 Set the Sockets to /proc/sys/net/ipv4/ip_local_port_range # echo 1024 65000 > /proc/sys/net/ipv4/ip_local_port_change Set the Process limit by using ulimit -u. This will give you the number of processes per user. ulimit -u 16384 39.4 Linux modules: ------------------Modules on Linux (1): --------------------- insmod, rmmod, lsmod lsmod: ------
lsmod - list loaded modules. SYNOPSIS lsmod [-hV] DESCRIPTION lsmod shows information about all loaded modules. The format is name, size, use count, list of referring modules. The information displayed is identical to that available from "/proc/modules". If the module controls its own unloading via a can_unload routine then the user count displayed by lsmod is always -1, irrespective of the real use count. insmod: ------insmod - install loadable kernel module SYNOPSIS insmod [-fhkLmnpqrsSvVxXyYN] [-e persist_name] [-o module_name] [-O blob_name] [-P prefix] module [ symbol=value ... ] DESCRIPTION insmod installs a loadable module in the running kernel. insmod tries to link a module into the running kernel by resolving all symbols from the kernel's exported symbol table. If the module file name is given without directories or extension, insmod will search for the module in some common default directories. The environment variable MODPATH can be used to override this default. If a module configuration file such as /etc/modules.conf exists, it will override the paths defined in MODPATH. The environment variable MODULECONF can also be used to select a different configuration file from the default /etc/modules.conf (or /etc/conf.modules (deprecated)). This environment variable will override all the definitions above. When environment variable UNAME_MACHINE is set, modutils will use its value instead of the machine field from the uname() syscall. This is mainly of use when you are compiling 64 bit modules in 32 bit user space or vice versa, set UNAME_MACHINE to the type of the modules. Current modutils does not support full cross build mode for modules, it is limited to choosing between 32 and 64 bit versions of the host architecture. rmmod: -----rmmod - unload loadable modules SYNOPSIS rmmod [ -aehrsvV ] module ... DESCRIPTION
rmmod unloads loadable modules from the running kernel. rmmod tries to unload a set of modules from the kernel, with the restriction that they are not in use and that they are not referred to by other modules. If more than one module is named on the command line, the modules will be removed in the given order. This supports unloading of stacked modules. With the option '-r', a recursive removal of modules will be attempted. This means that if a top module in a stack is named on the command line, all modules that are used by this module will be removed as well, if possible.
More info about the mod commands: --------------------------------- Hardware Detection with the Help of hwinfo hwinfo can detect the hardware of your system and select the drivers needed to run this hardware. Get a small introduction to this command with hwinfo --help. If you, for example, need information about your SCSI devices, use the command hwinfo --scsi. All this information is also available in YaST in the hardware information module. - Handling Modules The following commands are available: insmod insmod loads the requested module after searching for it in a subdirectory of /lib/modules/. It is better, however, to use modprobe rather than insmod. rmmod Unloads the requested module. This is only possible if this module is no longer needed. For example, the isofs module cannot be unloaded while a CD is still mounted. depmod Creates the file modules.dep in /lib/modules/ that defines the dependencies of all the modules. This is necessary to ensure that all dependent modules are loaded with the selected ones. This file will be built after the system is started if it does not exist. modprobe Loads or unloads a given module while taking into account dependencies of this module. This command is extremely powerful and can be used for a lot of things (e.g., probing all modules of a given type until one is successfully loaded). In contrast to insmod, modprobe checks /etc/modprobe.conf and therefore is the preferred method of loading modules. For detailed information about this
topic, refer to the corresponding man page. lsmod Shows which modules are currently loaded as well as how many other modules are using them. Modules started by the kernel daemon are tagged with autoclean. This label denotes that these modules will automatically be removed once they reach their idle time limit. modinfo Shows module information. /etc/modprobe.conf The loading of modules is affected by the files /etc/modprobe.conf and /etc/modprobe.conf.local and the directory /etc/modprobe.d. See man modprobe.conf. Parameters for modules that access hardware directly must be entered in this file. Such modules may need system-specific options (e.g., CD-ROM driver or network driver). The parameters used here are described in the kernel sources. Install the package kernel-source and read the documentation in the directory /usr/src/linux/Documentation. Kmod � the Kernel Module Loader The kernel module loader is the most elegant way to use modules. Kmod performs background monitoring and makes sure the required modules are loaded by modprobe as soon as the respective functionality is needed in the kernel. To use Kmod, activate the option �Kernel module loader� (CONFIG_KMOD) in the kernel configuration. Kmod is not designed to unload modules automatically; in view of today's RAM capacities, the potential memory savings would be marginal. For reasons of performance, monolithic kernels may be more suitable for servers that are used for special tasks and need only a few drivers. modprobe.conf: -------------Example 1: # This file is autogenerated from /etc/modules.conf using generate-modprobe.conf command alias eth1 sk98lin alias eth0 ipw2200 alias sound-slot-0 snd-hda-intel install scsi_hostadapter /sbin/modprobe ahci; /bin/true remove snd-hda-intel /sbin/modprobe -r snd-pcm-oss; /sbin/modprobe --first-time -r --ignore-remove snd-hda-intel install snd-hda-intel /sbin/modprobe --first-time --ignore-install snd-hda-intel && { /sbin/modprobe snd-pcm-oss; /bin/true; } install usb-interface /sbin/modprobe uhci-hcd; /sbin/modprobe ehci-hcd; /bin/true #alias eth1 eth1394
alias ieee1394-controller ohci1394 alias net-pf-10 off #irda alias tty-ldisc-11 irtty alias char-major-161-* ircomm-tty # Para nsc 383 SIO: alias char-major-160-* nsc-ircc alias irda0 nsc-ircc options nsc-irc io=0x2f8 irq=3 dma=0 install nsc-ircc { /bin/setserial /dev/ttyS1 uart none; } ; /sbin/modprobe -first-time --ignore-install nsc-ircc #irda: 0x2f8, irq 3, dma 0 #lpt: 0x3f8, irq 7, dma 1 options parport_pc io=0x378 irq=7 dma=1 Example 2: alias ieee1394-controller ohci1394 alias eth0 eepro100 alias sound-slot-0 emu10k1 alias net-pf-10 off install snd-emu10k1 /sbin/modprobe --first-time --ignore-install snd-emu10k1 && { /sbin/modprobe snd-pcm-oss; /bin/true; } install usb-interface /sbin/modprobe usb-uhci; /sbin/modprobe ehci-hcd; /bin/true remove snd-emu10k1 { /sbin/modprobe -r snd-pcm-oss; } ; /sbin/modprobe -r --firsttime --ignore-remove snd-emu10k1 /etc/sysconfig: --------------Note 1: ------SuSEconfig and /etc/sysconfig The main configuration of SUSE LINUX can be made with the configuration files in /etc/sysconfig. Former versions of SUSE LINUX relied on /etc/rc.config for system configuration, but it became obsolete in previous versions. /etc/rc.config is not created at installation time, as all system configuration is controlled by /etc/sysconfig. However, if /etc/rc.config exists at the time of a system update, it remains intact. The individual files in /etc/sysconfig are only read by the scripts to which they are relevant. This ensures that network settings, for instance, need to be parsed only by network-related scripts. Apart from that, there are many other system configuration files that are generated according to the settings in /etc/sysconfig. This task is performed by SuSEconfig. For example, if you change the network configuration, SuSEconfig is likely to make changes to the file /etc/host.conf as well, as this is one of the files
relevant for the network configuration. If you change anything in these files manually, run SuSEconfig afterwards to make sure all the necessary changes are made in all the relevant places. If you change the configuration using the YaST sysconfig editor, all changes are applied automatically � YaST automatically starts SuSEconfig to update the configuration files as needed. This concept enables you to make basic changes to your configuration without needing to reboot the system. Because some changes are rather complex, some programs must be restarted for the changes to take effect. For instance, changes to the network configuration may require a restart of the network programs concerned. This can be achieved by entering the commands rcnetwork stop and rcnetwork start. Note 2: ------The Linux sysconfig directory The /etc/sysconfig directory is where many of the files that control the system configuration are stored. This section lists these files and many of the optional values in the files used to make system changes. To get complete information on these files read the file /usr/doc/initscripts4.48/sysconfig.txt. /etc/sysconfig/clock Used to configure the system clock to Universal or local time and set some other clock parameters. An example file: UTC=false ARC=false Options: UTC - true means the clock is set to UTC time otherwise it is at local time ARC - Set true on alpha stations only. It indicates the ARC console's 42-year time offset is in effect. If not set to true, the normal Unix epoch is assumed. ZONE="filename" - indicates the zonefile under the directory /usr/share/zoneinfo that the /etc/localtime file is a copy of. This may be set to: ZONE="US/Eastern" /etc/sysconfig/init This file is used to set some terminal characteristics and environment variables. A sample listing: # color => new RH6.0 bootup # verbose => old-style bootup # anything else => new style bootup without ANSI colors or positioning BOOTUP=color # column to start "[ OK ]" label in RES_COL=60 # terminal sequence to move to that column. You could change this # to something like "tput hpa ${RES_COL}" if your terminal supports it MOVE_TO_COL="echo -en \\033[${RES_COL}G" # terminal sequence to set color to a 'success' color (currently: green) SETCOLOR_SUCCESS="echo -en \\033[1;32m"
# terminal sequence to set color to a 'failure' color (currently: red) SETCOLOR_FAILURE="echo -en \\033[1;31m" # terminal sequence to set color to a 'warning' color (currently: yellow) SETCOLOR_WARNING="echo -en \\033[1;33m" # terminal sequence to reset to the default color. SETCOLOR_NORMAL="echo -en \\033[0;39m" # default kernel loglevel on boot (syslog will reset this) LOGLEVEL=1 # Set to something other than 'no' to turn on magic sysrq keys... MAGIC_SYSRQ=no # Set to anything other than 'no' to allow hotkey interactive startup... PROMPT=yes Options: BOOTUP=bootupmode - Choices are color, or verbose. The choice color sets new boot display. The choice verbose sets old style display. Anything else sets a new display without ANSI formatting. LOGLEVEL=number - Sets the initial console logging level for the kernel. The default is 7. The values are: emergency, panic - System is unusable alert - Action must be taken immediately crit - Critical conditions err, error (depreciated) - Error conditions warning, warn (depreciated) - Warning conditions notice - Normal but significant conditions info - Informational message debug - Debug level message RES_COL=number - Screen column to start status labels at. The Default is 60. MOVE_TO_COL=command - A command to move the cursor to $RES_COL. SETCOLOR_SUCCESS=command - Set the color used to indicate success. SETCOLOR_FAILURE=command - Set the color used to indicate failure. SETCOLOR_WARNING=command - Set the color used to indicate warning. SETCOLOR_NORMAL=command - Set the color used tor normal color MAGIC_SYSRQ=yes|no - Set to 'no' to disable the magic sysrq key. PROMPT=yes|no - Set to 'no' to disable the key check for interactive mode. /etc/sysconfig/keyboard Used to configure the keyboard. Used by the startup script /etc/rc.d/rc.sysinit. An example file: KEYTABLE="us" Options: KEYTABLE="keytable file" - The line [ KEYTABLE="/usr/lib/kbd/keytables/us.map" ] tells the system to use the file shown for keymapping. KEYBOARDTYPE=sun|pc - The selection, "sun", indicates attached on /dev/kbd is a sun keyboard. The selection "pc" indicates a PS/2 keyboard is on the ps/2 port. /etc/sysconfig/mouse This file is used to configure the mouse. An example file: FULLNAME="Generic - 2 Button Mouse (PS/2)" MOUSETYPE="ps/2" XEMU3="yes" XMOUSETYPE="PS/2" Options: MOUSETYPE=type - Choices are microsoft, mouseman, mousesystems, ps/2, msbm,
logibm, atibm, logitech, mmseries, or mmhittab. XEMU3=yes|no - If yes, emulate three buttons, otherwise not. /etc/sysconfig/network Used to configure networking options. All IPX options default to off. An example file: NETWORKING=yes FORWARD_IPV4="yes" HOSTNAME="mdct-dev3" GATEWAY="10.1.0.25" GATEWAYDEV="eth0" Options: NETWORKING=yes|no - Sets network capabilities on or off. HOSTNAME="hostname". To work with old software, the /etc/HOSTNAME file should contain the same hostname. FORWARD_IPV4=yes|no - Turns the ability to perform IP forwarding on or off. Turn it on if you want to use the machine as a router. Turn it off to use it as a firewall or IP masquerading. DEFRAG_IPV4=yes|no - Set this to automatically defragment IPv4 packets. This is good for masquerading, and a bad idea otherwise. It defaults to 'no'. GATEWAY="gateway IP" GATEWAYDEV="gateway device" Possible values include eth0, eth1, or ppp0. NISDOMAIN="nis domain name" IPX=yes|no - Turn IPX ability on or off. IPXAUTOPRIMARY=on|off - Must not be yes or no. IPXAUTOFRAME=on|off IPXINTERNALNETNUM="netnum" IPXINTERNALNODENUM="nodenum" /etc/sysconfig/static-routes Configures static routes on a network. Used to set up static routing. An example file: eth1 net 192.168.199.0 netmask 255.255.255.0 gw 192.168.199.1 eth0 net 10.1.0.0 netmask 255.255.0.0 gw 10.1.0.153 eth1 net 255.255.255.255 netmask 255.255.255.255 The syntax is: device net network netmask netmask gw gateway The device may be a device name such as eth0 which is used to have the route brought up and down as the device is brought up or down. The value can also be "any" to let the system calculate the correct devices at run time. /etc/sysconfig/routed Sets up dynamic routing policies. An example file: EXPORT_GATEWAY="no" SILENT="yes" Options: SILENT=yes|no EXPORT_GATEWAY=yes|no /etc/sysconfig/pcmcia
Used to configure pcmcia network cards. An example file: PCMCIA=no PCIC= PCIC_OPTS= CORE_OPTS= Options: PCMCIA=yes|no PCIC=i82365|tcic PCIC_OPTS=socket driver (i82365 or tcic) timing parameters CORE_OPTS=pcmcia_core options CARDMGR_OPTS=cardmgr options /etc/sysconfig/amd Used to configure the auto mount daemon. An example file: ADIR=/.automount MOUNTPTS='/net /etc/amd.conf' AMDOPTS= Options: ADIR=/.automount (normally never changed) MOUNTPTS='/net /etc/amd.conf' (standard automount stuff) AMDOPTS= (extra options for AMD) /etc/sysconfig/tape Used for backup tape device configuration. Options: DEV=/dev/nst0 - The tape device. Use the non-rewinding tape for these scripts. For SCSI tapes the device is /dev/nst#, where # is the number of the tape drive you want to use. If you only have one then use nst0. For IDE tapes the device is /dev/ht#. For floppy tape drives the device is /dev/ftape. ADMIN=root - The person to mail to if the backup fails for any reason SLEEP=5 - The time to sleep between tape operations. BLOCKSIZE=32768 - This worked fine for 8mm, then 4mm, and now DLT. An optimal setting is probably the amount of data your drive writes at one time. SHORTDATE=$(date +%y:%m:%d:%H:%M) - A short date string, used in backup log filenames. DAY=$(date +log-%y:%m:%d) - Used for the log file directory. DATE=$(date) - Date string, used in log files. LOGROOT=/var/log/backup - Root of the logging directory LIST=$LOGROOT/incremental-list - This is the file name the incremental backup will use to store the incremental list. It will be $LIST-{some number}. DOTCOUNT=$LOGROOT/.count - For counting as you go to know which incremental list to use. COUNTER=$LOGROOT/counter-file - For rewinding when done...might not use. BACKUPTAB=/etc/backuptab - The file in which we keep our list of backup(s) we want to make. /etc/sysconfig/sendmail An example file: DAEMON=yes QUEUE=1h Options: DAEMON=yes|no - yes implies -bd QUEUE=1h - Given to sendmail as -q$QUEUE. The -q option is not given to sendmail
if /etc/sysconfig/sendmail exists and QUEUE is empty or undefined. /etc/sysconfig/i18n Controls the system font settings. The language variables are used in /etc/profile.d/lang.sh. An example i18n file: LANG="en_US" LC_ALL="en_US" LINGUAS="en_US" Options: LANG= set locale for all categories, can be any two letter ISO language code. LC_CTYPE= localedata configuration for classification and conversion of characters. LC_COLLATE= localedata configuration for collation (sort order) of strings. LC_MESSAGES= localedata configuration for translation of yes and no messages. LC_NUMERIC= localedata configuration for non-monetary numeric data. LC_MONETARY= localedata configuration for monetary data. LC_TIME= localedata configuration for date and time. LC_ALL= localedata configuration overriding all of the above. LANGUAGE= can be a : separated list of ISO language codes. LINGUAS= can be a ' ' separated list of ISO language codes. SYSFONT= any font that is legal when used as /usr/bin/consolechars -f $SYSFONT ... (See console-tools package for consolechars command) UNIMAP= any SFM (screen font map, formerly called Unicode mapping table - see consolechars(8)) /usr/bin/consolechars -f $SYSFONT --sfm $UNIMAP SYSFONTACM= any ACM (application charset map - see consolechars(8)) /usr/bin/consolechars -f $SYSFONT --acm $SYSFONTACM The above is used by the /sbin/setsysfont command (which is run by rc.sysinit at boot time.)
/etc/sysconfig/network-scripts/ifup: /etc/sysconfig/network-scripts/ifdown: These are symbolic links to /sbin/ifup and /sbin/ifdown, respectively. These symlinks are here for legacy purposes only. They will probably be removed in future versions. These scripts take one argument normally: the name of the device (e.g. eth0). They are called with a second argument of "boot" during the boot sequence so that devices that are not meant to be brought up on boot (ONBOOT=no, see below) can be ignored at that time. /etc/sysconfig/network-scripts/network-functions This is not really a public file. Contains functions which the scripts use for bringing interfaces up and down. In particular, it contains most of the code for handling alternative interface configurations and interface change notification through netreport. /etc/sysconfig/network-scripts/ifcfg-interface /etc/sysconfig/network-scripts/ifcfg-interface-clone Defines an interface. An example file called ifcfg-eth0: DEVICE="eth0" IPADDR="10.1.0.153"
NETMASK="255.255.0.0" ONBOOT="yes" BOOTPROTO="none" IPXNETNUM_802_2="" IPXPRIMARY_802_2="no" IPXACTIVE_802_2="no" IPXNETNUM_802_3="" IPXPRIMARY_802_3="no" IPXACTIVE_802_3="no" IPXNETNUM_ETHERII="" IPXPRIMARY_ETHERII="no" IPXACTIVE_ETHERII="no" IPXNETNUM_SNAP="" IPXPRIMARY_SNAP="no" IPXACTIVE_SNAP="no" The /etc/sysconfig/network-scripts/ifcfg-interface-clone file only contains the parts of the definition that are different in a "clone" (or alternative) interface. For example, the network numbers might be different, but everything else might be the same, so only the network numbers would be in the clone file, but all the device information would be in the base ifcfg file. Base items in the above two files: NAME="friendly name for users to see" - Most important for PPP. Only used in front ends. DEVICE="name of physical device" IPADDR= NETMASK= GATEWAY= ONBOOT=yes|no USERCTL=yes|no BOOTPROTO=none|bootp|dhcp - If BOOTPROTO is not "none", then the only other item that must be set is the DEVICE item; all the rest will be determined by the boot protocol. No "dummy" entries need to be created. Base items being deprecated: NETWORK="will be calculated automatically with ifcalc" BROADCAST="will be calculated automatically with ifcalc" Ethernet-only items: {IPXNETNUM,IPXPRIMARY,IPXACTIVE}_{802_2,802_3,ETHERII,SNAP} configuration matrix for IPX. Only used if IPX is active. Managed from /etc/sysconfig/networkscripts/ifup-ipx PPP/SLIP items: PERSIST=yes|no MODEMPORT=device - An example device is /dev/modem. LINESPEED=speed - An example speed is 115200. DEFABORT=yes|no - Tells netcfg whether or not to put default abort strings in when creating/editing the chat script and/or dip script for this interface. PPP-specific items WVDIALSECT="list of sections from wvdial.conf to use" - If this variable is set, then the chat script (if it exists) is ignored, and wvdial is used to open the PPP connection. PEERDNS=yes|no - Modify /etc/resolv.conf if peer uses msdns extension. DEFROUTE=yes|no - Set this interface as default route? ESCAPECHARS=yes|no -Simplified interface here doesn't let people specify which characters to escape; almost everyone can use asyncmap 00000000 anyway, and they can set PPPOPTIONS to asyncmap foobar if they want to set options perfectly). HARDFLOWCTL=yes|no - Yes implies "modem crtscts" options.
PPPOPTIONS="arbitrary option string" - It is placed last on the command line, so it can override other options like asyncmap that were specified differently. PAPNAME="name $PAPNAME" - On pppd command line. Note that the "remotename" option is always specified as the logical ppp device name, like "ppp0" (which might perhaps be the physical device ppp1 if some other ppp device was brought up earlier...), which makes it easy to manage pap/chap files -- name/password pairs are associated with the logical ppp device name so that they can be managed together. REMIP="remote ip address" - Normally unspecified. MTU= MRU= DISCONNECTTIMEOUT="number of seconds" The current default is 5. This is the time to wait before re-establishing the connection after a successfully-connected session terminates before attempting to establish a new connection. RETRYTIMEOUT="number of seconds" - The current default is 60. This is the time to wait before re-attempting to establish a connection after a previous attempt fails. /etc/sysconfig/network-scripts/chat-interface - This is the chat script for PPP or SLIP connection intended to establish the connection. For SLIP devices, a DIP script is written from the chat script; for PPP devices, the chat script is used directly. /etc/sysconfig/network-scripts/dip-interface A write-only script created from the chat script by netcfg. Do not modify this. In the future, this file may disappear by default and created on-the-fly from the chat script if it does not exist. /etc/sysconfig/network-scripts/ifup-post Called when any network device EXCEPT a SLIP device comes up. Calls /etc/sysconfig/network-scripts/ifup-routes to bring up static routes that depend on that device. Calls /etc/sysconfig/network-scripts/ifup-aliases to bring up aliases for that device. Sets the hostname if it is not already set and a hostname can be found for the IP for that device. Sends SIGIO to any programs that have requested notification of network events. It could be extended to fix up nameservice configuration, call arbitrary scripts, etc, as needed. /etc/sysconfig/network-scripts/ifup-routes Set up static routes for a device. An example file: #!/bin/sh # adds static routes which go through device $1 if [ "$1" = "" ]; then echo "usage: $0 " exit 1 fi if [ ! -f /etc/sysconfig/static-routes ]; then exit 0 fi #note the trailing space in the grep gets rid of aliases grep "^$1 " /etc/sysconfig/static-routes | while read device args; do /sbin/route add -$args $device done
/etc/sysconfig/network-scripts/ifup-aliases Bring up aliases for a device. /etc/sysconfig/network-scripts/ifdhcpc-done Called by dhcpcd once dhcp configuration is complete; sets up /etc/resolv.conf from the version dhcpcd dropped in /etc/dhcpc/resolv.conf Note 3: ------Red Hat Linux 8.0: The Official Red Hat Linux Reference Guide Prev Chapter 3. Boot Process, Init, and Shutdown Next -------------------------------------------------------------------------------The /etc/sysconfig/ Directory The following information outlines some of the files found in the /etc/sysconfig/ directory, their function, and their contents. This information is not intended to be complete, as many of these files have a variety of options that are only used in very specific or rare circumstances. The /usr/share/doc/initscripts-/sysconfig.txt file contains a more authoritative listing of the files found in the /etc/sysconfig directory and the configuration options available. Files in the /etc/sysconfig/ Directory The following files are normally found in the /etc/sysconfig/ directory: amd apmd arpwatch authconfig cipe clock desktop dhcpd firstboot gpm harddisks hwconf i18n identd init ipchains iptables irda keyboard kudzu mouse named netdump network
ntpd pcmcia radvd rawdevices redhat-config-users redhat-logviewer samba sendmail soundcard squid tux ups vncservers xinetd It is possible that your system may be missing a few of them if the corresponding program that would need that file is not installed. Next, we will take a look at each one. /etc/sysconfig/amd The /etc/sysconfig/amd file contains various parameters used by amd allowing for the automounting and automatic unmounting of file systems. /etc/sysconfig/apmd The /etc/sysconfig/apmd file is used by apmd as a configuration for what things to start/stop/change on suspend or resume. It is set up to turn on or off apmd during startup, depending on whether your hardware supports Advanced Power Management (APM) or if you choose not to use it. apm is a monitoring daemon that works with power management code within the Linux kernel. It can alert you to a low battery if you are using Red Hat Linux on a laptop, among other things. /etc/sysconfig/arpwatch The /etc/sysconfig/arpwatch file is used to pass arguments to the arpwatch daemon at boot time. The arpwatch daemon maintains a table of Ethernet MAC addresses and their IP address pairings. For more information about what parameters you can use in this file, type man arpwatch. By default, this file sets the owner of the arpwatch process to the user pcap. /etc/sysconfig/authconfig The /etc/sysconfig/authconfig file sets the kind of authorization to be used on the host. It contains one or more of the following lines: USEMD5=, where is one of the following: yes � MD5 is used for authentication. no � MD5 is not used for authentication. USEKERBEROS=, where is one of the following:
yes � Kerberos is used for authentication. no � Kerberos is not used for authentication. USELDAPAUTH=, where is one of the following: yes � LDAP is used for authentication. no � LDAP is not used for authentication. /etc/sysconfig/clock The /etc/sysconfig/clock file controls the interpretation of values read from the system hardware clock. The correct values are: UTC=, where is one of the following boolean values: true or yes � Indicates that the hardware clock is set to Universal Time. false or no � Indicates that the hardware clock is set to local time. ARC=, where is the following: true or yes � Indicates the ARC console's 42-year time offset is in effect. This setting is only for ARC- or AlphaBIOS-based Alpha systems. Any other value indicates that the normal UNIX epoch is in use. SRM=, where is the following: true or yes � Indicates the SRM console's 1900 epoch is in effect. This setting is only for SRM-based Alpha systems. Any other value indicates that the normal UNIX epoch is in use. ZONE= � Indicates the timezone file under /usr/share/zoneinfo that /etc/localtime is a copy of, such as: ZONE="America/New York" Earlier releases of Red Hat Linux used the following values (which are deprecated): CLOCKMODE=, where is one of the following: GMT � Indicates that the clock is set to Universal Time (Greenwich Mean Time). ARC � Indicates the ARC console's 42-year time offset is in effect (for Alphabased systems only). /etc/sysconfig/desktop The /etc/sysconfig/desktop file specifies the desktop manager to be run, such as: DESKTOP="GNOME" /etc/sysconfig/dhcpd The /etc/sysconfig/dhcpd file is used to pass arguments to the dhcpd daemon at boot time. The dhcpd daemon implements the Dynamic Host Configuration Protocol (DHCP) and the Internet Bootstrap
Protocol (BOOTP). DHCP and BOOTP assign hostnames to machines on the network. For more information about what parameters you can use in this file, type man dhcpd. /etc/sysconfig/firstboot Beginning with Red Hat Linux 8.0, the first time you boot the system, the /sbin/init program calls the etc/rc.d/init.d/firstboot script. This allows the user to install additional applications and documentation before the boot process completes. The /etc/sysconfig/firstboot file tells the firstboot command not to run on subsequent reboots. If you want firstboot to run the next time you boot the system, simply remove /etc/sysconfig/firstboot and execute chkconfig --level 5 firstboot on. /etc/sysconfig/gpm The /etc/sysconfig/gpm file is used to pass arguments to the gpm daemon at boot time. The gpm daemon is the mouse server which allows mouse acceleration and middle-click pasting. For more information about what parameters you can use in this file, type man gpm. By default, it sets the mouse device to /dev/mouse. /etc/sysconfig/harddisks The /etc/sysconfig/harddisks file allows you to tune your hard drive(s). You can also use / etc/sysconfig/hardiskhd[a-h], to configure parameters for specific drives. Warning Do not make changes to this file lightly. If you change the default values stored here, you could corrupt all of the data on your hard drive(s). The /etc/sysconfig/harddisks file may contain the following: USE_DMA=1, where setting this to 1 enables DMA. However, with some chipsets and hard drive combinations, DMA can cause data corruption. Check with your hard drive documentation or manufacturer before enabling this. Multiple_IO=16, where a setting of 16 allows for multiple sectors per I/O interrupt. When enabled, this feature reduces operating system overhead by 30-50%. Use with caution. EIDE_32BIT=3 enables (E)IDE 32-bit I/O support to an interface card. LOOKAHEAD=1 enables drive read-lookahead. EXTRA_PARAMS= specifies where extra parameters can be added. /etc/sysconfig/hwconf The /etc/sysconfig/hwconf file lists all the hardware that kudzu detected on your system, as well as the drivers used, vendor ID and device ID information. The kudzu program detects and configures new and/or changed hardware on a system. The /etc/sysconfig/hwconf file is not meant to be
manually edited. If you do edit it, devices could suddenly show up as being added or removed. /etc/sysconfig/i18n The /etc/sysconfig/i18n file sets the default language, such as: LANG="en_US" /etc/sysconfig/identd The /etc/sysconfig/identd file is used to pass arguments to the identd daemon at boot time. The identd daemon returns the username of processes with open TCP/IP connections. Some services on the network, such as FTP and IRC servers, will complain and cause slow responses if identd is not running. But in general, identd is not a required service, so if security is a concern, you should not run it. For more information about what parameters you can use in this file, type man identd. By default, the file contains no parameters. /etc/sysconfig/init The /etc/sysconfig/init file controls how the system will appear and function during the boot process. The following values may be used: BOOTUP=, where is one of the following: BOOTUP=color means the standard color boot display, where the success or failure of devices and services starting up is shown in different colors. BOOTUP=verbose means an old style display, which provides more information than purely a message of success or failure. Anything else means a new display, but without ANSI-formatting. RES_COL=, where is the number of the column of the screen to start status labels. Defaults to 60. MOVE_TO_COL=, where moves the cursor to the value in the RES_COL line. Defaults to ANSI sequences output by echo -e. SETCOLOR_SUCCESS=, where sets the color to a color indicating success. Defaults to ANSI sequences output by echo -e, setting the color to green. SETCOLOR_FAILURE=, where sets the color to a color indicating failure. Defaults to ANSI sequences output by echo -e, setting the color to red. SETCOLOR_WARNING=, where sets the color to a color indicating warning. Defaults to ANSI sequences output by echo -e, setting the color to yellow. SETCOLOR_NORMAL=, where sets the color to 'normal'. Defaults to ANSI sequences output by echo -e. LOGLEVEL=, where sets the initial console logging level for the kernel. The default is 7; 8 means everything (including debugging); 1 means
nothing except kernel panics. syslogd will override this once it starts. PROMPT=, where is one of the following boolean values: yes � Enables the key check for interactive mode. no � Disables the key check for interactive mode. /etc/sysconfig/ipchains The /etc/sysconfig/ipchains file contains information used by the kernel to set up ipchains packet filtering rules at boot time or whenever the service is started. This file is modified by typing the command /sbin/service ipchains save when valid ipchains rules are in place. You should not manually edit this file. Instead, use the /sbin/ipchains command to configure the necessary packet filtering rules and then save the rules to this file using /sbin/service ipchains save. Use of ipchains to set up firewall rules is not recommended as it is deprecated and may disappear from future releases of Red Hat Linux. If you need a firewall, you should use iptables instead. /etc/sysconfig/iptables Like /etc/sysconfig/ipchains, the /etc/sysconfig/iptables file stores information used by the kernel to set up packet filtering services at boot time or whenever the service is started. You should not modify this file by hand unless you are familiar with how to construct iptables rules. The simplest way to add rules is to use the /usr/sbin/lokkit command or the gnome-lokkit graphical application to create your firewall. Using these applications will automatically edit this file at the end of the process. If you wish, you can manually create rules using /sbin/iptables and then type /sbin/service iptables save to add the rules to the /etc/sysconfig/iptables file. Once this file exists, any firewall rules saved there will persist through a system reboot or a service restart. For more information on iptables see Chapter 13. /etc/sysconfig/irda The /etc/sysconfig/irda file controls how infrared devices on your system are configured at startup. The following values may be used: IRDA=, where is one of the following boolean values: yes � irattach will be run, which periodically checks to see if anything is trying to connect to the infrared port, such as another notebook computer trying to make a network connection. For infrared devices to work on your system, this line must be set to yes. no � irattach will not be run, preventing infrared device communication. DEVICE=, where is the device (usually a serial port) that handles infrared connections.
DONGLE=, where specifies the type of dongle being used for infrared communication. This setting exists for people who use serial dongles rather than real infrared ports. A dongle is a device that is attached to a traditional serial port to communicate via infrared. This line is commented out by default because notebooks with real infrared ports are far more common than computers with add-on dongles. DISCOVERY=, where is one of the following boolean values:d yes � Starts irattach in discovery mode, meaning it actively checks for other infrared devices. This needs to be turned on for the machine to be actively looking for an infrared connection (meaning the peer that does not initiate the connection). no � Does not start irattach in discovery mode. /etc/sysconfig/keyboard The /etc/sysconfig/keyboard file controls the behavior of the keyboard. The following values may be used: KEYBOARDTYPE=sun|pc, which is used on SPARCs only. sun means a Sun keyboard is attached on /dev/kbd, and pc means a PS/2 keyboard connected to a PS/2 port. KEYTABLE=, where is the name of a keytable file. For example: KEYTABLE="us". The files that can be used as keytables start in /lib/kbd/keymaps/i386 and branch into different keyboard layouts from there, all labeled .kmap.gz. The first file found beneath /lib/kbd/keymaps/i386that matches the KEYTABLE setting is used. /etc/sysconfig/kudzu The /etc/sysconfig/kuzdu allows you to specify a safe probe of your system's hardware by kudzu at boot time. A safe probe is one that disables serial port probing. SAFE=, where is one of the following: yes � kuzdu does a safe probe. no � kuzdu does a normal probe. /etc/sysconfig/mouse The /etc/sysconfig/mouse file is used to specify information about the available mouse. The following values may be used: FULLNAME=, where refers to the full name of the kind of mouse being used. MOUSETYPE=, where is one of the following: microsoft � A Microsoft� mouse. mouseman � A MouseMan� mouse. mousesystems � A Mouse Systems� mouse. ps/2 � A PS/2 mouse.
msbm � A Microsoft� bus mouse. logibm � A Logitech� bus mouse. atibm � An ATI� bus mouse. logitech � A Logitech� mouse. mmseries � An older MouseMan� mouse. mmhittab � An mmhittab mouse. XEMU3=, where is one of the following boolean values: yes � The mouse only has two buttons, but three mouse buttons should be emulated. no � The mouse already has three buttons.
XMOUSETYPE=, where refers to the kind of mouse used when X is running. The options here are the same as the MOUSETYPE setting in this same file. DEVICE=, where is the mouse device. In addition, /dev/mouse is a symbolic link that points to the actual mouse device. /etc/sysconfig/named The /etc/sysconfig/named file is used to pass arguments to the named daemon at boot time. The named daemon is a Domain Name System (DNS) server which implements the Berkeley Internet Name Domain (BIND) version 9 distribution. This server maintains a table of which hostnames are associated with IP addresses on the network. Currently, only the following values may be used: ROOTDIR="", where refers to the full directory path of a configured chroot environment under which named will run. This chroot environment must first be configured. Type info chroot for more information on how to do this. OPTIONS="", where any option listed in the man page for named except -t. In place of -t, use the ROOTDIR line above instead. For more information about what parameters you can use in this file, type man named. For detailed information on how to configure a BIND DNS server, see Chapter 16. By default, the file contains no parameters. /etc/sysconfig/netdump The /etc/sysconfig/netdump file is the configuration file for the /etc/init.d/netdump service. The netdump service sends both oops data and memory dumps over the network. In general, netdump is not a required service, so you should only run it if you absolutely need to. For more information about what parameters you can use in this file, type man netdump. /etc/sysconfig/network The /etc/sysconfig/network file is used to specify information about the desired
network configuration. The following values may be used: NETWORKING=, where is one of the following boolean values: yes � Networking should be configured. no � Networking should not be configured. HOSTNAME=, where should be the Fully Qualified Domain Name (FQDN), such as hostname.domain.com, but can be whatever hostname you want. Note For compatibility with older software that people might install (such as trn), the /etc/HOSTNAME file should contain the same value as here. GATEWAY=, where is the IP address of the network's gateway. GATEWAYDEV=, where is the gateway device, such as eth0. NISDOMAIN=, where is the NIS domain name. /etc/sysconfig/ntpd The /etc/sysconfig/ntpd file is used to pass arguments to the ntpd daemon at boot time. The ntpd daemon sets and maintains the system clock to synchronize with an Internet standard time server. It implements version 4 of the Network Time Protocol (NTP). For more information about what parameters you can use in this file, point a browser at the following file: /usr/share/doc/ntp-/ntpd.htm (where is the version number of ntpd). By default, this file sets the owner of the ntpd process to the user ntp. /etc/sysconfig/pcmcia The /etc/sysconfig/pcmcia file is used to specify PCMCIA configuration information. The following values may be used: PCMCIA=, where is one of the following: yes � PCMCIA support should be enabled. no � PCMCIA support should not be enabled. PCIC=, where is one of the following: i82365 � The computer has an i82365-style PCMCIA socket chipset. tcic � The computer has a tcic-style PCMCIA socket chipset. PCIC_OPTS=, where is the socket driver (i82365 or tcic) timing parameters. CORE_OPTS=, where is the list of pcmcia_core options. CARDMGR_OPTS=, where is the list of options for the PCMCIA cardmgr (such as -q for quiet mode; -m to look for loadable kernel modules in the specified directory, and so on). Read the cardmgr man page for more information. /etc/sysconfig/radvd The /etc/sysconfig/radvd file is used to pass arguments to the radvd daemon at
boot time. The radvd daemon listens to for router requests and sends router advertisements for the IP version 6 protocol. This service allows hosts on a network to dynamically change their default routers based on these router advertisements. For more information about what parameters you can use in this file, type man radvd. By default, this file sets the owner of the radvd process to the user radvd. /etc/sysconfig/rawdevices The /etc/sysconfig/rawdevices file is used to configure raw device bindings, such as: /dev/raw/raw1 /dev/sda1 /dev/raw/raw2 8 5
/etc/sysconfig/redhat-config-users The /etc/sysconfig/redhat-config-users file is the configuration file for the graphical application, User Manager. Under Red Hat Linux 8.0 this file is used to filter out system users such as root, daemon, or lp. This file is edited by the Preferences => Filter system users and groups pull-down menu in the User Manager application and should not be edited by hand. For more information on using this application, see the chapter called User and Group Configuration in the Official Red Hat Linux Customization Guide. /etc/sysconfig/redhat-logviewer The /etc/sysconfig/redhat-logviewer file is the configuration file for the graphical, interactive log viewing application, Log Viewer. This file is edited by the Edit => Preferences pull-down menu in the Log Viewer application and should not be edited by hand. For more information on using this application, see the chapter called Log Files in the Official Red Hat Linux Customization Guide. /etc/sysconfig/samba The /etc/sysconfig/samba file is used to pass arguments to the smbd and the nmbd daemons at boot time. The smbd daemon offers file sharing connectivity for Windows clients on the network. The nmbd daemon offers NetBIOS over IP naming services. For more information about what parameters you can use in this file, type man smbd. By default, this file sets smbd and nmbd to run in daemon mode. /etc/sysconfig/sendmail The /etc/sysconfig/sendmail file allows messages to be sent to one or more recipients, routing the message over whatever networks are necessary. The file sets the default values for the Sendmail application to run. Its default values are to run as a background daemon, and to check its queue once an hour in case something has backed up. The following values may be used: DAEMON=, where is one of the following boolean values: yes � Sendmail should be configured to listen to port 25 for incoming mail. yes implies the use of Sendmail's -bd options. no � Sendmail should not be configured to listen to port 25 for incoming mail. QUEUE=1h which is given to Sendmail as -q$QUEUE. The -q option is not given to Sendmail if /etc/sysconfig/sendmail exists and QUEUE is empty or undefined.
/etc/sysconfig/soundcard The /etc/sysconfig/soundcard file is generated by sndconfig and should not be modified. The sole use of this file is to determine what card entry in the menu to pop up by default the next time sndconfig is run. Sound card configuration information is located in the /etc/modules.conf file. It may contain the following: CARDTYPE=, where is set to, for example, SB16 for a Soundblaster 16 sound card. /etc/sysconfig/squid The /etc/sysconfig/squid file is used to pass arguments to the squid daemon at boot time. The squid daemon is a proxy caching server for Web client applications. For more information on configuring a squid proxy server, use a Web browser to open the /usr/share/doc/squid-/ directory (replace with the squid version number installed on your system). By default, this file sets squid top start in daemon mode and sets the amount of time before it shuts itself down. /etc/sysconfig/tux The /etc/sysconfig/tux file is the configuration file for the Red Hat Content Accelerator (formerly known as TUX), the kernel-based web server. For more information on configuring the Red Hat Content Accelerator, use a Web browser to open the /usr/share/doc/tux-/tux/index.html (replace with the version number of TUX installed on your system). The parameters available for this file are listed in /usr/share/doc/tux-/tux/parameters.html. /etc/sysconfig/ups The /etc/sysconfig/ups file is used to specify information about Uninterruptible Power Supplies (UPS) connected to your system. A valuable for a Red Hat Linux system because it gives you time to down the system in the case of power interruption. The following used:
any UPS can be very correctly shut values may be
SERVER=, where is one of the following: yes � A UPS device is connected to your system. no � A UPS device is not connected to your system. MODEL=, where must be one of the following or set to NONE if no UPS is connected to the system: apcsmart � For a APC SmartUPS� or similar device. fentonups � For a Fenton UPS�. optiups � For an OPTI-UPS� device. bestups � For a Best Power� UPS. genericups � For a generic brand UPS. ups-trust425+625 � For a Trust� UPS. DEVICE=, where specifies where the UPS is connected, such as /dev/ttyS0.
OPTIONS=, where is a special command that needs to be passed to the UPS. /etc/sysconfig/vncservers The /etc/sysconfig/vncservers file configures the way the Virtual Network Computing (VNC) server starts up. VNC is a remote display system which allows you to view a desktop environment not only on the machine where it is running but across different networks on a variety of architectures. It may contain the following: VNCSERVERS=, where is set to something like "1:fred", to indicate that a VNC server should be started for user fred on display :1. User fred must have set a VNC password using vncpasswd before attempting to connect to the remote VNC server. Note that when you use a VNC server, your communication with it is unencrypted, and so it should not be used on an untrusted network. For specific instructions concerning the use of SSH to secure the VNC communication, please read the information found at http://www.uk.research.att.com/vnc/sshvnc.html. To find out more about SSH, see Chapter 9 or Official Red Hat Linux Customization Guide. /etc/sysconfig/xinetd The /etc/sysconfig/xinetd file is used to pass arguments to the xinetd daemon at boot time. The xinetd daemon starts programs that provide Internet services when a request to the port for that service is received. For more information about what parameters you can use in this file, type man xinetd. For more information on the xinetd service, see the Section called Access Control Using xinetd in Chapter 8. Directories in the /etc/sysconfig/ Directory The following directories are normally found in /etc/sysconfig/ and a basic description of what they contain: apm-scripts � This contains the Red Hat APM suspend/resume script. You should not edit this file directly. If you need customization, simple create a file called /etc/sysconfig/apm-scripts/apmcontinue and it will be called at the end of the script. Also, you can control the script by editing /etc/sysconfig/apmd. cbq � This directory contains the configuration files needed to do Class Based Queuing for bandwidth management on network interfaces. networking � This directory is used by the Network Administration Tool (redhatconfig-network) and its contents should not be edited manually. For more information about configuring network interfaces using the Network Administration Tool, see the chapter called Network Configuration in the Official Red Hat Linux Customization Guide. network-scripts � This directory contains the following network-related configuration files: Network configuration files for each configured network interface, such as ifcfgeth0 for the eth0 Ethernet interface.
Scripts used to bring up and down network interfaces, such as ifup and ifdown. Scripts used to bring up and down ISDN interfaces, such as ifup-isdn and ifdownisdn Various shared network function scripts which should not be edited directly. For more information on the network-scripts directory, see Chapter 12 rhn � This directory contains the configuration files and GPG keys for the Red Hat Network. No files in this directory should be edited by hand. For more information on the Red Hat Network, see the Red Hat Network website at the following URL: https://rhn.redhat.com.
39.5 AIX kernel parameters: --------------------------Througout this document, you can find many AIX kernel parameter statements. Most commands are related to retrieving or changing attributes on the sys0 object. Please see section 9.2 for a complete description. For example, take a look at the following example: maxuproc: Values: Display: Change:
Specifies the maximum number of processes per user ID. Default: 40; Range: 1 to 131072 lsattr -E -l sys0 -a maxuproc chdev -l sys0 -a maxuproc=NewValue Change takes effect immediately and is preserved over boot. If value is reduced, then it goes into effect only after a system boot. Diagnosis: Users cannot fork any additional processes. Tuning: This is a safeguard to prevent users from creating too many processes. Kernel Tunable Parameters Following are kernel parameters, grouped into the following sections: -Scheduler and Memory Load Control Tunable Parameters -Virtual Memory Manager Tunable Parameters -Synchronous I/O Tunable Parameters -Asynchronous I/O Tunable Parameters -Disk and Disk Adapter Tunable Parameters -Interprocess Communication Tunable Parameters -Scheduler and Memory Load Control Tunable Parameters -Most of the scheduler and memory load control tunable parameters are fully described in the schedo man page. -The following are a few other related parameters:
40. NFS: ========
On Solaris: ----------NFS uses a number of deamons to handle its services. These services are initialized at startup from the "/etc/init.d/nfs.server" and "/etc/init.d/nfs.client" startup scripts. nfsd: handles filesystem exporting and file access from remote systems mountd: handles mount requests from nfs clients. provides also info about which filesystems are mounted by which clients. use the showmount command to view this information. lockd: runs on nfs server and nfs clients and provides locking services statd: runs on nfs server and nfs clients and provides crash and recovery functions for lockd rpcbind: facilitates the initial connection between client and server nfslogd: provides logging On AIX: ------To start the NFS daemons for each system, whether client or Server, you can use either # smitty mknfs # mknfs -N (or -B or -I) The mknfs command configures the system to rum the NFS daemons. The command also adds an entry to the /etc/inittab file, so that the /etc/rc.nsf file is executed on system restart. mknfs flags: -B: adds an entry to the inittab and it also executes /etc/rc.nsf to start the daemons now. -I: adds an entry to the inittab to execute rc.nfs at system restart. -N: executes rc.nfs now to start the daemons. The NFS daemons can be started individually or all at once. To start individual daemons, you can use the System Resource Controller: # startsrc -s daemon, like e.g. # startsrc -s nfsd To start the complete nfs system: (good command) # startsrc -g nfs Exporting NFS directories: To export filesystems using smitty, follow this procedure: 1. Verify that NFS is already running using the command "lssrc -g nfs". The output should indicate
that the nfsd and rpc.mountd daemons are active. # lssrc -g nfs Subsystem biod nfsd rpc.mountd rpc.statd rpc.lockd
Group nfs nfs nfs nfs nfs
PID 1234 5678 9101 1213 1516
Status active active active active active
2. To export the dirctory use either # smitty mknfsexp or # mknfsexp or # edit the /etc/exports file, like for example vi /etc/exports /home1 /home2 etc..
41. NETWORK COMMANDS AND FILES: =============================== 41.1 SOLARIS: ============= ifconfig: --------ifconfig enables or disables a network interface, sets its IP address, subnet mask, and sets various other options. syntax: ifconfig interface address options .. up Examples: # ifconfig -a Displays the systems IP address and mac address. # ifconfig en0 128.138.240.1 netmask 255.255.255 up # ifconfig lo0 127.0.0.1 up # ifconfig en0 128.138.243.151 netmask 255.255.255.192 broadcast 128.138.243.191 up An identifier as en0 identifies the network interface to which the command applies. Some common names are ie0, le0, le1, en0, we0, qe0, hme0, eth0, lan0, lo0 Under Solaris, network interfaces must be attached with "ifconfig interface plumb" before they become configurable.
rpcinfo: -------This utility can list all registered RPC services running on a system, for example # rpcinfo -p 192.168.1.21 You can also unregister an rpc service using the -d option, for example #rpcinfo -d sprayd 1 which would stop spayd route: -----The route command defines static routes. Syntax: route [-f] add/delete destination gateway [hop-count] # route add default gateway_ipaddress files: ------ /etc/hostname.interface The file contains the hostname or IP address associated with the networkinterface. Suppose the system is called system1 and the interface is le0 then the file would be "hostname.le0" and contains the entry "system1". - /etc/nodename The file should contain one entry: the hostname of the local machine. - /etc/defaultdomain The file is present if the network uses a name service. The file should contain one entry: the fully qualified Domain name of the administrative domain to which the local host belongs. - /etc/inet/hosts or /etc/hosts This is the well known local hosts file, which resolves names to IP addresses. The /etc/hosts is a symbolic link to /etc/inet/hosts. - /etc/defaultrouter This file should contain an entry for each router directly connected to the network. - /etc/inetd.conf The inetd deamon runs on behalf of other networkservices. It starts the appropriate server process when a request for that service is received. The /etc/inetd.conf file lists the services that inetd is to provide
- /etc/services This file lists the well known ports. - /etc/hosts.equiv This file contains a list of trusted hosts for a remote system, one per line. It has the following structure: system1 system2 user_a If the user attemps to login remotely by using rlogin from one of the hosts listed in this file, the system allows the user to login without a password. ~/.rhosts This file is the user equivalent of /etc/hosts.equiv file. This is normally regarded as a security hole. - /etc/resolv.conf Create or edit /etc/resolv.conf Here you tell it three things: What domain we're in Specify any additional search domains What the nameservers are (it will use them in the order you put them in the file) When you're done it should look something like this: # cat resolv.conf domain yourdomain.com search yourdomain.com search client1.com nameserver 192.168.0.9 nameserver 192.168.0.11
41.2 AIX: ========= 41.2.1 Network initialization at boot: -----------------------------------At IPL time, the init process will run the /etc/rc.tcpip after starting the SRC. This is so because in /etc/inittab the following record is present: rctcpip:23456789:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP daemons The /etc/rc.tcpip file is a shell script that uses SRC commands to initialize selected deamons. It can also be executed at any time from the command line. These deamons are: inetd (started by default),gated,routed,named,timed,rwhod There are also deamons specific to the bos or to other applications that can be
started through the rc.tcpip file. These deamons are lpd, portmap, sendmail, syslogd (started by default) The subsystems started from rc.tcpip can be stopped and restarted using the stopsrc and startsrc commands. Example: # stopsrc -s inetd To configure tcp/ip use the command # mktcpip or use smitty # # # #
smitty smitty smitty smitty
mktcpip (only for the first time) tcpip inet OR smitty chgenet (for configuring the network interface) configtcp (many advanced options)
or use the Web-based System manager. Smitty uses a number of screens to guide you through the process, As an example of the command, take a look at the following example: # mktcpip -h server1 -a 10.10.10.5 -m 255.255.255.0 -i en0 \ -n 10.10.10.254 -d abc.xyz.nl -g 10.10.10.254 -s -C -A no If you need to further configure your network, use # smitty configtcp 41.2.2 resolving hostnames and /etc/netsvc.conf: ----------------------------------------The default order in resolving host names is: - BIND/DNS (named) - Network Information Service (NIS) - Local /etc/hosts file The default order can be overwritten by creating the configuration file, /etc/netsvc.conf and specifying the desired order. Both the default and /etc/netsvc.conf can be overwritten with the environment variable NSORDER. You can override the order by creating the /etc/netsvc.conf file with an entry. If /etc/netsvc.conf does not exist, it will be just like you have the following entry: hosts = bind,nis,local You can override the order by changing the NSORDER environment variable. If it is not set, it will be just like you have issued the command:
export NSORDER=bind,nis,local the /etc/resolv.conf file: -------------------------If you use name services, you can provide the minimal information needed through the mktcpip command. Typically, the "/etc/resolv.conf" file stores your domain name and name server ip addresses. The mktcpip command creates or updates the /etc/resolv.conf file for you. 41.2.3 Adapter: --------------When an adapter is added to the system, a logical device is created in the ODM, for example Ethernet adapters as follows: # lsdev -Cc adapter | grep ent ent0 Available 10-80 IBM PCI Ethernet Adapter (22100020) ent1 Available 20-60 Gigabit Ethernet-SX PCI Adapter (14100401) So you will have an adapter, and a corresponding interface, like for example The Adapter is : ent0 Then the interface is: en0 To list all interfaces on the system, use: # lsdev -Cc if en0 Defined 10-80 en1 Defined 20-60 et0 Defined 10-80 et1 Defined 20-60 lo0 Available
Standard Ethernet Network Interface Standard Ethernet Network Interface IEEE 802.3 Ethernet Network INterface IEEE 802.3 Ethernet Network INterface Loopback Network INterface
A corresponding network interface will allow tcpip to use the adapter. Most of the time, we will deal with auto-detectable adapters, but in some cases an interface might need to be created manually with # smitty inet or smitty mkinet To change or view attributes like duplex settings, use # smitty chgenet more info: An Ethernet can have 2 interfaces: Standard ethernet (enX) or IEEE 802.3 (etX). X is the same number in the entX adapter name, like for example ent0 and en0. Only one of these interfaces can be using TCPIP at a time. The adapter ent0 can have en0 and et0 interfaces. An ATM adapter (atmX) can have only one atm interface (atX). For example ATM adapter atm0 has an at0 interface.
41.2.4 Other stuff: ------------------iptrace: -------The iptrace command can be used to record the packets that are exchanged on an interface to and from a remote host. This is like a Solaris snoop facility. Examples 1. To start the iptrace daemon with the System Resource Controller (SRC), enter: startsrc -s iptrace -a "/tmp/nettrace" To stop the iptrace daemon with SRC enter the following: stopsrc -s iptrace 2. To record packets coming in and going out to any host on every interface, enter the command in the following format: iptrace /tmp/nettrace The recorded packets are received on and sent from the local host. All packet flow between the local host and all other hosts on any interface is recorded. The trace information is placed into the /tmp/nettrace file. 3. To record packets received on an interface from a specific remote host, enter the command in the following format: iptrace - i en0 -p telnet -s airmail /tmp/telnet.trace The packets to be hostairmail, over /tmp/telnet.trace 4. To record packets enter the command
recorded are received on the en0 interface, from remote the telnet port. The trace information is placed into the file. coming in and going out from a specific remote host, in the following format:
iptrace -i en0 -s airmail -b /tmp/telnet.trace The packets to be recorded are received on the en0 interface, from remote hostairmail. The trace information is placed into the /tmp/telnet.trace file.
Adding routes: -------------Use smitty mkroute or use the route add command, like for example: # route add -net 192.168.1 -netmask 255.255.255.0 9.3.1.124 Changing the IP Address: ------------------------
You can check the interfaces whether they have IP addresses asigned to them with # ifconfig -a # ifconfig Changing the IP adress: # smitty mktcpip # smitty chinet or use the ifconfig command, like for example: # ifconfig # ifconfig # ifconfig # ifconfig # ifconfig # ifconfig interface
tr0 tr0 tr0 tr0 tr0 en0
up down detach delete 10.1.2.3 netmask 255.255.255.0 up
# # # # # #
activate interface deactivate interface removes the interface put it back again delete the IP address configure IP params on the
You can even use the chdev command like: # chdev -l en0 -a netaddr='9.3.240.58' -a netmask='255.255.255.0' Smitty and chdev will update the ODM database, and makes changes permanent, while ifconfig commands will not. host.equiv and .rhost files: ---------------------------- /etc/hosts.equiv This file contains a list of trusted hosts for a remote system, one per line. It has the following structure: system1 system2 user_a If the user attemps to login remotely by using rlogin from one of the hosts listed in this file, the system allows the user to login without a password. ~/.rhosts This file is the user equivalent of /etc/hosts.equiv file. This is normally regarded as a security hole. For example, to allow all the users on the host toaster and machine to login to the local host, you would have a host.equiv file like toaster starboss To allow only the user bob to login from starboss, you would have toaster starboss bob To allow the user lester to login from any host, you would have
toaster starboss bob + lester Show statistics and collisions of an interface: ----------------------------------------------# entstat -d en0 This command shows Media speed and that kind of stuff etc.. Check the current routing table: -------------------------------# netstat -nr Add or change routes can be done by using "smitty mkroute". If your system is going to be configured as a static router (it has 2 or more network interface cards), then it needs to be enabled as a router by the no command, that is the network option command, for example # no -o ipforwarding=1 note: ----The no command is used to displays current network attributes in the kernel. Whether the commands sets accompanying flag: the -o flag performs both
configure network attributes. The no commands sets or kernel. It will only operate on the currently running or displays an attribute is determined by the actions.
Some examples: # no -o thewall=3072 # no -o tcp_sendspace=16384 # no -o ipqmaxlen=512 (controls the number of incoming packets that can exists on the IP interrupt queue) # no -a arpqsize arpt_killc arptab_bsiz arptab_nb bcastping clean_partial_conns delayack delayackports dgd_packets_lost dgd_ping_time dgd_retry_time
= = = = = = = = = = =
12 20 7 149 0 1 0 {} 3 5 5
directed_broadcast extendednetstats fasttimo icmp6_errmsg_rate icmpaddressmask ie5_old_multicast_mapping ifsize inet_stack_size ip6_defttl ip6_prune ip6forwarding ip6srcrouteforward ip_ifdelete_notify ip_nfrag ipforwarding ipfragttl ipignoreredirects ipqmaxlen ipsendredirects ipsrcrouteforward ipsrcrouterecv ipsrcroutesend llsleep_timeout lo_perf lowthresh main_if6 main_site6 maxnip6q maxttl medthresh mpr_policy multi_homed nbc_limit nbc_max_cache nbc_min_cache nbc_ofile_hashsz nbc_pseg nbc_pseg_limit ndd_event_name ndd_event_tracing ndp_mmaxtries ndp_umaxtries ndpqsize ndpt_down ndpt_keep ndpt_probe ndpt_reachable ndpt_retrans net_buf_size net_buf_type net_malloc_police nonlocsrcroute nstrpush passive_dgd pmtu_default_age pmtu_expire pmtu_rediscover_interval psebufcalls
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
0 0 200 10 0 0 256 16 64 1 0 0 0 200 0 2 1 100 1 0 0 0 3 1 90 0 0 20 255 95 1 1 891289 131072 1 12841 0 1048576 {all} 0 3 3 50 3 120 5 30 1 {all} {all} 0 0 8 0 10 10 30 20
psecache pseintrstack psetimers rfc1122addrchk rfc1323 rfc2414 route_expire routerevalidate rto_high rto_length rto_limit rto_low sack sb_max send_file_duration site6_index sockthresh sodebug sodebug_env somaxconn strctlsz strmsgsz strthresh strturncnt subnetsarelocal tcp_bad_port_limit tcp_ecn tcp_ephemeral_high tcp_ephemeral_low tcp_finwait2 tcp_icmpsecure tcp_init_window tcp_inpcb_hashtab_siz tcp_keepcnt tcp_keepidle tcp_keepinit tcp_keepintvl tcp_limited_transmit tcp_low_rto tcp_maxburst tcp_mssdflt tcp_nagle_limit tcp_nagleoverride tcp_ndebug tcp_newreno tcp_nodelayack tcp_pmtu_discover tcp_recvspace tcp_sendspace tcp_tcpsecure tcp_timewait tcp_ttl tcprexmtthresh thewall timer_wheel_tick udp_bad_port_limit udp_ephemeral_high udp_ephemeral_low
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
1 24576 20 0 0 1 1 0 64 13 7 1 0 1048576 300 0 85 0 0 1024 1024 0 85 15 1 0 0 65535 32768 1200 0 0 24499 8 14400 150 150 1 0 0 1460 65535 0 100 1 0 0 16384 16384 0 1 60 3 1048576 0 0 65535 32768
udp_inpcb_hashtab_siz udp_pmtu_discover udp_recvspace udp_sendspace udp_ttl udpcksum use_isno use_sndbufpool
= = = = = = = =
24499 0 42080 9216 30 1 1 1
rcp command: -----------Purpose Transfers files between a local and a remote host or between two remote hosts. Syntax rcp [ -p] [ -F] [ -k realm ] { { User@Host:File | Host:File | File } { User@Host:File | Host:File | File | User@Host:Directory | Host:Directory | Directory } | [ -r] { User@Host:Directory | Host:Directory |Directory } { User@Host:Directory | Host:Directory | Directory } } -r Recursively copies Description The /usr/bin/rcp command is used to copy one or more files between the local host and a remote host, between two remote hosts, or between files at the same remote host. Remote destination files and directories require a specified Host: parameter. If a remote host name is not specified for either the source or the destination, the rcp command is equivalent to the cp command. Local file and directory names do not require a Host: parameter - Using Standard Authentication The remote host allows access if one of the following conditions is satisfied: The local host is included in the remote host /etc/hosts.equiv file and the remote user is not the root user. The local host and user name is included in a $HOME/.rhosts file on the remote user account. Although you can set any permissions for the $HOME/.rhosts file, it is recommended that the permissions of the .rhosts file be set to 600 (read and write by owner only). In addition to the preceding conditions, the rcp command also allows access to the remote host if the remote user account does not have a password defined. However, for security reasons, the use of a password on all user accounts is recommended. - For Kerberos 5 Authentication The remote host allows access only if all of the following conditions are satisfied:
The local user has current DCE credentials. The local and remote systems are configured for Kerberos 5 authentication (On some remote systems, this may not be necessary. It is necessary that a daemon is listening to the klogin port). The remote system accepts the DCE credentials as sufficient for access to the remote account. See the kvalid_user function for additional information. Examples: In the following examples, the local host is listed in the /etc/hosts.equiv file at the remote host. - To copy a local file to a remote host, enter: # rcp localfile host2:/home/eng/jane The file localfile from the local host is copied to the remote host host2. - The following example uses rcp to copy the local file, YTD_sum from the directory /usr/reports on the local host to the file year-end in the directory /usr/acct on the remote host moon: # rcp /usr/reports/YTD_sum
moon:/usr/acct/year-end
- To copy a remote file from one remote host to another remote host, enter: # rcp host1:/home/eng/jane/newplan host2:/home/eng/mary The file /home/eng/jane/newplan is copied from remote host host1 to remote host host2. - To send the directory subtree from the local host to a remote host and preserve the modification times and modes, enter: # rcp -p -r report jane@host2:report The directory subtree report is copied from the local host to the home directory of user jane at remote host host2 and all modes and modification times are preserved. The remote file /home/jane/.rhosts includes an entry specifying the local host and user name. Note: rcp is ofcourse used to copy files between unix systems. On nt/w2k/xp computers, rcp could be available with some different syntax, like rcp [{-a | -b}] [-h] [-r] [Host][.User:] [Source] [Host][.User:] [Path\Destination] Notes on the FTP services: ========================== Note 1: =======
Have a look at '/usr/lpp/tcpip/samples/anon.ftp'. It is a shell script and will set up a anonymous ftp site on your local RS/6000. Note: the ftpd that comes with AIX does not support the display messages every time a user changes a directory or even when they login. Note 2: ======= ftpd Daemon Purpose Provides the server function for the Internet FTP protocol. Syntax Note: The ftpd daemon is normally started by the inetd daemon. It can also be controlled from the command line, using SRC commands. /usr/sbin/ftpd [ -d ] [ -k ] [ -l ] [ -t TimeOut ] [ -T MaxTimeOut ] [ -s ] [ -u OctalVal ] Description The /usr/sbin/ftpd daemon is the DARPA Internet File Transfer Protocol (FTP) server process. The ftpd daemon uses the Transmission Control Protocol (TCP) to listen at the port specified with the ftp command service specification in the /etc/services file. Changes to the ftpd daemon can be made using the System Management Interface Tool (SMIT) or System Resource Controller (SRC), by editing the /etc/inetd.conf or /etc/services file. Entering ftpd at the command line is not recommended. The ftpd daemon is started by default when it is uncommented in the /etc/inetd.conf file. The inetd daemon gets its information from the /etc/inetd.conf file and the /etc/services file. - The ftpaccess.ctl file: The /etc/ftpaccess.ctl file is searched for lines that start with allow:, deny:, readonly:, writeonly:, readwrite:, useronly:, grouponly:, herald: and/or motd:. Other lines are ignored. If the file doesn't exist, then ftp access is allowed for all hosts. The allow: and deny: lines are for restricting host access. The readonly:, writeonly: and readwrite: lines are for restricting ftp reads (get) and writes (put). The useronly: and grouponly: lines are for defining anonymous users. The herald: and motd: lines are for multiline messages before and after login. - If the current authentication method is the Standard Operating system authentication method: Before the ftpd daemon can transfer files for a client process, it must authenticate the client process. The ftpd daemon authenticates client processes according to these rules:
The user must have a password in the password database, /etc/security/passwd. (If the user's password is not null, the client process must provide that password.) The user name must not appear in the /etc/ftpusers file. The user's login shell must appear in the shells attribute of the /etc/security/login.cfg file. If the user name is anonymous, ftp or is a defined anonymous user in the /etc/ftpaccess.ctl file, an anonymous FTP account must be defined in the password file. In this case, the client process is allowed to log in using any password. By convention, the password is the name of the client host. The ftpd daemon takes special measures to restrict access by the client process to the anonymous account. Note 3: ======= FTP memory-to-memory transfer This is useful for testing network performance between two machines while eliminating disk I/O (1 GB transfer example): ftp> bin ftp> put "| dd if=/dev/zero bs=512k count=2000" /dev/null Note 4: ======= Subject:
ftp, anonymous setup, troubleshooting - hp
Document Text Title : How to setup anonymous ftp, and troubleshooting ftp Date : 970828 Type : EN Document ID : A4786122 Problem Description Can you explain the proper setup of anonymous FTP and how to troubleshoot any problems? Configuration Info Operating System -HP-UX Version -10.10 Hardware System - HP 9000 Series -K400 Solution Verification and setup of services: 1.
Verify that the following line is in /etc/inetd.conf and not commented out (there should be no # in the first column):
10.X: ftp
stream tcp nowait root /usr/lbin/ftpd
ftpd
9.X: ftp
stream tcp nowait root /etc/ftpd
ftpd
or netstat -a |grep ftp the output should look like: tcp 2.
0
0
*ftp.
*.*
Verify the following services are in /etc/services and not commented out (with no # in the first column): ftp-data ftp
20/tcp 21/tcp
# File Transfer Protocol (Data) # File Transfer Protocol (Control)
*Note: If you are using NIS (Network Information Services) then verify on the master server that these services are available, or do 'ypcat services |grep ftp' Creation of anonymous FTP: If possible use SAM to create anonymous ftp by entering SAM Areas: Networking and Communications, and then Networking Services. Select the desired service then choose Actions and Enable. If this method is either undesirable or you are experiencing difficulties with SAM then do the following steps: 1.
Create an ftp user in /etc/passwd: 10.X: ftp:*:500:1:Anonymous FTP user:/home/ftp:/usr/bin/false 9.X: ftp:*:500:1:Anonymous FTP user:/users/ftp:/bin/false *Note: If UID 500 is not available, use a UID that is not currently being used. *Note: GID 1 is usually group 'other', verify that group 'other' does exist, and match its group ID in this field.
2.
Create a home directory for the ftp user that is owned by ftp and has permissions set to 0555: 10.X: mkdir /home/ftp chmod 555 /home/ftp chown ftp:other /home/ftp 9.X: mkdir /users/ftp chmod 555 /users/ftp chown ftp:other /users/ftp
3.
Create a bin directory that is owned by root and has
permissions set to 0555: 10.X: mkdir -p /home/ftp/usr/bin chmod 555 /home/ftp/usr/bin /home/ftp/usr chown root /home/ftp/usr/bin /home/ftp/usr *Note: ftp structure has changed from 9.X to 10.x, there is no longer a /home/ftp/bin. The bin directory was moved to be under /home/ftp/usr: 9.X: mkdir /users/ftp/bin chmod 555 /users/ftp/bin chown root /users/ftp/bin 4.
Copy 'ls' to the new bin directory with permissions set to 0111: 10.X: cp /sbin/ls /home/ftp/usr/bin/ls chmod 111 /home/ftp/usr/bin/ls 9.X: cp /bin/ls /users/ftp/bin/ls chmod 111 /users/ftp/bin/ls
5.
Create an etc directory that is owned by root and has permissions of 0555: 10.X: mkdir /home/ftp/etc chmod 555 /home/ftp/etc chown root /home/ftp/etc 9.X: mkdir /users/ftp/etc chmod 555 /users/ftp/etc chown root /users/ftp/etc This directory should contain versions of the files passwd and group. These files must be owned by root and have permissions of 0444: 10.X: cp /etc/passwd /etc/group /home/ftp/etc chown root /home/ftp/etc/passwd /home/ftp/etc/group chmod 444 /home/ftp/etc/passwd /home/ftp/etc/group 9.X: cp /etc/passwd /etc/group /users/ftp/etc chown root /users/ftp/etc/passwd /users/ftp/etc/group chmod 444 /users/ftp/etc/passwd /users/ftp/etc/group
6.
OPTIONAL: Create a dist directory that is owned by root and has permissions of 755. Superuser can put read-only files in this directory to make them available to anonymous ftp users.
10.X: mkdir /home/ftp/dist chown root /home/ftp/dist chmod 755 /home/ftp/dist 9.X: mkdir /users/ftp/dist chown root /users/ftp/dist chmod 755 /users/ftp/dist 7.
OPTIONAL: Create a pub directory that is owned by ftp and writable by all. Anonymous ftp users can put files in this directory to make them available to other anonymous ftp users. 10.X: mkdir /home/ftp/pub chown ftp:other /home/ftp/pub chmod 777 /home/ftp/pub 9.X: mkdir /users/ftp/pub chown ftp:other /users/ftp/pub chmod 777 /users/ftp/pub
Troubleshooting FTP: 1.
Verify the installation steps.
2.
If receiving message: ftp: connect: Connection refused. Verify that inetd is running by entering 'ps -ef|grep inetd'. You should see output like: root root
3730 2324
2217 1
1 13:54:57 ttyp2 0 13:43:28 ?
0:00 grep inetd 0:00 inetd
*Note: You may not see the grep process. If inetd is not currently running, then as root type 'inetd' 3.
If receiving either message: 530 access denied login failed, or 530 User [name] access denied. A.
Verify netrc. in the user's home directory. If the netrc. file contains password or account information for use other than for anonymous ftp, its owner must match the effective user ID of the current process. Its read, write, and execute permission bits for group and other must all be zero, and it must be readable by its owner. Otherwise, the file is ignored. So if you are unsure about this file, rename it to netrc.old. for troubleshooting purposes.
B.
Check /etc/ftpusers. ftpd rejects remote logins to local user accounts that are
named in /etc/ftpusers. Each restricted account name must appear alone on a line in the file. The line cannot contain any white space. User accounts that specify a restricted login shell in /etc/passwd should be listed in /etc/ftpusers because ftpd accesses local accounts without using their login shells. C.
You need to add or verify /etc/shells. /etc/shells is an ASCII file containing a list of legal shells on the system. Each shell is listed in the file by its absolute path name. To learn more about this file, run 'man shells'. To see the legal shells for your system run 'man getusershell'. This will list all valid shells for your system. If you use both 9.X and 10.X environments, include the shells for both operating systems. Example entries: /bin/sh Basic Configuration (Manual or IBM Tunnels) - Setting Up Tunnels and Filters For the simplest case, setting up a manual tunnel, it is not necessary to separately configure the filter rules.
As long as all traffic between two hosts goes through the tunnel, the necessary filter rules are automatically generated. The process of setting up a tunnel is to define the tunnel on one end, import the definition on the other end, and activate the tunnel and filter rules on both ends. Then the tunnel is ready to use. Information about the tunnel must be made to match on both sides if it is not explicitly supplied (see figure). For instance, the encryption and authentication algorithms specified for the source will be used for the destination if the destination values are not specified. This makes creating the tunnel much simpler. - Creating a Manual Tunnel on Host A You can configure a tunnel using the Web-based System Manager application Network, the SMIT fast path ips4_basic (for IP Version 4) or ips6_basic (for IP version 6), or you can use the following procedure. The following is a sample of the gentun command used to create a manual tunnel: # gentun -v 4 -t manual -s 5.5.5.19 -d 5.5.5.8 -a HMAC_MD5 -e DES_CBC_8 -N 23567 This will create a tunnel with output (using lstun -v 4) that looks similar to: Tunnel ID IP Version Source Destination Policy Tunnel Mode Send AH Algo Send ESP Algo Receive AH Algo Receive ESP Algo Source AH SPI Source ESP SPI Dest AH SPI Dest ESP SPI Tunnel Life Time Status Target Target Mask Replay New Header Snd ENC-MAC Algo Rcv ENC-MAC Algo
: : : : : : : : : : : : : : : : : : : : : :
1 IP Version 4 5.5.5.19 5.5.5.8 auth/encr Tunnel HMAC_MD5 DES_CBC_8 HMAC_MD5 DES_CBC_8 300 300 23576 23576 480 Inactive No Yes -
The tunnel will be activated when the mktun command is used: # mktun -v 4 -t1 The filter rules associated with the tunnel are automatically generated and output (using lsfilt -v 4) looks similar to: Rule 4:
Rule action Source Address Source Mask Destination Address Destination Mask Source Routing Protocol Source Port Destination Port Scope Direction Logging control Fragment control Tunnel ID number Interface Auto-Generated
: : : : : : : : : : : : : : : :
permit 5.5.5.19 255.255.255.255 5.5.5.8 255.255.255.255 yes all any 0 any 0 both outbound no all packets 1 all yes
: : : : : : : : : : : : : : : :
permit 5.5.5.8 255.255.255.255 5.5.5.19 255.255.255.255 yes all any 0 any 0 both inbound no all packets 1 all yes
Rule 5: Rule action Source Address Source Mask Destination Address Destination Mask Source Routing Protocol Source Port Destination Port Scope Direction Logging control Fragment control Tunnel ID number Interface Auto-Generated
These filter rules in addition to the default filter rules are activated by the mktun -v 4 -t 1 command. To set up the other side (when it is another AIX machine), the tunnel definition can be exported on host A then imported to host B. To export: # exptun -v 4 -t 1 -f /tmp This will export the tunnel definition into a file named ipsec_tun_manu.exp and any associated filter rules to the file ipsec_fltr_rule.exp in the directory indicated by the -f flag. - Creating a manual tunnel on Host B To create the matching end of the tunnel, the export files are copied to the remote side and imported into that remote AIX 4.3 machine by using the command: # imptun -v 4 -t 1 -f /tmp
where 1 is the tunnel to be imported and /tmp is the directory where the import files reside. This tunnel number is system generated and must be referenced from the output of the gentun command, or by using the lstun command to list the tunnels and determine the correct tunnel number to import. If there is only one tunnel in the import file, or if all the tunnels are to be imported, then the -t option is not needed. If the remote machine is not AIX 4.3, the export file can be used as a reference for setting up the algorithm, keys, and SPI values for the other end of the tunnel. Export files from the IBM Secure Network Gateway (SNG) can be imported to create tunnels in AIX 4.3. To do this, use the -n option when importing the file: # imptun -v 4 -f /tmp -n - Creating an IBM tunnel on Host A Setting up an IBM tunnel is similar to a manual tunnel, but some of the choices are different for the crypto algorithms and the keys are negotiated dynamically, so there is no need to import keys. IBM tunnels are limited to Keyed MD5 for authentication. If the HMAC MD5 or HMAC SHA algorithms are desired, a manual tunnel must be used. # gentun -s 9.3.100.1 -d 9.3.100.245 -t IBM -e DES_CBC_8 -n 35564 As with manual tunnels, from this point the tunnel and filter table must be activated to make the tunnel active: # mktun -v 4 -t1 To set up the other side, if the other host is an AIX 4.3 IP Security machine, the tunnel definition can be exported on host A, then imported to host B. To export: # exptun -v 4 -f /tmp This will export the tunnel definition into a file named ipsec_tun_ibm.exp and any associated filter rules to the file ipsec_fltr_rule.exp in the directory indicated by the -f flag. - Creating an IBM tunnel on Host B The procedure is the same for creating the second end of the tunnel on host B for an IBM tunnel. The tunnel definition is exported from host A and imported onto host B. The -n flag can be used for a file exported by an IBM Secure Network Gateway or an IBM Firewall 3.1/3.2. - Static Filter Rules and Examples Filtering can be set up to be simple, using mostly autogenerated filter rules, or can be complex by defining very specific filter functions based on the properties of the IP packets. Matches
on incoming packets are done by comparing the source address and SPI value to those listed in the filter table. Therefore, this pair must be unique. Each line in the filter table is known as a rule. A collection of rules will determine what packets are accepted in and out of the machine, and how they will be directed. Filter rules can be written based on source and destination addresses and masks, protocol, port number, direction, fragment control, source routing, tunnel, and interface. Below is a sample set of filter rules. Within each rule, fields are shown in the following order (an example of each field from rule 1 is shown in parentheses): Rule_number (1), Action (permit), Source_addr (0.0.0.0), Source_mask (0.0.0.0), Dest_addr (0.0.0.0), Dest_mask (0.0.0.0), Source_routing (no), Protocol (udp), Src_prt_operator (eq), Src_prt_value (4001), Dst_prt_operator (eq), Dst_prt_value (4001), Scope (both), Direction (both), Logging (no), Fragment (all packets), Tunnel (0), and Interface (all). 1 permit 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 no udp eq 4001 eq 4001 both both no all packets 0 all 2 permit 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 no ah any 0 any 0 both both no all packets 0 all 3 permit 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 no esp any 0 any 0 both both no all packets 0 all 4 permit 10.0.0.1 255.255.255.255 10.0.0.2 255.255.255.255 no all any 0 any 0 both outbound no all packets 1 all 5 permit 10.0.0.2 255.255.255.255 10.0.0.1 255.255.255.255 no all any 0 any 0 both inbound no all packets 1 all 6 permit 10.0.0.1 255.255.255.255 10.0.0.3 255.255.255.255 no tcp lt 1024 eq 514 local outbound yes all packets 2 all 7 permit 10.0.0.3 255.255.255.255 10.0.0.1 255.255.255.255 no tcp/ack eq 514 lt 1024 local inbound yes all packets 2 all 8 permit 10.0.0.1 255.255.255.255 10.0.0.3 255.255.255.255 no tcp/ack lt 1024 lt 1024 local outbound yes all packets 2 all 9 permit 10.0.0.3 255.255.255.255 10.0.0.1 255.255.255.255 no tcp lt 1024 lt 1024 local inbound yes all packets 2 all 10 permit 10.0.0.1 255.255.255.255 10.0.0.4 255.255.255.255 no icmp any 0 any 0 local outbound yes all packets 3 all 11 permit 10.0.0.4 255.255.255.255 10.0.0.1 255.255.255.255 no icmp any 0 any 0 local inbound yes all packets 3 all 12 permit 10.0.0.1 255.255.255.255 10.0.0.5 255.255.255.255 no tcp gt 1023 eq 21 local outbound yes all packets 4 all
13 permit 10.0.0.5 255.255.255.255 10.0.0.1 255.255.255.255 no tcp/ack eq 21 gt 1023 local inbound yes all packets 4 all 14 permit 10.0.0.5 255.255.255.255 10.0.0.1 255.255.255.255 no tcp eq 20 gt 1023 local inbound yes all packets 4 all 15 permit 10.0.0.1 255.255.255.255 10.0.0.5 255.255.255.255 no tcp/ack gt 1023 eq 20 local outbound yes all packets 4 all 16 permit 10.0.0.1 255.255.255.255 10.0.0.5 255.255.255.255 no tcp gt 1023 gt 1023 local outbound yes all packets 4 all 17 permit 10.0.0.5 255.255.255.255 10.0.0.1 255.255.255.255 no tcp/ack gt 1023 gt 1023 local inbound yes all packets 4 all 18 permit 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 no all any 0 any 0 both both yes all packets Rule 1 is for the IBM Session Key daemon and will only appear in IP Version 4 filter tables. It uses port number 4001 to control packets for refreshing the session key. It is an example of how the port number can be used for a specific purpose. This filter rule should not be modified except for logging purposes. Rules 2 and 3 are used to allow processing of Authentication Headers (AH) and Encapsulating Security Payload (ESP) headers. They should not be modified except for logging purposes. Rules 4 and 5 are a set of autogenerated rules that filter traffic between addresses 10.0.0.1 and 10.0.0.2 through tunnel #1. Rule 4 is for outbound traffic and rule 5 is for inbound traffic. Rules 6 through 9 are a set of user-defined rules that filter outbound rsh, rcp, rdump, rrestore, and rdist services between addresses 10.0.0.1 and 10.0.0.3 through tunnel #2. Note that logging is set to yes so the administrator can monitor this type of traffic. Rules 10 and 11 are a set of user-defined rules that filter both inbound and outbound icmp services of any type between addresses 10.0.0.1 and 10.0.0.4 through tunnel #3. Rules 12 through 17 are user-defined filter rules that filter outbound FTP service from 10.0.0.1 and 10.0.0.5 through tunnel #4. Rule 18 is an autogenerated rule always placed at the end of the table. In this case, it permits all packets that do not match the other filter rules. It may be set to deny all traffic not matching the other filter rules. Each rule may be viewed separately (using lsfilt) to make each field clear.
42.3 IPSEC and HP: =================== As you have read in section 42.1, you should know beforehand if you want AH or AH plus ESP, Manual keys or IKE, Transport mode or Tunnel mode, and what "filter rules" you want to apply. Depending on the number of NIC's in your Host, and what traffic you want to permit or deny, you will invest a certain a amount of effort to create those rules. Introducing Configuring IPSec: -----------------------------You configure HP-UX IPSec using a couple of commandline utilities like: ipsec_config ipsec_report ipsec_admin ipsec_policy To configure security certificates (used in the negotiation phase in IKE), use the "ipsec_mgr" utility, which has a graphical user interface (GUI). So you need an X terminal. You can also use preshared key instead of certificates (the preshared key is used only for the primary authentication). As an example of using the commandline, take a look at the following command: # ipsec_config add host my_host_policy -source 10.1.1.1 \ -destination 10.0.0.0/8/TELNET -pri 100 \ -action ESP_AES128_HMAC_SHA1 The above creates a "rule" or policy in the policy database "/var/adm/ipsec/config.db". The syntax with respect of addresses and ports, resembles somewhat the common syntax found in many types of router, gateway, firewall products. For example 0.0.0.0 means here all possible IPv4 addresses 10.0.0.0 means here all possible IPv4 addresses in 10. Instead of using a serie of individual commands to configure IPSec, HP recommends to create a "batchfile" with statements. All statements are parsed first, and either all statements pass and are executed, or all fail, even if only one statement is incorrectt. For the above example, a batchfile would look like: add host my_host_policy -source 10.1.1.1 \ -destination 10.0.0.0/8/TELNET -pri 100 \ -action ESP_AES128_HMAC_SHA1
Notice that we have used the "add" option of the ipsec_config command, indeed used to "add" to the config DB. It also suggest that there are other options, which is true: You can use: ipsec_config ipsec_config ipsec_config ipsec_config
add batch delete show
to to to to
add to the db use a batchfile delete from the db show information from the db
For example, the "ipsec_config show all" command displays the entire contents of the database. profiles: An ipsec_config profile file contains default argument values that are evaluated in ipsec_config add commands if the user does not specify the values in the command. The values are evaluated once, when the policy is added to the configuration database. Values used from the profile file become part of the configuration record for the policy. You can specify a profile file name with the -profile argument as part of an ipsec_config command. By default, ipsec_config uses the /var/adm/ipsec/.ipsec_profile profile file, which is shipped with HP-UX IPSec. In most topologies, you can use the default values supplied in the /var/adm/ipsec/.ipsec_profile file.
Installation: ------------The software takes about 110MB. Most of the software goes into /var/adm/ipsec. As root: As usual at installation on HP-UX, run the swinstall program using the command: # swinstall This opens the "Software Selection" window and the "Specify Source" window. On the Specify Source window, change the Source Host Name if necessary. Enter the mount point of the drive in the Source Depot Path field and click OK to return to the Software Selection window. The Software Selection window now contains a list of available software bundles to install. Highlight the HP-UX IPSec software for your system type. Choose Mark for Install from the Actions menu to choose the product to be installed. With the exception of the manpages and user�s manual, you must install the complete IPSec product.
swinstall loads the fileset, runs the control scripts for the fileset, and builds the kernel. Estimated time for processing: 3 to 5 minutes. Click OK on the Note window to reboot the system. When the system reboots, check the log files "/var/adm/sw/swinstall.log" and "/var/adm/sw/swagent.log" to make sure the installation was successful. -- Setting the HP-UX IPSec Password: When you install HP-UX IPSec, the HP-UX IPSec password is set to ipsec. You must change the HP-UX IPSec password after installing the product to use the autoboot feature and to load and configure security certificates. HP-UX IPSec uses the password to encrypt certificate files that contain cryptography keys for security certificates, and to control access to the ipsec_mgr security certificate configuration GUI. To set the password, run the following command: # ipsec_admin -newpasswd The ipsec_admin utility prompts you to establish the HP-UX IPSec password. Configuring IPSec (2): ---------------------From the HP-UX documentation, it is shown that you should do the following actions: Step Step Step Step Step Step Step Step Step Step
1: Configuring Host IPSec Policies 2: Configuring Tunnel IPSec Policies 3: Configuring IKE Policies 4: Configuring Preshared Keys Using Authentication Records (Or do Step 5) 5: Configuring Certificates 6: Configuring the Bypass List (Local IPv4 Addresses) 7: Verify Batch File Syntax 8: Committing the Batch File Configuration and Verifying Operation 9: Configuring HP-UX IPSec to Start Automatically 10: Creating Backup Copies of the Batch File and Configuration Database
43. SOLARIS OpenBoot PROM commands: =================================== -- Getting help -- -----------ok help / ok help [category] / ok help command For example, if you want to see the help messages for all commands in the category
"diag", type the following: ok help diag -- Display your physical devices -- ----------------------------ok show-devs [device path] -- Create or show device aliases -- ----------------------------A device pathnames can be long and hard to enter. A device alias allows a short name to represent an entire device pathname. For example the alias "disk0" might represent the device /sbus@1,f8000000/esp@0,40000/sd@3,0:a ok devalias ok
displays all current devices aliases creates the alias corresponding to the physical device
The following example creates a device alias named "disk3" which represents a SCSI disk with a target ID of 3. ok devalias disk3 /iommu/sbus/espdma@f,400000/esp@f,800000/sd@3,0 To make this permanent in NVRAM use: ok nvalias disk3 /iommu/sbus/espdma@f,400000/esp@f,800000/sd@3,0 -- OpenBoot Diagnostics -- -------------------Various hardware diagnostics can be run in OpenBoot. ok ok ok ok ok ok
probe-scsi probe-ide test device test-all watch-clock watch-net
identifies devices attached to as SCSI bus identifies IDE devices attached to the PCI bus executes the self-test method of the device test all devices that have a build-in self-test method tests the clock function monitors the network connection
-- OpenBoot NVRAM -- -------------System configuration parameters, like "auto-boot", are stored in NVRAM. You can list or modify these configuration parameters and any changes you make remain in effect, even after a power cycle because the are stored in NVRAM. Some of the most important parameters: auto-boot? default true if true, the machine boots automatically boot-command default boot the command that is executed if auto-boot is true boot-device disk or net device from which to start up input-device keyboard console input device, usually keyboard, ttya, ttyb security-mode none none, command, or full etc.. To show a parameter: ok printenv To set a parameter : ok setenv
ok setenv auto-boot? false ok printenv auto-boot? Once unix is loaded, root can also use the /usr/sbin/eeprom command to view or change an OpenBoot parameter. /usr/sbin/eeprom auto-boot?=true
44. Process priority: ===================== Solaris: -------NICE and PRIOCTL commands: nice: ----A high nice value means a low priority for your process: you are goiing to be nice. A low or negative value means a high priority: you are not very nice. Examples: # nice +10 ~/bin/longtask # renice -5 8829 The nice command uses the programname as an argument. The renice command takes the PID as argument. System -----Solaris HPUX Read Hat FreeBSD
Range ----0-39 0-39 -20-20 -20-20
prioctl: -------Solaris uses the prioctl command, intended as an improvement over the nice command, to modify process priorities. Syntax: # prioctl -s -p -i pid Example: # prioctl -s -p -5 -i pid 8200 AIX: ---In AIX we can use the nice and renice commands as well.
About the schedtune Command: Purpose Sets parameters for CPU scheduler and Virtual Memory Manager processing. Syntax schedtune [ -D | { [ -d n ] [ -e n ] [ -f n ] [ -h n ] [ -m n ] [ -p n ] [ -r n ] [ -t n ] [ -w n ] } ] Description Priority-Calculation Parameters The priority of most user processes varies with the amount of CPU time the process has used recently. The CPU scheduler's priority calculations are based on two parameters that are set with schedtune: -r and -d. The r and d values are in thirty-seconds (1/32); that is, the formula used by the scheduler to calculate the amount to be added to a process's priority value as a penalty for recent CPU use is: CPU penalty = (recently used CPU value of the process) * (r/32) and the once-per-second recalculation of the recently used CPU value of each process is: new recently used CPU value = (old recently used CPU value of the process) * (d/32)
44. ttymon and terminals: ========================= Solaris: -------The configuration of terminals in Solaris 8,9 is somewhat more elaborate than adding such a device on AIX, for example with the mkdev command. Here we shall only show the configuration in Solaris 8,9. Note 1: ------In Solaris, the usual getty is taken over by the portmonitor ttymon. $ cd /etc $ ls -al get* lrwxrwxrwx 1 root ../usr/lib/saf/ttymon
root
/var/saf/zsmon >sacadm -l PMTAG PMTYPE zsmon ttymon $ pmadm -l PMTAG zsmon /usr/bin/login zsmon
21 Aug 10
FLGS RCNT STATUS 0 ENABLED
2004 getty ->
COMMAND /usr/lib/saf/ttymon #
PMTYPE SVCTAG FLGS ID ttymon ttya u root /dev/term/a I - 9600 ldterm,ttcompat ttya login: - tvi925 y # ttymon ttyb u root /dev/term/b I -
/usr/bin/login - 9600 ldterm,ttcompat ttyb login:
- tvi925 y
#
ls -al \dev\term lrwxrwxrwx 1 root root 48 Aug 10 2004 a -> ../../devices/pci@1e,600000/isa@7/serial@0,3f8:a lrwxrwxrwx 1 root root 48 Aug 10 2004 b -> ../../devices/pci@1e,600000/isa@7/serial@0,2e8:b Note 2: ------Solaris 2.x systems come with a ttymon port monitor named zsmon and with serial ports A and B already configured with default settings for terminals, as shown in the following example: castle% /usr/sbin/sacadm -l PMTAG PMTYPE zsmon ttymon castle% /usr/sbin/pmadm -l PMTAG PMTYPE tcp listen lp $ sacadm -l PMTAG zsmon
FLGS RCNT STATUS 0 ENABLED SVCTAG - root
PMTYPE ttymon
COMMAND /usr/lib/saf/ttymon #
FLGS ID - p -
FLGS RCNT STATUS 0 ENABLED
COMMAND /usr/lib/saf/ttymon #
Note 3: ------$ tail -30 /var/saf/zsmon/log Wed Wed Wed Wed Wed Wed Wed Wed Wed Wed Wed Mon Mon Mon Mon Mon Mon Mon Mon Mon Mon Mon Mon
Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar
16 16 16 16 16 16 16 16 16 16 16 21 21 21 21 21 21 21 21 21 21 21 21
13:13:59 13:13:59 13:13:59 13:13:59 13:13:59 13:13:59 13:13:59 13:13:59 13:13:59 13:13:59 13:13:59 08:02:27 08:02:27 08:05:43 08:05:43 08:05:43 08:05:43 08:05:43 08:05:43 08:05:43 08:05:43 08:05:43 08:05:43
2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005; 2005;
453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453; 453;
********** ttymon starting ********** PMTAG: zsmon Starting state: enabled Got SC_ENABLE message max open files = 1024 max ports ttymon can monitor = 1017 *ptr == 0 SUCCESS *ptr == 0 SUCCESS Initialization Completed caught SIGTERM ********** ttymon exiting *********** ********** ttymon starting ********** PMTAG: zsmon Starting state: enabled Got SC_ENABLE message max open files = 1024 max ports ttymon can monitor = 1017 *ptr == 0 SUCCESS *ptr == 0
Mon Mar 21 08:05:43 2005; 453; SUCCESS Mon Mar 21 08:05:43 2005; 453; Initialization Completed Note 4: ------ttymon is a STREAMS-based TTY port monitor. Its function is to monitor ports, to set terminal modes, baud rates, and line disciplines for the ports, and to connect users or applications to services associated with the ports. Normally, ttymon is configured to run under the Service Access Controller, sac(1M), as part of the Service Access Facility (SAF). It is configured using the sacadm(1M) command. Each instance of ttymon can monitor multiple ports. The ports monitored by an instance of ttymon are specified in the port monitor's administrative file. The administrative file is configured using the pmadm(1M) and ttyadm(1M) commands. When an instance of ttymon is invoked by the sac command, it starts to monitor its ports. For each port, ttymon first initializes the line disciplines, if they are specified, and the speed and terminal settings. For ports with entries in /etc/logindevperm, device owner, group and permissions are set. (See logindevperm(4).) The values used for initialization are taken from the appropriate entry in the TTY settings file. This file is maintained by the sttydefs(1M) command. Default line disciplines on ports are usually set up by the autopush(1M) command of the Autopush Facility. ttymon then writes the prompt and waits for user input. If the user indicates that the speed is inappropriate by pressing the BREAK key, ttymon tries the next speed and writes the prompt again. When valid input is received, ttymon interprets the per-service configuration file for the port, if one exists, creates a utmpx entry if required (see utmpx(4)), establishes the service environment, and then invokes the service associated with the port. Valid input consists of a string of at least one non-newline character, terminated by a carriage return. After the service terminates, ttymon cleans up the utmpx entry, if one exists, and returns the port to its initial state. If autobaud is enabled for a port, ttymon will try to determine the baud rate on the port automatically. Users must enter a carriage return before ttymon can recognize the baud rate and print the prompt. Currently, the baud rates that can be determined by autobaud are 110, 1200, 2400, 4800, and 9600. SunOS 5.9
Last change: 11 Dec 2001
System Administration Commands
1 ttymon(1M)
If a port is configured as a bidirectional port, ttymon will allow users to connect to a service, and, if the port is free, will allow uucico(1M), cu(1C), or ct(1C) to use it for dialing out. If a port is bidirectional, ttymon will wait to read a character before it prints a prompt.
If the connect-on-carrier flag is set for a port, ttymon will immediately invoke the port's associated service when a connection request is received. The prompt message will not be sent. If a port is disabled, ttymon will not start any service on that port. If a disabled message is specified, ttymon will send out the disabled message when a connection request is received. If ttymon is disabled, all ports under that instance of ttymon will also be disabled. SERVICE INVOCATION The service ttymon invokes for a port is specified in the ttymon administrative file. ttymon will scan the character string giving the service to be invoked for this port, looking for a %d or a %% two-character sequence. If %d is found, ttymon will modify the service command to be executed by replacing those two characters by the full path name of this port (the device name). If %% is found, they will be replaced by a single %. When the service is invoked, file descriptor 0, 1, and 2 are opened to the port device for reading and writing. The service is invoked with the user ID, group ID and current home directory set to that of the user name under which the service was registered with ttymon. Two environment variables, HOME and TTYPROMPT, are added to the service's environment by ttymon. HOME is set to the home directory of the user name under which the service is invoked. TTYPROMPT is set to the prompt string configured for the service on the port. This is provided so that a service invoked by ttymon has a means of determining if a prompt was actually issued by ttymon and, if so, what that prompt actually was. See ttyadm(1M) for options that can be set for ports tored by ttymon under the Service Access Controller.
moni-
SECURITY ttymon uses pam(3PAM) for session management. The PAM configuration policy, listed through /etc/pam.conf, specifies the modules to be used for ttymon. Here is a partial pam.conf file with entries for ttymon using the UNIX session management module. ttymon SunOS 5.9
session
required
/usr/lib/security/pam_unix.so.1
Last change: 11 Dec 2001
System Administration Commands If there are no entries for the ttymon service, entries for the "other" service will be used.
2 ttymon(1M) then
the
Note 5: ------To add a login service to configure an existing port. Follow these steps to configure the SAF for a character terminal:
1. Become superuser. 2. Type sacadm -l and press Return. Check the output to make sure that a ttymon port monitor is configured. It is unlikely that you will need to add a new port monitor. If you do need to add one, type sacadm -a -p pmtag -t ttymon -c /usr/lib/saf/ttymon -v `ttymon -V` and press Return. 3.
Type
pmadm -a -p pmtag -s svctag -i root -fu -v `ttymon -V` -m �`ttyadm -t terminfo-type -d dev-path \ -l ttylabel -s /usr/bin/login`� 4.
and press Return. The port is configured for a login service. Attach all of the cords and cables to the terminal and turn it on.
In this example, a ttymon port monitor called ttymon0 is created and a login is enabled for serial port /dev/term/00: oak% su Password: # sacadm -l PMTAG PMTYPE FLGS RCNT STATUS COMMAND zsmon ttymon - � ENABLED /usr/lib/saf/ttymon # # sacadm -a -p ttymon� -t ttymon -c /usr/lib/saf/ttymon -v`ttyadm -V` # sacadm -l PMTAG PMTYPE FLGS RCNT STATUS COMMAND ttymonm� ttymon - � STARTING /usr/lib/saf/ttymon # zsmon ttymon - � ENABLED /usr/lib/saf/ttymon # # pmadm -a -p ttymon� -s tty�� -i root -fu -v `ttyadm -V` -m "`ttyadm -t tvi925 -d /dev/term/�� -l 96�� -s /usr/bin/login`" # pmadm -l PMTAG PMTYPE SVCTAG FLGS ID zsmon ttymon ttya u root /dev/term/a I /usr/bin/login - 96�� ldterm,ttcompat ttya login: - tvi925 y # zsmon ttymon ttyb u root /dev/term/b I /usr/bin/login - 96�� ldterm,ttcompat ttyb login: - tvi925 y # ttymon� ttymon tty�� u root /dev/term/�� - - ?/usr/bin/login - 96�� login: - tvi925 - # # Add a port monitor `ttyadm -V` -y "comment" Disable a port monitor Enable a port monitor Kill a port monitor List status information
sacadm -a -p pmtag -t ttymon -c /usr/lib/saf/ttymon -v sacadm -d -p pmtag sacadm -e -p pmtag sacadm -k -p pmtag
for a port monitor Remove a port monitor Start a port monitor Add a listen port monitor `ttyadm -V` -y "comment"
sacadm sacadm sacadm sacadm
-l -r -s -a
-p -p -p -p
pmtag pmtag pmtag pmtag -t listen -c /usr/lib/saf/listen -v
Add a standard terminal service pmadm -a -p pmtag -s svctag -i root -v `ttyadm -V` -m "`ttyadm -i `terminal disabled.' -l contty -m ldterm,ttcompat -d dev-path -s /usr/bin/login`" Disable a ttymon port monitor pmadm -d -p pmtag -s svctag Enable a ttymon port monitor pmadm -e -p pmtag -s svctag List all services pmadm -l List status information for one ttymon port monitor pmadm -l -p pmtag -s svctag Add a listen service pmadm -a -p pmtag -s lp -i root -v `nlsadmin -V` -m "`nlsadmin -o /var/spool/lp/fifos/listenS5`" Disable a listen port monitor pmadm -d -p pmtag -s lp Enable a listen port monitor pmadm -e -p pmtag -s lp List status information for one ttymon port monitor pmadm -l -p pmtag Note 7: ------3.23) What has happened to getty? What is pmadm and how do you use it? I was hoping you wouldn't ask. PMadm stands for Port Monitor Admin, and it's part of a ridiculously complicated bit of software over-engineering that is destined to make everybody an expert. Best advice for workstations: don't touch it! It works out of the box. For servers, you'll have to read the manual. This should be in admintool in Solaris 2.3 and later. For now, here are some basic instructions from Davy Curry. "Not guaranteed, but they worked for me." To add a terminal to a Solaris system: 1. Do a "pmadm -l" to see what's running. The serial ports on the CPU board are probably already being monitored by "zsmon". PMTAG zsmon
PMTYPE SVCTAG FLGS ID ttymon ttya u root \ /dev/term/a I - /usr/bin/login - 9600 ldterm,ttcompat ttya \ login: - tvi925 y #
2. If the port you want is not being monitored, you need to create a new port monitor with the command sacadm -a -p PMTAG -t ttymon -c /usr/lib/saf/ttymon -v VERSION where PMTAG is the name of the port monitor, e.g. "zsmon" or "alm1mon", and VERSION is the output of "ttyadm -V".
3. If the port you want is already being monitored, and you want to change something, you need to delete the current instance of the port monitor. To do this, use the command pmadm -r -p PMTAG -s SVCTAG where PMTAG and SVCTAG are as given in the output from "pmadm -l". Note that if the "I" is present in the field (as it is above), you need to get rid of it. 4. Now, to create a specific instance of ttymon for a port, issue the command: pmadm -a -p PMTAG -s SVCTAG -i root -fu -v 1 -m \ "`ttyadm -m ldterm,ttcompat -p 'PROMPT' -S YORN -T TERMTYPE \ -d DEVICE -l TTYID -s /usr/bin/login`" Note the assorted quotes; Bourne shell (sh) and Korn (ksh) users leave off the second backslash! In the above: PMTAG is the port monitor name you made with "sacadm", e.g. "zsmon". SVCTAG is the service tag, which can be the name of the port, e.g., "ttya" or "tty21". PROMPT is the prompt you want to print, e.g. "login: ". YORN is "y" to turn software carrier on (you want this for directly connected terminals" and "n" to leave it off (you want this for modems). TERMTYPE is the value you want in $TERM. DEVICE is the name of the device, e.g. "/dev/term/a" or "/dev/term/21". TTYID is the line you want from /etc/ttydefs that sets the baud rate and stuff. I suggest you use one of the "contty" ones for directly connected terminals. 5. To disable ("turn off") a terminal, run pmadm -d -p PMTAG -s SVCTAG To enable ("turn on") a terminal, run pmadm -e -p PMTAG -s SVCTAG Ports are enabled by default when you "create" them as above. 45: CDE: ======== Start Login Manager: -------------------The login Server, also called the Login Manager, usually starts up the CDE environment when the system is booted and the "/etc/rc2.d/S99dtlogin" script is run.
The login Server is a server responsible for displaying a graphical logon screen, authenticating users, and starting a user session. It can display a login screen on local or network bitmap displays It can also be started from the command line, for example, to start the Login Server use either: # /etc/init.d/dtlogin start or # /usr/dt/bin/dtlogin -deamon; exit To set the Login Manager to start CDE the next time the system is booted, give the command # /usr/dt/bin/dtconfig -e Stop Login manager: ------------------To stop the Login Manager, use # /etc/init.d/dtlogin stop or # /usr/dt/bin/dtconfig -kill If you do not want the CDE startup if the system is booted use # /usr/dt/bin/dtconfig -d Other facts of the Login manager: --------------------------------By default the Login manager stores its PID in /var/dt/Xpid The login manager is configurable throug a number of files like "Xconfig". You should copy "/usr/dt/config" to "/etc/dt/config" and make modifications there. To tell the Login Manager to reread Xconfig, use # /usr/dt/bin/dtconfig -reset Displaying a Login screen: -------------------------Upon startup, the Login Server checks the Xservers file to determine if an X server needs to be started and to determine if and how login screens should be displayed on local or network displays. To modify Xservers, copy Xservers from /usr/dt/config to /etc/dt/config. After modifying, tell the login server to reread Xservers by # /usr/dt/bin/dtconfig -reset The format of a record in Xservers is: display_name display_class display_type X_server_command
display_name
= the connection name to use when connecting to the X server (:0) An * is expanded to hostname:0 = identifies resources specific to this display (for example
display_class Local) display_type = tells the Login manager whether the display is local or a network display. X_server_command = identifies the commandline, connection number, and other options the Login server will use to start the X server (/usr/bin/X11/X :0) The connection number must match the number specified in display_name. The default Xservers line is similar to: :0 Local local@console /usr/bin/X11/X :0 Running the Login Server without a Local bitmap display: -------------------------------------------------------If your login server has no bitmap display, you should comment ou the line shown above like: # :0 Local local@console /usr/bin/X11/X :0 So when the login server starts, it runs in the background waiting for requests from network displays. 46. Make command: ================ Note 1: (Not geared to any particular unix version): ---------------------------------------------------ABOUT MAKE The make utility executes a list of shell commands associated with each target, typically to create or update a file of the same name. makefile contains entries that describe how to bring a target up to date with respect to those on which it depends, which are called dependencies. SYNTAX /usr/ccs/bin/make [ -d ] [ -dd ] [ -D ] [ -DD ] [ -e ] [ -i ] [ -k ] [ -n ] [ -p ] [ -P ] [ -q ] [ -r ] [ -s] [ -S ] [ -t ] [ -V ] [ -f makefile ] ... [-K statefile ] ... [ target ... ] [ macro = value ... ] /usr/xpg4/bin/make [ -d ] [ -dd ] [ -D ] [ -DD ] [ -e ] [ -i ] [ -k ] [ -n ] [ -p ] [ -P ] [ -q ] [ -r ] [ -s] [ -S ] [ -t ] [ -V ] [ -f makefile ] ... [ target... ] [ macro = value ... ]
DESCRIPTION The make utility executes a list of shell commands associated with each target, typically to create or update a file of the same name. makefile contains entries that describe how to bring a target up to date with respect to those on which it depends, which are called dependencies. Since each dependency is a target, it may have dependencies of its own. Targets, dependencies, and sub-dependencies comprise a tree structure that make traces when deciding whether or not to rebuild a target. The make utility recursively checks each target against its dependencies, beginning with the first target entry in makefile if no target argument is supplied on the command line. If, after processing all of its dependencies, a target file is found either to be missing, or to be older than any of its dependencies, make rebuilds it. Optionally with this version of make, a target can be treated as out-of-date when the commands used to generate it have changed since the last time the target was built. To build a given target, make executes the list of commands, called a rule. This rule may be listed explicitly in the target's makefile entry, or it may be supplied implicitly by make. If no target is specified on the command line, make uses the first target defined in makefile. If a target has no makefile entry, or if its entry has no rule, make attempts to derive a rule by each of the following methods, in turn, until a suitable rule is found. Each method is described under USAGE below. Note 2: An example -----------------# find . -name "make" -print ./usr/ccs/bin/make ./usr/share/lib/make ./usr/xpg4/bin/make ./usr/appserver/samples/rmi-iiop/cpp/src/client/make /opt/app/oracle/product/9.2/sqlplus/lib >/usr/ccs/bin/make -f ins_sqlplus.mk install If you want to do compilations on Solaris, it is best not have /usr/ucb in your PATH. If you want to have /usr/ucb in the PATH it must be the last entry. You also should put /usr/ccs/bin/ before /usr/xpg4/bin/ in the PATH to make sure that /usr/ccs/bin/make is used and not /usr/xpg4/bin/make. To be able to use 'make' 'as' and 'ld' you need to make sure that /usr/ccs/bin is in your path.
Alan Coopersmith wrote: >
[email protected] (Keg) writes in comp.sys.sun.admin: > |Just curious what the stuff under /usr/ucb is for? I was looking at > |the ps utility and apparently they are the same fiel in 2 different > |places: > For users and scripts that expect the BSD style options, in cases such > as ps & ls where they are incompatible with the SvsV options found in > the /usr/bin versions. It's there for historical reasons. SunOS 4.x was based on BSD unix. Solaris 2.x (= SunOS 5.x) was based on SYSV, with a bunch of commands having different syntax and behavior. To ease the transition, the /usr/ucb directory was created to hold the incompatible BSD versions. People who really wanted BSD could put /usr/ucb before /usr in their PATH. Note 3: ------How to write a simple makefile. Let use start with a very simple example. Suppose the executable sortit depends on the main Fortran source file "sortit_main.f90" and 2 additional files "readN.f90" and "sortarray.f90". The source files can be compiled and linked in 1 f90 command: f90 -o sortit sortit_main.f90 readN.f90 sortarray.f90 Now suppose only one file changes, and the files are not small but contains many codelines, then a better approach could be this: Suppose you seperate the compilation and linking stages: - compile into objectfiles: f90 -c sortit sortit_main.f90 readN.f90 sortarray.f90 - link the files: f90 -o sortit sortit_main.o readN.f90.o sortarray.o Suppose there were many source files, and thus many objectfiles. In this case it's better to make one definitionfile which explains it all. So if one source changes, the corresponding objectfile is out of date, and needs to be recreated. All that information can be in a definitionfile, for example: sortit: sortit_main.o readN.o sortarray.o f90 -o sortit sortit_main.o readN.o sortarray.o sortit_main.o: sortit_main.f90 f90 -c sortit_main.f90 readN.o: readN.f90 f90 -c readN.f90 sortarray.o: sortarray.f90 f90 -c sortarray.f90 By default, make looks for a makefile called "makefile" in the current directory.
Alternative files can be specified with the -f option followed by the name of the makefile, for example: make -f makefile1.mk or make -f makefile1.mk install One of the labels present in the Makefile happens to be named ' install ' . Further explanation: -------------------The make utility is embedded in UNIX history. It is designed to decrease a programmer's need to remember things. I guess that is actually the nice way of saying it decreases a programmer's need to document. In any case, the idea is that if you establish a set of rules to create a program in a format make understands, you don't have to remember them again. To make this even easier, the make utility has a set of built-in rules need to tell it what new things it needs to know to build your particular utility. For example, if you make love, make would first look for some new rules from you. If you didn't supply it any then it would built-in rules. One of those built-in rules tells make that it can run the linker (ld) on a program in .o to produce the executable program.
so you only typed in look at its name ending
So, make would look for a file named love.o. But, it wouldn't stop there. Even if it found the .o file, it has some other rules that tell it to make sure the .o file is up to date. In other words, newer than the source program. The most common source program on Linux systems is written in C and its file name ends in .c. If make finds the .c file (love.c in our example) as well as the .o file, it would check their timestamps to make sure the .o was newer. If it was not newer or did not exist, it would use another built-in rule to build a new .o from the .c (using the C compiler). This same type of situation exists for other programming languages. The end result, in any case, is that when make is done, assuming it can find the right pieces, the executable program will be built and up to date. The old UNIX joke, by the way, is what early versions of make said when it could not find the necessary files. In the example above, if there was no love.o, love.c or any other source format, the program would have said: make: don't know how to make love. Stop. Getting back to the task at hand, the default file for additional rules in Makefile in the current directory. If you have some source files for a program and there is a Makefile file there,
take a look. It is just text. The lines that have a word followed by a colon are targets. That is, these are words you can type following the make command name to do various things. If you just type make with no target, the first target will be executed. What you will likely see at the beginning of most Makefile files are what look like some assignment statements. That is, lines with a couple of fields with an equal sign between them. Surprise, that is what they are. They set internal variables in make. Common things to set are the location of the C compiler (yes, there is a default), version numbers of the program and such. This now beings up back to configure. On different systems, the C compiler might be in a different place, you might be using ZSH instead of BASH as your shell, the program might need to know your host name, it might use a dbm library and need to know if the system had gdbm or ndbm and a whole bunch of other things. You used to do this configuring by editing Makefile. Another pain for the programmer and it also meant that any time you wanted to install software on a new system you needed to do a complete inventory of what was where. As more and more software became available and more and more POSIX-compliant platforms appeared, this got harder and harder. This is where configure comes in. It is a shell script (generally written by GNU Autoconf) that goes up and looks for software and even tries various things to see what works. It then takes its instructions from Makefile.in and builds Makefile (and possibly some other files) that work on the current system. Background work done, let me put the pieces together. You run configure (you usually have to type ./configure as most people don't have the current directory in their search path). This builds a new Makefile. Type make This builds the program. That is, make would be executed, it would look for the first target in Makefile and do what the instructions said. The expected end result would be to build an executable program. Now, as root, type make install. This again invokes make, make finds the target install in Makefile and files the directions to install the program. This is a very simplified explanation but, in most cases, this is what you need to know. With most programs, there will be a file named INSTALL that contains installation instructions that will fill you in on other considerations. For example, it is common to supply some options to the configure command to change the final location of the executable program. There are also other make targets such as clean that remove unneeded files after an install and, in some cases test which allows you to test the software between the make and make install steps.
47. mkitab: =========== AIX: mkitab Command Purpose Makes records in the /etc/inittab file. Syntax mkitab [ -i Identifier ] { [ Identifier ] : [ RunLevel ] : [ Action ] : [ Command ] } Description The mkitab command adds a record to the /etc/inittab file. The Identifier:RunLevel:Action:Command parameter string specifies the new entry to the /etc/inittab file. You can insert a record after a specific record using the -i Identifier flag. The command finds the field specified by the Identifier parameter and inserts the new record after the one identified by the -i Identifier flag. Example: To add a new record to the /etc/inittab file, telling the init command to handle a login on tty2, enter: mkitab "tty002:2:respawn:/usr/sbin/getty /dev/tty2" To change currently existing entries from the file, use the chitab command. For example, to change tty2's runlevel, enter the command chitab "tty002:23:respawn:/usr/sbin/getty /dev/tty2" chitab "rcnfs:23456789:off:/etc/rc.nfs > /dev/console 2>&1 # Start NFS Daemons" This is also why an /etc/inittab is usually much bigger in AIX compared to Solaris. rmitab Command Purpose Removes records in the /etc/inittab file. Syntax rmitab Identifier Description The rmitab command removes an /etc/inittab record. You can specify a record to remove by using the Identifier parameter. The Identifier parameter specifies a field of one to fourteen characters used to uniquely identify an object. If the Identifier field is not
unique, the command is unsuccessful. Examples To remove the tty entry for tty2 , enter: rmitab "tty002"
48. Starting and stopping deamons: ================================== AIX: ---AIX has a unique way of managing processes: the System Resource Controller (SRC). The SRC takes the form of a daemon, "/usr/sbin/srcmstr", which is started by init via /etc/inittab. srcmstr manages requests to start, stop, or refresh a daemon or a group of daemons. Instead of typing the name of a daemon to start it, or instead of using the kill command to stop a daemon, you use an SRC command that does it for you. In this way you don't have to remember, for example, whether to use an ampersand when starting a daemon, or what signal to use when killing one. SRC also allows you to stop and start groups of related daemons with one command. AIX has a hierarchical organization of system processes, and this organization is configured into the ODM in the form of the SRCsubsys and SRCsubsvr object classes. Daemons at the lowest levels are subservers. On a newly loaded system the only subservers are those of the inetd subsystem: ftp, telnet, login, finger, etc. To view these subservers, use the odmget command: To start a subsystem, for example # startsrc -s lpd To stop a subsystem, for example # stopsrc -s lpd You can also use the refresh command, after for example editing a .conf file and you need the subsystem to reparse the config file. For example, you have started the httpd demon # startsrc -s httpd Now you have edited the /etc/httpd.conf file. To refresh the deamon, use the following command: # refresh -s httpd To list the status of a subsystem, use for example # lssrc -g nfs
# lssrc -s sshd Subsystem biod rpc.lockd nfsd rpc.statd rpc.mountd rpc.mountd
Group nfs nfs nfs nfs nfs nfs
Pid 11354 11108
Status active active inoperative inoperative inoperative inoperative
Starting and stopping daemons in general: ----------------------------------------In general, and in most cases, daemons which are not under the control of some resource controller, can be stopped or started in a way as shown in the following "stanza": # stop # start In many occasions, a script associated with the daemon is available, that will take "stop"or "start" as an argument.
49. Inodes, the superblock and related items: ============================================= 49.1 Solaris: ------------Following is a "light weight" discussion about the superblock and inodes in the UFS filesystem in Solaris: When you create an UFS filesystem, the disk slice is divided into cylindergroups. The slice is then divided into blocks to control and organize the structure of files within the cylinder group. Each block performs a specific function in the filesystem. A UFS filesystem has the following types of blocks: Boot block: stores information used when booting the system, and is the first 8KB in a slice (partition). Superblock: stores much of the information about the filesystem. Its located after the bootblock. Inode : stores all information about a file except its name datablock : stores data for each file The bootblock stores the procedures used in booting the system. Without a bootblock the system does not boot. If a filesystem is not used for booting, the bootblock is left blank. The bootblock appears only in the first cylinder group (cylinder group 0) and is the first 8KB in a slice.
The superblock stores much of the information about the filesystem. Following are the items contained in a superblock: - size and status of the fs - label (filesystem name and volume name) - size of the fs logical block - date and time of the last update - cylinder group size - number of datablocks in a cylinder group - summary data block - fs state (clean, stable, or active) - pathname of the last mount point The superblock is located at the beginning of the disk slice and is replicated in each cilinder group. Because it contains critical data, multiple superblocks are made when the fs is created. A copy of the superblock for each filesystem is kept up-to-date in memory. The sync command forces every superblock in memory to write its data to disk. An inode contains all the information about a file except its name which is kept in a directory. An inode is 128 bytes. For each file there corresponds one inode. The inode information is kept in the cylinder information block and contains the following: - the type of file (regular file, directory, block special, character special, link) - mode of the file (rwxrwxrwx) - number of hard links to the file - userid of the owner - groupid - number of bytes in the file - an array of 15 disk-block addresses - date and time the file was last accessed - date and time the file was last modified - date and time the file was created The maximum number of files per UFS file system is determined by the number of inodes allocated for a filesystem. The number of inodes depends on the amount of diskspace that is allocated for each inode and the total size of the filesystem. By default, on inode is allocated for each 2KB of dataspace. You can change this default with the newfs command. Inodes include pointers to the data blocks. Each inode contains 15 pointers: the first 12 pointers point directly to data blocks the 13th pointer points to an indirect block, a block containing pointers to data blocks the 14th pointer points to a doubly-indirect block, a block containing 128 addresses of singly indirect blocks the 15th pointer points to a triply indirect block (which contains pointers to doubly indirect blocks, etc.)
------------------------------| | | | | | | | | | | | | | | | ------------------------------| | | | | | | | | | | | | | |-------------------------data blocks | |-----------| | | | | ------------| | | | | | ------------||| ||| ||| data --------| | | | --------||| ||| data ----| | ----||| data
--------------------------------------------------------------------------| | | | | | | | | | | | | | | | | | B. B. | S. B. | Inodes | | | ... | Many Data Blocks ...... | | | | | | | | | | | | | | | | | | --------------------------------------------------------------------------In order to create a UFS filesystem on a formatted disk that already has been divided into slices you need to know the raw device filename of the slice that will contain the filesystem. Example: # newfs /dev/rdsk/c0t3d0s7 defaults on UFS on Solaris: blocksize 8192 fragmentsize 1024 one inode for each 2K of diskspace 49.2 AIX: --------Although we use the LVM to create Volume Groups, and Logical Volumes within a Volume Group, a file system resides on a single logical volume. Every file and directory belongs to a file system within a logical volume. The mkfs (make file system) command, or crfs command, or the System Management Interface Tool (smit command) creates a file system on a logical volume. - crfs The crfs command creates a file system on a logical volume within a previously created volume group. A new logical volume is created for the file system unless the name of an existing
logical volume is specified using the -d. An entry for the file system is put into the /etc/filesystems file. By the way, a newly installed AIX 5.x system has the following filesystem structure: "/" root is a filesystem. Certain standard directories are present within "/", like for example /bin. But also a set of separate filesystems like hd2=/usr, hd3=/tmp, hd9var=/var, are MOUNTED over the coresponding named directories or mountpoints. / | ---------------------------------------| | | | | | | /bin /dev /etc /usr /tmp /var /home directories file systems So, when you unmount all extra (later on) defined filesystems like /export, /software etc.. you still have / (with its standard directories like /etc, /bin etc..) and the standard filesystems like /usr etc.. inodes: -------- Working with JFS i-nodes: -- ------------------------Files in the journaled file system (JFS) are represented internally as index nodes (i-nodes). Journaled file system i-nodes exist in a static form on disk and contain access information for the file as well as pointers to the real disk addresses of the file's data blocks. The number of disk i-nodes available to a file system is dependent on the size of the file system, the allocation group size (8 MB by default), and the number of bytes per i-node ratio (4096 by default). These parameters are given to the mkfs command at file system creation. When enough files have been created to use all the available i-nodes, no more files can be created, even if the file system has free space. The number of available i-nodes can be determined by using the df -v command. Disk i-nodes are defined in the /usr/include/jfs/ino.h file. When a file is opened, an in-core i-node is created by the operating system. The in-core i-node contains a copy of all the fields defined in the disk i-node, plus additional fields for tracking the in-core i-node. In-core i-nodes are defined in the /usr/include/jfs/inode.h file. Disk i-node Structure for JFS
Each disk i-node in the journaled file system (JFS) is a 128-byte structure. The offset of a particular i-node within the i-node list of the file system produces the unique number (i-number) by which the operating system identifies the i-node. A bit map, known as the i-node map, tracks the availability of free disk i-nodes for the file system. Disk i-nodes include the following information: Field i_mode i_size i_uid i_gid i_nblocks i_mtime i_atime i_ctime i_nlink i_rdaddr[8] i_rindirect
Contents Type of file and access permission mode bits Size of file in bytes Access permissions for the user ID Access permissions for the group ID Number of blocks allocated to the file Last time file was modified Last time file was accessed Last time i-node was modified Number of hard links to the file Real disk addresses of the data Real disk address of the indirect block, if any
It is impossible to change the data of a file without changing the i-node, but it is possible to change the i-node without changing the contents of the file. For example, when permission is changed, the information within the i-node (i_ctime) is modified, but the data in the file remains the same. The i_rdaddr field within the disk i-node contains 8 disk addresses. These addresses point to the first 8 data blocks assigned to the file. The i_rindirect field address points to an indirect block. Indirect blocks are either single indirect or double indirect. Thus, there are three possible geometries of block allocation for a file: direct, indirect, or double indirect. Use of the indirect block and other file space allocation geometries are discussed in the article JFS File Space Allocation . Disk i-nodes do not contain file or path name information. Directory entries are used to link file names to i-nodes. Any i-node can be linked to many file names by creating additional directory entries with the link or symlink subroutine. To discover the i-node number assigned to a file, use the ls -i command. The i-nodes that represent files that define devices contain slightly different information from i-nodes for regular files. Files associated with devices are called special files. There are no data block addresses in special device files, but the major and minor device numbers are included in the i_rdev field. In normal situations, a disk i-node is released when the link count (i_nlink) to the i-node equals 0.
Links represent the file names associated with the i-node. When the link count to the disk i-node is 0, all the data blocks associated with the i-node are released to the bit map of free data blocks for the file system. The i-node is then placed on the free i-node map. In-core i-node Structure When a file is opened, the information in the disk i-node is copied into an incore i-node for easier access. The in-core i-node structure contains additional fields which manage access to the disk i-node's valuable data. The fields of the in-core i-node are defined in the inode.h file. Some of the additional information tracked by the in-core i-node is: -Status of the in-core i-node, including flags that indicate: An i-node lock A process waiting for the i-node to unlock Changes to the file's i-node information Changes to the file's data -Logical device number of the file system that contains the file -i-number used to identify the i-node -Reference count. When the reference count field equals 0, the in-core i-node is released. When an in-core i-node is released (for instance with the close subroutine), the in-core i-node reference count is reduced by 1. If this reduction results in the reference count to the in-core i-node becoming 0, the i-node is released from the in-core i-node table, and the contents of the in-core i-node are written to the disk copy of the i-node (if the two versions differ).
-- Working with JFS2 i-nodes: -- -------------------------Files in the enhanced journaled file system (JFS2) are represented internally as index nodes (i-nodes). JFS2 i-nodes exist in a static form on the disk and they contain access information for the files as well as pointers to the real disk addresses of the file's data blocks. The i-nodes are allocated dynamically by JFS2. When a file is opened, an in-core i-node is created by the operating system. The in-core i-node contains a copy of all the fields defined in the disk i-node, plus additional fields for tracking the in-core i-node. In-core i-nodes are defined in the /usr/include/j2/j2_inode.h file. Disk i-node Structure for JFS2 Each disk i-node in JFS2 is a 512 byte structure. The index of a particular i-node allocation map of the file system produces the unique number (i-number) by which the operating system identifies the i-node.
The i-node allocation map tracks the location of the i-nodes on the disk as well as their availability. Disk i-nodes include the following information: Field di_mode di_size di_uid di_gid di_nblocks di_mtime di_atime di_ctime di_nlink di_btroot
Contents Type of file and access permission mode bits Size of file in bytes Access permissions for the user ID Access permissions for the group ID Number of blocks allocated to the file Last time file was modified Last time file was accessed Last time i-node was modified Number of hard links to the file Root of B+ tree describing the disk addresses of the data
50. sendmail: ============= Solaris: -------To receive SMTP mail from the network, run sendmail as a daemon during system startup. The sendmail daemon listens to TCP port 25 and processes incoming mail. In most cases the code to start sendmail is already in one of your boot scripts. If it isn't, add it. # Start the sendmail daemon: if [ -x /usr/sbin/sendmail ]; then echo "Starting sendmail daemon (/usr/sbin/sendmail -bd -q 15m)..." /usr/sbin/sendmail -bd -q 15m fi First, this code checks for the existence of the sendmail program. If the program is found, the code displays a startup message on the console and runs sendmail with two command-line options. One option, the -q option, tells sendmail how often to process the mail queue. In the sample code, the queue is processed every 15 minutes (-q15m), which is a good setting to process the queue frequently. Don't set this time too low. Processing the queue too often can cause problems if the queue grows very large, due to a delivery problem such as a network outage. For the average desktop system, every hour (-q1h) or half hour (-q30m) is an adequate setting. The other option relates directly to receiving SMTP mail. The option (-bd) tells sendmail to run as a daemon and to listen to TCP port 25 for incoming mail. Use this option if you want your system to accept incoming TCP/IP mail.
The Linux example is a simple one. Some systems have a more complex startup script. Solaris 2.5, which dedicates the entire /etc/init.d/sendmail script to starting sendmail, is a notable example. The mail queue directory holds mail that has not yet been delivered. It is possible that the system went down while the mail queue was being processed. Versions of sendmail prior to sendmail V8, such as the version that comes with Solaris 2.5, create lock files when processing the queue. Therefore lock files may have been left behind inadvertently and should be removed during the boot. Solaris checks for the existence of the mail queue directory and removes any lock files found there. If a mail queue directory doesn't exist, it creates one. The additional code found in some startup scripts is not required when running sendmail V8. All you really need is the sendmail command with the -bd option. nlih30207858-08:/etc/rc2.d $ ps -ef | grep "sendmail" smmsp 412 1 0 Jan 09 ? 0:00 /usr/lib/sendmail -Ac -q15m root 413 1 0 Jan 09 ? 0:03 /usr/lib/sendmail -bd -q15m Setup sendmail user and group Before doing anything else, check that the mail user and group are set up. Look in /etc/passwd for user smmsp with uid 25. Then check in /etc/group for group smmsp with gid 25. If they are there, good. If not, add them with: groupadd -g 25 smmsp useradd -u 25 -g smmsp -d / smmsp Then edit /etc/passwd and remove the shell. You want the line to look something like "smmsp:x:25:25::/:". I notice that Slackware has the line set to "smmsp:x:25:25:smmsp:/var/spool/clientmqueue:", and that's okay too, so I leave it at that. In Solaris you should have an entry in passwd as follows: smmsp:x:25:25:SendMail Message Submission Program:/:/sbin/noshell Stoping and starting sendmail /etc/rc2.d/S88sendmail stop then start on Sun systems. /etc/rc.d/init.d/sendmail stop then start on Linux systems. Note: About mail: ----------------mail -f = show mail in your box enter the number at the ? prompt to read the mail examples: # mail -f
Mail [5.2 UCB] [AIX 5.X] "/root/mbox": 0 messages
Type ? for help.
# mail -f Mail [5.2 UCB] [AIX 5.X] Type ? for help. "/root/mbox": 3 messages > 1 root Tue Nov 1 17:05 13/594 2 MAILER-DAEMON Sun Oct 30 07:59 109/3527 "Postmaster notify: see trans" 3 daemon Wed Jan 26 10:59 34/1618 ? 1 Message 1: From root Tue Nov 1 17:05:34 2005 Date: Tue, 1 Nov 2005 17:05:34 +0100 From: root To: root .. ..
51. SAR: ======== AIX: ---sar Command Purpose Collects, reports, or saves system activity information. Syntax /usr/sbin/sar [ { -A | [ -a ] [ -b ] [ -c ] [ -k ] [ -m ] [ -q ] [ -r ] [ -u ] [ -V ] [ -v ] [ -w ] [ -y ] } ] [ -P ProcessorIdentifier, ... | ALL ] [ -ehh [ :mm [ :ss ] ] ] [ -fFile ] [ -iSeconds ] [ -oFile ] [ -shh [ :mm [ :ss ] ] ] [ Interval [ Number ] ] The sar command writes to standard output the contents of selected cumulative activity counters in the operating system. The accounting system, based on the values in the Number and Interval parameters, writes information the specified number of times spaced at the specified intervals in seconds. The default sampling interval for the Number parameter is 1 second. The collected data can also be saved in the file specified by the -o File flag. The sar command extracts and writes to standard output records previously saved in a file. This file can be either the one specified by the -f flag or, by default, the standard system activity daily data file, the /var/adm/sa/sadd file, where the dd parameter indicates the current day. To report system unit activity, enter: # sar To report current tty activity for each 2 seconds for the next 20 seconds, enter:
# sar -y -r 2 20 To watch system unit for 10 minutes and sort data, enter: # sar -o temp 60 10 To report cpu activity for the first two processors, enter: # sar -u -P 0,1 cpu %usr %sys %wio %idle 0 45 45 5 5 1 27 65 3 5 To report message, semaphore, and cpu activity for all processors and system-wide, enter: # sar -mu -P ALL On a four-processor system, this produces output similar to the following (the last line indicates system-wide statistics for all processors): cpu msgs/s sema/s %usr %sys %wio %idle 0 7 2 45 45 5 5 1 5 0 27 65 3 5 2 3 0 55 40 1 4 3 4 1 48 41 4 7 19 3 44 48 3 5 To collect all the statistics that sar monitors at 60 second intervals for a 10 hour period. Also redirects console output to null device # nohup sar -A -o /tmp/SAR.STATS 60 600 > /dev/null & The -A switch will cause all of the data collected by sar to be reported. The -ubcwyaqvm switch prevents some data from being reported. On the obsolete AIX versions 4.2 throught 5.1, you should also make sure that the schedtune and vmtune utilities can be found in /usr/samples/kernel . If they're not there, install bos.adt.samples. These utilites are used to report on the tunable parameters for the VMM and the scheduler, and SarCheck is much more useful if it can analyze the values of these parameters. On newer versions of AIX, this is not necessary because we look at ioo, schedo, vmo, and vmstat -v for the data we need. Solaris: -------Some specifics for Solaris with regards to the sar command: How to check File Access: # sar -a How to check Buffer Activity: (metadata= inodes, cylinder group blocks etc..) # sar -b How to check System Call Statistics: # sar -c
How to check Disk Activity: # sar -d How to check Page-Out and memory: # sar -g How to check Kernel Memory Allocation: # sar -k How to check Interprocess Communication: # sar -m How to check Page-In activity: # sar -p How to check Queue Activity: # sar -q How to check Unused Memory: # sar -r How to check CPU Utilization: # sar -u
52. Xwindows: ============= 52.1 About the XWindows system: ------------------------------The X Window System is a graphics system primarily used on Unix systems (and, less commonly, on VMS, MVS, and MS-Windows systems) that provides an inherently client/server oriented base for displaying windowed graphics. It provides a public protocol by which client programs can query and update information on X servers. The representation of "client" and "server" appears a little bit backwards from most client/server systems. Usually, people expect the "local" programs to be called a "client," and for the "server" to be something off in the back room. Which nicely represents the way database applications usually work, with many "clients" connecting to a central database "server." X reverses these roles, which, as the locations of the hosts are reversed, is quite appropriate: An X server is a program that manages a video system (and possibly other "interactive" I/O devices such as mice, keyboards, and some more unusual devices). The X server thus typically runs on a user's desktop, typically a relatively nonpowerful host that would commonly
be termed a "client system." It is, in this context, nonetheless acting as a server as it provides graphics services. On the other hand, an X client is typically an application program which must connect to an X Server in order to display things. The client will often run on another host, often a powerful Unix box that would commonly be known as a "server." The X client might itself also be a "server process" from some other point of view; there is no contradiction here. (Although calling it such may be unwise as it will naturally result in further confusion.) X nomenclature treats anything that provides display services as an X server. Which is not particularly different from someone saying that a program that provides database services is a database server. The upshot (and the point) of all this is that this allows use of the X system that allows processes on various computers on a network to display stuff on display devices elsewhere on the network. - GNOME: GNOME - GNU Network Object Model Environment GNOME is not a window manager. GNOME is an application framework that consists of libraries to assist in application development and a set of applications that use those libraries. It seeks to provide: An API for interapplication communications. This will represent a set of objects running via a CORBA Object Request Broker called ORBit. This is crucial piece of the infrastructure, with which they intend to implement a component architecture to build "compound documents" not entirely unlike OpenDoc; without this, GNOME is merely a "pretty face," consuming memory and disk space for relatively little value. This description strongly parallels that of CDE... - K Desktop Environment - KDE The KDE (K Desktop Environment) Project is building an integrated desktop environment including a window manager, file manager/web browser, and other components using the Trolltech "Qt" toolset, a development toolset written for C++ that allows applications to be deployed atop either X11 or Win32. KDE had been using the MICO CORBA ORB to construct an application embedding framework known as KOM and OpenParts. According to the [ KDE-Two: Second KDE Developers Conference], they found
themselves unable to use the standardized CORBA framework, citing problems with concurrency, reliability and performance, and have instead decided to create Yet Another IPC Framework involving a shared library called libICE. On the other hand, the KDE Technology Overview for Version 2.0 provides a somewhat different story, so it's not completely clear just what is going on; they indicate the use of an IPC scheme called DCOP, indicating it to be a layer atop libICE, with the option of also using XML-RPC as an IPC scheme. 52.2 Running Cygwin on a PC, to have a Xwin Server: --------------------------------------------------Example of starting a xwin session C:\cygwin\usr\X11R6\bin\XWin.exe -query hostname -fullscreen -fp tcp/hostname:7100". X & xhost + export DISPLAY=:0 When using X from a terminal server session, take note of the right ip and port. 52.3 XWin on AIX: ----------------The xdm (X Display Manager) command manages a collection of X displays, which may be on the local host or remote servers. The design of the xdm command was guided by the needs of X terminals as well as the X Consortium standard XDMCP, the X Display Manager Control Protocol. The xdm command provides services similar to those provided by the init, getty, and login commands on character terminals: prompting for login name and password, authenticating the user, and running a session. Starting xdm xdm is typically started at system boot time. This is typically done in either an rc file in the /etc directory, or in the inittab file. Starting xdm in an rc file is usually simply a matter of adding the desired command line to the file, as in the example below. /usr/bin/X11/xdm -daemon -config /usr/lib/X11/xdm/xdm-config & IBM wants xdm to integrate into their src subsystem. The AIX version of the above command is a bit different. start /usr/bin/X11/xdm $src_running
The problem with this not really integrated the src subsystem, so not work properly. An alternative, which the inittab file.
is that since xdm is not supported in R4 under AIX, it is into the attendant startup, shutdown, and other src commands do works on many other systems as well, is to start xdm from
xdm:2:respawn:/usr/bin/X11/xdm -nodaemon -config /usr/lib/X11/xdm-config The -nodaemon flag keeps xdm from starting a daemon and exiting, which would cause the respawn option to start another copy of xdm, whereupon the process would repeat itself, quickly filling up your process table and dragging your system to its knees attempting to run oodles of managers and servers. xdm attempts to use system lock calls to prevent this from happening. It nevertheless happens on some systems. 52.4 XWin on Linux: ------------------52.4.1 Redhat: -------------While the heart of Red Hat Linux is the kernel, for many users, the face of the operating system is the graphical environment provided by the X Window System, also called simply X. This chapter is an introduction to the behind-the-scenes world of XFree86, the open-source implementation of X provided with Red Hat Linux. X uses a client-server architecture. An X server process is started and X client processes can connect to it via a network or local loopback interface. The server process handles the communication with the hardware, such as the video card, monitor, keyboard, and mouse. The X client exists in the user-space, issuing requests to the X server. The X server performs many difficult tasks using a wide array of hardware, requiring detailed configuration. If some aspect of your system changes, such as the monitor or video card, XFree86 will need to be reconfigured. In addition, if you are troubleshooting a problem with XFree86 that cannot be solved using a configuration utility, such as the X Configuration Tool (redhatconfig-xfree86), you may need to access its configuration file directly. Red Hat Linux 8.0 uses XFree86 version 4.2 as the base X Window System, which includes the various necessary X libraries, fonts, utilities, documentation, and development tools. - The X Window System resides primarily in two locations in the file system: /usr/X11R6/ directory
A directory containing X client binaries (the bin directory), assorted header files (the include directory), libraries (the lib directory), and manual pages (the man directory), and various other X documentation (the /usr/X11R6/lib/X11/doc/ directory). /etc/X11/ directory The /etc/X11/ directory hierarchy contains all of the configuration files for the various components that make up the X Window System. This includes configuration files for the X server itself, the X font server (xfs), the X Display Manager (xdm), and many other base components. Display managers such as gdm and kdm, as well as various window managers, and other X tools also store their configuration in this hierarchy. - The Redhat X configuration tool: from command line: # redhat-config-xfree86 from X: go to the Main Menu Button (on the Panel) => System Tools => Display - XFree86 configuration file "etc/X11/XF86Config" XFree86 version 4 server is a single binary executable � /usr/X11R6/bin/XFree86. This server dynamically loads various X server modules at runtime from the "/usr/X11R6/lib/modules/" directory including video drivers, font engine drivers, and other modules as needed. Some of these modules are automatically loaded by the server, whereas some are optional features that you must specify in the XFree86 server's configuration file, "/etc/X11/XF86Config", before they can be used. The video drivers are located in the /usr/X11R6/lib/modules/drivers/ directory. The DRI hardware accelerated 3D drivers are located in the /usr/X11R6/lib/modules/dri/ directory. - Running a simple X client: You do not have to run a complicated window manager in conjunction with a particular desktop environment to use X client applications. Assuming that you are not already in an X environment and do not have an .xinitrc file in your home directory, type the xinit command to start X with a basic terminal window (the default xterm application). You will see that this basic environment utilizes your keyboard, mouse, video card, and monitor with the XFree86 server, using the server's hardware preferences. Type exit at the xterm prompt to leave this basic X environment. - Running X: The startx command When you start X using the "startx" command, a pre-specified desktop environment is utilized. To change the default desktop environment used when X starts, open a terminal and
type the switchdesk command. This brings up a graphical utility that allows you to select the desktop environment or window manager to use the next time X starts. Most users run X from runlevels 3 or 5. Runlevel 3 places your system in multiuser mode with full networking capabilities. The machine will boot to a text-based login prompt with all necessary preconfigured services started. Most servers are run in runlevel 3, as X is not necessary to provide any services utilized by most users. Runlevel 5 is similar to 3, except that it automatically starts X and provides a graphical login screen. Many workstation users prefer this method, because it never forces them to see a command prompt. The default runlevel used when your system boots can be found in the /etc/inittab file. If you have a line in that file that looks like id:3:initdefault:, then your system will boot to runlevel 3. If you have a line that looks like id:5:initdefault:, your system is set to boot into runlevel 5. As root, change the runlevel number in this file to set a different default. Save the file and restart your system to verify that it boots to the correct runlevel. When in runlevel 3, the preferred way to start an X session is to type the startx command. startx, a front-end to the xinit program, launches the XFree86 server and connects the X clients to it.
53. TAPE DRIVES: ================ 53.1 AIX: --------Some usefull examples, using a tape: -----------------------------------# # # #
mksysb -i /dev/rmt0 backup -0 -uf /dev/rmt0 /data tctl -f /dev/rmt0 rewind savevg -if /dev/rmt0 uservg
# lsdev -Cc tape rmt0 Available 10-60-00-5,0 # lsattr -El rmt0 mode yes block_size 1024 extfm no ret no ..
SCSI 8mm Tape Drive
Use DEVICE BUFFERS during writes Block size (0=variable length) Use EXTENDED file marks RETENSION on tape change or reset
True True True True
.. To list the default values for that tape device (-D flag), use # lsattr -l -D rmt0 # lscfg -vl rmt0 Manufacturer...............EXABYTE Machine Type and Model.....IBM-20GB Device Specific(Z1)........38zA Serial Number..............60089837 .. .. Its very important which /dev/rmtx.y you use in some backup command like tar. See the following table: special file rewind on close retension on open density setting -------------------------------------------------------------------------------/dev/rmtx yes no #1 /dev/rmtx.1 no yes #1 /dev/rmtx.2 yes yes #1 /dev/rmtx.3 no yes #2 /dev/rmtx.4 yes no #2 /dev/rmtx.5 no no #2 /dev/rmtx.6 yes yes #2 /dev/rmtx.7 no yes #2 54. WSM Web based System Manager: ================================= AIX only: --------Web based System manager is a graphical user interface administration tool for AIX 5.x systems. This is a Java based suite of system management tools. To start WSM, use the following command from the command line of a graphical console: # wsm - The WSM can be run in stand-alone mode, that is, you can use the tool to perform system administration on the AIX system you are currently running on. - However, the WSM also supports a client-server environment. In this environment, it is possible to administer an AIX system from a remote PC or from another AIX system using a graphics terminal. In this environment, the AIX system being administered is the Server and the system you are performing the administration functions from is the client. The client can operate in either application mode on AIX with jave 1.3, or in applet mode on platforms that support Java 1.3. Thus, the AIX system can be managed from another AIX system or from a PC with a browser and Java.
55. SOFTWARE INSTALLATIONS ON AIX 5.x: ====================================== 55.1 Installing VisualAge C++ / C compiler on AIX 5.x: ====================================================== IBM VisualAge is a commandline C and C++ compiler for the AIX operating system. You can use VisualAge as a C compiler for files with a .c suffix, or as a C++ compiler for files with a .C, .cc, .cpp or .cxx suffix. The compiler processes your textbased program source files to create an executable object module. In most cases you should use the xlC command to compile your C++ source files, and the xlc command to compile C source files. You can use VisualAge to develop both 32 bit and 64 bit appliactions. If you want to install VisualAge C++ for AIX, check first if the following required filesets are installed. bos.adt.include bos.adt.l1b bos.adt.l1bm bos.net.ncs 1for_ls.compat 1for_ls.base
Base Application Development Include Files Base Application Development Libraries Base Application Development Math Libraries Base Network Computing Services License Use Management version 4 compatibility License Use Management version 4 Base
Use the following command to see whether these are installed: # lslpp -h bos.adt.include bos.adt.l1b bos.adt.l1bm \ bos.net.ncs 1for_ls.compat 1for_ls.base For some components, the following needs to be installed as well: X11.base.rte, bos.rte.11bpthreads, 1pfx.rte, 1for_ls.base.gu1, 1for_ls.client.gui Make sure the AppDev package has been installed in order to have access to commands like "make" etc... Notes: ====== Note 1: ------IBM C and C++ Compilers Usage: xlC [ option | inputfile ]... xlc [ option | inputfile ]... cc [ option | inputfile ]... c89 [ option | inputfile ]... xlC128 [ option | inputfile ]... xlc128 [ option | inputfile ]... cc128 [ option | inputfile ]... xlC_r [ option | inputfile ]... xlc_r [ option | inputfile ]...
cc_r [ option | inputfile ]... xlC_r4 [ option | inputfile ]... xlc_r4 [ option | inputfile ]... cc_r4 [ option | inputfile ]... CC_r4 [ option | inputfile ]... xlC_r7 [ option | inputfile ]... xlc_r7 [ option | inputfile ]... cc_r7 [ option | inputfile ]... Description: The xlC and related commands compile C and C++ source files. They also processes assembler source files and object files. Unless the -c option is specified, xlC calls the linkage editor to produce a single object file. Input files may be any of the following: 1. file name with .C suffix: C++ source file 2. file name with .i suffix: preprocessed C or C++ source file 3. file name with .c suffix: C source file 4. file name with .o suffix: object file for ld command 5. file name with .s suffix: assembler source file 6. file name with .so suffix: shared object file xlc : ANSI C compiler with UNIX header files. Use this command for most new C programs. cc : Extended C compiler. This command invokes a non-ANSI compliant compiler. Use it for legacy C programs. c89 : Strict ANSI C compiler with ANSI header files. Use this command for maximum portability of your C programs. xlC : Native (i.e., non-cfront) C++ compiler. Use this command for compiling and linking all C++ code. The following additional command names, plus their "-tst" and "-old" variants, are also available at SLAC for compiling and linking reentrant programs: xlc_r, cc_r; xlC_r : For use with POSIX threads xlc_r4, cc_r4; xlC_r4, CC_r4 : For use with DCE threads Note 2: ------install VisualAge C++: -
insert CD smitt install_latest press F4 to display all devices select CDROM device press F4 to select the filesets you want to install
After you have installed VisualAge C++ for AIX, you need to enroll your license for the product before using it. VisualAge C++ is not automatically installed in /usr/bin. To invoke the compiler
without having to specify the full path, do one of the following steps: - create symbolic links for the specific driver contained in /usr/vacpp/bin and /usr/vac/bin to /usr/bin - add /usr/vacpp/bin and /usr/vac/bin to your path Note 3: ------Note: usage of vac examples: Example 1: xlc -I/usr/local/include -L/usr/local/lib simple.c -lcurl -lz Example 2: The commands listed below invoke versions of the XL C compiler, which then translates C source code statements into object code, sends .s files to the assembler, and links the resulting object files with object files and libraries specified on the command line in the order in which they are listed, producing a single executable file called "a.out" by default. The -o flag may be used to rename the resulting executable file. Where commands are shown, they are generally given as generic examples. In any case, you type the appropriate command and press the Return (or Enter) key as usual. You compile a source program and/or subprograms by typing the following command: xlc cmd_line_opts input_files input_files are source files (.c or .i), object files (.o), or assembler files (.s) For example, to compile a C program whose source is in source file "prog.c" you would enter the following command: xlc prog.c After the xlc command completes, you will see a new executable file named "a.out" in your directory. If you specify -c as a compiler option, XL C only compiles the source program, producing an object file whose default name is that of the program with a .o extension. Before running the program, you must invoke the linkage editor phase. Either invoke the linker using the ld command or issue the xlc command a second time without the -c option, using the desired object (.o) filenames. For example, you may compile a subprogram "second.c" and then use it in your main program "prog.c" with the following sequence of commands:
xlc -c second.c xlc prog.c second.o Some important files on a test system: # find -name "crt0_64.o" -print /usr/lib/crt0_64.o /usr/css/lib/crt0_64.o # find -name "crt0_32.o" -print /usr/lib/crt0_64.o /usr/css/lib/crt0_64.o Check out if vac is installed: root@zd110l02:/root#lslpp -l vacpp* lslpp: Fileset vacpp* not installed. root@zd110l02:/root#lslpp -l xlC* Fileset Level State Description ---------------------------------------------------------------------------Path: /usr/lib/objrepos xlC.aix50.rte 7.0.0.6 COMMITTED C Set ++ Runtime for AIX 5.0 xlC.cpp 6.0.0.0 COMMITTED C for AIX Preprocessor xlC.rte 7.0.0.1 COMMITTED C Set ++ Runtime
Note 4: ------At a certain organisation, the installation goes as follows: install: # cd /prj/tmp # tar xv # ./driver
(tape in rmt0)
config licentie: # /usr/vac/bin/vac6_licentie # l4blt -r6 # /usr/opt/ifor/ls/aix/bin/i4blt -r6 test: - using existing sourcefile: # cd /prj/vac/cctst # cc fac.c -o fac # ./fac
Or... - make a simple c source and compile it: #include int main(void) { printf("Hello World!\n"); return 0; } now compile it # /usr/vac/bin/xlc hello.c -o hello now run it # ./hello
Note 5: LUM ----------i4lmd - Network License Server Subsystem The i4lmd subsystem starts the network license server on the local node. Examples Start a license server and do not log checkin, vendor, product, timeout, or message events: startsrc -s i4lmd -a "-no cvptm" Start a license server changing the default log-file: startsrc -s i4lmd -a "-l /ifor/ls/my_log" On an example p520 systeem: --------------------------In /etc/inittab: i4ls:2:wait:/etc/i4ls.rc > /dev/null 2>&1 # Start i4ls cat /etc/i4ls.rc #!/bin/ksh # IBM_PROLOG_BEGIN_TAG # This is an automatically generated prolog. # # bos520 src/bos/usr/opt/ifor/var/i4ls.rc 1.8 # # Licensed Materials - Property of IBM # # (C) COPYRIGHT International Business Machines Corp. 1996,2001 # All Rights Reserved # # US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # IBM_PROLOG_END_TAG /usr/opt/ifor/ls/os/aix/bin/i4cfg -start -nopause exit 0 On an example p550 system 29-12-2006, all apps down: ---------------------------------------------------# ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 Dec 11 - 3:08 /etc/init root 327918 1 0 Dec 11 - 0:00 /usr/lib/errdemon root 352504 1 0 Dec 11 - 0:00 /usr/ccs/bin/shlap64 root 360466 1 0 Dec 11 - 253:18 /usr/sbin/syncd 60 root 548880 1724510 0 08:33:45 pts/0 0:00 -ksh root 585948 548880 1 09:11:19 pts/0 0:00 ps -ef cissys 880788 1060964 0 09:07:51 - 0:00 /usr/sbin/sftp-server root 983044 1011962 0 Dec 11 - 0:00 /usr/sbin/qdaemon root 999432 1 0 Dec 11 - 0:00 /usr/sbin/uprintfd root 1003764 1 0 Dec 11 - 0:34 /usr/sbin/cron root 1011962 1 0 Dec 11 - 0:00 /usr/sbin/srcmstr root 1024034 1 0 Dec 11 - 0:00 /usr/local/sbin/syslog-ng -f /usr/local/etc/syslog-ng.conf root 1028102 1 0 Dec 11 - 0:00 ./mflm_manager root 1036402 1011962 0 Dec 11 - 0:00 /etc/ncs/llbd root 1040402 1052716 0 Dec 11 - 0:00 /usr/opt/ifor/bin/i4lmd -l /var/ifor/logdb -n clwts root 1052716 1011962 0 Dec 11 - 0:44 /usr/opt/ifor/bin/i4lmd -l /var/ifor/logdb -n clwts root 1056788 1011962 0 Dec 11 - 0:00 /usr/sbin/rsct/bin/IBM.AuditRMd cissys 1060964 1532138 0 09:07:51 - 0:01 sshd: cissys@notty root 1065016 1011962 0 Dec 11 - 0:05 /usr/sbin/rsct/bin/IBM.CSMAgentRMd root 1073192 1011962 0 Dec 11 - 0:00 /usr/sbin/rsct/bin/IBM.ServiceRMd root 1077274 1 0 Dec 11 - 0:01 /opt/hitachi/HNTRLib2/bin/hntr2mon -d root 1081378 1011962 0 Dec 11 - 0:28 /usr/DynamicLinkManager/bin/dlmmgr root 1085478 1011962 0 Dec 11 - 0:06 /etc/ncs/glbd root 1089574 1101864 0 Dec 11 - 0:00 /usr/opt/ifor/bin/i4llmd -b -n wcclwts -l /var/ifor/llmlg root 1101864 1011962 0 Dec 11 - 3:14 /usr/opt/ifor/bin/i4llmd -b -n wcclwts -l /var/ifor/llmlg root 1110062 1011962 0 Dec 11 - 0:01 /usr/sbin/rsct/bin/rmcd -a IBM.LPCommands -r root 1114172 1011962 0 Dec 11 - 0:00 /usr/sbin/rsct/bin/IBM.ERrmd root 1122532 1167500 0 08:23:22 - 0:00 sshd: reserve [priv] root 1126476 1 0 Dec 27 lft0 0:00 -ksh root 1167500 1011962 0 03:17:38 - 0:00 /usr/sbin/sshd -D oracle 1175770 1 0 Dec 11 - 12:29 /apps/oracle/product/9.2/bin/tnslsnr listener -inherit root 1532138 1167500 0 09:07:50 - 0:00 sshd: cissys [priv] root 1708224 1126476 4 08:40:14 lft0 0:45 tar -cvf /dev/rmt0 /prj/was reserve 1724510 1786036 0 08:23:34 pts/0 0:00 -ksh reserve 1786036 1122532 0 08:23:34 - 0:00 sshd: reserve@pts/0
inittab: -------init:2:initdefault: brc::sysinit:/sbin/rc.boot 3 >/dev/console 2>&1 # Phase 3 of system boot powerfail::powerfail:/etc/rc.powerfail 2>&1 | alog -tboot > /dev/console # Power Failure Detection mkatmpvc:2:once:/usr/sbin/mkatmpvc >/dev/console 2>&1 atmsvcd:2:once:/usr/sbin/atmsvcd >/dev/console 2>&1 load64bit:2:wait:/etc/methods/cfg64 >/dev/console 2>&1 # Enable 64-bit execs tunables:23456789:wait:/usr/sbin/tunrestore -R > /dev/console 2>&1 # Set tunables rc:23456789:wait:/etc/rc 2>&1 | alog -tboot > /dev/console # Multi-User checks rcemgr:23456789:once:/usr/sbin/emgr -B > /dev/null 2>&1 fbcheck:23456789:wait:/usr/sbin/fbcheck 2>&1 | alog -tboot > /dev/console # run /etc/firstboot srcmstr:23456789:respawn:/usr/sbin/srcmstr # System Resource Controller rctcpip:23456789:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP daemons sniinst:2:wait:/var/adm/sni/sniprei > /dev/console 2>&1 : rcnfs:23456789:wait:/etc/rc.nfs > /dev/console 2>&1 # Start NFS Daemons cron:23456789:respawn:/usr/sbin/cron : piobe:2:wait:/usr/lib/lpd/pio/etc/pioinit >/dev/null 2>&1 # pb cleanup qdaemon:23456789:wait:/usr/bin/startsrc -sqdaemon : writesrv:23456789:wait:/usr/bin/startsrc -swritesrv uprintfd:23456789:respawn:/usr/sbin/uprintfd shdaemon:2:off:/usr/sbin/shdaemon >/dev/console 2>&1 # High availability daemon l2:2:wait:/etc/rc.d/rc 2 logsymp:2:once:/usr/lib/ras/logsymptom # for system dumps : itess:23456789:once:/usr/IMNSearch/bin/itess -start search >/dev/null 2>&1 diagd:2:once:/usr/lpp/diagnostics/bin/diagd >/dev/console 2>&1 : httpdlite:23456789:once:/usr/IMNSearch/httpdlite/httpdlite -r /etc/IMNSearch/httpdlite/httpdlite.conf & >/dev/console 2>&1 ha_star:h2:once:/etc/rc.ha_star >/dev/console 2>&1 cons:0123456789:respawn:/usr/sbin/getty /dev/console hntr2mon:2:once:/opt/hitachi/HNTRLib2/etc/D002start dlmmgr:2:once:startsrc -s DLMManager ntbl_reset:2:once:/usr/bin/ntbl_reset_datafiles rcml:2:once:/usr/sni/aix52/rc.ml > /dev/console 2>&1 perfstat:2:once:/usr/lib/perf/libperfstat_updt_dictionary >/dev/console 2>&1 ctrmc:2:once:/usr/bin/startsrc -s ctrmc > /dev/console 2>&1 tty1:2:off:/usr/sbin/getty /dev/tty1 tty0:2:off:/usr/sbin/getty /dev/tty0 : i4ls:2:wait:/etc/i4ls.rc > /dev/null 2>&1 # Start i4ls mF:2345:wait:sh /etc/mflmrcscript > /dev/null 2>&1 i4ls:2:wait:/etc/i4ls.rc > /dev/null 2>&1 # Start i4ls documentum:2:once:/etc/rc.documentum start >/dev/null 2>&1 Note 7: ------IBM C/C++ Compilers This describes the IBM implementation of the C and C++ compilers. Contents Invoking the Compiler
C Compiler Modes C++ Compiler Modes Source Files and Preprocessing Default Datatype Sizes Distributed-memory parallelism Shared-memory parallelism 64-bit addressing Optimization Related Information Memory Management Porting programs from the Crays to the SP Mixing C and Fortran -------------------------------------------------------------------------------Invoking the Compiler The IBM C compiler is described in the IBM C for AIX User's Manual and the IBM C++ compiler is described in the IBM Visual Age C++ Batch Compiler manual. Both of these manuals are on line. As with the IBM XL Fortran compiler, there are several different commands that invoke the C or C++ compilers, each of which is really an alias for the main C or C++ command packaged with a set of commonly used options. The most basic C compile is of the form % xlc source.c This will produce an executable named a.out. The other C Compiler modes are described below in the section C Compiler Modes. The most basic C++ compile is of the form %
xlC source.C
This will produce an executable named a.out. The other C++ Compiler modes are described below in the section C++ Compiler Modes. Note: There is no on-line man page for the C++ compiler. "man xlC" brings up the man page for the C compiler. For complete documentation of C++ specific options and conventions see the on-line C++ manual. The commands xlc, mpcc, and mpCC all have on-line man pages. C Compiler Modes There are four basic compiler invocations for C compiles: xlc, cc, c89, and mpcc. All but c89 have one or more subinvocations with different defaults. xlc xlc invokes the compiler for C with an ansi language level. This is the basic invocation that IBM recommends. These are the two most useful subinvocations of xlc:
xlc_r This invokes the thread safe version of xlc. It should be used when any kind of multi-threaded code is being built. This is equivalent to invoking the compiler as xlc -D_THREAD_SAFE and the loader as xlc -L/usr/lib/threads -Lusr/lib/dce -lc_r -lpthreads. xlc128 This is equivalent to invoking the compiler as xlc -qldbl128 -lC128. It increases the size of long double data types from 64 to 128 bits. cc cc invokes the compiler for C with an extended language level. This is for source files with legacy C code that IBM refers to as "RT compiler extensions". This include older pre-ansi features such as those in the Kernighan and Ritchie's "The C Programming Language". The two most useful subinvocations are cc_r which is the cc equivalent of xlc_r and cc128 which is the cc equivalent of xlc128. c89 c89 should be used when strict conformance to the C ANSI ANSI standard (ISO/IEC 9899:1990) is desired. There are no subinvocations associated with this compiler invocation. mpcc mpcc is a shell script that compiles C programs in the Partition Manager, Message Passing Interface (MPI), and/or Message passed by mpcc to the xlc command, so any of the xlc options can be used with mpcc a program the Partition Manager and message passing interface are automatically executable that dynamically binds with the message passing libraries.
with the cc compiler while linking Passing Library (MPL). Flags are as well. When mpcc is used to link linked in. The script creates an
There is one subinvocation with mpcc, mpcc_r which is the mpcc equivalent of cc_r. This invocation also links in the Partition Manager, the threaded implementation of Message Passing Interface (MPI), and Low-level Applications Programming Interface (LAPI). ANSI compliance can be achieved by compiling with the option -qlanglvl=ansi. Compiler summary This table summarizes the features of several different C compiler invocations: Compiler Name Functionality C defaults DM Parallel SM Parallel xlc ansi No No xlc_r ansi No Yes xlc128 ansi No No cc extended No No cc_r extended No Yes
cc128 extended No No c89 strict No No mpcc extended* Yes No mpcc_r extended* Yes Yes * ANSI compliance can be achieved by compiling with the option -qlanglvl=ansi. In the table above, C defaults indicates the default C standards behavior of the compiler. DM Parallel refers to distributed-memory parallelism through the MPI library. SM Parallel refers to shared-memory parallelism, available through OpenMP, IBM tasking directives, automatic parallelization by the compiler, or the pthreads API. C++ Compiler Modes There are two basic compiler invocations for C++ compiles: xlC and mpCC. If a program consists of source code modules in different program languages, it must be linked with a form of one of these invocations in order to use the correct C++ run time libraries. All of the C++ invocations will compile source files with a .c suffix as ansi C source files unless the -+ option to the C++ compiler is specified. Any of the C compiler invocations will also compile a file with the appropriate suffix as a C++ file. xlC Among the subinvocations of xlC are: xlC_r: the xlC equivalent of xlc_r xlC128: the xlC equivalent of xlc128 xlC128_r: this combines the features of the xlC_r and xlC128 subinvocations. mpCC mpCC is a shell script that compiles C++ programs with the xlC compiler while linking in the Partition Manager, Message Passing Interface (MPI), and/or Message Passing Library (MPL). Flags are passed by mpCC to the xlC command, so any of the xlC options can be used on the mpCC shell script. When mpCC is used to link a program the Partition Manager and message passing interface are automatically linked in. The script creates an executable that dynamically binds with the message passing libraries. By default, the mpCC compiler uses the regular C program MPI bindings. In order to use the full C++ MPI bindings use the compiler flag -cpp There is one mpCC subinvocation, mpCC_r. This invokes a shell script that compiles C++ programs while linking in the Partition Manager, the threaded implementation of Message Passing Interface (MPI), and Low-level Applications Programming Interface (LAPI). Source Files and Preprocessing All of the C and C++ compiler invocations process assembler source files and object files as well as preprocessing and compiling C and C++ source files. Unless the -c option is specified, they also
call the linkage editor to produce a single executable object file. All invocations of the C or C++ compilers follow these suffix conventions for input files: .C, .cc, .cpp, or .cxx - C++ source file. .c - C source file .i - preprocessed C source file .so - shared object file .o - object file for ld command .s - assembler source file By default, the preprocessor is run on both C and C++ source files. Default Datatype Sizes These are the default sizes of the standard C/C++ datatypes. Type Length (bytes) bool1 1 char 1 wchar_t1 2 short 2 int 4 long 4 /8 2 float 4 double 8 long double 8 /163 1C++ only. 264 bit mode -q64. 3 128 suffix compiling mode. Distributed-Memory Parallelism Invoking any of the compilers starting with "mp" enables the program for running across several nodes. Of course, you are responsible for using a library such as MPI to arrange communication and coordination in such a program. Any of the mp compilers sets the include path and library paths to pick up the MPI library. To use the MPI with C++ or to use the MPI I/O subroutines, the thread-safe version of the compiler must be used. % mpcc_r a.c % mpCC_r -cpp a.C The example, hello.c, demonstrates the use of MPI from a C code. The example, hello.C, demonstrates the use of MPI from a C++ code. Shared-Memory Parallelism The IBM C and C++ compilers support a variety of shared-memory parallelism. OpenMP OpenMP directives are fully supported by the IBM C and C++ compilers when one of the invocations with _r suffix is used. See Using OpenMP on seaborg for details. Automatic Parallelization
The IBM C compiler will attempt to automatically parallelize simple loop constructs. Use the option "-qsmp" with one of the _r invocations: % xlc_r -qsmp a.c 64 Bit Addressing Both the IBM C and C++ compilers support 64 bit addressing through the -q64 option. The default mode can be set through the environment variable OBJECT_MODE on Bassi, OBJECT_MODE=64 has been set to make 64-bit mode the default. On Seaborg the default is 32-bit addressing mode. In 64-bit mode all pointers are 64 bits in length and length of long datatypes increase from 32 to 64 bits. It does not change the default size of any other datatype. The following points should be kept in mind if 64-bit is used: If you have some object files that were compiled in 32-bit mode and others compiled in 64-bit mode the objects will not bind. You must recompile to ensure that all objects are in the same mode. Your link options must reflect the type of objects you are linking. If you compiled 64-bit objects, you must also link these objects with the -q64 option. Optimization The default for all IBM compilers is for there to be no optimization. The NERSC/IBM recommended optimization options for both C and C++ compiles are -O3 -qstrict -qarch=auto -qtune=auto.
55.2 Installing Tuxedo 8.1 or 9: ================================ Before installing make sure you understand the BEA and Tuxedo home dirs, and give appropriate ownership/permissions to a dedicated BEA account. GUI mode or console mode are available. GUI: ==== Go to the directory where you downloaded the installer and invoke the installation procedure by entering the following command: prompt> sh filename.bin where filename is the name of the BEA Tuxedo installer file. Select the install set that you want installed on your system. The following seven choices are available:
Full Install (the default)�all Tuxedo server and client software components Server Install�Tuxedo server software components only Full Client Install�Tuxedo client software components only Jolt Client Install�Jolt client software components only ATMI (/WS) Client Install�Tuxedo ATMI client software components only CORBA Client Install�Tuxedo CORBA client software components only Custom Install�select specific Tuxedo server and client software components. The following table entry provides a summary of options for the Custom Install. For a detailed list of software components for each install set, see Install Sets. Select (add) or deselect (clear) one or more software components from the selected install set, or choose one of the other five install sets or Custom Set from the drop-down list menu and customize its software components. For a description of the JRLY component, see Jolt Internet Relay. Observe the following software component mappings: Server�contains ATMI server software; CORBA C++ server software; BEA Jolt server software; BEA SNMP Agent software, and BEA Tuxedo Administration Console software ATMI Client�contains BEA ATMI Workstation (/WS) client software CORBA Client�contains BEA CORBA C++ client software (C++ client ORB) including environmental objects Jolt JRLY�contains BEA Jolt Relay software Jolt Client�contains BEA Jolt client software After selecting or deselecting one or more software components from the selected install set, click Next to continue with the installation. The appropriate encryption software for LLE and/or SSL is automatically included. Specify the BEA Home directory that will serve as the central support directory for all BEA products installed on the target system. If you already have a BEA Home directory on your system, you can select that directory (recommended) or create a new BEA Home directory. If you choose to create a new directory, the BEA Tuxedo installer program automatically creates the directory for you. For details about the BEA Home directory, see BEA Home Directory. Choose a BEA Home directory and then click Next to continue with the installation. Console mode: ============= Console-mode installation is the text-based method of executing the BEA Installation program. It can be run only on UNIX systems and is intended for UNIX systems with nongraphics consoles. Console-mode installation offers the same capabilities as graphics-based installation
Go to the directory where you downloaded the installer and invoke the installation procedure by entering the following command: prompt> sh filename.bin -i console where filename is the name of the BEA Tuxedo installer file. The tekstbased installation resembles from then on, the GUI installation. Tuxedo 8.1 binaries and what can you do with them: ================================================== /spl/SPLDEV1/product/tuxedo8.1/bin:>ls AUTHSVR TMNTSFWD_T tpaclcvt AUTHSVR.pbk TMQFORWARD tpacldel BBL TMQUEUE tpaclmod BBL.pbk TMS tpaddusr BRIDGE TMS.pbk tpdelusr BRIDGE.pbk TMSYSEVT tpgrpadd BSBRIDGE TMSYSEVT.pbk tpgrpdel BSBRIDGE.pbk TMS_D tpgrpmod CBLDCLNT TMS_QM tpmigldap CBLDSRVR TMS_QM.pbk tpmodusr CBLVIEWC TMS_SQL tpusradd CBLVIEWC32 TMS_SQL.pbk tpusrdel DBBL TMUSREVT tpusrmod DMADM TMUSREVT.pbk tux_snmpd DMADM.pbk WSH tux_snmpd.pbk GWADM WSH.pbk tuxadm GWTDOMAIN WSL tuxadm.pbk GWTDOMAIN.pbk bldc_dce tuxwsvr GWTOPEND blds_dce txrpt ISH build_dgw ud ISH.pbk buildclient ud32 ISL buildish uuidgen
dmadmin
snmp_integrator.pbk
dmadmin.pbk
snmp_version
dmloadcf
snmp_version.pbk
dmloadcf.pbk
snmpget
dmunloadcf
snmpget.pbk
dmunloadcf.pbk
snmpgetnext
epifreg
snmpgetnext.pbk
epifregedt
snmptest
epifunreg
snmptest.pbk
esqlc
snmptrap
evt2trapd
snmptrap.pbk
evt2trapd.pbk
snmptrapd
genicf
snmptrapd.pbk
idl
snmpwalk
idl2ir
snmpwalk.pbk
idltojava
sql
idltojava.pbk
stop_agent
ir2idl
stop_agent.pbk
irdel
tidl
jrly
tlisten
jrly.pbk
tlisten.pbk
mkfldhdr
tlistpwd
ISL.pbk viewc JRAD viewc.pbk JRAD.pbk viewc32 JREPSVR viewc32.pbk JSH viewdis JSH.pbk viewdis32 JSL wgated LAUTHSVR wgated.pbk TMFFNAME wlisten TMFFNAME.pbk wlisten.pbk TMIFRSVR wtmconfig TMNTS wud TMNTSFWD_P wud32
buildobjclient
mkfldhdr32
tmadmin
buildobjserver
ntsadmin
tmadmin.pbk
buildserver
qmadmin
tmboot
buildtms
reinit_agent
tmboot.pbk
buildwsh
reinit_agent.pbk
tmconfig
cleanupsrv
restartsrv
tmipcrm
cleanupsrv.pbk
restartsrv.pbk
tmipcrm.pbk
cns
rex
tmloadcf
cnsbind
rmskill
tmloadcf.pbk
cnsls
sbbl
tmshutdown
cnsunbind
show_agent
tmshutdown.pbk
cobcc
show_agent.pbk
tmunloadcf
cobcc.pbk
snmp_integrator
tpacladd
txrpt: -----Name txrpt-BEA TUXEDO system server/service report program Synopsis txrpt [-t] [-n names] [-d mm/dd] [-s time] [-e time] Description txrpt analyzes the standard error output of a BEA TUXEDO system server to provide a summary of service processing time within the server. The report shows the number of times dispatched and average elapsed time in seconds of each service in the period covered. txrpt takes its input from the standard input or from a standard error file redirected as input. Standard error files are created by servers invoked with the -r option from the servopts(5) selection; the file can be named by specifying it with the -e servopts option. Multiple files can be concatenated into a single input stream for txrpt. Options to txrpt have the following meaning: -t order the output report by total time usage of the services, with those consuming the most total time printed first. If not specified, the report is ordered by total number of invocations of a service.
-n names restrict the report to those services specified by names. names is a commaseparated list of service names. -d mm/dd limit the report to service requests on the month, mm, and day, dd, specified. The default is the current day. -s time restrict the report to invocations starting after the time given by the time argument. The format for time is hr[:min[:sec]]. -e time restrict the report to format for time is the same as the -s flag. The report produced by records from more than the -d option controls
invocations that finished before the specified time. The txrpt covers only a single day. If the input file contains one day, the day reported on.
tuxadm: ------Name tuxadm�BEA Tuxedo Administration Console CGI gateway. Synopsis http://cgi-bin/tuxadm[TUXDIR=tuxedo_directory | INIFILE=initialization_file][other_parameters] Description tuxadm is a common gateway interface (CGI) process used to initialize the Administration Console from a browser. As shown in the "Synopsis" section, this program can be used only as a location, or URL from a Web browser; normally it is not executed from a standard command line prompt. Like other CGI programs, tuxadm uses the QUERY_STRING environment variable to parse its argument list. tuxadm parses its arguments and finds a Administration Console initialization file. If the TUXDIR parameter is present, the initialization file is taken to be $TUXDIR/udataobj/webgui/webgui.ini by default. If the INIFILE option is present, then the value of that parameter is taken to be the full path to the initialization file. Other parameters may also be present. Any additional parameters can be used to override values in the initialization file. See the wlisten reference page for a complete list of initialization file parameters. The ENCRYPTBITS parameter may not be overridden by the tuxadm process unless the override is consistent with the values allowed in the actual initialization file.
The normal action of tuxadm is to generate, to its standard output, HTML commands that build a Web page that launches the Administration Console applet. The general format of the Web page is controlled by the TEMPLATE parameter of the initialization file, which contains arbitrary HTML commands, with the special string %APPLET% on a line by itself in the place where the Administration Console applet should appear. Through the use of other parameters from the initialization file (such as CODEBASE, WIDTH, HEIGHT, and so on) a correct APPLET tag is generated that contains all the parameters necessary to create an instance of the Administration Console. Errors tuxadm generates HTML code that contains an error message if a failure occurs. Because of the way CGI programs operate, there is no reason to return an error code of any kind from tuxadm. See Also tuxwsvr(1), wlisten(1) MSTMACH: -------Is the machine name, and usually corresponds to the LMID, the logical machine ID. There should be an entry of the hostname in /etc/hosts. tmboot: ------tmboot(1) Name tmboot�Brings up a BEA Tuxedo configuration. Synopsis tmboot [-l lmid] [-g grpname] [-i srvid] [-s aout] [-o sequence] [-S] [-A] [-b] [-B lmid] [-T grpname] [-e command] [-w] [-y] [-g] [-n] [-c] [-M] [-d1] Description tmboot brings up a BEA Tuxedo application in whole or in part, depending on the options specified. tmboot can be invoked only by the administrator of the bulletin board (as indicated by the UID parameter in the configuration file) or by root. The tmboot command can be invoked only on the machine identified as MASTER in the RESOURCES section of the configuration file, or the backup acting as the MASTER, that is, with the DBBL already running (via the master command in tmadmin(1)). Except, if the -b option is used; in that case, the system can be booted
from the backup machine without it having been designated as the MASTER. With no options, tmboot executes all administrative processes and all servers listed in the SERVERS section of the configuration file named by the TUXCONFIG and TUXOFFSET environment variables. If the MODEL is MP, a DBBL administrative server is started on the machine indicated by the MASTER parameter in the RESOURCES section. An administrative server (BBL) is started on every machine listed in the MACHINES section. For each group in the GROUPS section, TMS servers are started based on the TMSNAME and TMSCOUNT parameters for each entry. All administrative servers are started followed by servers in the SERVERS sections. Any TMS or gateway servers for a group are booted before the first application server in the group is booted. The TUXCONFIG file is propagated to remote machines as necessary. tmboot normally waits for a booted process to complete its initialization (that is, tpsvrinit()) before booting the next process. Booting a gateway server implies that the gateway advertises its administrative service, and also advertises the application services representing the foreign services based on the CLOPT parameter for the gateway. If the instantiation has the concept of foreign servers, these servers are booted by the gateway at this time. Booting an LMID is equivalent to booting all groups on that LMID. Application servers are booted in the order specified by the SEQUENCE parameter, or in the order of server entries in the configuration file (see the description in UBBCONFIG(5)). If two or more servers in the SERVERS section of the configuration file have the same SEQUENCE parameter, then tmboot may boot these servers in parallel and will not continue until they all complete initialization. Each entry in the SERVERS section can have a MIN and MAX parameter. tmboot boots MIN application servers (the default is 1 if MIN is not specified for the server entry) unless the -i option is specified; using the -i option causes individual servers to be booted up to MAX occurrences. If a server cannot be started, a diagnostic is written on the central event log (and to the standard output, unless -q is specified), and tmboot continues�except that if the failing process is a BBL, servers that depend on that BBL are silently ignored. If the failing process is a DBBL, tmboot ignores the rest of the configuration file. If a server is configured with an alternate LMID and fails to start on its primary machine, tmboot automatically attempts to start the server on the alternate machine and, if successful, sends a message to the DBBL to update the server group section of TUXCONFIG. For servers in the SERVERS section, only CLOPT, SEQUENCE, SRVGRP, and SRVID are used by tmboot. Collectively, these are known as the server's boot parameters. Once the server has been booted,
it reads the configuration file to find its run-time parameters. (See UBBCONFIG(5) for a description of all parameters.) All administrative and application servers are booted with APPDIR as their current working directory. The value of APPDIR is specified in the configuration file in the MACHINES section for the machine on which the server is being booted. The search path for the server executables is APPDIR, followed by TUXDIR/bin, followed by /bin and /usr/bin, followed by any PATH specified in the ENVFILE for the MACHINE. The search path is used only if an absolute pathname is not specified for the server. Values placed in the server's ENVFILE are not used for the search path. When a server is booted, the variables TUXDIR, TUXCONFIG, TUXOFFSET, and APPDIR, with values specified in the configuration file for that machine, are placed in the environment. The environment variable LD_LIBRARY_PATH is also placed in the environment of all servers. Its value defaults to $APPDIR:$TUXDIR/lib:/lib:/usr/lib:lib> where is the value of the first LD_LIBRARY_PATH= line appearing in the machine ENVFILE. See UBBCONFIG(5) for a description of the syntax and use of the ENVFILE. Some Unix systems require different environment variables. For HP-UX systems, use the SHLIB_PATH environment variable. FOR AIX systems, use the LIBPATH environment variable. The ULOGPFX for the server is also set up at boot time based on the parameter for the machine in the configuration file. If not specified, it defaults to $APPDIR/ULOG. All of these operations are performed before the application initialization function, tpsvrinit(), is called. Many of the command line options of tmboot serve to limit the way in which the system is booted and can be used to boot a partial system. The following options are supported. -l lmid For each group whose associated LMID parameter is lmid, all TMS and gateway servers associated with the group are booted and all servers in the SERVERS section associated with those groups are executed. -g grpname All TMS and gateway servers for the group whose SRVGRP parameter is grpname are started, followed by all servers in the SERVERS section associated with that group. TMS servers are started based on the TMSNAME and TMSCOUNT parameters for the group entry.
-i srvid All servers in the SERVERS section whose SRVID parameter is srvid are executed. -s aout All servers in the SERVERS section with name aout are executed. This option can also be used to boot TMS and gateway servers; normally this option is used in this way in conjunction with the -g option. -o sequence All servers in the SERVERS section with SEQUENCE parameter sequence are executed. -S All servers in the SERVERS section are executed. -A All administrative servers for machines in the MACHINES section are executed. Use this option to guarantee that the DBBL and all BBL and BRIDGE processes are brought up in the correct order. (See also the description of the -M option.) -b Boot the system from the BACKUP machine (without making this machine the MASTER). -B lmid A BBL is started on a processor with logical name lmid. -M This option starts administrative servers on the master machine. If the MODEL is MP, a DBBL administrative server is started on the machine indicated by the MASTER parameter in the RESOURCES section. A BBL is started on the MASTER machine, and a BRIDGE is started if the LAN option and a NETWORK entry are specified in the configuration file. -d1 Causes command line options to be printed on the standard output. Useful when preparing to use sdb to debug application services. -T grpname All TMS servers for the group whose SRVGRP parameter is grpname are started (based on the TMSNAME and TMSCOUNT parameters associated with the group entry). This option is the same as booting based on the TMS server name (-s option) and the group name (-g).
-e command Causes command to be executed if any process fails to boot successfully. command can be any program, script, or sequence of commands understood by the command interpreter specified in the SHELL environment variable. This allows an opportunity to bail out of the boot procedure. If command contains white space, the entire string must be enclosed in quotes. This command is executed on the machine on which tmboot is being run, not on the machine on which the server is being booted. Note: If you choose to do redirection or piping on a Windows 2000 system, you must use one of the following methods: Do redirection or piping from within a command file or script. To do redirection from within the queue manager administration program, precede the command with cmd. For example: cmd /c ipconfig > out.txt If you choose to create a binary executable, you must allocate a console within the binary executable using the Windows AllocConsole() API function -w Informs tmboot to boot another server without waiting for servers to complete initialization. This option should be used with caution. BBLs depend on the presence of a valid DBBL; ordinary servers require a running BBL on the processor on which they are placed. These conditions cannot be guaranteed if servers are not started in a synchronized manner. This option overrides the waiting that is normally done when servers have sequence numbers. -y Assumes a yes answer to a prompt that asks if all administrative and server processes should be booted. (The prompt appears only when the command is entered with none of the limiting options.) -q Suppresses the printing of the execution sequence on the standard output. It implies -y. -n The execution sequence is printed, but not performed. -c Minimum IPC resources needed for this configuration are printed. When the -l, -g, -i, -o, and -s options are used in combination, only servers that
satisfy all qualifications specified are booted. The -l, -g, -s, and -T options cause TMS servers to be booted; the -l, -g, and -s options cause gateway servers to be booted; the -l, -g, -i, -o, -s, and -S options apply to application servers. Options that boot application servers fail if a BBL is not available on the machine.The -A, -M, and -B options apply only to administrative processes. The standard input, standard output, and standard error file descriptors are closed for all booted servers. Interoperability tmboot must run on the master node, which in an interoperating application must be the highest release available. tmboot detects and reports configuration file conditions that would lead to the booting of administrative servers such as Workstation listeners on sites that cannot support them. Portability tmboot is supported on any platform on which the BEA Tuxedo server environment is supported. Environment Variables During the installation process, an administrative password file is created. When necessary, the BEA Tuxedo system searches for this file in the following directories (in the order shown): APPDIR/.adm/tlisten.pw and TUXDIR/udataobj/tlisten.pw. To ensure that your password file will be found, make sure you have set the APPDIR and/or TUXDIR environment variables. Link-Level Encryption If the link-level encryption feature is in operation between tmboot and tlisten, link-level encryption will be negotiated and activated first to protect the process through which messages are authenticated. Diagnostics If TUXCONFIG is set to a non-existent file, two fatal error messages are displayed: error processing configuration file configuration file not found If tmboot fails to boot a server, it exits with exit code 1 and the user log should be examined for further details. Otherwise tmboot exits with exit code 0. If tmboot is run on an inactive non-master node, a fatal error message is displayed: tmboot cannot run on a non-master node.
If tmboot is run on an active node that is not the acting master node, the following fatal error message is displayed: tmboot cannot run on a non acting-master node in an active application. If the same IPCKEY is used in more than one TUXCONFIG file, tmboot fails with the following message: Configuration file parameter has been changed since last tmboot If there are multiple node names in the MACHINES section in a non-LAN configuration, the following fatal error message is displayed: Multiple nodes not allowed in MACHINES for non-LAN application. If tlisten is not running on the MASTER machine in a LAN application, a warning message is printed. In this case, tmadmin(1) cannot run in administrator mode on remote machines; it is limited to read-only operations. This also means that the backup site cannot reboot the master site after failure. Examples To start only those servers located on the machines logically named CS0 and CS1, enter the following command: tmboot -l CS0 -l CS1 To start only those servers named CREDEB that belong to the group called DBG1, enter the following command: tmboot -g DBG1 -s CREDEB1 To boot a BBL on the machine logically named PE8, as well as all those servers with a location specified as PE8, enter the following command. tmboot -B PE8 -l PE8 To view minimum IPC resources needed for the configuration, enter the following command. tmboot -c The minimum IPC requirements can be compared to the parameters set for your machine. See the system administration documentation for your machine for information about how to change these parameters. If the -y option is used, the display will differ slightly from the previous example. Notices The tmboot command ignores the hangup signal (SIGHUP). If a signal is detected during boot, the process continues. Minimum IPC resources displayed with the -c option apply only to the configuration described in the configuration file specified; IPC resources required for a resource manager or for other BEA Tuxedo configurations are not considered in the calculation.
See Also tmadmin(1), tmloadcf(1), tmshutdown(1), UBBCONFIG(5) Administering BEA Tuxedo Applications at Run Time
Notes in Dutch on Tuxedo: ========================= Note 1 CDX or ETM application (middleware component, based on Tuxedo): ---------------------------------------------------------------------Recompile van de tuxconfig.bin file, na changes in de ubb file. ETM op AIX wordt geinstalleerd in het directory "/prj/spl/", zoals bijvoorbeeld "/prj/spl/ivocf01" of bijvoorbeeld "/prj/spl/SPLS3". Het "gedrag" van Tuxedo wordt bijna geheel bepaald door de configuratie file "/prj/spl//etc/tuxconfig.bin". De source van tuxconfig.bin, is de ascii file "/prj/spl//etc/ubb". Dit houdt in, dat als men een wijziging pleegt in de ubb file (bijv. het aantal servers verhogen), dan moet er een nieuwe tuxconfig.bin file worden gegenereerd. Hiervoor heeft SPL in het directory "/prj/spl//bin" een shell script gemaakt, met de naam "gentuxedo.sh". Het script kan verschillende flags worden meegegeven. Zie opmerking 2 hieronder. 1. Logon als de ETM software owner (bijv. ccbsys of etmsys) 2. Check je environment (staan al je environment vars goed?) 3. Attach jezelf aan de juiste environment. Gebruikelijk is, dat er een "alias" bestaat met de naam die gelijk is aan de Instance Name. Je hoeft dan alleen maar de alias vanaf de promt in te voeren. Voorbeeld: Stel de instance naam is "IVOCF01". Direkt na het inloggen als de ETM owner (of via "su - ownerccount"), kun je vanaf de prompt de alias aanroepen met IVOCF01, en je wordt geattached aan de IVOCF01 instance. 4. Change directory naar "/prj/spl//bin" 5. Om nu, na een wijziging in de ubb file, de tuxconfig.bin file opnieuw te compileren, gebruik dan het commando ./gentuxedo.sh -m Gebruik "./gentuxedo.sh -u" om de ubb en de bin file vanaf de template te genereren.
Opmerkingen: 1. Hetzelfde kan bereikt worden met het tuxedo utility "tmloadcf" tmloadcf -y $SPLEBASE/etc/ubb 2. De flags die men aan gentuxedo.sh kan meegeven: #% #% #% #% #% #% #% #% #% #% #% #% option.
USAGE: USAGE: USAGE: USAGE: USAGE: USAGE: USAGE: USAGE: USAGE: USAGE: USAGE: USAGE:
gentuxedo.sh -h = HELP -r = Recreate the default tuxedo server This will recreate all of the default service lists ( see option -n ) as well as create UBB files -u = Create the UBB file from template only -m = use tmloadcf to recreate ubb binary from $SPLEBASE/etc/ubb Once modifications have been made to the $SPLEBASE/etc/ubb file it is necessary to compile those changes. use the -m option to do this. -s = Create the Servers This will create only the Servers as defined in the -n
Note 2: ------Connecten, of attachen, naar een AIX ETM instance Op een AIX lpar (logical partition, ofwel een virtual machine, ofwel een volledig zelfstandige AIX machine), draaien 1 of meer ETM instance(s). Een ETM instance, is middleware, bestaande uit tuxedo services, een Cobol Application server, en Cobol business objects. De ETM user (of software owner) kan zich �verbinden� met een dergelijke Instance, bijvoorbeeld om administratieve handelingen uit te voeren zoals het starten of stoppen van de Instance. Op je te verbinden (of attachen) naar een bepaalde ETM instance, kun je het �splenviron.sh� script gebruiken welke is gelegen in �/prj/spl//bin� directory. Mogelijk is het pad toch iets anders van vorm, zoals bijvoorbeeld �/prj/etm_1520/IVOOCF/bin� of zoiets dergelijks. Het belangrijkste is om te weten dat binnen de directorytree die bij een instance hoort, dat er een �bin� directory bestaat met een aantal .sh shell scripts, waaronder dus ook het �splenviron.sh� script. Het .profile van de etm user, dient echter zodanig te zijn ingesteld, dat reeds een aantal environment variabelen �goed� zijn neergezet, en correct verwijzen naar de juiste Cobol, Tuxedo en DB2 locaties. Er vanuit gaande dat het .profile goed is, kan de etm user zich verbinden met een Instance via: splenviron.sh �e
Voorbeeld: Stel op een AIX machine (of lpar) bestaat de ETM Instance �SPLDEV1� welke geinstalleerd is in het directory �/spl/SPLDEV1�. Men kan zich dan attachen via het command: /spl/SPLDEV1/bin $ ./splenviron.sh -e SPLDEV1 Version ................ (SPLVERSION) : V1.5.20.0 Database Type ............... (SPLDB) : oracle ORACLE_SID ............. (ORACLE_SID) : SPLDEV1 NLS_LANG ............... (NLS_LANG) : AMERICAN_AMERICA.WE8ISO8859P15 App Dir - Logs ............. (SPLAPP) : /spl/splapp/SPLDEV1 Environment Name ....... (SPLENVIRON) : SPLDEV1 Environment Code Directory (SPLEBASE) : /spl/SPLDEV1 Build Directory .......... (SPLBUILD) : /spl/SPLDEV1/cobol/build Runtime Directory .......... (SPLRUN) : /spl/SPLDEV1/runtime/oracle Cobol Copy Path ......... (SPLCOBCPY) : /spl/SPLDEV1/cobol/source/cm:/spl/SPLDEV1/tuxedo/templates: /spl/SPLDEV1/tuxedo/genSources:/spl/SPLDEV 1/cobol/source: /spl/SPLDEV1/product/tuxedo8.1/cobinclude De belangrijkste functie van �splenviron.sh� is hier dan, dat een aantal variablen correct worden neergezet zodat alle kenmerken van deze applicatie (zoals build directory e.d.) goed staan. Behalve het gebruik van splenviron.sh, is het heel goed mogelijk dat in het .profile van de etm user, reeds een aantal �aliases� zijn gedefinieerd. Als er inderdaad aliases zijn gedefinieerd, is het attachen naar een Instance heel makkelijk. Men dient dan alleen nog maar de alias vanaf de unix prompt in te voeren. Voorbeeld: Stel dat in het .profile van de ETM user het volgende is opgenomen: alias SPLDEV1='/spl/SPLDEV1/bin/splenviron.sh -e SPLDEV1' Dan kan de ETM user zich direct aan SPLDEV1 attachen via het command: SPLDEV1 Dus om een aantal ETM instances te stoppen en weer te starten (bijv. in een backupscript): #STOPPEN ETM instances: su - cissys -c '/spl/SPLDEV1/bin/splenviron.sh -e SPLDEV1 -c "spl.sh -t stop"' sleep 2 su - cissys -c '/spl/SPLDEV2/bin/splenviron.sh -e SPLDEV2 -c "spl.sh -t stop"' sleep 2 su - cissys -c '/spl/SPLCONF/bin/splenviron.sh -e SPLCONF -c "spl.sh -t stop"' sleep 2 #STARTEN ETM instances:
su - cissys -c '/spl/SPLDEV1/bin/splenviron.sh -e SPLDEV1 -c "spl.sh -t start"' sleep 2 su - cissys -c '/spl/SPLDEV2/bin/splenviron.sh -e SPLDEV2 -c "spl.sh -t start"' sleep 2 su - cissys -c '/spl/SPLCONF/bin/splenviron.sh -e SPLCONF -c "spl.sh -t start"' sleep 2 Note 3: ------Hoe te (her-)compileren van de ETM Cobol objecten Je kunt hiervoor het "co.sh" of het customized "co_BD.sh" script gebruiken. Het co_BD.sh script, is een copy van het co.sh script in het /prj/spl//bin directory, en dit script prompt de gebruiker voor de DB2USER / DB2PASSWORD credentials. Syntax: co_BD.sh -p .cbl Hoe te gebruiken: 1. Logon als de juiste etmuser op AIX 2. Run nu de alias van de juiste instance om de juiste environment in te stellen, en om je aan de juiste-ETM instance te verbinden. 3. Zorg ervoor dat je de juiste DB2User and DB2Password kent. Nu kun je cobol objecten compileren, als in het volgende voorbeeld: Voorbeeld op "S3" partition op AIX: Na AIX logon als �ccbsys� (de etm instance owner op de S3 partition): Type SPLS3 or SPLUI to set the environment /home/ccbsys >SPLS3 060918.13:37:40 DB2DIR Environment set to /prj/db2/admin/iinvu02/sqllib/ Version ................ (SPLVERSION) : V1.5.15.0 Database Type ............... (SPLDB) : db2 App Dir - Logs ............. (SPLAPP) : /prj/spl/splapp/SPLS3 Environment Name ....... (SPLENVIRON) : SPLS3 Environment Code Directory (SPLEBASE) : /prj/spl/SPLS3 Build Directory .......... (SPLBUILD) : /prj/spl/SPLS3/cobol/build Runtime Directory .......... (SPLRUN) : /prj/spl/SPLS3/runtime/db2 Cobol Copy Path ......... (SPLCOBCPY) : /prj/spl/SPLS3/cobol/source/cm:/prj/spl/SPLS3/tuxedo/templates:/prj/spl/SPLS3/tuxe do/genSources:/prj/spl/SPLS3/cobol/source:/prj/spl/SPLS3/product/tuxedo8.1/cobincl ude /prj/spl/SPLS3 >cd /prj/spl/SPLS3/cobol/source/cm /prj/spl/SPLS3/cobol/source/cm >co_BD.sh -p CMPCSU2B.cbl 060918.13:37:57 co_BD.sh : Compile Started Mon Sep 18 13:37:57 CDT 2006 060918.13:37:57 Build Directory = /prj/spl/SPLS3/cobol/build
060918.13:37:57 060918.13:37:57 060918.13:37:57 060918.13:37:57 060918.13:37:57
Compiling for db2 database Compilation requested by ccbsys for version V1.5.15.0 Environment SPLS3 Using cobol directory /opt/microfocus/cobol DB2DIR Environment set to /prj/db2/admin/iinvu02/sqllib/
Please, type DBUSER userid to connect to database : Please, type in a password of c userid to connect to database : 060918.13:38:27 DB2 Compile : Local DB ALIAS = IVOOIS01 060918.13:38:27 DB2 Compile : collection = IVOOIS 060918.13:38:28 060918.13:38:29 060918.13:38:29 060918.13:38:30 060918.13:38:30
Compiling one object Program : CMPCSU2B ; Program : CMPCSU2B ; Program : CMPCSU2B ; FINISHED COMPILATION
only - CMPCSU2B.cbl Expand Return Code.. : 0 Prepare Return Code. : 0 Compile Return Code. : 0
Note 4: ------Hoe test je een DB2 connectie vanaf een AIX partition. Indien op een AIX partition, �DB2 connect ESE� correct geinstalleerd is, wil je misschien de verbinding vanaf AIX, naar DB2 op Z testen. Dat kan zoals in het volgende voorbeeld: 1. 2.
login als de juiste ETM instance owner (zoals bijv. iinvu02) type db2
De DB2 client utility wordt gestart en de bijbehorende prompt verschijnt: db2 => Voer nu in: db2=> Connect to user Vervolgens wordt om het password gevraagd, en hierbij is dan ook getest of de verbinding werkt. Voorbeeld: db2=> connect to IVOOCF01 user $SCCB60 using sa876dfy Als extra test, kun je ook proberen om de huidige datum uit een DB2 dummy table op te vragen, via het commando: db2=> select current date from sysibm.sysdummy1 Opmerking: De ETM instance owner dient wel in zijn .profile een aantal DB2 environment variables te hebben staan, zodat DB2 correct werkt, zoals: export DB2_HOME=/prj/db2/admin/ . $DB2_HOME/sqllib/db2profile
Note 5: ------Environment variabelen voor de ETM Instance owner op UNIX De ETM software owner, of ook wel de ETM Instance owner, heeft op unix / AIX, een aantal noodzakelijke environment variabelen nodig in het .profile bestand. Stel dat we als voorbeeld nemen, de Instance SPLDEV1 die geinstalleerd is in �/spl/SPLDEV1� In dat geval heeft de Instance owner zeker de volgende variabelen nodig. Je kunt ze aanpassen naar de environment die voor jou speelt, en direkt in het .profile file kopieren. 1. Algemene vars die verwijzen naar Support software als Java, Perl, DB2 connect e.d. export COBDIR=/opt/SPLcobAS40 # of hogere versie export COBMODE=64 export JAVA_HOME=/usr/java131 # of hogere versie export LC_MESSAGES=C export LANG=C LD_LIBRARY_PATH=/spl/V1515_SFix2_BASE_SUN_DB2/runtime/db2:/spl/V1515_SFix2_BASE_SU N_DB2/product/tuxedo8.1/lib:/opt/SPLcobAS40/lib:/usr/local/lib:/opt/IBMdb2/db282/s qllib/lib:: 3.
Vars mbt �deze� Instance
SPLAPP=/spl/splapp/V1515_SFix2_BASE_SUN_DB2 SPLBCKLOGDIR=/tmp SPLBUILD=/spl/V1515_SFix2_BASE_SUN_DB2/cobol/build SPLCOBCPY=/spl/V1515_SFix2_BASE_SUN_DB2/cobol/source/cm:/spl/V1515_SFix2_BASE_SUN_ DB2/tuxedo/templates:/spl/V1515_SFix2_BASE_SUN_DB2/tuxedo/genSources:/spl/V1515_SF ix2_BASE_SUN_DB2/cobol/source:/spl/V1515_SFix2_BASE_SUN_DB2/product/tuxedo8.1/cobi nclude SPLCOMMAND='ksh -o vi' SPLCOMP=microfocus SPLDB=db2 SPLEBASE=/spl/V1515_SFix2_BASE_SUN_DB2 SPLENVIRON=V1515_SFix2_BASE_SUN_DB2 SPLFUNCGETOP='' SPLGROUP=cisusr SPLHOST=sf-sunapp-22 SPLLOCALLOGS=/spl/vInd/local/logs SPLLOGS=/spl/V1515_SFix2_BASE_SUN_DB2/logs SPLQUITE=N SPLRUN=/spl/V1515_SFix2_BASE_SUN_DB2/runtime/db2 SPLSOURCE=/spl/V1515_SFix2_BASE_SUN_DB2/cobol/source SPLSUBSHELL=ksh SPLSYSTEMLOGS=/spl/V1515_SFix2_BASE_SUN_DB2/logs/system SPLUSER=cissys SPLVERS=1 SPLVERSION=V1.5.15.1 SPLWEB=/spl/V1515_SFix2_BASE_SUN_DB2/cisdomain/applications T=/spl/V135_MASTERTEMPLATE_UNIX TERM=ansi
THREADS_FLAG=native TUXCONFIG=/spl/V1515_SFix2_BASE_SUN_DB2/etc/tuxconfig.bin TUXDIR=/spl/V1515_SFix2_BASE_SUN_DB2/product/tuxedo8.1 ULOGPFX=/spl/V1515_SFix2_BASE_SUN_DB2/logs/system/ULOG
55.3 Installing Micro focus: ============================ 55.4 Installing Java or JRE: ============================ What is it?: ------------ Java Compiler (javac): language into bytecodes.
Compiles programs written in the Java programming
- Java Interpreter (java): Executes Java bytecodes. programs written in the Java programming language.
In other words, it runs
- The Java 2 Runtime Environment is intended for software developers and vendors to redistribute with their applications. The Java(TM) 2 Runtime Environment contains the Java virtual machine, runtime class libraries, and Java application launcher that are necessary to run programs written in the Java progamming language. It is not a development environment and does not contain development tools such as compilers or debuggers. For development tools, see the Java 2 SDK, Standard Edition. - SDK, JDK Java 2 Platform, Standard Edition (J2SE) provides a complete environment for applications development on desktops and servers and for deployment in embedded environments. It also serves as the foundation for the Java 2 Platform, Enterprise Edition (J2EE) and Java Web Services. - The PATH statement enables a system to find the executables (javac, java, javadoc, etc.) from any current directory. - The CLASSPATH tells the Java virtual machine and other applications (which are located in the "jdk_\bin" directory) where to find the class libraries, such as classes.zip file (which is in the lib directory). The LIBPATH environment variable tells AIX applications, such as the JVM where to find shared libraries. This is equivalent to the use of LD_LIBRARY_PATH in other Unix-based systems. On AIX, LIBPATH must be set instead of LD_LIBRARY_PATH. On HP UX, SHLIB_PATH must be set instead of LD_LIBRARY_PATH. On Windows NT, no variable for shared libraries is required.
For AIX, a number of Java SDK's and JRE's are available, e.g. December 2004 - SDK 1.3.1 32-bit PTF (APAR IY65310) released and JRE 1.3.1 32-bit refreshed, both using ca131-20041210 build (SR8). December 2004 - SDK 1.3.1 64-bit PTF (APAR IY65311) released and JRE 1.3.1 64-bit refreshed, both using caix64131-20041210 build (SR8).
How to install?: ---------------- Question: Can all these java releases co-exist on a machine? In which directories are these releases installed? Answer: Yes, releases can co-exist. Java 1.1.8 installs in /usr/jdk_base Java 1.2.2 installs in /usr/java_dev2 Java 1.3.0 installs in /usr/java130 Java 1.3.1 64-bit install in /usr/java13_64 Java 1.3.1 installs in /usr/java131 Java 1.4 64-bit install in /usr/java14_64 Java 1.4 installs in /usr/java14 - Question: What AIX levels are required for Java releases? Answer: To take advantage of latest AIX fixes it is recommended/required that latest AIX Recommended Maintenance Level be used. The following is the minimum AIX level required at the time when a Java release was first released: Java 1.1.8 requires AIX 4.2.1 Java 1.2.2 requires AIX 4.3.3 PLUS fixes Java 1.3.0 requires AIX 4.3.3.10 PLUS fixes Java 1.3.1 64-bit requires AIX 5.1.0.10 Java 1.3.1 requires AIX 4.3.3.75 Java 1.4 64-bit requires at least AIX 5.1.0.75 or AIX 5.2.0.10 Java 1.4 requires at least AIX 5.1.0.75 or AIX 5.2.0.10 Question: What AIX levels are required for Java releases? Answer: To take advantage of latest AIX fixes it is recommended/required that latest AIX Recommended Maintenance Level be used. The following is the minimum AIX level required at the time when a Java release was first released: Java 1.1.8 requires AIX 4.2.1 Java 1.2.2 requires AIX 4.3.3 PLUS fixes Java 1.3.0 requires AIX 4.3.3.10 PLUS fixes Java 1.3.1 64-bit requires AIX 5.1.0.10 Java 1.3.1 requires AIX 4.3.3.75 Java 1.4 requires at least AIX 5.1.0.75 or AIX 5.2.0.10 Java 5 requires at least AIX 5.2.0.75 or AIX 5.3.0.30
- Question: What paths do I need to set to use a specific Java release on my system? Answer: Java 1.1.8: PATH=/usr/jdk_base/bin:$PATH Java 1.2.2: PATH=/usr/java_dev2/jre/sh:/usr/java_dev2/sh:$PATH Java 1.3.0 PATH=/usr/java130/jre/bin:/usr/java130/bin:$PATH Java 1.3.1 64-bit: PATH=/usr/java13_64/jre/bin:/usr/java13_64/bin:$PATH Java 1.3.1 PATH=/usr/java131/jre/bin:/usr/java131/bin:$PATH Java 1.4 64-bit: PATH=/usr/java14_64/jre/bin:/usr/java14_64/bin:$PATH Java 1.4 PATH=/usr/java14/jre/bin:/usr/java14/bin:$PATH Install JDK or SDK: For base images after you downloaded either packagename.tar or the packagename.tar.gz file (the latter is recommended if you have gunzip utility available), you need to extract packagename from the downloaded file: # tar -xvf packagename.tar (example: tar -xvf Java14.sdk.tar), or # gunzip -c packagename.tar.gz | tar -xvf - (example: gunzip -c Java14.sdk.tar.gz | tar -xvf - ) For update images the .bff files are ready to be installed. Before installing, remove the old .toc file (if it exist) in the directory containing the .bff images. You can use the smitty command to install (both base and update images): Run "smitty install" Select "Install and Update Software" Select "Install Software" Specify directory containing the images Install JRE: The JRE installation is simple. After downloading the package, create a directory where you want to install, then unpackage the files where /java_home is a directory of your choice and jre## refers to the specific JRE image from the download page. mkdir -p /java_home cd /java_home tar -xvpf jre##.tar
or gunzip -c < jre##.tar.gz | tar -xvpf How to check your java version? ------------------------------/software/java:>java -version java version "1.3.1" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1) Classic VM (build 1.3.1, J2RE 1.3.1 IBM AIX build ca131ifx-20040721a SR7P (JIT enabled: jitc)) /software/java:>java -fullversion java full version "J2RE 1.3.1 IBM AIX build ca131ifx-20040721a SR7P" /root:>which java /usr/java131/bin/java To check the Java filesets on your system: # lslpp -l | grep Java /root:>lslpp -l | grep Java Java131.rte.bin 1.3.1.16 Java131.rte.lib 1.3.1.16
idebug.rte.hpj idebug.rte.jre idebug.rte.olt.Java
9.2.5.0 9.2.5.0 9.2.5.0
COMMITTED COMMITTED
COMMITTED COMMITTED COMMITTED
Java Runtime Environment Java Runtime Environment Java-based build tool. JavaBeans(TM) (EJB(TM)). Javadocs Java(TM) technology-based Web Java(TM) technology-based Web Javadocs High-Performance Java Runtime Java Runtime Environment Object Level Trace Java
Notes: -----Note 1: ------thread Q: Unable to install Java 1.4 due to License Problem I am trying to install Java14_64.sdk package on AIX 5.3 ML4. The install fails with the message below, the license file IS on the system/media but for some reason is not recognized. When I try to install the license on its own it fails with a pre-requisite failure, the pre-requisite being the above package - Java14_64.sdk. Any ideas out there ?
Selected Filesets ----------------Java14_64.sdk 1.4.0.1 # Java SDK 64-bit > FILESET STATISTICS -----------------1 Selected to be installed, of which: 1 Passed pre-installation verification ---1 Total to be installed LICENSE AGREEMENT FAILURES -----------------The installation cannot proceed because the following filesets require software license agreement files which could not be found on the system or installation media: Java14_64.sdk A: The downloadable install images at: http://www-128.ibm.com/developerwork...x/service.html http://www-128.ibm.com/developerworks/java/jdk/aix/service.html have both the 1.4.2.0 base images (ca1420-20040626) and the current 'latest' level (ca142-20060824). You should be able to use the 1.4.2.0 from that site plus your 1.4.2.1 update. Paul Landay Some jre versions on AIX: ------------------------AIX 5.1 ML5 comes with APAR IY52512 IBM SDK 1.3.1 SR7 32-bit (APAR IY52512) JavaTM 2 Runtime Environment, Standard Edition (build 1.3.1) Classic VM (build 1.3.1, J2RE 1.3.1 IBM AIX build ca131-20040517 (JIT enabled: jitc)) AIX 5.2 ML5 comes with APAR IY58350 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1) Classic VM (build 1.3.1, J2RE 1.3.1 IBM AIX build ca131ifx-20040721a SR7P (JIT enabled: jitc)) IY65305: JAVA142 32-BIT PTF : CA142IFX-20041203 == IY58350 : JAVA 1.3.1 32-bit SR7P : ca131ifx-20040721a SDK 1.3.1 32-bit PTFs since GA: ca131-20040517 Java131.rte.bin APAR # Fullversion fileset level -----------------------------IY76252 ca131-20051025 1.3.1.18
"SR" # -----SR 9
IY65310 IY58350 IY52512 IY50443 IY49074 IY47055 IY45632 IY45288 IY40440 IY39508 IY38011 IY33957 IY30887
-> ->
ca131-20041210 1.3.1.17 ca131ifx-20040721a 1.3.1.16 ca131-20040517 1.3.1.15 ca131-20031105 1.3.1.13 ca131-20031021 1.3.1.12 ca131-20030630a 1.3.1.11 ca131-20030630 1.3.1.10 ca131-20030329 1.3.1.9 ca131-20030329 1.3.1.8 ca131-20030122a 1.3.1.7 ca131-20021107 1.3.1.6 ca131-20021102 1.3.1.5 ca131-20020706 1.3.1.2
SR 8 SR 7P
SR 7 SR 6a SR 6 N/A SR 5 N/A SR 4 N/A SR 3W SR 3 SR 2
SDK 1.3.1 64-bit PTFs since GA: Java13_64.rte.bin APAR # Fullversion fileset level "SR" # -------------------------------- -----IY76253 IY65311 IY58414 IY57370 IY49076 IY45633 IY42844 IY34010 IY30923
caix64131-20051025 1.3.1.10 caix64131-20041210 1.3.1.9 caix64131ifx-20040721 1.3.1.8 caix64131-20040517 1.3.1.7 caix64131-20031021 1.3.1.6 caix64131-20030618 1.3.1.5 caix64131-20030329 1.3.1.4 caix64131-20021102 1.3.1.3 caix64131-20020706 1.3.1.2
SDK 1.4 64-bit PTFs since 1.4.0 GA: APAR # ------
Fullversion -----------
IY84054 caix64142-20060421 IY81444 caix64142ifx-20060209 IY77461 caix64142-20060120 IY75004 caix64142-20050929 IY72502 caix64142-20050609 IY70332 caix64142sr1aifx-20050414 IY68122 caix64142sr1a-20050209 == IY62851 (IY63533 for download) caix64142-20040917 IY54664 caix641420-20040626 IY58415 caix641411ifx-20040810 IY52686 caix641411-20040301 IY48526 caix641411-20030930 IY47538 caix64141-20030703a IY43716 caix64141-20030522
Java14_64.sdk fileset level -------------
SR 8 SR 7P SR 7 SR 5 SR 3
SR 6 SR 4 SR 2
"SR" # ------
1.4.2.75 1.4.2.51 1.4.2.50 1.4.2.20 1.4.2.10 1.4.2.5 1.4.2.3
142 142 142 142 142 N/A 142
1.4.2.1 1.4.2.0 1.4.1.4 1.4.1.3 1.4.1.2 1.4.1.1 1.4.1.0
1.4.2 SR 1 N/A (1.4.2 GA code) 1.4.1 SR 3 1.4.1 SR 2 1.4.1 SR 1 N/A N/A
Latest: 1.4.2 Service Release 5 (caix64142-20060421) Other notes: ------------
SR 9
SR5 SR4 (repackaged) SR4 (bad) SR3 SR2 SR1a
jre 131 32 bit: installs in /usr/java131 5100-08 (APAR IY70781) 5200-06 (APAR IY67913) 5300-02 (APAR IY69190)
- min AIX51 - min AIX52 - min AIX53
jre 131 64 bit: installs in /usr/java13_64 5100-08 (APAR IY70781) 5200-06 (APAR IY67913) 5300-02 (APAR IY69190)
- min AIX51 - min AIX52 - min AIX53
Java 1.1.8, 1.2.2, and 1.4.1 are no longer supported by IBM. For AIX 4.3.3, which is Recommended Maintenance For AIX 5.1, Java 1.3.1 For AIX 5.2, Java 1.3.1 For AIX 5.3, Java 1.3.1
out of support, Java 1.3.1 requires the AIX 4330-10 Level. requires the AIX 5100-03 Recommended Maintenance Level. requires the AIX 5200-01 Recommended Maintenance Level. requires Version 5.3.0.1 (APAR IY58143) or later.
Java version on AIX 5.3: ======================== The latest Java technology is included with base AIX 5L V5.3. The IBM 32-bit SDK for AIX 5L, Java 2 Technology Edition V1.4 ships with AIX 5L V5.3. The IBM 64-bit SDK for AIX 5L, Java 2 Technology Edition V1.4 is available on the AIX 5L V5.3 Expansion Pack and the AIX 5L Java Web site at ibm.com/developerworks/java/jdk/aix. JVM problems and AIX Environment Variables in relation to Java: =============================================================== Default Behavior of Java on AIX This section describes the settings as they are right now. These settings may, and in most cases will, change over time. The README or SDK Guide accompanying the SDK are always the most up-to-date references for such settings. Java uses the following environment settings: AIXTHREAD_SCOPE=S This setting is used to ensure that each Java thread maps 1x1 to a kernel thread. The advantage of this approach is seen in several places; a notable example is how Java exploits Dynamic Logical Partitioning (DLPAR); when a new CPU is added to the partition, a Java thread can be scheduled on it. This setting should not be changed under normal circumstances. AIXTHREAD_COND_DEBUG, AIXTHREAD_MUTEX_DEBUG and AIXTHREAD_RWLOCK_DEBUG
These flags are used for kernel debugging purposes. These may sometimes be set to OFF. If not, switching them off can provide a good performance boost. LDR_CNTRL=MAXDATA=0x80000000 This is the default setting on Java 1.3.1, and controls how large the Java heap can be allowed to grow. Java 1.4 decides the LDR_CNTRL setting based on requested heap. See Getting more memory in AIX for your Java applications for details on how to manipulate this variable. JAVA_COMPILER This decides what the Just-In-Time compiler will be. The default is jitc, which points to the IBM JIT compiler. It can be changed to jitcg for the debug version of JIT compiler, or to NONE for switching the JIT compiler off (which in most cases is the absolute worst thing you can do for performance). IBM_MIXED_MODE_THRESHOLD This decides the number of invocations after which the JVM JIT-compiles a method. This setting varies by platform and version; for example, it is 600 for Java 1.3.1 on AIX. Note 1: ------About o_maxdata and LDR_CNTRL: ... space for the native heap. Moving the fence down allows the native heap to grow, while reducing shared memory. For a setting of o_maxdata = N, the fence is placed at 0x30000000+N. For several good reasons, it is recommended to set o_maxdata to a value that is the start of a particular segment, such as 0xn0000000. In this case, the fence sits between segments 2+n and 3+n, which translates to n segments for the native heap, and 10-n segments for shared memory. o_maxdata=8: o_maxdata=7: o_maxdata=6: o_maxdata=5: o_maxdata=4: o_maxdata=3: o_maxdata=2:
8 7 6 5 4 3 2
seg seg seg seg seg seg seg
for for for for for for for
native, native, native, native, native, native, native,
2 3 4 5 6 7 8
seg seg seg seg seg seg seg
for for for for for for for
shared shared shared shared shared shared * shared
By default, o_maxdata is set to 0x80000000, leaving 2 GB for native heap and 512 MB for shared memory. If you attempt to allocate a Java heap larger than 1 GB, it fails because Java tries to use shared memory for heap, and there is only 512 MB of shared memory available. If you set IBM_JAVA_MMAP_JAVA_HEAP in the environment and try to allocate a heap larger than 512 MB, JVM will be unable to allocate the heap. The solution is to adjust o_maxdata in such a way that the size of shared memory grows large enough
to accommodate the Java heap. The next section shows you how to do this. So how do you go to a larger Java heap? You need to change o_maxdata to increase the amount of shared memory address space. You can use the following calculations to come up with the appropriate value for o_maxdata. Supposing you need a maximum heap size of J bytes, you would invoke Java as java -mxJ If J is less than 1 GB, and IBM_JAVA_MMAP_JAVA_HEAP is not set, the default setup will suffice. If J is > 1 GB, or if IBM_JAVA_MMAP_JAVA_HEAP is set, use o_maxdata = 0xn0000000 where
n = (10 - ceil(J/256M)) or 8
whichever is smaller. The function ceil rounds up the argument to the next integer. For example, if you need to allocate 1500 MB of heap, we have n = (10 - ceil(1500M/256M)) = (10 - 6) = 4. If you set o_maxdata = 0x40000000, you will be able to allocate the needed size of heap. To change o_maxdata, set the following environment variable: LDR_CNTRL=MAXDATA= The above example would set the following environment variable: LDR_CNTRL=MAXDATA=0x40000000 To verify that your calculation is accurate, you can try the following commands: $ export LDR_CNTRL=MAXDATA=0x40000000 $ java -mx1500m -version Setting the IBM_JAVA_MMAP_JAVA_HEAP variable # export IBM_JAVA_MMAP_JAVA_HEAP=true So, if you need to enhance memory for Websphere 5.x 32 bits, put the following lines into the startServer.sh script, or in /prj/was/omgeving.rc: export LDR_CNTRL=MAXDATA=0xn0000000 export IBM_JAVA_MMAP_JAVA_HEAP=true try: export export export export export export
AIXTHREAD_SCOPE=S AIXTHREAD_MUTEX_DEBUG=OFF AIXTHREAD_RWLOCK_DEBUG=OFF AIXTHREAD_COND_DEBUG=OFF LDR_CNTRL=MAXDATA=0x40000000 IBM_JAVA_MMAP_JAVA_HEAP=TRUE
or export IBM_JAVA_MMAP_JAVA_HEAP=true export LDR_CNTRL=MAXDATA=0x80000000 or export IBM_JAVA_MMAP_JAVA_HEAP=true export LDR_CNTRL=MAXDATA=0x80000000 Note 2: ------I think the problem is that there are typically a lot of JNI allocations in the heap that are pinned and are allocated for the life of the application. Most of these are allocated during startup. If the min and max heap sizes are the same, these pinned allocations are scattered throughout the heap. Whereas if the min heap size is quite low, most of these allocations will be closer together at the start of the heap, leaving the bulk of the heap (when it's expanded) more free of pinned memory.
55.5 Installing Perl: ===================== AIX supports dynamically loadable objects as well as shared libraries. Shared libraries by convention end with the suffix .a, which is a bit misleading, as an archive can contain static as well as dynamic members. For perl dynamically loaded objects we use the .so suffix also used on many other platforms. Note that starting from Perl 5.7.2 (and consequently 5.8.0) and AIX 4.3 or newer Perl uses the AIX native dynamic loading interface in the so called runtime linking mode instead of the emulated interface that was used in Perl releases 5.6.1 and earlier or, for AIX releases 4.2 and earlier. This change does break backward compatibility with compiled modules from earlier perl releases. The change was made to make Perl more compliant with other applications like Apache/mod_perl which are using the AIX native interface. This change also enables the use of C++ code with static constructors and destructors in perl extensions, which was not possible using the emulated interface. Starting from AIX 4.3.3 Perl 5 ships standard with AIX. (Perl 5.8.0 with AIX 5L V5.2, 5.6.0 with AIX 5L V5.1, 5.005_03 with AIX 4.3.3.) You either get the source code and compile Perl, or in some situations you might be happy with installing a binary build.
55.6 Installing DB2 Connect Enterprise Edition 8.x: =================================================== DB2 Connect DB2(R) Connect provides fast and robust connectivity to IBM(R) mainframe databases for e-business and other applications running under UNIX(R) and Windows(R) operating systems. DB2 Connect Personal Edition provides direct connectivity to host and iSeries DB2 servers, while DB2 Connect Enterprise Edition provides indirect connectivity that allows clients to access host and iSeries DB2 servers through the DB2 Connect server. DB2 Connect Unlimited Edition 7 and DB2 Connect Application Server Edition provide unique packaging solutions that make product selection and licensing easier.
Note 1: ------Log on to the system as a user with root authority. Refer to the CD-ROM label to ensure that you are using the CD-ROM with your appropriate language. Change to the directory where the CD-ROM is mounted by entering the following command: cd /cdrom - For AIX 4.3.3, HP-UX and Linux Enter the ./db2setup command to start the DB2 Setup wizard. - For Solaris Operating Environment and AIX 5L Copy product.tar.Z, where product represents the product you are licensed to install, to a temporary filesystem. Enter the following command to start the DB2 Setup wizard: # zcat product.tar.Z | tar -xf - ; ./product/db2setup For example, if the product name for DB2 Enterprise Server Edition is ese, then enter the following command: # zcat ese.tar.Z | tar -xf - ; ./ese/db2setup After a moment, the IBM DB2 Setup Launchpad opens. When you have completed your installation, DB2 will be installed in the one of the following directories: For AIX: /usr/opt/db2_08_01
For HP-UX, Linux, Solaris Operating Environment: /opt/IBM/db2/V8.1 The installation logs db2setup.his, db2setup.log, and db2setup.err are located, by default, in the /tmp directory. You can specify the location of the log files. The db2setup.log file captures all DB2 installation information including errors. The db2setup.his records all DB2 installations on your machine. DB2 appends the db2setup.log file to the db2setup.his file. The db2setup.err file captures any error output that is returned by Java (for example, exceptions and trap information). If you want your DB2 product to have access to DB2 documentation either on your local computer or on another computer on your network, then you must install the DB2 Information Center. The DB2 Information Center contains documentation for DB2 Universal Database and DB2 related products. Note 2: db2admin ---------------db2admin - DB2 Administration Server Command This utility is used to manage the DB2 Administration Server. Authorization Local administrator on Windows, or DASADM on UNIX based systems. Required connection None Command syntax >>-db2admin-----------------------------------------------------> >--+-----------------------------------------------------------------+->< +-START-----------------------------------------------------------+ +-STOP--+--------+------------------------------------------------+ | '-/FORCE-' | +-CREATE--+----------------------+--+---------------------------+-+ | '-/USER:--user-account-' '-/PASSWORD:--user-password-' | +-DROP------------------------------------------------------------+ +-SETID--user-account--user-password------------------------------+ +-SETSCHEDID--sched-user--sched-password--------------------------+ +- -?-------------------------------------------------------------+ '- -q------------------------------------------------------------Note: If no parameters are specified, and the DB2 Administration Server exists, this command returns the name of the DB2 Administration Server. START Start the DB2 Administration Server. STOP /FORCE Stop the DB2 Administration Server. The force option is used to force the DB2 Administration Server to stop, regardless of whether or not it is in the process of servicing any requests.
CREATE /USER: user-account /PASSWORD: user-password Create the DB2 Administration Server. If a user name and password are specified, the DB2 Administration Server will be associated with this user account. If the specified values are not valid, the utility returns an authentication error. The specified user account must be a valid SQL identifier, and must exist in the security database. It is recommended that a user account be specified to ensure that all DB2 Administration Server functions can be accessed. Note: To create a DAS on UNIX systems, use the dascrt command. Starting and stopping the DAS: db2admin stop db2admin start Note 3: db2start ---------------db2start - Start DB2 Command Starts the current database manager instance background processes on a single database partition or on all the database partitions defined in a partitioned database environment. Start DB2 at the server before connecting to a database, precompiling an application, or binding a package to a database. db2start can be executed as a system command or a CLP command Note 4: example cronjobs -----------------------30 20 * * 1-6 /usr/opt/db2_08_01/adm/db2stop force >> /home/db2inst1/DBMaintenance/dbbkup.log 2>&1 31 20 * * 1-6 /usr/opt/db2_08_01/adm/db2start >> /home/db2inst1/DBMaintenance/dbbkup.log 2>&1 Note 5: sample db2 connect processes: ------------------------------------Using AIX, you would use the command ps -ef in order to examine processes. On Solaris and HP-UX, ps -ef will only show the db2sysc process (the main DB2 engine process) for all serverside processes (eg: agents, loggers, page cleaners, and prefetchers). If you're using Solaris or HP-UX, you can see these side processes with the command /usr/ucb/ps -axw. Both of these versions of the ps command work on Linux. When performing this command on a computer running the DB2 Universal Database client or server software, you may see several DB2 processes listed.
Example 1: /root:#ps -ef | grep db2 iinvu02 188456 422094 0 13:53:02 - 0:00 db2agent (idle) 0 db2as 266468 1 0 13:52:10 - 0:00 /prj/db2/admin/db2as/das/adm/db2dasrrm iinvu02 282624 417996 0 13:53:03 - 1:13 db2disp 0 root 295060 1 0 13:52:24 - 0:00 db2wdog 0 iinvu01 299158 303256 0 13:52:26 - 0:00 db2resync 0 iinvu01 303256 295060 0 13:52:24 - 0:00 db2sysc 0 root 307350 303256 0 13:52:24 - 0:00 db2ckpwd 0 root 311448 303256 0 13:52:24 - 0:00 db2ckpwd 0 root 315546 303256 0 13:52:24 - 0:00 db2ckpwd 0 iinvu01 319644 303256 0 13:52:24 - 0:00 db2gds 0 iinvu01 323742 303256 0 13:52:24 - 0:00 db2ipccm 0 iinvu01 327840 303256 0 13:52:25 - 0:00 db2tcpcm 0 iinvu01 331938 303256 0 13:52:25 - 0:00 db2tcpcm 0 iinvu01 336036 303256 0 13:52:25 - 0:00 db2tcpcm 0 iinvu01 340134 303256 0 13:52:25 - 0:00 db2tcpcm 0 iinvu01 344232 319644 0 13:52:26 - 0:00 db2srvlst 0 iinvu01 348330 303256 0 13:52:26 - 0:00 db2spmrsy 0 iinvu01 352428 319644 0 13:52:26 - 0:00 db2spmlw 0 iinvu02 356606 401604 0 13:52:46 - 0:16 db2hmon 0 iinvu01 360624 303256 0 13:52:26 - 0:18 db2hmon 0 iinvu01 377016 1 0 13:52:32 - 3:00 /prj/db2/admin/iinvu01/sqllib/bin/db2fmd -i iinvu01 -m /prj/db2/admin/iinvu01/sqllib/lib/libdb2gcf.a iinvu02 389128 417996 0 13:52:46 - 0:00 db2srvlst 0 root 393408 1 0 13:52:38 - 0:00 db2wdog 0 iinvu02 397514 401604 0 13:52:46 - 0:00 db2resync 0 iinvu02 401604 393408 0 13:52:38 - 0:00 db2sysc 0 root 405702 401604 0 13:52:38 - 0:00 db2ckpwd 0 root 409800 401604 0 13:52:38 - 0:00 db2ckpwd 0 root 413898 401604 0 13:52:38 - 0:00 db2ckpwd 0 iinvu02 417996 401604 0 13:52:38 - 0:00 db2gds 0 iinvu02 422094 401604 0 13:52:39 - 0:00 db2ipccm 0 iinvu02 426192 1 5 13:52:52 - 2:55 /prj/db2/admin/iinvu02/sqllib/bin/db2fmd -i iinvu02 -m /prj/db2/admin/iinvu02/sqllib/lib/libdb2gcf.a root 475370 1 0 13:53:50 - 0:18 /usr/opt/db2_08_01/bin/db2fmcd db2as 528466 1 0 13:55:52 - 0:00 /prj/db2/admin/db2as/das/bin/db2fmd -i db2as -m /prj/db2/admin/db2as/das/lib/libdb2dasgcf.a iinvu01 561230 323742 0 13:57:29 - 0:03 db2agent (idle) 0 iinvu02 573686 417996 0 15:11:41 - 0:02 db2agent (idle) 0 Example 2: root db2inst1 db2inst1 db2inst1 db2inst1 db2inst1 db2inst1 db2inst1 db2inst1
49504 25844 35124 35540 41940 45058 49300 49626 55852
1 35124 65638 35124 65638 35124 35124 35124 65638
0 0 0 0 0 0 0 0 0
13:13:07 16:04:50 16:04:17 16:04:50 16:04:19 16:04:50 16:04:19 16:04:50 16:04:17
-
0:00 0:00 0:00 0:00 0:00 0:00 0:00 0:00 0:00
db2wdog db2pfchr db2gds db2loggr (SAMPLE) db2resync db2pfchr db2srvlst db2dlock (SAMPLE) db2ipccm
db2inst1 58168 35124 db2inst1 59048 35124 db2inst1 64010 55852 db2inst1 65638 22238 db2inst1 70018 35124 db2inst1 72120 35124 db2inst1 74198 65638 db2inst1 74578 1 50112C14631 5
0 0 0 0 0 0 0 0
16:04:50 16:04:50 16:04:50 16:04:17 16:04:50 16:04:51 16:04:17 16:04:47
-
0:00 0:00 0:00 0:00 0:00 0:00 0:00 0:00
db2loggw (SAMPLE) db2pfchr db2agent (SAMPLE) db2sysc db2pclnr db2event (DB2DETAILDEADLOCK) db2syslog /home/db2inst1/sqllib/bin/db2bp
- db2dasrrm: The DB2 Admin Server process. This process supports both local and remote administration requests using the DB2 Control Center - db2pclnr: I/O cleaners, associated with data cache buffers - db2rebal: This process is used to perform a rebalancing of the data when a container is added to a DMS table space. - db2disp: The DB2 agent dispatcher process. This process dispatches application connections between the logical agent assigned to the application and the available coordinating agents when connection concentration is enabled. This process will only exist when connection concentration is enabled. - The db2ckpwd utility in DB2 is used to verify usernames and passwords for the operating system. db2ckpwd takes a file descriptor as a command line argument and reads the username and password information from that file descriptor. - db2gds: The DB2 Global Daemon Spawner process that starts all DB2 EDUs (processes) on UNIX. There is one db2gds per instance or database partition - db2ipccm: listener process for local applications. - db2tcpcm: A remote client establishes TCP/IP communications through the db2tcpcm listener process. - db2sysc: The main DB2 system controller or engine. Without this process, the database server cannot function. - db2resync: The resync manager process used to support applications that are using two-phase commit - db2wdog: The DB2 watchdog. This process is required since processes in UNIX can only track their parent process ID. Each time a new process is started, the db2gds notifies the DB2 watchdog. In the event that any DB2 process receive a ctrl-c or other abnormal signal, the process send the signal to the watchdog, and it propagates the signal to all of the other processes in the instance.
- db2ca: Starts the Configuration Assistant. The Configuration Assistant is a graphical interface that is used to manage DB2 database configuration such as database manager configuration, DB2 registry, node directory, database directory and DCS directory - Agents An agent can be thought of as a 'worker' that performs all database operations on behalf of an application. There are two main types of DB2 agents: Coordinator Agent (db2agent) A coordinator agent (or a coordinating agent) coordinates the work on behalf of an application and communicates to other agents using interprocess communication (IPC) or remote communication protocols. All connection requests from client applications, whether they are local or remote, are allocated a corresponding coordinator agent. Subagent (db2agntp) When the intra_parallel database manager configuration parameter is enabled, the coordinator agent distributes the database requests to subagents (db2agntp). These agents perform the requests for the application. Once the coordinator agent is created, it handles all database requests on behalf of its application by coordinating subagents (db2agent) that perform requests on the database. When an agent or subagent completes its work it becomes idle. When a subagent becomes idle, its name changes from db2agntp to db2agnta. For example: db2agntp processes are active subagents which are currently performing work for the coordinator agent. These processes will only exist when intra-partition parallelism is enabled. db2agnta processes are idle subagents that were used in the past by a coordinator agent. - db2hmon: The db2hmon process has changed in DB2 Universal Database Version 8.2 and is no longer associated with the HEALTH_MON database manager configuration parameter. In DB2� Universal Database� (DB2 UDB) Version 8.1, the db2hmon process was controlled by the HEALTH_MON database manager configuration parameter. When HEALTH_MON was set to ON, a single-threaded independent coordinator process named db2hmon would start. This process would terminate if HEALTH_MON was set to OFF. In DB2 UDB Version 8.2, the db2hmon process is no longer controlled by the HEALTH_MON database manager configuration parameter. Rather, it is a stand-alone process that is part of the database server so when DB2 is started, the db2hmon process starts. db2hmon is a special multithreaded DB2FMP process
that is named db2hmon on UNIX/Linux platforms and DB2FMP on Windows. Note 6: db2icrt --------------On UNIX-based systems, the db2icrt utility is located in the DB2DIR/instance directory, where DB2DIR represents /usr/opt/db2_08_01 on AIX, and /opt/IBM/db2/V8.1 on all other UNIX-based systems. If you have a FixPak or modification level installed in an alternate path, the DB2DIR directory is /usr/opt/db2_08_FPn on AIX and opt/IBM/db2/V8.FPn on all other UNIX-based systems, where n represents the number of 1 the FixPak or modification level. The db2icrt utility creates an instance on the directory from which you invoke it. >>-db2icrt--+-----+--+-----+--+---------------+-----------------> +- -h-+ '- -d-' '- -a--AuthType-' '- -?-' >--+---------------+--+---------------+--+----------------+-----> '- -p--PortName-' '- -s--InstType-' '- -w--WordWidth-' >--+---------------+--InstName--------------------------------->< '- -u--FencedID-' On an AIX machine, to create an instance called "db2inst1" on the directory /u/db2inst1/sqllib/bin, issue the following command from that directory: Example 1 On a client machine: 1 usr/opt/db2_08_01/instance/db2icrt db2inst1 On a server machine: 1 usr/opt/db2_08_01/instance/db2icrt -u db2fenc1 db2inst1 where db2fenc1 is the user ID under which fenced user-defined functions and fenced stored procedures will run. Example 2 On an AIX machine, if you have Alternate FixPak 1 installed, run the following command to create an instance running FixPak 1 code from the Alternate FixPak install path: /usr/opt/db2_08_FP1/instance/db2icrt -u db2fenc1 db2inst1 Note 7: Whats an instance? Compared to Unix / Z ----------------------------------------------1. What's an Instance? And where is my Subsystem? Posted 11/8/2005 | by Chris Eaton | Comments (0) | TrackBacks (0) If you are new to DB2 LUW from a DB2 for z/OS background then the first thing you probably noticed is that there is no subsystem on the LUW platform. Instead you will hear the term Instance used in a similar manner.
An instance in DB2 for LUW is like a copy of the RDBMS including all the processes that run DB2 and memory (address spaces) associated with that instance of DB2 and some configuration parameters (ZPARMS) to control that instance. Think of it as a copy of the DB2 code running on a server. You can have as many instances as you like running on a single server. Associated with an instance is the concept of an instance owner. This is the user that "owns" that instance and has SYSADM authority over the instance and all databases inside that instance. SYSADM authority is the highest level of authority in DB2 and lets this user do anything within the databases it manages (create, drop, access all data, grant, revoke, etc). You can have one or more databases in each instance but a database is not exactly the same as you have on z/OS either. On z/OS you have one catalog per subsystem and a database is merely a logical collection of tables, indexes that usually have a distinct relationship to a given application. On the LUW platform each database has its own catalogs associated with it which stores all the metadata about that database. Why the difference? Well, as with many of the differences you will find at the server or storage layer, they are mostly due to the "culture" or "industry standard terms" that are typically used in a Linux, UNIX or for that matter a Windows environment. An Instance is a common term across a number of distributed platform RDBMSs to represent a copy of the database management code running on a server. And you won't likely find the term subsystem used to describe anything on a distributed platform (except for maybe some people talking about storage but if you dig a bit you will likely find that in a past life these people worked on a mainframe). The other important distinction in this area is that your application connects to a database in the LUW environment (not a subsystem or instance). As well if you want to join tables across different databases you would use the federated query support built into DB2. On MVS, OS390, zos:
On UNIX/Windows:
---------------------------| Subsystem | ---------------------------| | | -------------------------|CATALOG| |DB| |DB| DB+catalog| --------------------------
-------------------------------|INSTANCE| |INSTANCE | -------------------------------| | | ----------------------|DB+catalog|
|DB+catalog|
------------
------------
|
So, a
Z "Subsystem" an Unix "Instance".
2. Aanvullende Info op Unix: Na de installatie van DB2 kunt u alleen met DB2 communiceren door het instanti�ren van DB2. Met andere woorden, u maakt een object (lees: Database Manager) binnen DB2 aan, die voor u de communicatie verzorgt. Dus een "Instance" "Database Manager" Stel u heeft een instance van een Database Manager aangemaakt. Deze Database Manager verzorgt de communicatie met zowel lokale als remote databases. U dient de Database Manager te instrueren hoe en op welke wijze bepaalde databases benaderd kunnen worden. Tevens geeft u aan onder welke �eenvoudige� naam deze set van instructies gebruikt kunnen worden. Dit is de zogenaamde Alias. In onderstaand figuur wordt schematisch weergegeven hoe de communicatie tussen de platformen wordt gerealiseerd. AIX
z/OS
------------------------------
-------------------------------------
| | | |
| | Een Partitie | |
------------|Application| ------|------|
| | | |
---------------| DBMS 1 port A |
| | | |
| -----------------------| | | ---| | | | Instance = | | |------------------------> |DB| | | | | Database Manager | | | | | ---| | | | | | | | | ---| | | | ---------| | |---------------------->|DB| | | | | |Alias 1 | | | | | | ---| | | | | |-----------------| ---------------| | | ---------| | | ---------------| | | | | | |DBMS 2 port B | | | | ---------| | | | | | | | |Alias 2 | | | alias | | ---| | | | | |---------------------------------------> |DB| | | | | ---------| | | | ---| | | | | | | | | | | -----------------------| | ----------------| -------------------------------------------------------------------Zoals u ziet verloopt communicatie tussen een Applicatie, bijv. Websphere Application Server (WAS), en het mainframe platform via DB2. Voor de eenvoud nemen we voor nu even aan dat de applicatie binnen de WAS de communicatie rechtstreeks aangaat. Binnen DB2 verzorgt een instance van
een Database Manager de voorgedefinieerde connecties. De Database Manager stelt deze connecties ter beschikking middels een alias. De middels pijltjes �eenvoudig� weergegeven connecties tussen de twee platformen dienen nader bekeken te worden. De pijl vanaf een alias tot aan een database op het mainframe wordt een node genoemd. Deze node dient vooraf voorzien te worden van informatie op basis waarvan toegang tot de betreffende database op het mainframe verkregen kan worden. Het pakket aan informatie gekoppeld aan een node noemen we een catalog. De node wordt alsvolgt opgebouwd: ------------------------------------------------------------------|Alias (heeft de database op het mainframe gekoppeld aan de Node) | ------------------------------------------------------------------| | -----------------------------------------------------------------------------------------|Node (kent het IP nummer van het mainframe en het poortnummer van de DBMS op de partitie)| -----------------------------------------------------------------------------------------E�n alias heeft ��n verbinding met ��n DBMS op ��n partitie op het mainframe. Binnen het DBMS �leven� namelijk meerdere databases. Indien een connectie moet worden gelegd tussen AIX en een andere database in een andere DBMS op dezelfde partitie dient een nieuwe alias (en dus node) aangemaakt te worden. Bij het configureren van een Remote Database praten we dus over de connectie tussen DB2 en een database op een partitie op het mainframe. De volgende stappen moeten we doorlopen om een werkende connectie aan te maken: � � � �
Aanmaken Koppelen Koppelen Koppelen
van van van van
de node; node aan ip-nummer van het mainframe; node aan poortnummer van een partitie op het mainframe; database op het mainframe aan een alias op AIX
De implementatie zullen we laten zien aan de hand van een voorbeeld: Catalog= ( node={IP + port} ( {Alias=DB} ) ) -----------------------------------------------db2=> Catalog tcpip node server Het laatste commando initieert feitelijk de node gekoppeld aan het ipnummer van de mainframe en het poortnummer van de partitie, waarbij:
Nodenaam: De naam van de node. Deze kunt u zelf kiezen (bijv NOO49 : NOde Ontwikkeling 49). Ip-adres mainframe: T-partitie: 10.73.64.183 Poortnummer mainframe T-partitie: 447 of 448 (afhankelijk van DBMS): BACDB2O = 447 (Ontwikkel omgeving) BACDB2I = 448 (Integratie omgeving) -- Ter controle: db2=> list node directory Adds a Transmission Control Protocol/Internet Protocol (TCP/IP) node entry to the node directory. The TCP/IP communications protocol is used to access the remote node. The CATALOG TCPIP NODE command is run on a client. ----------------------------------------------Vervolgens koppelen we de database op het mainframe middels een node aan een alias. Voer uit: db2=> Catalog database databasenaam as alias at node nodenaam authentication dcs Databasenaam: Een bestaande database binnen het DBMS op het mainframe Alias: Vrij te kiezen naam Nodenaam: De naam van de hierboven aangemaakte node -- Ter controle: db2=> list db directory Nu doen we db2=> Catalog dcs database databasenaam as DBMS Databasenaam DBMS
De hierboven bestaande database binnen het DBMS op het mainframe Dit is het DataBase Management Systeem op het mainframe. Bijv. T-partitie: BACDB2O (Ontwikkel omgeving) BACDB2I (Integratie omgeving)
-- Ter controle: db2=> list dcs directory Vervolgens loggen wij in het mainframe in om de connectie te testen: db2=> connect to aliasnaam user user using password Aliasnaam De zojuist hierboven aangemaakte alias voor een verbinding met het mainframe User Uw userid of een userid met voldoende rechten op het mainframe (bijv. BDN account) Password Password van het toepaste userid Dus een sessie tot stand brengen gaat als in het onderstaande voorbeeld:
connect to pscrx user u@mnx01 using PSWVDB2C; set current sqlid = 'F@MNX01'
Dus hoe zit het nu: =================== Je wilt via DB2 connect naar een remote DB op een mainframe. Op de client doe je: db2=> Catalog tcpip node server db2=> list node directory (=controle statement) db2=> Catalog database databasenaam as alias at node nodenaam authentication dcs db2=> list db directory (=controle statement) db2=> Catalog dcs database databasenaam as DBMS db2=> list dcs directory (=controle statement) Je neemt een willekeurige handig nodenaam (door jou te kiezen dus) en koppel dat begrip aan de remote IP en poort. Dan koppel je de echte databasenaam aan een handige (door jou te kiezen dus) Alias, en dat koppel je dan ook aan de nodenaam. Voortaan kun je dan met de Alias een connectie opzetten !
Note: Connection via DB2 Connect: --------------------------------First of all install the DB2 client (for me it was DB2connect 7.1) and register it with the proper license (using db2licm). Now you are ready to register your remote database. I'll need to provide: hostname, port, database name, authentication method. For every DB, I need three registrations: tcp/ip node, database and DCS. Let's start from the tcp/ip node. Connect to your db2 user (by default db2inst1): db2inst1@brepredbls01:~> db2 (c) Copyright IBM Corporation 1993,2001 Command Line Processor for DB2 SDK 7.2.0 db2 => -- Now from the db2 client command prompt:
catalog tcpip node remote server where nodename is an alias you choose, hostname is the DB2 remote hostname and the port is the DB2 listening port. example: catalog tcpip node RIHEP remote rihep.rit server 5023 to unregister it: uncatalog node RIHEP and to list the register nodes: db2 => list node directory Node Directory Number of entries in the directory = 3 Node 1 entry: Node name Comment Protocol Hostname Service name
= = = = =
AMDSPT
= = = = =
AMSVIL
= = = = =
RIHEP
TCPIP amdahlsvil.ras 5023
Node 2 entry: Node name Comment Protocol Hostname Service name
TCPIP amdahlsvil.ras 6021
Node 3 entry: Node name Comment Protocol Hostname Service name
TCPIP rihep.rit 5023
-- Now you need to catalog your remote DB2 database: catalog database as at node authentication DCS Where DBname is the name of the remote database, DBalias is the name you are going to use in your connection and nodename is the node alias you registered above. The chosen authentication has been DCS for my environment. Example:
catalog database ITFINDB2 as ITFINDB2 at node RIHEP authentication DCS If you wish to unregister the DB: uncatalog database ITFINDB2 for the list: db2 => list db directory System Database Directory Number of entries in the directory = 3 Database 1 entry: Database alias Database name Node name Database release level Comment Directory entry type Authentication Catalog node number
= = = = = = = =
ITFINDB2 ITFINDB2 RIHEP 9.00
= = = = = = = =
DB2PROD DB2PROD AMSVIL 9.00
= = = = = = = =
DB2DSPT DB2DSPT AMDSPT 9.00
Remote DCS -1
Database 2 entry: Database alias Database name Node name Database release level Comment Directory entry type Authentication Catalog node number
Remote DCS -1
Database 3 entry: Database alias Database name Node name Database release level Comment Directory entry type Authentication Catalog node number
Remote DCS -1
-- Last registration step: the DCS. catalog dcs database as example: catalog dcs database ITFINDB2 as ITFINDB2 to unregister: unregister dcs ITFINDB2
For the list: db2 => list dcs directory Database Connection Services (DCS) Directory Number of entries in the directory = 3 DCS 1 entry: Local database name Target database name Application requestor name DCS parameters Comment DCS directory release level
= DB2DSPT = DB2DSPT = = = = 0x0100
DCS 2 entry: Local database name Target database name Application requestor name DCS parameters Comment DCS directory release level
= DB2PROD = DB2PROD = = = = 0x0100
DCS 3 entry: Local database name Target database name Application requestor name DCS parameters Comment DCS directory release level
= ITFINDB2 = ITFINDB2 = = = = 0x0100
Now you can check if your configuration is correct: db2 => connect to ITFINDB2 user sisbanc Enter current password for sisbanc: Database Connection Information Database server SQL authorization ID Local database alias
= DB2 OS/390 7.1.1 = SISBANC = ITFINDB2
This indicate a succesful connection. An error or a command prompt without output indicates a failure. ex: db2 => connect to ITFINDB2 user sisbanc Enter current password for sisbanc: db2 => db2 =>
Note 9: license for DB2 Connect 8.x ----------------------------------To license DB2 Connect 8.x, you typically use a statement like /usr/opt/db2_08_01/adm/db2licm -a /prj/db2/install/udb/8.1/db2ese.lic Note 10: DB2 Connect Configuration files: ----------------------------------------- db2nodes.cfg This topic provides information about the format of the node configuration file (db2nodes.cfg). The db2nodes.cfg file is used to define the database partition servers that participate in a DB2 instance. The db2nodes.cfg file is also used to specify the IP address or host name of a high-speed interconnect, if you want to use a high-speed interconnect for database partition server communication. The format of the db2nodes.cfg file 7 is as follows: nodenum
hostname
logical port
netname
resourcesetname
Note 11: Most important Err messages: ------------------------------------1. db2=> connect to user using SQL1032N No start database manager command was issued.
SQLSTATE=57019
I keep getting the following error: [IBM][CLI Driver] SL1032N No start database manager command was issued. SQLSTATE=57019 I tried starting the database, and I still get the above error. Exacly how am I suppose to start the database, and how do I get rid of the above error?
56. Setting up an ASCII terminal on AIX: ======================================== The 3151 display can connect directly, or through a modem, to an AIX system. The connection to the AIX system can be made to one of the native serial ports, or to an asynchronous adapter. To add a TTY, use the following procedure:
- use "smitty tty" and select "Add a TTY" or use "smitty maktty" - or use mkdev # mkdev -c tty -t tty -s rs232 -p sa0 -w s1 -a login=enable -a term=ibm3151 # mkdev -c tty -t tty -s rs232 -p sa0 -w s0 -a login=enable -a term=ibm3151 To validate that the tty has been added to the customized VPD object class, enter # lscfg -vp | grep tty tty0 01-S1-00-00 Asynchronous Terminal To display the name of the systemconsole effective on the next startup, enter # lscons -b /dev/tty0 You can remove a terminal with # rmdev -l tty_name -d On the ASCII terminal, set the communications options as follows: Line speed (baud rate) = 9600 Word Length (bits per character) = 8 Parity = no (none) Number of Stop Bits = 1 Interface = RS-232C or RS-422A Line Control = IPRTS 57: chroot: =========== chroot Run a command with a different root directory 'chroot' runs a command with a specified root directory. On many systems, only the super-user can do this. SYNTAX chroot NEWROOT [COMMAND [ARGS]...] chroot OPTION Ordinarily, filenames are looked up starting at the root of the directory structure, i.e. '/' 'chroot' changes the root to the directory NEWROOT (which must exist) and then runs COMMAND with optional ARGS. If COMMAND is not specified, the default is the value of the `SHELL' environment variable or `/bin/sh' if not set, invoked with the `-i' option. The only options are `--help' and `--version' AIX: ---chroot Command
Purpose Changes the root directory of a command. Syntax chroot Directory Command Description Attention: If special files in the new root directory have different major and minor device numbers than the real root directory, it is possible to overwrite the file system. The chroot command can be used only by a user operating with root user authority. If you have root user authority, the chroot command changes the root directory to the directory specified by the Directory parameter when performing the Command. The first / (slash) in any path name changes to Directory for the specified Command and any of its children. The Directory path name is always relative to the current root. Even if the chroot command is in effect, the Directory path name is relative to the current root of the running process. A majority of programs may not operate properly after the chroot command runs. For example, the commands that use the shared libraries are unsuccessful if the shared libraries are not in the new root file system. The most commonly used shared library is the /usr/ccs/lib/libc.a library. The ls -l command is unsuccessful in giving user and group names if the current root location makes the /etc/passwd file beyond reach. In addition, utilities that depend on localized files (/usr/lib/nls/*) may also be unsuccessful if these files are not in the new root file system. It is your responsibility to ensure that all vital data files are present in the new root file system and that the path names accessing such files are changed as necessary. Examples Attention: The commands in the following examples may depend on shared libraries. Ensure that the shared libraries are in the new root file system before you run the chroot command. To run the pwd command with the /usr/bin directory as the root file system, enter: # mkdir /usr/bin/lib # cp /usr/ccs/lib/libc.a /usr/bin/lib chroot /usr/bin pwd To run a Korn shell subshell with another file system as the root file system, enter: # chroot /var/tmp /usr/bin/ksh This makes the directory name / (slash) refer to the /var/tmp for the duration of
the /usr/bin/ksh command. It also makes the original root file system inaccessible. The file system on the /var/tmp file must contain the standard directories of a root file system. In particular, the shell looks for commands in the /bin and /usr/bin files on the /var/tmp file system. Running the /usr/bin/ksh command creates a subshell that runs as a separate process from your original shell. Press the END OF FILE (Ctrl-d) key sequence to end the subshell and go back to where you were in the original shell. This restores the environment of the original shell, including the meanings of the . (current directory) and the / (root directory). 58. The date command: ===================== The date command can be very interesting to use on shell scripts, for example for testing purposes. You can device a test like daynumber=`date -u %d` export daynumber if daynumber=31 then .. The following shows what can be done using date. NAME date - print or set the system date and time SYNOPSIS date [OPTION]... [+FORMAT] date [-u|--utc|--universal] [MMDDhhmm[[CC]YY][.ss]] DESCRIPTION Display the current time in the given FORMAT, or set the system date. -d, --date=STRING display time described by STRING, not `now' -f, --file=DATEFILE like --date once for each line of DATEFILE -ITIMESPEC, --iso-8601[=TIMESPEC] output date/time in ISO 8601 format. TIMESPEC=`date' for date only, `hours', `minutes', or `seconds' for date and time to the indicated precision. --iso-8601 without TIMESPEC defaults to `date'. -r, --reference=FILE display the last modification time of FILE -R, --rfc-822 output RFC-822 compliant date string
-s, --set=STRING set time described by STRING -u, --utc, --universal print or set Coordinated Universal Time --help display this help and exit --version output version information and exit FORMAT controls the output. The only valid option for the second specifies Coordinated Universal Time. Interpreted sequences are:
form
%%
a literal %
%a
locale's abbreviated weekday name (Sun..Sat)
%A
locale's full weekday name, variable length (Sunday..Saturday)
%b
locale's abbreviated month name (Jan..Dec)
%B
locale's full month name, variable length (January..December)
%c
locale's date and time (Sat Nov 04 12:02:33 EST 1989)
%C
century [00-99]
(year
divided
by
100 and
truncated
to an integer)
%d
day of month (01..31)
%D
date (mm/dd/yy)
%e
day of month, blank padded ( 1..31)
%F
same as %Y-%m-%d
%g
the 2-digit year corresponding to the %V week number
%G
the 4-digit year corresponding to the %V week number
%h
same as %b
%H
hour (00..23)
%I
hour (01..12)
%j
day of year (001..366)
%k
hour ( 0..23)
%l
hour ( 1..12)
%m
month (01..12)
%M
minute (00..59)
%n
a newline
%N
nanoseconds (000000000..999999999)
%p
locale's upper case AM or PM indicator (blank in many locales)
%P
locale's lower case am or pm indicator (blank in many locales)
%r
time, 12-hour (hh:mm:ss [AP]M)
%R
time, 24-hour (hh:mm)
%s
seconds since `00:00:00 1970-01-01 UTC' (a GNU extension)
%S
second (00..60); the 60 is necessary to accommodate a leap ond
sec-
%t
a horizontal tab
%T
time, 24-hour (hh:mm:ss)
%u
day of week (1..7);
%U
week number of year with Sunday as first day of week (00..53)
%V
week number of year with Monday as first day of week (01..53)
%w
day of week (0..6);
%W
week number of year with Monday as first day of week (00..53)
%x
locale's date representation (mm/dd/yy)
%X
locale's time representation (%H:%M:%S)
%y
last two digits of year (00..99)
%Y
year (1970...)
%z
RFC-822 style numeric timezone (-0500) (a nonstandard extension)
%Z
1 represents Monday
0 represents Sunday
time zone (e.g., EDT), or nothing if minable
no
time
zone
is
deter-
By default, date pads numeric fields with zeroes. GNU date recognizes the following modifiers between `%' and a numeric directive. `-' (hyphen) do not pad the field `_' (underscore) pad the field with spaces ENVIRONMENT TZ
Specifies the timezone, unless overridden by command line parameters. If neither is specified, the setting from /etc/localtime is used.
DATE=$(date +%d"-"%B"-"%Y) ERRORDATE=$(date +%m%d0000%y)
================================== 59. SOME NOTES ON LPARS ON POWER5: ================================== This section is about pSeries and AIX only. 59.1 General architecture: -------------------------Before the POWER5 Architecture, you could only use lpars with dedicated cpu's, and disks dedicated to an lpar. As from POWER5 you can use "Micro Partitioning" (assign cpu power in increments of 10% to lpars), you can use "Dynamic LPAR" (reassign resouces to and from lpars without a reboot of lpars) and every resource (SCSI, Netcards etc..) can be virtualized. But DLPAR was also available before Power5. - "Virtual IO Server" (VIOS) must be installed on a partition (Nederlands: de beheer partitie) to enable virtualization services. The other partitions can be AIX52, AIX53, Linux (Redhat, Suse) and i5/OS (AIX52 cannot use virtualized services, so you have to assign dedicated cpu's and disks to that partition). Also, if you do not have VIOS, you can only use the traditional lpars. VIOS provides the IO and ethernet resources to the other lpars. You cannot use VOIS as a usable operating system for applications. It is only used to provide virtual resources to other partitions. You must use the HMC or IVM to assign resources to lpars. - You can use HMC to define partitions and administer partitions (e.g. start, shutdown an lpar) The HMC is a desktop connected with ethernet to the pSeries machine. - You can use Integrated Virtualization Manager (IVM) on systems where an HMC is not used. You can use the local IVM to create and administer lpars. This is a Webbased interface. If you want or need to use IVM, you need to install the VIOS on a nonpartitioned Server first. Then you can use a PC with a LAN connection to the Server, and use the browser interface. - The Partion Load Manager (PLM) makes it possible to re-assign resources from lpars with lower needs (at a time) to lpars who needs higher number of resources (at a time). Policies can be defined on how to manage that.
HMC makes use of "partition profiles", in which you for example, can define for a lpar what the desired and minimum and maximum resource values are. The IVM does not make use of profiles. You can create a "system profile" that lists which partion profiles are to be used when the Server is restarted. Take notice of the fact that the HMC has the lpar configuration information in the form of saved profiles. IVM does not have a commandline interface. You can telnet or ssh from your PC to the lpar for VOIS, and use the "mkvt" command to create a vt to another lpar. In order to use the PLM, you need to have a HMC connected to the managed Server, and you must have an AIX 5.2 ML4 or 5.3 lpar or Server where PLM will be running. You can create a Virtual Ethernet and VLAN's with VID's which enables lpars to communicate with each other through this "internal" network. Server Operating Systems can be placed in LPARS, like AIX 5.2, AIX 5.3, Linux and some others. For AIX, only 5.3 can be a virtual client of virtualized resources. Access to real storage devices is implemented through the Virtual SCSI services, a part of the VIOS. Logical volumes that are created and exported on the Virtual I/O Server partition are shown at the virtual storage client partition as a SCSI disk. The Virtual I/O Server supports logical mirroring and RAID. Logical Volumes created on RAID or JOBD are bootable. The VIOS and PLM is delivered on CD. To enable Power5 Partitioning, you must have obtained a key from IBM. But on the 570 and above, this feature is per default implemented. An AIX 5.2 lpar needs dedicated resources. AIX 5.3 can use all virtualization features.
59.2 Create an AIX logical partition and profile: -------------------------------------------------
logon to HMC Choose "Server and Partition" Choose "Server management" Choose your Server from list Rightclick on Partitions -> Click Create -> Click Logical Partition
59.3 Create a virtual ethernet adapter for AIX: -----------------------------------------------
-
logon to HMC Choose "Server and Partition" Choose "Server management" Choose your Server from list click on Partitions -> rightclick the partitionprofile of the partition who is about to use the virtual ethernet adapter -> Select Dynamic Logical Partitions -> Virtual adapterrescouces -> Add/Remove -> Choose the tab Virtual I/O -> Choose Ethernet -> Create -> A dialog Properties will be displayed -> Fill in the slotnumber, Port Virtual LAN ID (PVID)
chown emcdmeu:emcdgeu 59.4 Installation of PLM: ------------------------Preparation: ============ 1. Put the hostname of every lpar fullyqualified, like lpar1.domain.com lpar2.domain.com 2. If you do not use DNS, put in every hostfile of all lpars, the hostname of the PLM Server, the other hostnames of all other lpars, and the hostname of the HMC, like for example 172.16.0.30 172.16.0.33 172.16.0.100 172.16.0.3
lpar1.domain.com lpar2.domain.com plmserver1.domain.com p5hmc1.domain.com
lpar1 lpar2 plmserver1 p5hmc1
3. Check whether Dynamic partitioning is possible for an lpar # lssrc -a | grep rsct If the deamon IBM.DRM is started, then an active RMC session is present on this lpar with the HMC. RMC stands for Resource Monitoring and Control. In order for DLPAR to work on an lpar, you need to see the following subsystems installed and active: Subsystem ctrmc Resource monitoring and control subsystem IBM.CSMAgentRM is for handshaking between the lpar and hmc IBM.ServiceRM IBM.DRM is for executing the dlpar commands on the lpar IBM.HostRM is for obtaining OS information On the HMC, you can check which lpars are ready for DLPAR with the following command: # lspartition -dlpar
4. You need to have rsh and rcp access for all lpars. If those are not enabled, the do the following: - edit the .rhosts file on any lpar, and type in the lines plmserver1 root plmserver1.domain.com root - chmod 4554 /usr/sbin/rshd - chmod 4554 /usr/bin/rcp - edit /etc/inetd.conf and make sure that this line is not commented out: shell stream tcp6 nowait root /usr/sbin/rshd rshd - Start the inetd deamon again with refresh -s inetd - Test the rsh access from the PLM Server with: rsh root@lpar1 date rsh root@lpar2 date - Create the account "plmuser" on the PLM Server - You need to have an ssh connection between the HMC and the PLM Server. Install Openssh on the PLM Server, and create a ssh user on the HMC. To install Openssh on AIX, you need to have Openssl as well. Create the ssh keys to make communication possible from HMC to PLM Server. Installation: ============= 1. Place the PLM CD in the drive 2. smitty install_latest 3. The following filesets will be installed: plm.license plm.server.rte plm.sysmgt.websm plm.msg.en_US.server plm.msg.en_US.websm IOSCLI: ======= The command line interface of the VIOS is called the IOSCLI. The shell is a restricted shell, for example, you cannot change directories or change your PATH env. variable. You can either work in the traditional mode or interactive mode. - In traditional mode, you start a command with "ioscl", like in # ioscli lsdev -virtual
(to list all virtual devices)
- In interactive mode, you use the aliases for the ioscli subcommands. That is, start the ioscli, and then just type the subcommand, like in
# ioscli # lsdev -virtual You cannot run external commands from interactive mode, like grep or sed. First leave the interactive mode with "exit". To escape from the limitations of ioscli, run "oem_setup_env" and you have access to regular commands.
59.5 Important IOSCLI commands: ------------------------------Only on the VIOS: lsmap command: -------------Displays the mapping between physical, logical, and virtual devices. Syntax lsmap { -vadapter ServerVirtualAdapter | -plc PhysicalLocationCode | -all } lsmap [ -type BackingDeviceType | -net ] lsmap [ -fmt Delimiter ] [ -field FieldNames ] Description The lsmap command displays the mapping between virtual host adapters and the physical devices they are backed to. Given a device name (ServerVirtualAdapter) or physical location code (PhysicalLocationCode) of a server virtual adapter, the device name of each connected virtual target device (child devices), its logical unit number, backing device(s) and the backing devices physical location code is displayed. If the -net flag is specified the supplied device must be a virtual server Ethernet adapter. The -fmt flag divides the output by a user-specified delimiter/character (delimiter). The delimiter can be any non-white space character. This format is provided to facilitate scripting. Examples: - To list all virtual target devices and backing devices mapped to the server virtual SCSI adapter vhode2, type: # lsmap �vadapter vhost2 The system displays a message similar to the following: SVSA Physloc Client Partition ID ------------ -------------------------------------------- -----------------vhost0 U9111.520.10004BA-V1-C2 0x00000004 VTD LUN
vtscsi0 0x8100000000000000
Backing device Physloc
vtd0-1
VTD LUN Backing device Physloc
vtscsi1 0x8200000000000000 vtd0-2
VTD LUN Backing device Physloc
vtscsi2 0x8300000000000000 hdisk2 U787A.001.0397658-P1-T16-L5-L0
- To list the shared Ethernet adapter and backing device mapped to the virtual server Ethernet adapter ent4, type: # lsmap -vadapter ent4 �net The system displays a message similar to the following: SVEA Physloc ------ -------------------------------------------ent4 P2-I1/E1 SEA Backing device Physloc
ent5 ent1 P2-I4/E1
- To list the shared Ethernet adapter and backing device mapped to the virtual server Ethernet adapter ent5 in script format separated by a : (colon), type: # lsmap �vadapter ent5 �fmt ":" The system displays a message similar to the following: ent5:ent8:ent2 - To list all virtual target devices and backing devices, where the backing devices are of type disk or lv, type: # lsmap -all -type disk lv The system displays a message similar to the following: SVSA Physloc Client Partition ID --------------- -------------------------------------------- -----------------vhost0 U9117.570.10D1B0E-V4-C3 0x00000000 VTD LUN Backing device Physloc
vtscsi0 0x8100000000000000 hdisk0 U7879.001.DQD0KN7-P1-T12-L3-L0
VTD LUN Backing device Physloc
vtscsi2 0x8200000000000000 lv04
SVSA Physloc Client Partition ID --------------- -------------------------------------------- -----------------vhost1 U9117.570.10D1B0E-V4-C4 0x00000000 VTD LUN Backing device Physloc
vtscsi1 0x8100000000000000 lv03
mkvdev command: --------------Purpose Adds a virtual device to the system. Syntax To create a virtual target device: mkvdev [ -f ] {-vdev TargetDevice | -dplc TDPhysicalLocatonCode } { -vadapter VirtualServerAdapter | -aplc VSAPhysicalLocationCode} [ -dev DeviceName ] - To create a Shared Ethernet Adapter: # mkvdev -sea TargetDevice -vadapter VirtualEthernetAdapter... -default DefaultVirtualEthernetAdapter -defaultid SEADefaultPVID [ -attr Attribute=Value [ Attribute=Value... ] ] - To create an Link Aggregation adapter: # mkvdev -lnagg TargetAdapter... [ -attr Attribute=Value [ Attribute=Value... ] ] - To create a VLAN Ethernet adapter: # mkvdev -vlan TargetAdapter -tagid TagID Description The mkvdev command creates a virtual device. The name of the virtual device will be automatically generated and assigned unless the -dev DeviceName flag is specified, in which case DeviceName will become the device name. If the -lnagg flag is specified, a Link Aggregation or IEEE 802.3 Link Aggregation (automatic Link Aggregation) device is created. To create an IEEE 802.3 Link Aggregation set the mode attribute to 8023ad. If the -sea flag is specified, a Shared Ethernet Adapter is created. The TargetDevice may be a Link Aggregation adapter (note, however, that the VirtualEthernetAdapter may not be Link Aggregation adapters). The default virtual Ethernet adapter, DefaultVirtualEthernetAapter, must also be included as one of the virtual Ethernet adapters, VirtualEthernetAdapter. The -vlan flag is used to create a VLAN device and the -vdev flag creates a virtual target device which maps the VirtualServerAdapter to the TargetDevice.
If the backing device that is specified by the -vdev or -dplc flags is already in use, an error will be returned unless the -f flag is also specified. Examples: --------Example 1: ---------Suppose you have VIOS running, and you want to create three AIX53 client lpars, LPS1, LPS2 and LPS3. Suppose from VIOS, you have created a number of virtual scsi controllers: - Listing virtuele scsi controllers. # lsdev �virtual You will see a listing of virtual scsi controllers: vhost0, vhost1, en vhost2 - From VIOS, create Volume Groups. Suppose hdisk2, hdisk3, and hdisk4 are not yet assigned, and thus are free to create VG's. # mkvg �f �vg rootvg_lpar1 # mkvg �f �vg rootvg_lpar2 # mkvg �f �vg rootvg_lpar3
hdisk2 hdisk3 hdisk4
- Now create LV�s. # mklv �lv rootvg_lps1 rootvg_lpar1 15G # mklv �lv rootvg_lps2 rootvg_lpar2 15G # mklv �lv rootvg_lps3 rootvg_lpar3 15G Note: this # mklv �lv # mklv �lv # mklv �lv
could also be have done: rootvg_lps1 rootvg_lpar1 15G rootvg_lps2 rootvg_lpar1 15G rootvg_lps3 rootvg_lpar1 15G
The lv�s rootvg_lps1, rootvg_lps2, and rootvg_lps3 will become the rootvg�s for the AIX53 client partitions. - Create mappings. # mkvdev �vdev rootvg_lps1 �vadapter vhost0 # mkvdev �vdev rootvg_lps2 �vadapter vhost1 # mkvdev �vdev rootvg_lps3 �vadapter vhost2 vhostx = LV \ vhosty = LV -> VG {disk(s)} vhostz = LV /
More examples: -------------- From a AIX 5.3 client partition run the lsdev command, like # lsdev -Cc disk -s vscsi hdisk2 Available Virtual SCSI Disk Drive # lscfg -vpl hdisk2 hdisk2 11.520.10DDEDC-V3-C5-T1-L810000000 Virtual SCSI Disk Drive root@zd110l06:/root#lscfg -vpl hdisk2 hdisk2 U9117.570.65B61FE-V6-C7-T1-L810000000000 Drive
Virtual SCSI Disk
PLATFORM SPECIFIC Name: disk Node: disk Device Type:
block
- To create the mapping of a virtual scsi adapter vhost0, to a logical volume (rootvg_nim) that an AIX partition will use later as a disk, use # mkvdev -vdev rootvg_nim -vadapter vhost0 -dev vnim - To create a virtual target device that maps the logical volume lv20 as a virtual disk for a client partition hosted by the vhost0 virtual server adapter, type: # mkvdev -vdev lv20 �vadapter vhost0 The system displays a message similar to the following: vtscsi0 available - To create a virtual target device that maps the physical volume hdisk6 as a virtual disk for a client partition served by the vhost2 virtual server adapter, type: # mkvdev -vdev hdisk6 �vadapter vhost2 The system displays a message similar to the following: vtscsi1 available - To create a Shared Ethernet Adapter that maps the physical Ethernet adapter "ent4" as a virtual Ethernet adapter for the client partitions served by the virtual Ethernet adapters ent6, ent7, and ent9, using ent6 as the default adapter and 8 as the default ID, type: # mkvdev �sea ent4 �vadapter ent6,ent7,ent9 �default ent6 -defaultid 8 The system displays a message similar to the following: ent10 available (which is the sea)
Remember how to create a SEA on the VIOS: - To create a Shared Ethernet Adapter: # mkvdev -sea PhysTargetDevice -vadapter VirtualEthernetAdapter... -default DefaultVirtualEthernetAdapter -defaultid SEADefaultPVID [ -attr Attribute=Value [ Attribute=Value... ] ] - To create an automatic Link Aggregation with primary adapters ent4 and ent5 and backup adapter ent6, type: # mkvdev �lnagg ent4,ent5 �attr backup_adapter=ent6 mode=6023ad The system displays a message similar to the following: ent10 available
lsdev command (on VIOS): -----------------------The lsdev command on a VIO Server has a bit of a different syntax compared to a regular AIX partition. Commands like "lsdev -Cc tape" does not work on VIO. Instead, you have a limited number of parameters you can give to the lsdev command. Usage: lsdev [-type DeviceType ...] [-virtual] [-state DeviceState] [-field FieldName ...] [-fmt delimiter] lsdev {-dev DeviceName | -plc PhysicalLocationCode} [-child] [-field FieldName ...] [-fmt delimiter] lsdev {-dev DeviceName | -plc PhysicalLocationCode} [-parent | -attr [Attribute] | -range Attribute | -slot | -vpd] lsdev -slots lsdev -vpd So normally you will use the following on a VIO Server: lsdev -dev [options]
like "lsdev -dev" "lsdev -dev " "lsdev -dev -vpd"
lsdev -slots lsdev -vpd lsdev -virtual
>> Examples of Usage of lsdev on VIOS: # tn vioserver1 Trying...
Connected to vioserver1. Escape character is '^T'. telnet (vioserver1) IBM Virtual I/O Server login: padmin padmin's Password: Last unsuccessful login: Mon Sep 24 04:25:04 CDT 2007 on /dev/vty0 Last login: Wed Nov 21 05:10:29 CST 2007 on /dev/pts/0 from starboss.antapex.org Suppose you have logged on as padmin on a VIO server. Now you try the following commands to retrieve information of the system: $ lsdev -dev fcs* name fcs0 fcs1 fcs2 fcs3 $
status Available Available Available Available
description FC FC FC FC
Adapter Adapter Adapter Adapter
lsdev -dev fcs0
name fcs0
status Available
description FC Adapter
$ lsdev -dev fcs* -vpd|grep Z8 Device Specific.(Z8)........20000000C95CDDEE Device Specific.(Z8)........20000000C95C88F1 Device Specific.(Z8)........20000000C95AB49A Device Specific.(Z8)........20000000C95CDBFD
$ lsdev -dev fcs0 -vpd fcs0
U7879.001.DQDTZXG-P1-C6-T1
FC Adapter
Part Number.................03N7069 EC Level....................A Serial Number...............1B64505069 Manufacturer................001B Feature Code/Marketing ID...280B FRU Number.................. 03N7069 Device Specific.(ZM)........3 Network Address.............10000000C95CDBFD ROS Level and ID............02881955 Device Specific.(Z0)........1001206D Device Specific.(Z1)........00000000 Device Specific.(Z2)........00000000 Device Specific.(Z3)........03000909 Device Specific.(Z4)........FF801413
Device Device Device Device Device Device Device Device
Specific.(Z5)........02881955 Specific.(Z6)........06831955 Specific.(Z7)........07831955 Specific.(Z8)........20000000C95CDBFD Specific.(Z9)........TS1.91A5 Specific.(ZA)........T1D1.91A5 Specific.(ZB)........T2D1.91A5 Specific.(YL)........U7879.001.DQDTZXG-P1-C6-T1
PLATFORM SPECIFIC Name: fibre-channel Model: LP10000 Node: fibre-channel@1 Device Type: fcp Physical Location: U7879.001.DQDTZXG-P1-C6-T1
$ lsdev -slots # Slot U7311.D11.655157B-P1-C4 U7311.D11.655157B-P1-C5 U7311.D11.655158B-P1-C6 U7311.D20.655159B-P1-C04 U7879.001.DQDTPAK-P1-C5 U7879.001.DQDTZXG-P1-C6 U7879.001.DQDTPAK-P1-T12 U9117.570.65B61FE-V17-C0 U9117.570.65B61FE-V17-C11 U9117.570.65B61FE-V17-C12 .. U9117.570.65B61FE-V17-C324
Description Logical I/O Logical I/O Logical I/O Logical I/O Logical I/O Logical I/O Logical I/O Virtual I/O Virtual I/O Virtual I/O
Slot Slot Slot Slot Slot Slot Slot Slot Slot Slot
Virtual I/O Slot
Device(s) pci12 ent0 ent1 pci13 fcs2 pci14 fcs3 pci9 sisscsia0 pci10 fcs1 pci8 fcs0 pci11 sisscsia1 vsa0 vhost0 vhost1 vhost33
$ lsdev -type disk name hdisk0 hdisk1 .. hdisk10 hdisk11 hdisk12 .. hdisk35 vg01sanl02 vg01sanl03 .. vg04sanl14 vg05sanl14 vzd110l01 vzd110l02 .. vzd110l14
status Available Available
16 Bit LVD SCSI Disk Drive 16 Bit LVD SCSI Disk Drive
description
Available Available Available
16 Bit LVD SCSI Disk Drive SAN Volume Controller MPIO Device SAN Volume Controller MPIO Device
Available Available Available
SAN Volume Controller MPIO Device Virtual Target Device - Disk Virtual Target Device - Disk
Available Available Available Available
Virtual Virtual Virtual Virtual
Available
Virtual Target Device - Logical Volume
Target Target Target Target
Device Device Device Device
-
Disk Disk Logical Volume Logical Volume
$ lsdev -virtual name vhost0 vhost1 vhost2 .. vhost33 vsa0 vg01sanl02 vg01sanl03 .. vg05sanl14 .. vzd110l01 vzd110l14 $ lsdev -vpd
status Available Available Available
Virtual SCSI Server Adapter Virtual SCSI Server Adapter Virtual SCSI Server Adapter
description
Available Available Available Available
Virtual SCSI Server Adapter LPAR Virtual Serial Adapter Virtual Target Device - Disk Virtual Target Device - Disk
Available
Virtual Target Device - Disk
Available Available
Virtual Target Device - Logical Volume Virtual Target Device - Logical Volume
# gives a huge list of output
INSTALLED RESOURCE LIST WITH VPD The following resources are installed on your machine. Model Architecture: chrp Model Implementation: Multiple Processor, PCI bus sys0 System Object sysplanar0 System Planar vio0 Virtual I/O Bus vhost33 U9117.570.65B61FE-V17-C324 Virtual SCSI Server Adapter Device Specific.(YL)........U9117.570.65B61FE-V17-C324 vg05sanl14 U9117.570.65B61FE-V17-C324-L2 Virtual Target Device - Disk vg03sanl14 U9117.570.65B61FE-V17-C324-L1 Virtual Target Device - Disk vhost32 U9117.570.65B61FE-V17-C323 Virtual SCSI Server Adapter Device Specific.(YL)........U9117.570.65B61FE-V17-C323 vg04sanl14 U9117.570.65B61FE-V17-C323-L2 Virtual Target Device - Disk vg03sanl13 U9117.570.65B61FE-V17-C323-L1 Virtual Target Device - Disk vhost31 U9117.570.65B61FE-V17-C224 Virtual SCSI Server Adapter Device Specific.(YL)........U9117.570.65B61FE-V17-C224 vg02sanl14 U9117.570.65B61FE-V17-C224-L1 Virtual Target Device - Disk
vhost30 U9117.570.65B61FE-V17-C223 Virtual SCSI Server Adapter Device Specific.(YL)........U9117.570.65B61FE-V17-C223 .. .. vg01sanl05 U9117.570.65B61FE-V17-C115-L1 Virtual Target Device - Disk vhost15 U9117.570.65B61FE-V17-C113 Virtual SCSI Server Adapter Device Specific.(YL)........U9117.570.65B61FE-V17-C113 vg04sanl03 U9117.570.65B61FE-V17-C113-L3 Virtual Target Device - Disk vg03sanl03 U9117.570.65B61FE-V17-C113-L2 Virtual Target Device - Disk vg01sanl03 U9117.570.65B61FE-V17-C113-L1 Virtual Target Device - Disk vhost14 U9117.570.65B61FE-V17-C112 Virtual SCSI Server Adapter Device Specific.(YL)........U9117.570.65B61FE-V17-C112 .. .. Device Specific.(YL)........U9117.570.65B61FE-V17-C0 vty0 U9117.570.65B61FE-V17-C0-L0 Asynchronous Terminal pci6 U7311.D11.655158B-P1 PCI Bus Device Specific.(YL)........U7311.D11.655158B-P1 pci14 PCI Bus
U7311.D11.655158B-P1 Device Specific.(YL)........U7311.D11.655158B-P1
fcs3 FC Adapter
U7311.D11.655158B-P1-C6-T1
Part Number.................03N7069 EC Level....................A Serial Number...............1B64504CA3 Manufacturer................001B Feature Code/Marketing ID...280B FRU Number.................. 03N7069 Device Specific.(ZM)........3 Network Address.............10000000C95CDDEE ROS Level and ID............02881955 Device Specific.(Z0)........1001206D Device Specific.(Z1)........00000000 Device Specific.(Z2)........00000000 Device Specific.(Z3)........03000909 Device Specific.(Z4)........FF801413 Device Specific.(Z5)........02881955 Device Specific.(Z6)........06831955
Device Device Device Device Device Device
Specific.(Z7)........07831955 Specific.(Z8)........20000000C95CDDEE Specific.(Z9)........TS1.91A5 Specific.(ZA)........T1D1.91A5 Specific.(ZB)........T2D1.91A5 Specific.(YL)........U7311.D11.655158B-P1-C6-T1
fcnet3 U7311.D11.655158B-P1-C6-T1 Fibre Channel Network Protocol Device fscsi3 U7311.D11.655158B-P1-C6-T1 FC SCSI I/O Controller Protocol Device pci5 U7311.D11.655157B-P1 PCI Bus Device Specific.(YL)........U7311.D11.655157B-P1
Other Example: ============== See the differences between 1 and 2: 1. LPAR using only storage via VIO root@zd110l06:/root#lspv hdisk0 00cb61fe223c3926 hdisk1 00cb61fe2360b1b7 hdisk2 00cb61fe3339af9f hdisk3 00cb61fe3339b066
rootvg rootvg appsvg datavg
root@zd110l06:/root#lsdev hdisk0 Available Virtual hdisk1 Available Virtual hdisk2 Available Virtual hdisk3 Available Virtual
-Cc disk -s vscsi SCSI Disk Drive SCSI Disk Drive SCSI Disk Drive SCSI Disk Drive
root@zd110l06:/root#lsdev hdisk0 Available Virtual hdisk1 Available Virtual hdisk2 Available Virtual hdisk3 Available Virtual
-Cc disk SCSI Disk SCSI Disk SCSI Disk SCSI Disk
active active active active
Drive Drive Drive Drive
root@zd110l06:/root#lsdev -Cc adapter ent0 Available Virtual I/O Ethernet Adapter (l-lan) ent1 Available 02-08 2-Port 10/100/1000 Base-TX PCI-X Adapter ent2 Available 02-09 2-Port 10/100/1000 Base-TX PCI-X Adapter ent3 Available 03-08 2-Port 10/100/1000 Base-TX PCI-X Adapter ent4 Available 03-09 2-Port 10/100/1000 Base-TX PCI-X Adapter vsa0 Available LPAR Virtual Serial Adapter vscsi0 Available Virtual SCSI Client Adapter vscsi1 Available Virtual SCSI Client Adapter vscsi2 Available Virtual SCSI Client Adapter vscsi3 Available Virtual SCSI Client Adapter vscsi4 Available Virtual SCSI Client Adapter vscsi5 Available Virtual SCSI Client Adapter
(14108902) (14108902) (14108902) (14108902)
2. LPAR using storage via VIO and dedicated FC cards
[email protected]:/root#lspv hdisk0 00cb61fe09fe92bd hdisk1 00cb61fe0a47a802 hdisk2 00cb61fe336bc95b hdisk3 00cb61fe321664d1
rootvg rootvg appsvg datavg
active active active active
[email protected]:/root#lsdev -Cc disk -s vscsi hdisk0 Available Virtual SCSI Disk Drive hdisk1 Available Virtual SCSI Disk Drive
[email protected]:/root#lsdev -Cc disk hdisk0 Available Virtual SCSI Disk Drive hdisk1 Available Virtual SCSI Disk Drive hdisk2 Available 02-08-02 SAN Volume Controller MPIO Device hdisk3 Available 02-08-02 SAN Volume Controller MPIO Device
[email protected]:/root#lsdev -Cc adapter ent0 Available Virtual I/O Ethernet Adapter (l-lan) fcs0 Available 02-08 FC Adapter fcs1 Available 03-08 FC Adapter vsa0 Available LPAR Virtual Serial Adapter vscsi0 Available Virtual SCSI Client Adapter vscsi1 Available Virtual SCSI Client Adapter
>> More on lsdev on a VIOS: Purpose Displays Virtual I/O Server devices and their characteristics. Syntax To list devices lsdev [ -type DeviceType... ] [ -virtual ] [ -field FieldName... ] [ -fmt Delimiter ] [-state State ] To display information about a specific device: lsdev { -dev DeviceName | -plc PhysicalLocationCode } [ -child ] [ -field FieldName... ] [ -fmt Delimiter ] lsdev { -dev DeviceName | -plc PhysicalLocationCode } [ -attr [ Attribute ] | -range Attribute | -slot | -vpd | -parent] lsdev -vpd lsdev -slots
Description: The lsdev command displays information about devices in the Virtual I/O Server. If no flags are specified, a list of all devices, both physical and virtual, in the Virtual I/O Server is displayed. To list devices, both physical and virtual, of a specific type use the -type DeviceType flag. Use the -virtual flag to list only virtual devices. Combining both the -type and -virtual flags will list the virtual devices of the specified type. To display information about a specific device, use the -dev DeviceName or -plc PhysicalLocationCode. Use either the -child, -parent, -attr, -range, -slot, or -vpd flag to specify what type of information is displayed. If none of these flags are used, the name, status, and description of the device will be displayed. Using the -vpd flag, without specifying a device, displays platform-specific information for all devices. Examples - To list all virtual adapters and display the name and status fields, type: # lsdev �type adapter �virtual �field name status The system displays a message similar to the following: name status vhost0 vhost1 vhost2 ent6 ent7 ent8 ent9
Available Available Available Available Available Available Available
- To list all devices of type disk and display the name and physical location fields, type: # lsdev �type disk �field name physloc The system displays a message similar to the following: name physloc hdisk0 hdisk1 hdisk2 hdisk3 hdisk4 hdisk5 hdisk6 hdisk7 hdisk8
U9111.520.10004BA-T15-L5-L0 U9111.520.10004BA-T15-L8-L0 U9111.520.10004BA-T16-L5-L0 U9111.520.10004BA-T16-L8-L0 UTMP0.02E.00004BA-P1-C4-T1-L8-L0 UTMP0.02E.00004BA-P1-C4-T2-L8-L0 UTMP0.02F.00004BA-P1-C8-T2-L8-L0 UTMP0.02F.00004BA-P1-C4-T2-L8-L0 UTMP0.02F.00004BA-P1-C4-T2-L11-L0
vtscsi0 vtscsi1 vtscsi2 vtscsi3 vtscsi4 vtscsi5
U9111.520.10004BA-V1-C2-L1 U9111.520.10004BA-V1-C3-L1 U9111.520.10004BA-V1-C3-L2 U9111.520.10004BA-V1-C4-L1 U9111.520.10004BA-V1-C4-L2 U9111.520.10004BA-V1-C5-L1
- To display the parent of a devices, type: # lsdev �dev hdisk0 -parent The system displays a message similar to the following: parent scsi0 - To display all I/O slots that are not hot-pluggable but can have DLPAR operations performed on them, type: # lsdev -slots The system displays a message similar to the following: U787A.001.DNZ00Y1-P1-C1 Logical I/O Slot pci4 sisscsia0 U787A.001.DNZ00Y1-P1-T5 Logical I/O Slot pci3 ent0 ent1 U787A.001.DNZ00Y1-P1-T7 Logical I/O Slot pci2 usbhc0 usbhc1 U9111.520.10DFD8C-V2-C0 Virtual I/O Slot vsa0 U9111.520.10DFD8C-V2-C2 Virtual I/O Slot vhost0 U9111.520.10DFD8C-V2-C4 Virtual I/O Slot Unknown - The client partition accesses its assigned disks through a virtual SCSI client adapter. The virtual scsi client adapter sees standard scsi devices and LUNs through this virtual adapter. The commands in the following example show how the disks appear on a AIX 53 partition: # lsdev -Cc disk -s vscsi hdisk2 Available Virtual SCSI Disk Drive # lscfg -vpl hdisk2 hdisk2 111.530.10DDEDC-V3-C5-T1
Virtual SCSI Disk Drive
- To configure an optical device as a virtual SCSI device is the same as configuring a disk or logical volume into a vscsi device. Using either a new or previously defined vhost adapter with the client partition, run the following command: # mkvdev -vdev cd0 -vadapter vhost0 vtopt0 Available Virtual Target Device - Optical Media On the client partition, run the cfmgr command and a cd0 device will be configured for use. Mounting the CD device is now possible, as is using the mkdvd command.
rmvdev command: --------------Purpose To remove the connection between a physical device and its associated virtual SCSI adapter. Syntax rmvdev [ -f ] { -vdev TargetDevice | -vtd VirtualTargetDevice } [-rmlv] Description The rmdev command removes the connection between a physical device and its associated virtual SCSI adapter. The connection can be identified by specifying the backing (physical) device or the virtual target device. If the connection is specified by the device name and there are multiple connections between the physical device and virtual SCSI adapters and error is returned unless the -f flag is also specified. If -f is included then all connections associated with the physical device are removed. If the backing (physical) device is a logical volume and the -rmlv flag is specified, then logical volume will be removed as well. Example: # rmvdev -dev vhost0 -recursive Example: how to remove a dynamically allocated i/o slot in a DLPAR in IBM AIX Description To remove a dynamically allocated I/O slot (must be a desired component) from a partition on a P-series IBM server partition: 1) Find the slot you wish to remove from the partition: # lsslot -c slot # Slot Description Device(s) U1.5-P2/Z2 Logical I/O Slot pci15 scsi2 U1.9-P1-I8 Logical I/O Slot pci13 ent0 U1.9-P1-I10 Logical I/O Slot pci14 scsi0 scsi1 In our case, it is pci14. 2) Delete the PCI adapter and all of its children in AIX before removal: # rmdev -l pci14 -d -R cd0 deleted rmt0 deleted scsi0 deleted
scsi1 deleted pci14 deleted 3) Now, you can remove the PCI I/O slot device using the HMC: a) Log in to the HMC b) Select "Server and Partition", and then "Server Management" c) Select the appropriate server and then the appropriate partition d) Right click on the partition name, and then on "Dynamic Logical Partitioning" e) In the menu, select "Adapters" f) In the newly created popup, select the task "Remove resource from this partition" g) Select the appropriate adapter from the list (only desired one will appear) h) Select the "OK" button i) You should have a popup window which tells you if it was successful. Example lsslot -c slot; rmdev -l pci14 -d -R mkdvd command: -------------Examples of the mkdvd command: To generate a bootable system backup to the DVD-R device named /dev/cd1, enter: # mkdvd -d /dev/cd1 To generate a system backup to the DVD-R or DVD-RAM device named /dev/cd1, enter: # mkdvd -d /dev/cd1 To generate a non-bootable volume group backup of the volume group myvg to /dev/cd1, enter: # mkdvd -d /dev/cd1 -v myvg Note: All savevg backup images are non-bootable. To generate a non-bootable system backup, but stop mkdvd before the DVD is created and save the final images to the /mydata/my_cd file system, and create the other mkdvd file systems in myvg, enter: # mkdvd -B -I /mydata/my_cd -V myvg -S To create a DVD or DVD that duplicates an existing directory structure /mycd/a
/mycd/b/d /mycd/c/f/g use the following command: # mkdvd -r /mycd -d /dev/cd1 After mounting with mount -o ro /dev/cd1 /mnt, cd to /mnt; a find . -print command displays: ./a ./b ./b/d ./c ./c/f ./c/f/g lparstat command: ----------------From the AIX prompt in a lpar, you can enter the lparstat -i command to get a list of names and resources like, for example, if the partition is capped or uncapped etc.. # lparstat -i cfgdev command: --------------On the VIOS partition, run the "cfgdev" command to rebuild the list of visible devices. This is neccessary after you have created the partition and have added virtual controllers. The virtual SCSI server adapters are now available to the VIOS. The name of these adapters are vhostx where x is a number assigned by the system. Use the following command to make sure your adapters are available: $ lsdev -virtual name status description ent2 Available Virtual Ethernet Adapter vhost0 Available Virtual SCSI Server Adapter vhost1 Available Virtual SCSI Server Adapter vhost2 Available Virtual SCSI Server Adapter vhost3 Available Virtual SCSI Server Adapter vsa0 Available LPAR Virtual Serial Adapter lspath command: --------------lspath Command Purpose Displays information about paths to a MultiPath I/O (MPIO) capable device. Syntax lspath [ -dev DeviceName ] [ -pdev Parent ] [ -status Status ] [ -conn
Connection ] [ -field FieldName ] [ -fmt Delimiter ] lspath -dev DeviceName -pdev Parent [ -conn Connection ] -lsattr [ -attr Attribute... ] lspath -dev DeviceName -pdev Parent [ -conn Connection ] -range -attr Attribute Description The lspath command displays one of three types of information about paths to an MPIO capable device. It either displays the operational status for one or more paths to a single device, or it displays one or more attributes for a single path to a single MPIO capable device. The first syntax shown above displays the operational status for one or more paths to a particular MPIO capable device. The second syntax displays one or more attributes for a single path to a particular MPIO capable device. Finally, the third syntax displays the possible range of values for an attribute for a single path to a particular MPIO capable device. Displaying Path Status with the lspath Command When displaying path status, the set of paths to display is obtained by searching the device configuration database for paths that match the following criteria: The target device name matches the device specified with the -dev flag. If the -dev flag is not present, then the target device is not used in the criteria. The parent device name matches the device specified with the -pdev flag. If the -pdev flag is not present, then parent is not used in the criteria. The connection matches the connection specified with the -conn flag. If the -conn flag is not present, then connection is not used in the criteria. The path status matches status specified with the -status flag. If the -status flag is not present, the path status is not used in the criteria. If none of the -dev, -pdev, -conn, or -status flags are specified, then all paths known to the system are displayed. By default, this command will display the information in columnar form. When no flags are specified that qualify the paths to display, the format of the output is: status device parent Possible values that can appear for the status column are: -enabled Indicates that the path is configured and operational. It will be considered when paths are selected for IO. -disabled Indicates that the path is configured, but not currently operational. It has been manually disabled and will not be considered when paths are selected for IO. -failed Indicates that the path is configured, but it has had IO failures that have rendered it unusable. It will not be considered when paths are selected for IO.
-defined Indicates that the path has not been configured into the device driver. -missing Indicates that the path was defined in a previous boot, but it was not detected in the most recent boot of the system. -detected Indicates that the path was detected in the most recent boot of the system, but for some reason it was not configured. A path should only have this status during boot and so this status should never appear as a result of the lspath command. Displaying Path Attributes with the lspath Command When displaying attributes for a path, the path must be fully qualified. Multiple attributes for a path can be displayed, but attributes belonging to multiple paths cannot be displayed in a single invocation of the lspath command. Therefore, in addition to the -lsattr, -dev, and -pdev flags, the -conn flags are required to uniquely identify a single path. For example: if only one path between a device and a specific parent, the -conn flag is not required if there are multiple paths between a device and a specific parent, the -conn flag is required Furthermore, the -status flag is not allowed. By default, this command will display the information in columnar form. attribute value description user_settableFlags -attr Attribute Identifies the specific attribute to list. The 'Attribute' is the name of a path specific attribute. When this flag is provided, only the identified attribute is displayed. Multiple instances of this flag may be used to list multiple attributes. If this flag is not specified at all, all attributes associated with the identified path will be listed. -lsattr Displays the attribute names, current values, descriptions, and usersettable flag values for a specific path. -dev Name Specifies the logical device name of the target device whose path information is to be displayed. -field FieldNames Specifies the list of fields to display. The following fields are supported: status Status of the path name Name of the device parent Name of the parent device conn Path connection. -fmt Delimiter Specifies a delimiter character to separate output fields. -pdev Parent Indicates the logical device name of the parent device of the path(s) to be displayed. -range Displays the legal values for an attribute name. The -range flag displays the list attribute values in a vertical column as follows: Value1 Value2 . . ValueN The -range flag displays the range attribute values as x...n(+i) where x is the
start of the range, n is the end of the range, and i is the increment. -status Status The -status Status flag indicates the status to use in qualifying the paths to be displayed. When displaying path information, the allowable values for this flag are: enabled Display paths that are enabled for MPIO path selection. disabled Display paths that are disabled from MPIO path selection. failed Display paths that are failed due to IO errors. available Display paths whose path_status is PATH_AVAILABLE (that is, paths that are configured in the system, includes enabled, disabled, and failed paths). defined Display paths whose path_status is PATH_DEFINED. missing Display paths whose path_status is PATH_MISSING. -conn Connection Indicates the connection information to use in qualifying the paths to be displayed. Exit Status Return code Description 1 Invalid status value. Examples: To display, without column headers, the set of paths whose operational status is disabled, enter: # lspath -status disabled The system will display a message similar to the following: disabled disabled disabled disabled
hdisk1 hdisk2 hdisk23 hdisk25
scsi1 scsi1 scsi8 scsi8
To display the set of paths whose operational status is failed, enter: # lspath -status failed The system will display a message similar to the following: failed hdisk1 scsi1 failed hdisk2 scsi1 failed hdisk23 scsi8 failed hdisk25 scsi8 If the target device is a SCSI disk, to display all attributes for the path to parent scsi0 at connection 5,0, use the command: # lspath -dev hdisk10 -pdev scsi0 -conn "5,0" -lsattr The system will display a message similar to the following: weight
1
Order of path failover selection
true
To display the status of all paths to hdisk1 with column headers and I/O counts, type: # lspath -l hdisk1 -H The system displays a message similar to the following: STATUS enabled disabled missing
PARENT scsi0 scsi1 scsi2
(4) (0)
CONNECTION 5,0 5,0 5,0
To display without column headers, the set of paths whose operational status is disabled, type: # lspath -s disabled The system displays a message similar to the following: hdisk1 hdisk2 hdisk23 hdisk25
scsi1 scsi1 scsi8 scsi8
5, 6, 3, 4,
0 0 0 0
chpath command: --------------chpath Command Purpose Changes the operational status of paths to an MultiPath I/O (MPIO) capable device, or changes an attribute associated with a path to an MPIO capable device. Syntax chpath -l Name -s OpStatus [ -p Parent ] [ -w Connection ] chpath -l Name -p Parent [ -w Connection ] [ -P ] -a Attribute=Value [ -a Attribute=Value ... ] chpath -h Description The chpath command either changes the operational status of paths to the specified device (the -l Name flag) or it changes one, or more, attributes associated with a specific path to the specified device. The required syntax is slightly different depending upon the change being made. The first syntax shown above changes the operational status of one or more paths to a specific device. The set of paths to change is obtained by taking the set of paths which match the following criteria: The target device matches the specified device. The parent device matches the specified parent (-p Parent), if a parent is
specified. The connection matches the specified connection (-w Connection), if a connection is specified. The path status is PATH_AVAILABLE. The operational status of a path refers to the usage of the path as part of MPIO path selection. The value of enable indicates that the path is to be used while disable indicates that the path is not to be used. It should be noted that setting a path to disable impacts future I/O, not I/O already in progress. As such, a path can be disabled, but still have outstanding I/O until such time that all of the I/O that was already in progress completes. As such, if -s disable is specified for a path and I/O is outstanding on the path, this fact will be output. Disabling a path affects path selection at the device driver level. The path_status of the path is not changed in the device configuration database. The lspath command must be used to see current operational status of a path. The second syntax shown above changes one or more path specific attributes associated with a particular path to a particular device. Note that multiple attributes can be changed in a single invocation of the chpath command; but all of the attributes must be associated with a single path. In other words, you cannot change attributes across multiple paths in a single invocation of the chpath command. To change attributes across multiple paths, separate invocations of chpath are required; one for each of the paths that are to be changed. Flags -a Attribute=Value Identifies the attribute to change as well as the new value for the attribute. The Attribute is the name of a path specific attribute. The Value is the value which is to replace the current value for the Attribute. More than one instance of the -a Attribute=Value can be specified in order to change more than one attribute. -h Displays the command usage message. -l Name Specifies the logical device name of the target device for the path(s) affected by the change. This flag is required in all cases. -p Parent Indicates the logical device name of the parent device to use in qualifying the paths to be changed. This flag is required when changing attributes, but is optional when change operational status. -P Changes the path's characteristics permanently in the ODM object class without actually changing the path. The change takes affect on the path the next time the path is unconfigured and then configured (possibly on the next boot). -w Connection Indicates the connection information to use in qualifying the paths to be changed. This flag is optional when changing operational status. When changing attributes, it is optional if the device has only one path to the indicated parent. If there are multiple paths from the parent to the device, then this flag is required to identify the specific path being changed. -s OpStatus Indicates the operational status to which the indicated paths should be changed. The operational status of a path is maintained at the device driver level. It determines if the path will be considered when performing path selection.The allowable values for this flag are: enable Mark the operational status as enabled for MPIO path selection. A path with this status will be considered for use when performing path selection. Note that enabling a path is the only way to recover a path from a failed condition. disable Mark the operational status as disabled for MPIO path selection. A path with this status will not be considered for use when performing path selection. This flag is required when changing operational status. When used in conjunction with the -a Attribute=Value flag, a usage error is generated.
Security Privilege Control: Only the root user and members of the system group have execute access to this command. Auditing Events: Event Information DEV_Change The chpath command line. Examples To disable the paths between scsi0 and the hdisk1 disk device, enter: # chpath -l hdisk1 -p scsi0 -s disable The system displays a message similar to one of the following: paths disabled or some paths enabled The first message indicates that all PATH_AVAILABLE paths from scsi0 to hdisk1 have been successfully enabled. The second message indicates that only some of the PATH_AVAILABLE paths from scsi0 to hdisk1 have been successfully disabled. 59.5 Example of usage of virtualization commands: ------------------------------------------------Suppose we have the following lpar: # uname -L 12 zd110l12 # oslevel -r 5300-05 # lsdev -Cc disk hdisk0 Available Virtual SCSI Disk Drive hdisk1 Available Virtual SCSI Disk Drive >>.
1 Start Install Now with Default Settings 2 Change/Show Installation Settings and Install 3 Start Maintenance Mode for System Recovery 88 Help ? 99 Previous Menu >>> Choice [1]: 2 __
Step 4. Verify or Change BOS Installation Settings, as follows:
Type 1 in the Choice field to select the System Settings option.
Type 1 for New and Complete Overwrite in the Choice field and press Enter. Note: The installation methods available depend on whether your disk has a previous version of AIX installed. When the Change Disk(s) screen displays, you can change the destination disk for the installation. If the default shown is correct, type 0 in the Choice field and press Enter. To change the destination disk, do the following: Type the number for each disk you choose in the Choice field and press Enter. Do not press Enter a final time until you have finished selecting all disks. If you must deselect a disk, type its number a second time and press Enter. When you have finished selecting the disks, type 0 in the Choice field and press Enter. The Installation and Settings screen displays with the selected disks listed under System Settings. If needed, change the primary language environment. Use the following steps to change the primary language used by this installation to select the language and cultural convention you want to use. Note: Changes to the primary language environment do not take effect until after the Base Operating System Installation has completed and your system is rebooted. Type 2 in the Choice field on the Installation and Settings screen to select the Primary Language Environment Settings option. Select the appropriate set of cultural convention, language, and keyboard options. Most of the options are a predefined combination, however, you can define your own combination of options. To choose a predefined Primary Language Environment, type that number in the Choice field and press Enter. Monitoring VIOS: ---------------Note 1: ------With Virtual I/O Server fix pack 8.1.0, you can install and configure the "IBM Tivoli Monitoring System Edition for System p� agent" on the Virtual I/O Server. IBM Tivoli Monitoring System Edition for System p enables you to monitor the health and availability of multiple IBM System p servers (including the Virtual I/O Server) from the Tivoli Enterprise� Portal. IBM Tivoli Monitoring System Edition (SE) for System p V6.1 is a new offering of the popular IBM Tivoli
Monitoring (ITM) product specifically designed for IBM System p AIX customers. ITM SE for System p V6.1 monitors the health and availability of System p servers, providing rich graphical views of your AIX, LPAR, CEC, and VIOS resources in a single console, delivering robust monitoring and quick time to value. ITM SE for System p includes out-of-the-box best practice solutions created by AIX and VIOS developers. These best practice solutions include predefined thresholds for alerting on key metrics, Expert Advice that provides an explanation of the alert and recommends potential actions to take to resolve the issue, and the ability to take resolution actions directly from the Tivoli Enterprise Portal or set up automated actions. In addition, users have the ability to visualize the monitoring data in the Tivoli Enterprise Portal to determine the current state of the AIX, LPAR, CEC, and VIOS resources. Note 2: ------How to monitor IBM's Virtual-IO-Server (VIO) with OpenSMART The following steps tells you, how to monitor IBM's Virtual-IO-Server can be monitored by OpenSMART. Download the latest agent- (or whole source-) pack from the OpenSMART home page. Transfer this tar file to the VIO-Server (we assume to /tmp/opensmart-client0.4.tar.gz) and do: telnet vio-server IBM Virtual I/O Server login: padmin padmin's Password: Last unsuccessful login: Tue Feb 28 03:08:08 CST 2006 on /dev/vty0 Last login: Wed Mar 15 16:14:11 CST 2006 on /dev/pts/0 from 192.168.1.1 $ oem_setup_env # mkdir /home/osmart # useradd -c "OpenSMART Monitoring" -d /home/osmart osmart # chown -R saicsadm:staff /home/osmart # passwd osmart Changing password for "saicsadm" osmart's New password: ****** Enter the new password again: ***** # su - osmart $ mkdir ostemp $ cd ostemp $ gunzip /tmp/opensmart-client-0.4.tar.gz $ tar -xf /tmp/opensmart-client-0.4.tar $ ./agent/install_agent ~ [ ... ] Copy ../lib/opensmartresponse.dtd -> /usr/local/debis/os/etc/opensmartresponse.dtd chmod 644 /usr/local/debis/os/etc/opensmartresponse.dtd
********************************************** * OpenSMART agent installed successfully * ********************************************** $ cd ~ $ rm -rf ostemp That's it - your installation is complete. Now you can configure your osagent (and do not forget to set up a cronjob for your osagent). We recommend the following checks: DISK Section 9.12, �Configuration for the disk check.� LOGS Section 9.20, �Configuration for the logs check.� ERRPT Section 9.14, �Configuration for the errpt check� LOAD Section 9.19, �Configuration for the load check.� PROC Section 9.35, �Configuration for the proc check.� AIXSWRAID Section 9.8, �Configuration for the aixswraid check.� Note 3: lpar2rrd ---------------LPAR2RRD Micro-Partitioning statistics tool The tool is capable produce historical graphs of shared CPU usage on micropartitioned systems. Idea and rough design has been initiated by Ondrej Plachy, IBM Czech Republic. Tool itself has been written by Pavel Hampl, IBM Czech Republic. FEATURES It intended only for Micro-Partitioned systems it creates charts based on utilization data collected on HMC's it does not need any clients (agents) on LPARs it creates automatically a menu based WWW front end for viewing charts it is easy to install, configure and use (initial configuration should not take more than an hour! adding next HMC takes up to 5mins) no any additional management when ANY change of LPAR configuration (tool recognizes new LPARs automatically) it supports all types of LPAR Micro-partitions and OSes (pSeries/iSeries, AIX/Linux/AS400) supported only on HMC >= V5R2.1 (it must support : Utilization data collection, check prerequisities for more) when Utilization data collection is supported, but disabled then the tool prompts you for enabling it (then it needs 2 hours at least to allow HMC collect data and let the tool show any data in charts) graphs are created 1 year back if historical utilization data on HMC's is available (note HMC saves hourly averages for last 2 months, daily averages for last 2 years when collection of data is enabled) initially the tool loads all historical data back to 1 year, then it loads only new data every hour, saves it in RRDTool databases and redraws the graphs
it uses ssh-keys based access to HMC servers to get data automatically optionally for one time chart creation can be used whatever account on HMC and password authentification (you will be prompted to type a password couple of times when the tool is running) it does not cause considerable load on the hosted server where the tool is installed (it runs once an hour for couple of seconds) tool can be hosted on any *NIX platform, just needs a web server, ssh, perl and RRDTool installed. (check prerequisities bellow) it creates 4 kind of graphs for each lpar, shared pool and memory pool. First 3 (last day, week and month) are based on hourly average data, last one (yearly chart) is based on daily averages
More information about pSeries lpars an AIX: -------------------------------------------www.ibm.com/servers/eserver/pseries/lpar/ publib.boulder.ibm.com/infocenter/pseries/index.jsp?topic=/com.ibm.help.doc/welcom e.htm Errors at VIOS: --------------Note 1: ------Procedure: Install/Update HDLM drivers # login to vio server as "padmin". # Switch to "oem" prompt. oem_setup_env umount /mnt mount bosapnim01:/export/lpp_source/hitachi /mnt # # cd cd cd cd
Install and update all filesets from the directories below. "smitty install_all" /mnt/hdlm_5601/aix_odm/V5.0.0.1 /mnt/hdlm_5601/aix_odm/V5.0.0.4u /mnt/hdlm_5601/aix_odm/V5.0.1.4U /mnt/hdlm_5601/aix_odm/V5.0.52.1U
# Copy license file. cd /mnt/hdlm_5601/license/enterprise cp *.plk /var/tmp/hdlm_license # # # cd
install and update all filesets from the above directory "smitty install_all" Fileset DLManager 5.60.1.100 Hitachi Dynamic Link Manager /mnt/hdlm_5601
#
Leave the current Directory and unmount Driver Source Directory.
cd / umount /mnt Procedure: Install/Update VIO fixpack: ====================================== # Login to VIO server as "padmin" # Obtain current IOS level ioslevel # Update VIO to latest IOS level mount bosapnim01:/export/lpp_source/aix/vio_1200 /mnt updateios -dev /mnt ** Enter "y" to continue install # Return to "root" shell prompt and HALT system. oem_setup_env shutdown -Fh # Activate LPAR from HMC WebSM Procedure: Configure VIO Server to utilize Boot Disks: ====================================================== # Login as "padmin" # Switch to "oem" prompt oem_setup_env # Run in korn shell 93 ksh93 # Remove any vhost adapter configuration settings for (( i=0; i> Is my shared volume group online? The following sequence will determine if the sharedvg volume group is currently online (often useful in application start scripts): if lsvg -o | grep -q -w sharedvg ; then echo sharedvg is online else echo sharedvg is offline fi Note the use of the -w option on the grep invocation - this ensures that if you have a sharedvg and a sharedvg2 volume group then the grep only finds the sharedvg line (if it exists). If you need to do something if the volume group is offline and don't need to do anything if it is online then use this: if lsvg -o | grep -q -w sharedvg ; then : # null commmand if the volume group is online else echo sharedvg is offline fi Some people don't like the null command in the above example. They may prefer the following alternative: lsvg -o | grep -q -w sharedvg if [ $? -ne 0 ] ; then echo sharedvg is offline fi Although we're not particularily keen on the null command in the first approach, we really don't like the use of $? in if tests since it is far to easy for the command generating the $? value to become separated from the if test (a classic example of how this happens is if you add an echo command immediately before the if command when you're debugging the script). If we find ourselves needing to test the exit status of a command in an if test then we either use the command itself as the if test (as in the first approach) or we do the following: lsvg -o | grep -q -w sharedvg
rval=$? if [ $rval -ne 0 ] ; then echo sharedvg is offline fi In our opinion (your's may vary), this makes it much more obvious that the exit status of the grep command is important and must be preserved.
>>Starting a non-root process from within an application start script A common requirement in an application start script is the need to start a program and/or shell script which is to be run by a non-root userid. This snippet does the trick: su - dbadmin -c "/usr/local/db/startmeup.sh" This will run the startmeup.sh script in a process owned by the dbadmin user. Note that it is possible to pass parameters to the script/program as well: su - dbadmin -c "/usr/local/db/startmeup.sh PRODDB" This runs the startmeup.sh script with a parameter indicating which database is to be started. A bit of formalism never hurts when it comes time later to do script maintenance. For example, use shell variables to specify the username and the command to be invoked: DBUSER=dbadmin DBNAME=PRODDB STARTCMD="/usr/local/db/startmeup.sh $DBNAME" su - $DBUSER -c "$STARTCMD" This makes it easy to change the username, database name or start command (this is particularily important if any of these appear more than once within the application start script). The double quotes around $STARTCMD in the su command are necessary as the command to be executed must be passed as a single parameter to the su command's -c option. >> Note 1: Killing processes owned by a user A common requirement in application stop scripts is the need to terminate all processes owned by a particular user. The following snippet terminates all processes owned by the dbadmin user (this could be part of an application stop script that corresponds to the previous snippet that started the DB as dbadmin). DBUSER=dbadmin kill ` ps -u $DBUSER -o pid= `
Since a simple kill is rarely enough and a kill -9 is a rather rude way to start a conversation, the following sequence might be useful: DBUSER=dbadmin kill ` ps -u $DBUSER -o pid= ` sleep 10 kill -9 ` ps -u $DBUSER -o pid= ` To see how this works, just enter the ps command. It produces output along these lines: 12276 12348 Note that equal sign in the pid= part is important as it eliminates the normal PID title which would appear at the top of the column of output. I.e. without the equal sign, you'd get this: PID 12276 12348 Passing PID to the kill command is just a bad idea as writing scripts which normally produce error messages makes it much more difficult to know if things are working correctly. >> A more complete example of an application stop script A common requirement in application stop scripts is the need to terminate all processes owned by a particular user. For example, a script along the following lines could be used to first gently and then forcibly terminate the database processes started in the previous example: #!/bin/ksh DBUSER=dbadmin STOPCMD="/usr/local/db/stopdb.sh" # ask nicely su - $DBUSER -c "$STOPCMD" # wait twenty seconds and then get rude sleep 20 kill ` ps -u $DBUSER -o pid= ` # wait ten more seconds and then get violent sleep 10 kill -9 ` ps -u $DBUSER -o pid= ` # terminate any processes using our two shared filesystems fuser -k /dev/sharedlv1 fuser -k /dev/sharedlv2 # make sure that our exit status is 0 exit 0
Good HACMP site: http://www.coredumps.de/doc/ibm/cluster/HAES/haes/gtoc.html
Note 8: Internal logic error in Group Services d ================================================ >> thread: Q: Hello, I get below grpsvcs errors on my cluster nodes (HACMP 5.4 - cluster is UP and STABLE): 463A893D 0425054607 P O grpsvcs Internal logic error in Group Services d A: ok, I think I have found it - it is a bug in rsct 2.4.6 and cab be fixed installing fix for APAR IY91960 http://www-1.ibm.com/support/docview.wss?uid=isg1IY91960 it is: rsct.basic.rte.2.4.6.3.bff rsct.core.hostrm.2.4.6.1.bff rsct.core.rmc.2.4.6.3.bff rsct.core.sec.2.4.6.3.bff rsct.core.sensorrm.2.4.6.1.bff rsct.core.utils.2.4.6.3.bff rsct.opt.saf.amf.2.4.6.1.bff rsct.opt.storagerm.2.4.6.3.bff >> thread: APAR IY26257 APAR status Closed as program error. Error description detection of bouncing nodes is too slow Local fix Problem summary When the RSCT Topology Services daemon exits in one node, it takes a finite time for the node to be detected as down by the other nodes on each of the networks being monitored. This happens because the other nodes need to go through a
process of missing incoming heartbeats from the given node, and can only declare the node down after enough heartbeats are missed. If a new instance of the daemon is started then it is possible for the old instance to be still thought as alive by other nodes by the time the new instance starts. The current behavior may result in other nodes never detecting the given node as down. This occurs especially when different networks use different Topology Services heartbeating tunable values -- which is often the case in HACMP. In HACMP/ES, if the cluster is stopped in one node and is then restarted quickly, it is possible for the cluster to become "hung", with this node being unable to join the others in the cluster. The following AIX error log entry may appear: LABEL: GS_DOM_NOT_FORM_WA IDENTIFIER: AA8DB7B3 Type: INFO Resource Name: grpsvcs Description: Group Services daemon has not been established. Other nodes may present the entry below: LABEL: IDENTIFIER:
GS_ERROR_ER 463A893D
The problem is aggravated by the presence of HAGEO networks, which have very large timeout values. Problem conclusion A number of protocol changes were introduced into the RSCT Topology Services daemon. With the changes - nodes where the Topology Services daemon exits are going to be detected as down faster than before the fix. - nodes where the Topology Services daemon exits and is restarted quickly are going to be detected as down soon after the new instance starts. With the fix, error log entries like GS_DOM_NOT_FORM_WA should no longer occur when restarting the HACMP cluster on a node. In addition, because the demise of the previous instance of the Topology Services daemon is detected sooner, the new instance is allowed to join its adapter memberships faster. Temporary fix Comments APAR information APAR number IY26257 Reported component name RSCT Reported component ID 5765D5101 Reported release 121
Status CLOSED PER PE NoPE HIPER NoHIPER Submitted date 2001-12-11 Closed date 2001-12-11 Last modified date 2003-10-03 >> thread: Note 9: ------Typical 2 node /etc/hosts file: # # HACMP - Do not modify! # 10.17.4.11 n5101l01-boot.nl.eu.abnamro.com n5101l01-boot 10.17.4.10 zd101l01-boot.nl.eu.abnamro.com zd101l01-boot 10.17.3.59 n5101l01.nl.eu.abnamro.com n5101l01 10.17.3.51 zd101l01.nl.eu.abnamro.com zd101l01 10.17.3.100 sonriso.nl.eu.abnamro.com sonriso # # End of HACMP #
====================================================================== 79. Notes on Installation and Migration AIX, HP-UX, Linux: ====================================================================== 79.1 Migrations AIX 5.1,AIX 5.2,AIX 5.3: ---------------------------------------- New and Complete Overwrite This method installs AIX 5.3 on a new machine or completely overwrites any BOS version that exists on your system. For instructions on installing AIX on a new machine or to completely overwrite the BOS on an existing machine, refer to Installing new and complete BOS overwrite or preservation. -- Preservation This method replaces an earlier version of the BOS but retains the root volume group, the user-created logical volumes, and the /home file system. The system file systems /usr, /var, /tmp, and / (root) are overwritten. Product (application) files and configuration data stored in these file systems will be lost. Information stored in other non-system file systems will be preserved. For instructions on preserving the user-defined structure of an existing BOS, refer to Installing new and complete BOS overwrite or preservation.
-- Migration This method upgrades from AIX 4.2, 4.3, 5.1, or 5.2 versions of the BOS to AIX 5.3 (see the release notes for restrictions). The migration installation method is used to upgrade from an existing version or release of AIX to a later version or release of AIX. A migration installation preserves most file systems, including the root volume group, logical volumes, and system configuration files. It overwrites the /tmp file system. Installation Steps New and Complete Overwrite Migration Create rootvg Yes No Create file system /,/usr,/var Yes Create file system /home Yes No Save Configuration No No Restore BOS Yes Yes Install Additional Filesets Yes Yes Restore Configuration No No
Preservation No Yes
No Yes Yes Yes Yes
No
Note 1: ------thread Found that the prngd subsystem (used with ssh, random number generator) on AIX 5.1 is incompatible with the AIX 5.2 upgrade. BEFORE migration this subsystem should be disabled either in /etc/rc.local or erased completely: rmssys -s prngd It has to be remade after migration (see customization). If prngd is not disabled, the final boot after 5.2 installation coredumps with 0C9 and the machine never recovers. In this case: Boot into maintenance mode (needs first 5.2 CD and SMS console) Limited function shell (or getrootfs) vi /etc/rc.local to disable prngd - Firmware/Microcode upgrade It is wise to update the firmware/microcode of your system before upgrading the system. Checkout the IBM support site Directly via ftp site. - Base system Straightforward like installing from scratch. When asked, select "Migration" instead of "Overwrite" installation. Note 2: ------thread:
Problem creating users on AIX 5.2 Reply from tcarlson on 6/28/2007 6:14:00 PM It appears to working now. Thanks for the replies. Not exactly sure what fixed it, but I ran usrck, grpck, and pwdck and it started working again. Note 3: ------AIX 5.2 Installation Tips (Doc Number=1612) Fix Readme April 27, 2005 -------------------------------------------------------------------------------This document contains the latest tips for successful installation of AIX 5.2, and will be updated as new tips become available. APARs and PTFs mentioned in this document, when available, can be obtained from the following web site. http://www.ibm.com/servers/eserver/support/pseries/aixfixes.html http://www14.software.ibm.com/webapp/set2/sas/f/genunix3/aixfixes.html The AIX installation CD-ROMs and the level of AIX pre-installed on new systems may not contain the latest fixes available at the time you install the system, and may contain errors. Some these fixes may be critical to the proper operation of your system. We recommend that you update to the latest service level, which can be obtained from http://www.ibm.com/servers/eserver/support/pseries/aixfixes.html. The compare_report command, which is documented in the AIX Commands Reference, can be used to determine which available updates are newer than those installed on your system. -------------------------------------------------------------------------------Reads from Frozen JFS2 Filesystem Hang System Firmware for POWER 4 Systems Critical Updates for 5200-04 CD-ROM Installation of JS20 Appears to Hang oslevel -r Does not Indicate 5200-04 After Update Documentation Library Service Broken Links lppchk Error on /usr/lib/perl with HACMP Installed License Agreement Failures Possible Data Error on DR Memory Remove Possible File Corruption Running defragfs ksh: clean_up_was: not found Installation of devices.artic960 5.2 ARTIC960Hx SDLC and Bisync Support Inventory Scout HMC 3.2.0 Upgrade TSM 5.1 Not Supported on AIX 5.2 AIXlink/X.25 Version 2 on AIX 5.2 --------------------------------------------------------------------------------
Reads from Frozen JFS Filesystem Hang After application of the 5.2.0.60 level kernels (bos.mp, bos.mp64, bos.up), which are included on the 5/2005 Update CD and in the 5200-06 Recommended Maintenance package, reads from a frozen JFS2 filesystem will no longer be possible. All reads from a frozen filesystem will be blocked until the filesystem is thawed. Because of this, a filesystem level backup, such as a backup using the backup command or through TSM, will appear to hang until the filesystem is thawed. This restriction will be lifted in APAR IY70225. Backups using FlashCopy or similar logical volume or device level backups are still possible on a frozen filesystem.
-------------------------------------------------------------------------------System Firmware for POWER 4 Systems The AIX 5200-04 (or later) Recommended Maintenance package exposes a problem in older levels of POWER 4 system firmware that can manifest itself as either a system hang or hang in some diagnostic commands. The commands that expose the problem include, but may not be limited to snap, lscfg, and lsresource. This problem can be resolved by installing the latest system firmware, available at the following web site. http://techsupport.services.ibm.com/server/mdownload/ http://www14.software.ibm.com/webapp/set2/firmware/gjsn -------------------------------------------------------------------------------Critical Updates for 5200-04 When installing the 5200-04 Recommended Maintenance package, it is also recommended that you install the following APARs. IY64978 Possible system hang while concurrently renaming and unlinking under JFS. This APAR is currently available. IY63366 Loader may fail to find symbol even though the symbol is present in the symbol table. This can cause applications that use dynamically loaded modules to fail. Prior to APAR availability, an emergency fix is available at: ftp://service.software.ibm.com/aix/efixes/iy63366/ Systems running bos.rte.lvm 5.2.0.41 or later should install APAR IY64691. APAR IY64691 fixes a problem with the chvg-B command that can cause data corruption on Big volume groups which were converted from normal volume groups. Prior to APAR availability, obtain the emergency fix for APAR IY64691 from: A href="ftp://service.software.ibm.com/aix/efixes/iy64691/">ftp://service.software.i bm.com/aix/efixes/iy64691/ Systems running bos.rte.lvm 5.2.0.50 should install APAR IY65001. APAR IY65001 fixes a possible corruption issue with mirrored logical volumes. This APAR also contains the fix for APAR IY64691. Prior to APAR availability, obtain the emergency fix for APAR IY65001 from: ftp://service.software.ibm.com/aix/efixes/iy65001/ Systems running bos.rte.aio 5.2.0.50 should install APAR IY64737. APAR IY64737 fixes a problem where applications that use Asynchronous I/O (AIO) can cause a system hang. Prior to APAR availability, obtain the emergency fix for APAR IY64737 from:
ftp://service.software.ibm.com/aix/efixes/iy64737/
-------------------------------------------------------------------------------CD-ROM Installation of JS20 Appears to Hang Following installation of packages from CD-ROM volume 1, the installation appears to hang for 45 to 60 minutes before prompting for volume 2. During this time, the installation process is verifying the installed packages. The problem will be fixed in a later level of the AIX installation media. -------------------------------------------------------------------------------oslevel -r Does not Indicate 5200-04 After Update After updating from the 8/2004 Update CD or the 5200-04 Recommended Maintenance package, the 'oslevel -r' command may not indicate 5200-04. This occurs when updating from a level lower than 5200-03 because the bos.pmapi.tools update does not install. Performing a second update from the media will install the bos.pmapi.tools update and correct the problem. -------------------------------------------------------------------------------Documentation Library Service Broken Links A search of the Documentation Library Service will return hits, but the links result in "404 Not Found" errors. This problem occurs with the sysmgt.websm filesets at the 5.2.0.30 level. This can be resolved using the following command, where $DOC_LANG is any language directory installed under /usr/HTTPServer/htdocs (example: de_DE, en_US, etc.). ln -sf /usr/share/man/info /usr/HTTPServer/htdocs/$DOC_LANG/doc_link -------------------------------------------------------------------------------lppchk Error on /usr/lib/perl with HACMP Installed After installing the cluster.es.server.rte fileset at the 5.2.0.0 level, the lppchk command may return an error due to a missing /usr/lib/perl link. The error can be resolved by doing a force overwrite install of perl.rte from the base AIX media, or by running the following command as root. ln -s /usr/opt/perl5/lib /usr/lib/perl -------------------------------------------------------------------------------License Agreement Failures Installation of some device packages using SMIT may fail due to license agreement failures. This is caused by a missing SMIT "ACCEPT new license agreements" option. To resolve this issue, first install APAR IY52152, which is included in bos.sysmgt.smit 5.2.0.30 or later. -------------------------------------------------------------------------------Possible Data Error on DR Memory Remove For systems running Dynamic Logical Partitioning (DLPAR), it is imperative that the fix for APAR IY50852 be installed. To determine if APAR IY50852 is installed
on your system, use the command: instfix -ik IY50852 When doing a dynamic reconfiguration memory remove operation with DMA operations ongoing, it is possible that data actively being DMAed to pages within the memory being removed may be misdirected to memory that is no longer active in the partition. This could result in a program reading wrong data.
-------------------------------------------------------------------------------Possible File Corruption Running defragfs For systems using JFS2 filesystems, it is imperative that the fix for APAR IY50791 be installed. To determine if APAR IY50791 is installed on your system, use the command: instfix -ik IY50791 When data is synced (written to disk) soon after running the defragfs command on a JFS2 filesystem, incomplete data can be written. Sync operations can be performed with the sync command, but are also performed when unmounting a filesystem or during a system shutdown or reboot.
-------------------------------------------------------------------------------ksh: clean_up_was: not found When attempting to run the clean_up_was shell script as part of installing the Websphere Application Server 5.0.1 trial on the AIX 5.2 Bonus Pack (LCD4-1141-02), the following error may be encountered. ksh: clean_up_was: not found. This problem is caused by control characters at the end each line within the script. To correct the script, use the following procedure: mv clean_up_was clean_up_was.orig tr -d '\015' clean_up_was chmod 755 clean_up_was -------------------------------------------------------------------------------Installation of devices.artic960 5.2 To successfully upgrade to devices.artic960 5.2 from a previous version, it is necessary to install APAR IY48642. -------------------------------------------------------------------------------ARTIC960Hx SDLC and Bisync Support The devices.pci.14108c00 fileset provides support for SDLC and bisynchronous protocols on the IBM ARTIC960Hx 4-Port Selectable PCI Adapter, (FC 2947). When combined with the installation of the devices.artic960 5.2.0.0 fileset, Enhanced Error Handling (EEH) support is provided. APAR IY44132 provides 64-bit support. -------------------------------------------------------------------------------Inventory Scout Inventory Scout introduces a new microcode management graphical user interface (GUI). This feature is available on your AIX system by installing an additional
fileset, invscout.websm, onto the system, or if a Hardware Management Console (HMC) is attached, using the microcode update function. This GUI is a Web-based System Manager plug-in that surveys the microcode levels of the system, and on POWER4 systems, downloads and installs microcode. Inventory Scout continues to work with the applet found at https://techsupport.services.ibm.com/server/aix.invscoutMDS to survey only. This release of Inventory Scout significantly changes the method used to determine the microcode levels of systems, adapters, and devices to compare to the latest available levels. Previously, data was collected and sent to IBM to determine the current state of the system. The new microcode management feature does the following: Downloads a catalog of currently available levels to the system being examined Conducts a microcode survey on the system and compares to the latest available microcode On the POWER4 systems, allows you to download and flash to the latest microcode available This new microcode survey procedure might cause some problems with some customer techniques used today for surveying systems and might require changes to those procedures. This microcode management feature relies on system features that were not present in previous generations of systems. Support for microcode on these systems is limited to survey only. For more information about microcode updates, see http://techsupport.services.ibm.com/server/mdownload. To enable this new Inventory Scout functionality, you will need the following filesets at the specified levels or higher: invscout.com 2.1.0.1 invscout.ldb 2.1.0.2 invscout.rte 2.1.0.1 invscout.websm 2.1.0.1 To obtain the required filesets, order APAR IY44381. Go to the following URL: http://www.ibm.com/servers/eserver/support/pseries/aixfixes.html If you are using this microcode management feature tool through the HMC, your HMC must be at Release 3, Version 2.2. This can be obtain by ordering APAR IY45844. The HMC code can be obtained from http://techsupport.services.ibm.com/server/hmc/. Known Problems: The following devices supported in POWER4 systems have limitations in the ability to update microcode with this microcode management feature. SCSI Enclosure Services (ses) Microcode for 7311-D20, 7038-6M2 & 7028-6C4/6E4 7040-61D SCSI I/O Drawer PCI 4-Channel Ultra3 SCSI RAID Adapter CD-ROM and DVD-ROM Drives RAID Devices SSA devices and adapters For more information about these devices, see the Readme files at http://techsupport.services.ibm.com/server/mdownload. When updating system firmware from an HMC, the connection between the HMC and the
system might get out of sync. This situation can be recovered by going to your server management panel on the HMC and selecting Rebuild Managed System. Some adapters and devices do not support concurrent operation with microcode flashing. Such devices must be taken off-line to update microcode. This situation creates a problem when updating microcode for these communications adapters, such as Ethernet adapters used to communicate with the Internet to obtain the microcode updates or communicate with an HMC. In this case, if the adapters are on-line and the update is attempted, the final step of flashing the device is not completed. You can complete the update procedure by taking the device off-line, and going into diagnostic service aids to download microcode to that device. Due to the changes in how the survey works, you can no longer concatenate survey results prior to sending them to IBM. There is a known system firmware upgrade problem with pSeries 690 or pSeries 670 Servers that have six 7040-61D I/O Drawers and three Integrated Battery Features (IBFs) (battery backup) OR seven or more 7040-61D I/O Drawers, regardless of the number of IBFs. Systems with this configuration should not use the new GUI for microcode management to update the system firmware. For additional information, reference the 7040-681 and/or 7040-671 Readme files which can be found at http://techsupport.services.ibm.com/server/mdownload.
-------------------------------------------------------------------------------HMC 3.2.0 Upgrade The following enhancements delivered for the p670 and p690 systems in May 2003 will not be available unless the Hardware Management Console (HMC) is upgraded to the 3.2.0 or later level. New HMCs delivered after May 2003 will be at the required level. You can obtain the latest HMC update from the Download section of the pSeries Support web pages at http://www.ibm.com/servers/eserver/support/pseries. 32 partitions Distributed RMC CUoD - email home CUoD memory - permanent CUoD memory - try & buy CUoD processor - try & buy Customer firmware management Fast activation of a partition Flat Panel display support Full HMC command line Microcode download from HMC -------------------------------------------------------------------------------TSM 5.1 Not Supported on AIX 5.2 Tivoli Storage Manager (TSM) 5.1 is not compatible with AIX 5.2 and will cause a system crash if installed. TSM 5.1 is shipped in error on the AIX 5L for POWER V5.2 Bonus Pack (LCD4-1141-00) dated 10/2002, and should not be installed. Once TSM 5.1 is installed on AIX 5.2, the system will crash on every reboot. To recover from this situation, the system will have to be booted in maintenance mode from the AIX 5.2 installation media or a system backup (mksysb) to uninstall the tivoli.tsm.* filesets. Alternatively, the following line can be uncommented in /etc/inittab by inserting a ':' (colon) at the beginning of the line.
adsmsmext:2:wait:/etc/rc.adsmhsm > /dev/console AIXlink/X.25 Version 2 on AIX 5.2 To avoid a system crash when using TCP/IP over X.25 functionality, it is necessary to install APAR IY45606. See: http://www-1.ibm.com/support/docview.wss?uid=isg1SSRVAIX52TIPS081512_450 Note 4: ------thread: Q: Attention msg during mksysb Hi, I am running AIX 5.2 ML03, I am receving following Attention msg during the mksysb ****ATTENTION**** The boot image you created might fail to boot because the size exceeds the system limit. For information about fixes or workarounds, see/usr/lpp/bos.sysmgt/README. ****ATTENTION**** .. Creating list of files to back up.. Backing up 569000 files................................. What am I missing in it? any help or hints or tips will be of great value to me. Thanks A: This solution DOES NOT WORK on models 7028, 7029, 7038, 7039, and 7040 systems, see option 4 regarding these models. If APAR IY40824 (AIX 5.1) or IY40975 (AIX 5.2) was installed prior to making the backup, then you may boot from the backup and go to the open firmware prompt. To get to the open firmware prompt, when the system beeps twice after powering it on, press F8 on the keyboard (or the 8 key on an ASCII terminal). You can also get to the open firmware prompt from SMS. The open firmware prompt is also referred to as the "OK" prompt. On some systems there will be a menu option located on the initial SMS menu. On others, it will be located under the Multiboot menu. From the open firmware prompt execute the following: >setenv real-base 1000000 >reset-all Notes: a) To use this option, the backup must have this APAR in it and therefore must be created after installing the APAR. b) The above commands will have to be executed each time you boot from the
large boot image backup media. Note 5: ------Configuring mksysb image on system backup tapes Use the swmksysb command to ensure that the boot image, BOS Installation/Maintenance image, and the table of contents image are created with a tape block_size value of 512. Bootable mksysb tapes comprise the following images: Boot image BOS Installation/Maintenance image Table of contents image System backup image The system backup image is the actual backup of the files in the rootvg in all JFS-mounted file systems. The boot image, BOS Installation/Maintenance image, and the table of contents image must be created with a tape block_size value of 512. The mksysb command ensures that the block size is 512 when these images are created. There are no restrictions on the block size used for the fourth (system backup image) on the tape. The block size of the system, before it was temporarily set to 512, is used for the fourth image on the tape. The value of the block size must be saved in the /tapeblksz file in the second image on the tape. The second and fourth images are stored in backup/restore format. Again, mksysb ensures the correctness of the tapes created by using the mksysb command. If there are problems with the bosinst.data file, the image.data file, or the tapeblksz file, these files can be restored from the second image on the tape and checked. These files, as well as commands necessary for execution in the RAM file system (when running in maintenance mode after booting from the tape), are stored in the second image. Note 6: ------thread Before you migrate 5.1 -> 5.2, do as an absolute minimum the following: - errpt, and resolve all serious issues. If you can't, then STOP. - enough free space rootvg, /, /tmp, /usr, /var - lppchk -v If dependencies are not OK, then correct or STOP. - check firmware. Is the current firmware ok for AIX52? Use "prtconf" or "lsmcode". Example: To display the system firmware level and service processor (if present), type:
# lsmcode -c The system displays a message similar to the following: System Firmware level is TCP99256 If the Firmware version is not current enough, then upgrade or STOP. Or use # lscfg -vp | grep -p Platform - Always create a mksysb tape. Note: its quite likely that your apps still need a number of AIX fixes, APARS before they can run on AIX52. POWER5 Firmware releases: Release SF240 SF235 SF230 SF225 SF222 SF220 SF210
End of Currency To be announced March 2007 March 2007 Out of Currency Out of Currency Out of Currency Out of Currency
Firmware lower than SF230 is not usable for upgrades/migration. Note 7: ------thread Migration AIX 4.3.3 to 5.2, Rebooting don't stop Reply from Simone on 2/9/2005 10:17:00 AM Hi, the Reboot problem during migration to 5.2 is SOLVED. As described in the previous messages, we have 4 networks cards and two are unused (no cable attached, no tcpip adress defined and no network mask allocated). During the reboot, file "/etc/rc.net" "/usr/lib/methods/cfgif" which configure the network (ethernet static routes). Because of the two unconfigured cards "/usr/lib/methods/cfgif", server do a and reboot again.
is executed (boot stage two). This one call adapter, server name, default gateway, and the execution of "SYSTEM DUMP DEV"
To solve this issue, two ways are possible: - detach the unconfigured cards (chdev -l en0 -a state=detach) - configure the cards Please note, that no informations have been founded into IBM documentation about this issue.
THEN, BEFORE A AIX UPGRADE 4.3.3 TO 5.2, BE SURE TO HAVE ALL cards are correctly configured. Thanks Note 8: -------
========================== 80. Some IP subnetting: ========================== Traditional IP Classes are: The
first byte in the 4 byte address corresponds to:
Class A: 1-126 Class B: 128-191 Class C: 192-223 Class D: 224 multicast)
0xxxxxxx.yyyyyyyy.yyyyyyy.yyyyyyyy 10xxxxxx.xxxxxxxx.yyyyyyy.yyyyyyyy 110xxxxx.xxxxxxxx.xxxxxxx.yyyyyyyy 1110----.--------.-------.-------- (not used, or
Notice the first bits in the first byte in the class address. Note : 127.aaaaaaaa.aaaaaaa.aaaaaaaa is reserved for debugging/testing purpose, or local host
In an IP address aaaaaaaa.aaaaaaaa.aaaaaaaa.aaaaaaaa, the 8 bits "aaaaaaaa" corresponds to ax2macht7+ax2macht6+ax2macht6+ax2macht5+ax2macht4+ax2macht3+ax2macht2+ax2macht1+ax 2macht0 with "a" is a bit, that is, a=0 or a=1 1x128 + 1x64 + 1x32 + 1x16 + 1x8 + 1x4 + 1x2 + 1x1 So, in for example in class A: 0xxxxxxx, means that the first byte is at maximum value of 0x128 + 1x64 + 1x32 + 1x16 + 1x8 + 1x4 + 1x2 + 1x1 = 127, but 127 is reserved, so Class A runs from 1 - 126 Similar for Class B: it can be minimum of 10000000 or 10111111 in the first byte, and thats 128-191 Remember, by design, the first two bits in B, MUST BE "10", and the other 6 bits can vary. Subnetting: Class C subnetting:
No of No of No of No of subnets hosts subnetbits hostbits ----------------------------------------------------------*255.255.255.128 NA NA 1 7 routers 255.255.255.192 2 62 2 6 255.255.255.224 6 30 3 5 255.255.255.240 14 14 4 4 255.255.255.248 30 6 5 3 255.255.255.252 62 2 6 2
* not valid with most
Class B subnetting: No of No of No of No of subnets hosts subnetbits hostbits ----------------------------------------------------------255.255.128.0 NA NA 1 15 255.255.192.0 2 16382 2 14 255.255.224.0 6 8190 3 13 255.255.240.0 14 4094 4 12 255.255.248.0 30 2046 5 11 255.255.252.0 62 1022 6 10 255.255.254.0 126 510 7 9 255.255.255.0 254 254 8 8 255.255.255.128 510 126 9 7 255.255.255.192 1022 62 10 6 255.255.255.224 2046 30 11 5 255.255.255.240 4094 14 12 4 255.255.255.248 8190 6 13 3 255.255.255.252 16382 2 14 2
======================================== 81. Notes on TSM: ======================================== 81.1 Notes on TSM client dsmc: ============================== Installing the TSM 5.1 client under IBM AIX 4.3.3 These instructions will guide you through the installation and configuration of the Tivoli Storage Manager client, so you can back up your data using DoIT's Bucky Backup service. You should be familiar with the AIX operating system distribution and have root or root-equivalent access to the machine you are working with. These instructions and the AIX client are specific to the pSeries & RS/6000 architecture. Data that has been backed up or archived from a TSM v5.1 client cannot be restored or retrieved to any previous level client. The data must be restored or retrieved by a v5.1.0 or
higher level client. Once you migrate to 5.1 you cannot go back to an older client (but you can certainly restore older data). This is non-negotiable. You have been warned. This product installs into /usr/tivoli/tsm/client. It requires 40 to 50 megabytes of space. During the installation SMIT will extend the filesystem if you do not have enough space. If you do not have space in rootvg, you can symlink /usr/tivoli/tsm/client into a directory where you do have enough space. You must have registered a node and have received confirmation of your node name. Make sure you know the password that you specified when applying for the node. You must have xlC.rte installed in order to install the client. If you wish to use the graphical client under AIX you must have AIXwindows X11R6, Motif 1.2 or Motif 2.0, and the CDE installed. Acquire the software from Tivoli. You can use wget or lynx to retrieve the files from their web site (or use the "Save Target As..." feature of your browser): ftp://service.boulder.ibm.com/storage/tivoli-storagemanagement/maintenance/client/v5r1/ Start SMIT to install the software: smitty install Select "Install and Update Software", then "Install and Update from LATEST Available Software". When it prompts you for the "INPUT device / directory for software" specify the directory in which you saved the installation files. Proceed to install the software ("_all_latest") Change to the new directories created for the client: cd /usr/tivoli/tsm/client/ba/bin Create and edit the dsm.sys, dsm.opt, and inclexcl files for your system. Sample files are linked. At a minimum, you will have to edit dsm.sys and insert your node name. Start dsmc by using the ./dsmc command. Enter the command "query schedule" and you will be prompted for your node's password. Enter your password and press enter. Once it successfully displays the node's backup schedule, enter the command "quit" to exit it. This saves your node's password, so that backups and other operations can happen automatically. To start the TSM client on reboot, edit /etc/inittab and insert the line (all one line):
tsm:2:once:/usr/tivoli/tsm/client/ba/bin/dsmc schedule servername=bucky3 > /dev/null 2>&1 < /dev/null Issue the following command on the command line, as root, to manually start dsmc: nohup /usr/tivoli/tsm/client/ba/bin/dsmc schedule -servername=bucky3>/dev/null & Verify that the client has started and is working by checking the log files in /usr/tivoli/tsm/client/ba/bin. You can perform a manual backup to test your settings using the command: /usr/tivoli/tsm/client/ba/bin/dsmc incremental Remember that if you change the settings in dsm.sys, dsm.opt, or inclexcl you need to restart the software. Upgrading the TSM client from 4.2 to 5.1 To upgrade the TSM client from 4.2.1 to 5.1 use the following procedure: Obtain a copy of the software (use the links at the top of this page). Kill the running copy of dsmc (a "ps -ef | grep dsmc" will show you what is running. Kill the parent process). Back up dsm.opt, dsm.sys, and inclexcl from your old configuration (probably in /usr/tivoli/tsm/client/ba/bin). The upgrade will preserve them, but it pays to have a backup copy. Upgrade the TSM client packages using "smitty install". Select "Install and Update Software", then "Update Installed Software to Latest Level (Update All)". Specify the directory in which the software was downloaded. Edit your dsm.sys file and ensure that the TCPServeraddress flag is set to buckybackup2.doit.wisc.edu OR buckybackup3.doit.wisc.edu (this just ensures future compatibility with changes to the service). This setting could be either server, depending on when you registered your node. Restart dsmc using the command: nohup /usr/tivoli/tsm/client/ba/bin/dsmc schedule -servername=bucky2 >/dev/null & Watch your logs to ensure that a backup happened. You can also invoke a manual backup using "dsmc incremental" from the command line. So how to install: Run the script tsm-instl Modify /usr/tivoli/tsm/client/ba/bin/dsm.opt Modify /usr/tivoli/tsm/client/ba/bin/dsm.sys Modify /var/tsm/inclexcl.dsm Register the target machine name with TSM The config files are thus "dsm.opt" and "dsm.sys"
zd77l06:/usr/tivoli/tsm/client/ba/bin>cat dsm.opt SErvername dateformat compressalways followsymbolic numberformat subdir timeformat
ZTSM01 4 no yes 5 yes 1
zd77l06:/usr/tivoli/tsm/client/ba/bin>cat dsm.sys SErvername COMMmethod TCPPort TCPServeraddress HTTPPort PASSWORDACCESS schedmode nodename compression SCHEDLogretention ERRORLogretention ERRORLogname SCHEDLogname
ZTSM01 TCPip 1500 cca-tsm01.ao.nl.abnamro.com 1581 GENERATE PROMPTED zd77l06 yes 7 7 /beheer/log/tsm/dsmerror.log /beheer/log/tsm/dsmsched.log
On HP these directories could be /opt/tivoli/tsm/client/ba/bin/dsm.opt
If you need to exclude a filesystem in the backup run, you can edit dsm.sys and put in an exclude statement like in the following example: SErvername ZTSM01 Exclude "/data/documentum/dmadmin/*" COMMmethod TCPip TCPPort 1500 TCPServeraddress cca-tsm01.ao.nl.abnamro.com HTTPPort 1581 PASSWORDACCESS GENERATE schedmode PROMPTED nodename zd110l14 compression yes SCHEDLogretention 7 ERRORLogretention 7 ERRORLogname /beheer/log/tsm/dsmerror.log SCHEDLogname /beheer/log/tsm/dsmsched.log
81.2 Examples of the dsmc command: ==================================
To view schedules that are defined for your client node, enter: # dsmc query schedule # dsmc q ses To change the password: # /usr/bin/dsmc set password To make a test incr backup of /tmp now, to see if backups work: # /usr/bin/dsmc inc /tmp /usr/bin/dsmc inc /home/se1223 To see what the mksysb backup status is: # dsmc q archive /mkcd/mksysb.img
81.3 Restore with dsmc: ======================= -- Example 1: To restore a file /a/b to /c/d : # dsmc restore /a/b /c/d -- Example 2: Restore the most recent backup version of the /home/monnett/h1.doc file, even if the backup is inactive. # dsmc restore /home/monnett/h1.doc -latest -- Example 3: Display a list of active and inactive backup versions of files from which you can select versions to restore. # dsmc restore "/user/project/*"-pick -inactive -- Example 4: Restore the files in the /home file system and all of its subdirectories. # dsmc restore /home/ -subdir=yes -- Example 5: Restore all files in the /home/mydir directory to their state as of 1:00 PM on August 17, 2002. # dsmc restore -pitd=8/17/2002 -pitt=13:00:00 /home/mydir/ -- Example 6: Restore all files from the /home/projecta directory that end with .bak to the /home/projectn/ directory. # dsmc restore "/home/projecta/*.bak" /home/projectn/ # dsmc restore /data/documentum/dmadmin/backup1008/* # dsmc restore /data/documentum/dmadmin/backup1608/* small script for scheduling a restore job from cron:
!#/usr/bin/ksh echo "Starting backup at: " >> /beheer/adhoc_restore.log date >> /beheer/adhoc_restore.log cd /data/documentum/dmadmin dsmc restore /data/documentum/dmadmin/backup_3011/* echo "End of backup at: " >> /beheer/adhoc_restore.log date >> /beheer/adhoc_restore.log
-- Example 7: - Use of FROMDate=date Specify a beginning date for filtering backup versions. Do not restore files that were backed up before this date. You can use this option with the TODATE option to create a time window for backup versions. You can list files that were backed up between two dates. For example, to restore all the files that you backed up from the /home/case directory from April 7, 1995 through April 14, 1995, enter: # REStore "/home/case/" -FROMDate=04/07/1995 -TODate=04/14/1995 As another example, to restore backup versions of files that were created during the last week of March 1995 for the files in the /home/jones directory, enter: # Restore -FROMDate=03/26/1995 -TODate=03/31/1995 /home/jones The date must be in the format you select with the DATEFORMAT option. For example, the date for date format 1 is mm/dd/yyyy, where mm is month; dd is day; and yyyy is year. If you include DATEFORMAT with the command, it must precede FROMDATE and TODATE. - Use of TODate=date Specify an end date for filtering backup versions. ADSM does not restore backup versions that were backed up after this date. You can use this option with the FROMDATE option to create a time window for backups. You can restore backup versions that were backed up between two dates For example, to restore files from the /home/case directory that were backed up between April 7, 1995 and April 14, 1995, enter the following: res "/home/case/" -FROMDate=04/07/1995 -TODate=4/14/1995
The date must be in the format you select with the DATEFORMAT option. For example, the date for date format 1 is mm/dd/yyyy, where mm is month; dd is day; and yyyy is year. If you include DATEFORMAT with the command, it must precede FROMDATE and TODATE. To start the clients Graphical User Interface enter dsm. The TSM GUI appears.
Example in Dutch: ----------------Bestanden terughalen van de backup. Elke nacht worden er backup's gemaakt van alle data. Als U, om wat voor een reden dan ook, een bestand kwijt bent geraakt, kunt U dit zelf terughalen van de backup als er aan de volgende voorwaarden wordt voldaan: -het bestand heeft minstens 1 nacht op de server gestaan -U bent het minder dan 30 dagen geleden kwijtgeraakt Files die u dezelfde dag op het systeem zet en weer weggooid, kunt u niet met een restore terughalen! Om een bestand terug te halen (restore) gaat U als volgt te werk: Log in op de machine en tik op de commando prompt: $ dsmc restore -ina -subdir=yes "file-selectie" waarbij voor "file-selectie" de filenaam opgegeven wordt van het bestand dat U kwijt bent. Weet U de naam niet meer precies tik dan in: dsmc restore -ina -subdir=yes "*" met de "'s. --Een voorbeeld Voorbeeld van een restore De voorbeeld file: -rw-rw-r--
1 faq
faq
269 Mar 18 16:12 testfile
File (per ongeluk) weggooien: $ rm testfile Controle op het (niet meer) bestaan van de file: $ ls -l testfile ls: testfile: No such file or directory Starten van een restore:
$ dsmc restore -pick "test*" TSM Scrollable PICK Window - Restore # Backup Date/Time File Size A/I File --------------------------------------------------------------x 1. | 19-03-2002 03:13:22 269 B A /www/faq/testfile | | | | 0---------10--------20--------30--------40--------50--------60-=Up =Down =Top =Bottom =Right =Left =Goto Line # =Toggle Entry =Select All =Deselect All =Select A Range =Deselect A Range =Ok =Cancel pick> Selecteer de te restoren file, in dit geval kiezen we voor testfile pick> 1 TSM Scrollable PICK Window - Restore #
Backup Date/Time File Size A/I File --------------------------------------------------------------x 1. | 19-03-2002 03:13:22 269 B A /www/faq/testfile | | | | 0---------10--------20--------30--------40--------50--------60-=Up =Down =Top =Bottom =Right =Left =Goto Line # =Toggle Entry =Select All =Deselect All =Select A Range =Deselect A Range =Ok =Cancel pick> Bevestig met OK pick> o ** Interrupted ** ANS1114I Waiting for mount of offline media. Opmerking: wachttijd is afhankelijk van de drukte op de TSM-server Restoring
269 /www/faq/testfile [Done]
Restore processing finished. Total number of objects restored: 1 Total number of objects failed: 0 Total number of bytes transferred: 296 B Data transfer time: 0.00 sec Network data transfer rate: 19,270.83 KB/sec Aggregate data transfer rate: 0.00 KB/sec Elapsed processing time: 00:04:05 Controle op het bestaan van de file:
$ ls -l testfile -rw-rw-r-1 faq
faq
269 Mar 18 16:12 testfile
De (test-)file is weer te gebruiken. Example: -------- Backup von Dateien: Mittels des Befehls: C:>dsmc incremental -subdir=yes "d:\*.*" kann beispielsweise der Inhalt der ganzen Festplatte (oder Partition) d:\ Ihres PCs gesichert werden. Analog lassen sich Unterverzeichnisse derselben Platte sichern. Hier noch ein Beispiel unter dem Betriebssystem Unix: # dsmc incremental -subdir=no /usr/users/holo Dieser Befehl sichert alle Dateien in dem Verzeichnis /usr/users/holo . - Anzeige von mittels Backup gesicherten Dateien: Um herauszufinden welche Dateien durch Backup im TSM Server gespeichert sind, gibt es folgendes Kommando: dsmc query backup -subdir=yes "*" womit Sie alle Ihre gesicherten Dateien aufgelistet bekommen. Die Option -inactive gestattet zus�tzlich das Auflisten aller gespeicherten fr�heren Versionen Ihrer Dateien. Haben Sie z.B. unter Unix im Verzeichnis /u/holo/briefe/1997 durch �nderungen mehrere Versionen Ihrer Briefe konferenz97.tex abgespeichert, so bekommen Sie eine Liste aller Dateien durch: # dsmc query backup -inactive \ /u/holo/briefe/1997/konferenz97.tex Der obige \ ist die Unix Zeilenfortsetzung. - Restore von Dateien: Es ist passiert: Sie haben sich eine Datei die Sie sp�ter ben�tigen gel�scht. Mittels des Kommandos restore k�nnen Sie Dateien die mittels Backup gesichert wurden, wiederherstellen. Der Befehl: # dsmc restore -subdir=yes "/u/holo/briefe/*" speichert alle aktiven Dateien im Unterverzeichnis /u/holo/briefe wieder zur�ck. Falls Sie dabei existierende Dateien �berschreiben wollen, so k�nnen Sie die Option -replace=yes
angeben. Es ist auch m�glich ein Zeitintervall anzugeben, in welchem die Sicherung erfolgt sein mu�, um so auf �ltere Versionen zur�ckzugehen (die z.B. noch frei von Computerviren sind): dsmc restore -replace=yes -todate=1997-12-22 d:\*.doc
81.4 Oracle and TSM: TDPO: ========================== RMAN and Tivoli Data Protection for Oracle The Oracle Recovery Manager provides consistent and secure backup, restore, and recovery performance for Oracle databases. While the Oracle RMAN initiates a backup or restore, TDP for Oracle acts as the interface to the Tivoli Storage Manager server (Version 4.1.0 or later). The Tivoli Storage Manager server then applies administrator-defined storage management policies to the data. TDP for Oracle Version 2.2.1 implements Oracle defined Media Management API 2.0, which interfaces with RMAN for backup and restore operations and translates Oracle commands into Tivoli Storage Manager API calls to the Tivoli Storage Manager server. With the use of RMAN, TDP for Oracle allows you to perform the following functions: Full backup function for the following while online or offline: -databases -tablespaces -datafiles -archive log files -control files -Full database restore while offline -Tablespace and datafile restore while online or offline TDPO.OPT File This feature provides a centralized place to define all the options needed by RMAN for TDP for Oracle backup and restore operations. This eliminates the need to specify environment variables for each session, thereby reducing the potential for human error. This also simplifies the establishment of multiple sessions. The Data Protection for Oracle options file, tdpo.opt, contains options that determine the behavior and performance of Data Protection for Oracle. The only environment variable Data Protection for Oracle Version 5.2 recognizes within an RMAN script is the fully qualified path name to the tdpo.opt file. Therefore, some RMAN scripts may need to be edited to use TDPO_OPTFILE=fully qualified path and file name of options file variable in place of other environment variables. For example:
allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/home/rman/scripts/tdpo.opt)'See Scripts for further information. If a fully qualified path name is not provided, Data Protection for Oracle uses the tdpo.opt file located in the Data Protection for Oracle default installation directory. If this file does not exist, Data Protection for Oracle proceeds with default values.
Note 1: ------Installing Data Protection for Oracle 5.1 This chapter provides information on the required client environment for Data Protection for Oracle and instructions on installing Data Protection for Oracle. Make sure these conditions exist before installing Data Protection for Oracle: - Tivoli Storage Manager Server Version 5.1.0 (or later) is configured. - Tivoli Storage Manager API Version 5.1.5 (or later) is installed. This version of the Tivoli Storage Manager API is included in the Data Protection for Oracle product media. Attention: A root user must install the Tivoli Storage Manager API before installing Data Protection for Oracle on the workstation where the target database resides. After Data Protection for Oracle is installed, you must perform the following configuration tasks: -Define Data Protection for Oracle options in the tdpo.opt file. -Register the Data Protection for Oracle node to a Tivoli Storage Manager Server. -Define Tivoli Storage Manager options in the dsm.opt and dsm.sys files. -Define Tivoli Storage Manager policy requirements. -Initialize the password with a Tivoli Storage Manager Server. See Configuring Data Protection for Oracle for detailed task instructions. Note 2: ------New Password File Generation Data Protection for Oracle uses a new password utility for password generation and maintenance. The new TDPO configuration utility, 'tdpoconf' replaces the previous executable 'aobpswd'. To generate or update a password, invoke 'tdpoconf' as follows: tdpoconf password [-tdpo_optfile=/mydir/myfile.opt] Successful execution of 'tdpoconf password' should generate apassword file with the prefix 'TDPO.' followed by your nodename.
For more information, please see the 'Using the Utilities' section in the Data Protection for Oracle User's Guide. Note 3: ------thread Q: Any good step-by-step docs out there? I just need to get this thing setup and working quickly. Don't have time (unless it is my only choice of course) do filter through several manuals to pick out the key info... Help if you can - I surly would appreciate it A: What needs to happen is this -1. Get the manuals downloaded. 2. Download the TDP and perform default installations 3. Create a node name for the TDP - i.e TDP_Oracle _<hostname>, register it using a simple password because you are going to need it. 3. Add a stanza in dsm.sys for the TDP, this should be the second or third stanza since the first stanza is for the client. 4. In the TDP installation directory, modify the tdpo.opt file - this is the configuration file for the TDP. This file is self explanatory 5. Execute tdpconf showenv - you should get a response back from tsm. 6. Execute tdpoconf passwd - to create tdpo password - the password file will be created and stored in the TDP home directory. If will have the host name as part of the file name. 7. Once you have gotten this far, in Oracle's home directory - create the dsm.opt file and make sure it contains only one line, the servername line of the newly created stanza. The file needs to be owned by oracle. 8. If you are using tracing, the tdpo.opt file will identify the location. 9. Configure RMAN 10. Test and verify Note 4: -------
thread Q: I see this question has been asked several times in the list, but I fail to see any answers on ADSM.ORG. I'm getting the "ANS0263E Either the dsm.sys file was not found, or the Inclexcl file specified in the dsm.sys was not found" error when trying to set the password after installing the 64 bit TDPO on Solaris 8. (The 32 bit version installs fine) Anyone have the fix for this handy? A: Dale, Did you check the basics of, as oracle, or your tdpo user: # env | grep DSM Make sure the DSMI variables point to the right locations, then verify those files are readable by your user. If after verifying this, you might want to let us know what version of oracle, tdpo and tsmc you have on this node. A: We had an issue with this and discovered that it was looking in the api directory for the dsm.sys and not the ba/bin directory so we just put a link in api to bin and it worked. A: You may want to break the link to prevent TDP from using the INCLEXCL file that's normally in a dsm.sys file. If you don't, you'll generate errors. If linked, and commented out, your normal backups won't have an INCLEXCL file, hence, you'll backup everything on your client server during your regular client backup. Note 5: ------http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg24012732 TSM for Databases v5.3.3, Data Protection for Oracle Downloads by Platform Downloadable files Abstract Data Protection for Oracle v5.3.3 refresh.
Download Description Data Protection for Oracle v5.3.3 refresh. These packages contains no license file. The customer must already have a Paid version of the package to obtain the license file. These packages contain fixes for APARs IC48436, IC48248, IC48056, IC46968, IC45462, IC43896, IC41501, IC38717, IC38681, IC38430, IC38061, IC37459, IC36686, IC36389 Prerequisites A Paid version of the Data Protection for Oracle package is required. Installation Instructions See the README.TDPO in the download directory. Note 6: ------IC44171: ON AIX, FILESET TIVOLI.TSM.CLIENT.API.32BIT 5.3.0.0 IS A PRE-REQFOR INSTALLING TIVOLI.TSM.CLIENT.API.64BIT 5.3.0.0 APAR status Closed as documentation error. Error description When installing tivoli.tsm.client.api.64bit 5.3.0.0 on AIX, tivoli.tsm.client.api.32bit 5.3.0.0 is required as pre-requsite for the installation. The installation will fail if tivoli.tsm.client.api.32bit 5.3.0.0 is not avaiable for install. tivoli.tsm.client.api.32bit 5.3.0.0 is needed because of languages enhancement in 5.3. Local fix Problem summary **************************************************************** * USERS AFFECTED: AIX CLIENTS * **************************************************************** * PROBLEM DESCRIPTION: API 32bit PREREQ for API 64bit not in * * README. * **************************************************************** * RECOMMENDATION: apply next available fix. * **************************************************************** Problem conclusion Add info to README files and database. Files in TSM client and tdpo: tivoli.tivguid tivoli.tsm.books.en_US.client.htm tivoli.tsm.books.en_US.client.pdf tivoli.tsm.client.api.32bit tivoli.tsm.client.api.64bit tivoli.tsm.client.ba.32bit.base tivoli.tsm.client.ba.32bit.common
� � � � � � �
tivoli.tsm.client.ba.32bit.image tivoli.tsm.client.ba.32bit.nas tivoli.tsm.client.ba.32bit.web tivoli.tsm.client.oracle.aix.64bit tivoli.tsm.client.oracle.books.htm tivoli.tsm.client.oracle.books.pdf tivoli.tsm.client.oracle.tools.aix.64bit
� � � � � �
81.5 Other stuff with TSM client, stopping and starting: ======================================================== The TSM scheduler dsmcad: -------------------------- Check if its running: ps -ef | grep dsm root 245896 1
0
Jan 08
-
0:24 /usr/tivoli/tsm/client/ba/bin/dsmcad
-- To start the process: #! /bin/sh # Copyright (c) 1989, Silicon Graphics, Inc. #ident "$Revision: 1.1 $" if $IS_ON verbose ; then ECHO=echo else ECHO=: fi
# For a verbose startup and shutdown # For a quiet startup and shutdown
state=$1 case $state in 'start')
set `who -r` if [ $8 != "0" ] then exit fi $ECHO "Starting dsm schedule:" DSM_LOG="/usr/tivoli/tsm/client/ba" DSM_CONFIG="/usr/tivoli/tsm/client/ba/bin/dsm.opt" DSM_DIR="/usr/tivoli/tsm/client/ba/bin" export DSM_LOG DSM_CONFIG DSM_DIR if [ -f /usr/tivoli/tsm/client/ba/bin/dsmcad ]; then /usr/tivoli/tsm/client/ba/bin/dsmcad > /dev/null 2>&1 & if [ $? -eq 0 ]; then $ECHO " done" else $ECHO " failed" exit 2
fi else fi ;; 'stop')
echo " failed, no dsm installed" exit 3
$ECHO "Stopping dsm schedule:" killall dsmcad ;;
esac It is also possible now to start and stop dsmcad using the script. For example : - To start dsmcad manually run: /etc/init.d/dsmcad start - To stop dsmcad run: /etc/init.d/dsmcad stop - To restart dsmcad (for example to refresh daemon after dsm.sys or dsm.opt modification) /etc/init.d/dsmcad restart - To check if dsmcad is running run: /etc/init.d/dsmcad status -orps -ef | grep dsmcad Or use: (root) /sbin/init.d/tsmclient stop (root) /sbin/init.d/tsmclient start
It could also be implemented in a proprierty way as in the following example: root@zd111l08:/etc#./rc.dsm stop dsmcad en scheduler gestopt root@zd111l08:/etc#./rc.dsm start root@zd111l08:/etc#IBM Tivoli Storage Manager Command Line Backup/Archive Client Interface - Version 5, Release 2, Level 3.0 (c) Copyright by IBM Corporation and other(s) 1990, 2004. All Rights Reserved. Querying server for Node Name: ZD111L08 Session established Server Version 5, Server date/time:
next scheduled event. with server ZTSM05: AIX-RS/6000 Release 2, Level 4.5 06.08.2007 08:19:13 Last access: 30.07.2007 14:54:54
Next operation scheduled: -----------------------------------------------------------Schedule Name: DAG01U_ALG_CCAZ Action: Incremental Objects: Options: -su=yes Server Window Start: 01:00:00 on 07.08.2007 -----------------------------------------------------------Waiting to be contacted by the server.
81.6 TSCM: Tivoli Security Compliance Manager : ----------------------------------------------
-- client.pref: The client.pref configuration file contains configuration parameters for the Tivoli Security Compliance Manager client and is located in the client installation directory. The default installation directories are: UNIX /opt/IBM/SCM/client -- stopping and starting the client: Stopping the client on UNIX systems Note: You must log in as the root user to complete this task. To stop the client component on a UNIX system: Open a command shell. Go to the directory where the client component is installed. The default installation directory is /opt/IBM/SCM/client. Enter the following command: ./jacclient stop To start it, use ./jacclient start -- Show status of the client: ./jacclient status HCVIN0033I The Tivoli Security Compliance Manager client is currently running. -- Start of the client on boot:
On AIX, the client is started from inittab: #cat /etc/inittab | grep jac ibmscmcli:2:once:/opt/IBM/SCM/client/jacclient start >/dev/console 2>&1 # Start Security Compliance Manager Client 81.7 ANS1005E TCP/IP read error on socket xx errono=73: ------------------------------------------------------ANS1005E TCP/IP read error on socket xx errono=73 Technote (FAQ) Problem ANS1005E TCP/IP read error on socket = 6, errno = 73, reason: 'A connection with a remote socket was reset by that socket.'. Cause The same ANR1005E message with errno 10054 is well-documented, but very little documentation exists for errno 73 Solution ANS1005E TCP/IP read error on socket = 6, errno = 73, reason: 'A connection with a remote socket was reset by that socket.'. The errno 73 seen in the message above indicates that the connection was reset by the peer, usually an indication that the session was cancelled or terminated on the TSM Server. In all likelihood these sessions were terminated on the server because they were in an idle wait for a period of time exceeding the idletimeout value on the TSM Server. We see that the sessions successfully reconnected and no further errors were seen. Sessions sitting in an idle wait is not uncommon and is frequently seen when backing up large amounts of data. With multi-threaded clients, some sessions are responsible for querying the server to identify which files are eligible to be backed up (producer sessions) while the other sessions are responsible for the actual transfer of data (consumer sessions). It usually takes longer to backup files across the network than it takes for a list of eligible files to be generated. Once the producer sessions have completed building lists of eligible files they will sit idle while the producer sessions actually backup these files to the TSM Server. After some time, the TSM Server will terminate the producer sessions because they have been idle for a period of time longer than the IDLETIMEOUT value specified on the server. Many times this issue can be seen in firewall environment and has been seen with network DNS problems and/or network config problems. One of the most common is when a passive device (router, switch, hub, etc.) is in between the client & the server. If the port on the passive device is set to Auto-Negotiate, it will automatically defer
to the active device (the NIC in the client) to set the connection speed. If the NIC is also set to Auto-Negotiate (default in most OS's) this often causes excessive delays and interruptions in connectivity. This is because the NIC is looking to the network appliance to set the connection speed and vice-versa, so it takes some time before the network device will find a suitable connection speed (not always optimal, just suitable) and begin data transfer. This repeats every time a data packet is sent across the network. While the negotiating period is relatively short by human standards (usually in the nanosecond range) it adds up over time when trying to send a large amount of data at a high speed and causes the connection to be broken. The best workaround for that is to hard code both the NIC and the network port for a specific setting. This is usually 100Mb Full Duplex for a standard CAT-5 copper connection, although older equipment may require reconfiguration of 10/100 NICs to allow for that speed. The other possible workaround for this issue is to estimate the file transfer time and increase the IDLETIMEOUT to a level higher than that time.
========= 82. LDAP: ========= 82.1: Introduction: =================== The Lightweight Directory Access Protocol, better known as LDAP, is based on the X.500 standard, but is significantly simpler and more readily adapted to meet custom needs. Unlike X.500, LDAP supports TCP/IP, which is necessary for Internet access. The core LDAP specifications are all defined in RFCs. Associated with LDAP, there must be an "information store" somewhere on Server(s), that holds objects and all their related properties, like useraccounts and all properties belonging to those accounts. Strictly speaking, though, LDAP isn't a database at all, but a protocol used to access information stored in an information directory (also known as an LDAP directory). So, the protocol does not make any assumptions on the actual type or sort of database which is involved, but it does specify how to describe objects, classes, properties and how to retrieve and store this information. The socalled "schema" specifies all object classes and properties. LDAP directory servers store their data hierarchically. If you've seen the topdown representations of
DNS trees or UNIX file directories, an LDAP directory structure will be familiar ground. As with DNS host names, an LDAP directory record's Distinguished Name (DN for short) is read from the individual entry, backwards through the tree, up to the top level. It's just a "way" to represent a LDAP entry (or record). It has a Distinguished Name (DN) that fully and uniquely describes the object in the "tree", similar to a file in a subdirectory on a filesystem. -- What's in a name? The DN of an LDAP entry: All entries stored in an LDAP directory have a unique "Distinguished Name," or DN. The DN for each LDAP entry is composed of two parts: the Relative Distinguished Name (RDN) and the location within the LDAP directory where the record resides. Some people like to refer to "container objects", holding other objects, and "leaf objects" that are endpoints in the tree. Containers are mostly referred to as "Organizational Units" or OU's. OU's are completely compairable to the domain components (dc's) of a fully qualified Domain Name. Compared to a filesystem, an OU looks a lot like a directory. Some attributes of an object are required, while other attributes are optional. An objectclass definition sets which attributes are required and which are not for each entry. An object is represented (or can be found) by listing all ou's or dc's until you have reached the "endpoint": -- Example 1: OU=com.Ou=shell.OU=research.harry harry.OU=research.OU=shell.OU=com
or better according to convention:
There are quite a few implementations that describe objects. For example, in Novell NDS, a user's Distinguished Name might be like the following example: -- Example 2: CN=jdoe.OU=hrs.O=ADMN or abbreviated to jdoe.hrs.admn Note: In Novell NDS, the toplevel OU is called an Organization, or just "O". As another example: CN=lpIII.OU=development.OU=engineering.O=VerySmallCompany -- Example 3: An object could also be described as in the following example.
cn=Oatmeal Deluxe,ou=recipes,dc=foobar,dc=com Which means: In com, then in foobar, then in recipes, we can find the object "Oatmeal Deluxe". An LDAP Server is capable of propagating its directories to other LDAP servers throughout the world, providing global access to information. Currently, however, LDAP is more commonly used within individual organizations, like universities, government departments, and private companies. LDAP is a client-server system. The server can use a variety of databases to store a directory, each optimized for quick and copious read operations. When an LDAP client application connects to an LDAP server it can either query a directory or upload information to it. In the event of a query, the server either answers the query or, if it can not answer locally, it can refer the query upstream to a higher level LDAP server which does have the answer. If the client application is attempting to upload information to an LDAP directory, the server verifies that the user has permission to make the change and then adds or updates the information. Note: LDAP processes listen per default on port 389.
82.2 API's dealing with LDAP: ============================= -- Programming: -- -----------Almost all programming languages, have libraries or modules to access a LDAP Directory Server, and to query, or add, delete or modify objects. -- Utilities: -- ---------Also, on many platforms, commandline utilities exist which can do manipulation of objects. In this case, in many implementations, LDIF files can be used. Lightweight Directory Interchange Format (LDIF) is a text-based format used to describe and modify, add, and delete--directory entries. In the latter capacity, it provides input to command-line utilities. The two LDIF files immediately following represent a directory entry for a printer. The string in the first line of each entry is the entry's name, called a distinguished name.
The difference between the files is that the first describes the entry--that is, the format is an index of the information that the entry contains. The second, when used as input to the command-line utility, adds information about the speed of the printer. Description dn: cn=LaserPrinter1, ou=Devices, dc=acme,dc=com objectclass: top objectclass: printer objectclass: epsonPrinter cn: LaserPrinter1 resolution: 600 description: In room 407 Modification dn: cn=LaserPrinter1, ou=Devices, dc=acme, dc=com changetype: modify add: pagesPerMinute pagesPerMinute: 6 As a few examples in programming languages, consider the following examples: Java example: ------------Listing 1 shows a simple JNDI program that will print out the cn attributes of all the Person type objects on your console. Listing 1. SimpleLDAPClient.java public class SimpleLDAPClient { public static void main(String[] args) { Hashtable env = new Hashtable(); env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory" );
env.put(Context.PROVIDER_URL, "ldap://localhost:10389/ou=system"); env.put(Context.SECURITY_AUTHENTICATION, "simple"); env.put(Context.SECURITY_PRINCIPAL, "uid=admin,ou=system"); env.put(Context.SECURITY_CREDENTIALS, "secret"); DirContext ctx = null; NamingEnumeration results = null; try { ctx = new InitialDirContext(env); SearchControls controls = new SearchControls(); controls.setSearchScope(SearchControls.SUBTREE_SCOPE); results = ctx.search("", "(objectclass=person)", controls); while (results.hasMore()) { SearchResult searchResult = (SearchResult) results.next(); Attributes attributes = searchResult.getAttributes();
Attribute attr = attributes.get("cn"); String cn = (String) attr.get(); System.out.println(" Person Common Name = " + cn);
}
} } catch (NamingException e) { throw new RuntimeException(e); } finally { if (results != null) { try { results.close(); } catch (Exception e) { } } if (ctx != null) { try { ctx.close(); } catch (Exception e) { } } }
} VB.Net example: --------------'To retrieve list of all
LDAP users
'This function returns HashTable _ldapServerName = ldapServerName Dim sServerName As String = "mail" Dim oRoot As DirectoryEntry = New DirectoryEntry("LDAP://" & ldapServerName & _ "/ou=People,dc=mydomainname,dc=com") Dim Dim Dim Dim
oSearcher As DirectorySearcher = New DirectorySearcher(oRoot) oResults As SearchResultCollection oResult As SearchResult RetArray As New Hashtable()
Try oSearcher.PropertiesToLoad.Add("uid") oSearcher.PropertiesToLoad.Add("givenname") oSearcher.PropertiesToLoad.Add("cn") oResults = oSearcher.FindAll For Each oResult In oResults If Not oResult.GetDirectoryEntry().Properties("cn").Value = "" Then RetArray.Add( oResult.GetDirectoryEntry().Properties("uid").Value, _ oResult.GetDirectoryEntry().Properties("cn").Value) End If Next
Catch e As Exception 'MsgBox("Error is " & e.Message) Return RetArray End Try Return RetArray End Function Some frgaments in C++: ---------------------Establishing an LDAP Connection: LDAPConnection lc("localhost"); try { lc.bind("cn=user,dc=example,dc=org","secret"); } catch (LDAPException e) { std::cerr /tmp/pfiles.out" and then look in /tmp/pfiles.out for the portnumber. The picld process is a new abstraction layer for programs who want to access platform specific information. Instead of using some platform specific program applications can use the picl library to access information in a generic way. Disabling the picld daemon will affect applications which are using the libpicltree. You can use the "ldd" command to identify such applications and decide whether
you're using them or not. Example applications are "prtpicl" or "locator" (see the manpages). The "syseventd" is responsible for delivering system events and disabling this service will affect your ability to create new devices on the fly (e.g. for dynamic reconfiguration). The "efdaemon" is another example of such a process which is needed for dynamic reconfiguration. Disabling syseventd and/or efdaemon havily depends on your required services. After creating your devices (boot -r) you can safely turn of these daemons but you'll run into trouble when trying dynamic reconfiguration... Without knowing your requirements we can't tell whether it's ok to disable those services or not. bpbkar: ======= bpbkar is part of the Veritas Netbackup client, usually installed at /usr/openv/netbackup . process: ================== Note 1: In general, defunct processes are caused by a parent process not reaping its children. Find out which process is the parent process of all those zombies (ps -e). It's that process that has a bug. In Solaris 2.3 (and presumably earlier) there is a bug in the pseudo tty modules that makes them hang in close. This causes processes to hang forever while exiting. Fix: Apply patch 101415-02 (for 2.3). In all Solaris 2 releases prior to 2.5 (also fixed in the latest 2.4 kernel jumbo patch), init (process 1) calls sync() every five minutes which can hang init for some considerable time. This can cause a lot of zombies accumulating with process 1 as parent, but occurs only in rare circumstances. Note 2: My app has a parent that forks a child. Sometimes, one of them dies and leaves a defunct process, along with shared memory segments. I try to get rid of the shared memory and kill the defunct task, but to no avail. I then have to reboot the system to clean up the shared memory and to get rid of the defunct process. How can I kill a defunct process and get rid of the associated shared memory ?
A defunct task is already dead. You can not kill a "zombie". The problem is obviously that the app does not expect a child to die and does not make the necessary wait calls to relieve the child from its return code. Did you stopp the app and see what happens? use ipcrm to release shared memory. But a zombie indicates also a programming problem with the application. So it is time to redesign the application. Note 3: A zombie process is a process which has died and whose parent process is still running and has not wait()ed for it. In other words, if a process becomes a zombie, it means that the parent process has not called wait() or waitpid() to obtain the child process's termination status. Once the parent retrieves a child's termination status, that child process no longer appears in the process table. You cannot kill a zombie process, because it's already dead. It is taking up space in the process table, and that's about it. If any process terminates before its children do, init inherits those children. When they die, init calls one of the wait() functions to retrieve the child's termination status, and the child disappears from the process table. A zombie process is not, in and of itself, harmful, unless there are many of them taking up space in the process table. But it's generally bad programming practice to leave zombies lying around, in the same way that it's generally a Bad Thing to never bother to free memory you've malloc()ed. Note 4: Other than Windows, unix manages an explicit parent-child relationships between processes. When a child process dies, the parent will receive a notification. It is then the duty of the parent process to explicitly take notice of the childs demise by using the wait() system call. The return value of the wait() is the process ID of the child, which gives the parent exact control about which of its children are still alive. As long as the parent hasn't called wait(), the system needs to keep the dead child in the global process list, because that's the only place where the process ID is stored. The purpose of the "zombies" is really just for the system to remember the process ID, so that it can inform the parent process about it on request. If the parent "forgets" to collect on its children, then the zombie will stay undead forever. Well, almost forever. If the parent itself dies, then "init" (the system process with the ID 0) will take over
fostership over its children and catch up on the neglected parental duties
S_IFCHR and S_IFDOOR: ===================== Suppose you use the pfiles command on a PID # /usr/proc/bin/pfiles 194 194: /usr/sbin/nscd Current rlimit: 256 file descriptors 0: S_IFCHR mode:0666 dev:85,1 ino:3291 uid:0 gid:3 rdev:13,2 O_RDWR 1: S_IFCHR mode:0666 dev:85,1 ino:3291 uid:0 gid:3 rdev:13,2 O_RDWR 2: S_IFCHR mode:0666 dev:85,1 ino:3291 uid:0 gid:3 rdev:13,2 O_RDWR 3: S_IFDOOR mode:0777 dev:275,0 ino:0 uid:0 gid:0 size:0 O_RDWR FD_CLOEXEC door to nscd[194] # /usr/proc/bin/pfiles 254 254: /usr/dt/bin/dtlogin -daemon Current rlimit: 2014 file descriptors 0: S_IFDIR mode:0755 dev:32,24 ino:2 uid:0 gid:0 size:512 O_RDONLY|O_LARGEFILE 1: S_IFDIR mode:0755 dev:32,24 ino:2 uid:0 gid:0 size:512 O_RDONLY|O_LARGEFILE 2: S_IFREG mode:0644 dev:32,24 ino:143623 uid:0 gid:0 size:41 O_WRONLY|O_APPEND|O_LARGEFILE 3: S_IFCHR mode:0666 dev:32,24 ino:207727 uid:0 gid:3 rdev:13,12 O_RDWR 4: S_IFSOCK mode:0666 dev:174,0 ino:4686 uid:0 gid:0 size:0 O_RDWR|O_NONBLOCK 5: S_IFREG mode:0644 dev:32,24 ino:143624 uid:0 gid:0 size:4 O_WRONLY|O_LARGEFILE advisory write lock set by process 245 7: S_IFSOCK mode:0666 dev:174,0 ino:3717 uid:0 gid:0 size:0 O_RDWR 8: S_IFDOOR mode:0444 dev:179,0 ino:65516 uid:0 gid:0 size:0 O_RDONLY|O_LARGEFILE FD_CLOEXEC door to nscd[171] This listing shows the files open by the dtlogin process. Notice how easy it is to decipher the file types in this output. We have: S_IFDIR directory files S_IFREG regular files S_IFCHR character mode device S_IFSOCK sockets S_IFDOOR a "door" file Flags That Specify Access Type The following OFlag parameter flag values specify type of access: O_RDONLY The file is opened for reading only. O_WRONLY The file is opened for writing only. O_RDWR The file is opened for both reading and writing. Limits on the number of files that a process can open can be changed system-wide in the /etc/system file. If you support a process that opens a lot of sockets, then you can monitor the
number of open files and socket connections by using a command such as this: # /usr/proc/bin/pfiles | grep mode | wc -l The third limit determines how many file references can be held in memory at any time (in the inode cache). If you're running the sar utility, then a sar -v command will show you (in one column of its output (inod-sz)) the number of references in memory and the maximum possible. On most systems, these two numbers will be oddly stable throughout the day. The system maintains the references even after a process has stopped running -- just in case it might need them again. These references will be dropped and the space reused as needed. The sar output might look like this: 00:00:00 proc-sz ov inod-sz ov file-sz ov 11:20:00 400/20440 0 41414/46666 0 1400/1400 0 0/0 The 4th field reports the number of files currently referenced in the inode cache and the maximum that can be stored.
EXP shell script: ================= #!/usr/bin/ksh NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 export NLS_LANG ORACLE_SID=ECM export ORACLE_SID cd /u03/dumps/ECM mv ECM.dmp.Z ECMformer.dmp.Z exp system/arcturus81 file=ECM.dmp full=y statistics=none cp ECM.dmp /u01/dumps/ECM compress -v ECM.dmp xntpd: ====== The xntpd daemon sets and maintains a Unix system time-of-day in compliance with Internet standard time servers. The xntpd daemon is a complete implementation of the Network Time Protocol (NTP) version 3 standard, as defined by RFC 1305, and also retains compatibility with version 1 and 2 servers as defined by RFC 1059 and RFC 1119, respectively. The xntpd daemon does all computations in fixed point arithmetic and does not require floating point code. The xntpd daemon reads from a configuration file (/etc/ntp.conf is the default) at startup time. You can override the configuration file name from the command line. You can also specify a working, although limited, configuration entirely on the command line, eliminating the need
for a configuration file. Use this method when configuring the xntpd daemon as a broadcast or multicast client, that determines all peers by listening to broadcasts at runtime. You can display the xntpd daemon internal variables with the ntpq command (Network Time Protocol (NTP) query program). You can alter configuration options with the xntpdc command. Note for AIX: checking the status of the xntpd subsystem: # lssrc -s xntpd utmpd: ====== Solaris: NAME
utmpd - utmpx monitoring daemon
SYNOPSIS utmpd [-debug] DESCRIPTION The utmpd daemon monitors the /var/adm/utmpx file. utmpx(4) (and utmp(4) for historical information).
See
utmpd receives requests from pututxline(3C) by way of a named pipe. It maintains a table of processes and uses poll(2) on /proc files to detect process termination. When utmpd detects that a process has terminated, it checks that the process has removed its utmpx entry from /var/adm/utmpx. If the process' utmpx entry has not been removed, utmpd removes the entry. By periodically scanning the /var/adm/utmpx file, utmpd also monitors processes that are not in its table. OPTIONS -debug Run in debug mode, leaving the process connected to the controlling terminal. Write debugging information to standard output. HP-UX 11i: NAME
[Toc] [Back] utmpd - user accounting database daemon
SYNOPSIS [Toc] [Back] /usr/sbin/utmpd DESCRIPTION [Toc] [Back] utmpd, user accounting database daemon, manages the user accounting database which is the database of currently logged-in users. This was previously maintained by /etc/utmp and /etc/utmpx files on HP-UX.
Upon startup, utmpd writes its pid to the file /etc/useracct/utmpd_pid. Applications can add, update, or query entries into the database using the getuts() APIs. See the getuts(3C) manual page for more information. utmpd(1M) takes care of synchronizing the legacy /etc/utmpx file and its own in-memory database. The synchronization is bi-directional from the utmpd's database to the /etc/utmpx and from the /etc/utmpx file to utmpd's database. However, this synchronization does not happen in real time. There is a time lag which could span from a few seconds on a lightly loaded system to a few minutes on a heavily loaded system. pwconv: ======= NAME
pwconv - installs and updates /etc/shadow from /etc/passwd
DESCRIPTION The pwconv command creates and information from /etc/passwd.
updates
with
information
/etc/shadow
with
pwconv relies on a special value of 'x' in the password field of /etc/passwd. This value of 'x' indicates that the password for the user is already in /etc/shadow and should not be modified. If the /etc/shadow file does not exist, this command will create /etc/shadow with information from /etc/passwd. The command populates /etc/shadow with the user's login name, password, and password aging information. If password aging information does not exist in /etc/passwd for a given user, none will be added to /etc/shadow. However, the last changed information will always be updated. If the /etc/shadow file does exist, the following tasks will be performed: Entries that are in the /etc/passwd file and not in the /etc/shadow file will be added to the /etc/shadow file. Entries that are in the /etc/shadow file and not in the /etc/passwd file will be removed from /etc/shadow. Password attributes (for example, password and aging information) that exist in an /etc/passwd entry will be moved to the corresponding entry in /etc/shadow. The pwconv command can only be used by the super-user. ESCON: ====== The Enterprise System Connection Architecture�, ESCON, was developed by IBM as a
channel connection architecture with the intent of improving connectivity by incorporating fibre optics into a network. ESCON uses fibre optics to replace existing bus and tag cables in a new or existing data centre. Designed to connect a wide range of peripherals to IBM mainframe computers, the architecture supports data communications at a speed of 200Mbps. Basically, its a fiber optic switch, connecting Control Units or other nodes. FICON: ====== FICON (for Fiber Connectivity) is a high-speed input/output (I/O) interface for mainframe computer connections to storage devices or other nodes. As part of IBM's S/390 or z servers, FICON channels increase I/O capacity through the combination of a new architecture and faster physical link rates to make them up to eight times as efficient as ESCON (Enterprise System Connection), IBM's previous fiber optic channel standard. nscd: ===== nscd is a process that provides a cache for the most common name service requests. It starts up during multi-user boot. The default configuration-file /etc/nscd.conf determines the behavior of the cache daemon. See nscd.conf(4). nscd provides caching for the passwd(4), group(4), hosts(4), ipnodes(4), exec_attr(4), prof_attr(4), and user_attr(4) databases through standard libc interfaces, such as gethostbyname(3NSL), getipnodebyname(3SOCKET), gethostbyaddr(3NSL), and others. Each cache has a separate time-to-live for its data; modifying the local database (/etc/hosts, /etc/resolv.conf, and so forth) causes that cache to become invalidated upon the next call to nscd. The shadow file is specifically not cached. getspnam(3C) calls remain uncached as a result. nscd also acts as its own administration tool. If an instance of nscd is already running, commands are passed to the running version transparently. In order to preserve NIS+ security, the startup script for nscd (/etc/init.d/nscd) checks the permissions on the passwd table if NIS+ is being used. If this table cannot be read by unauthenticated users, then nscd will make sure that any encrypted password information returned from the NIS+ server is supplied only to the owner of that password. A sample /etc/nscd.conf file, which minimizes the functionality of nscd, is as follows:
logfile enable-cache enable-cache positive-time-to-live negative-time-to-live suggested-size keep-hot-count old-data-ok check-files enable-cache enable-cache enable-cache
/var/adm/nscd.log passwd no group no hosts 3600 hosts 5 hosts 211 hosts 20 hosts no hosts yes exec_attr no prof_attr no user_attr no
If your system has any instability with respect to host names and/or IP addresses, it is possible to substitute the following line for all the above lines containing hosts. This may slow down host name lookups, but it should fix the name translation problem. enable-cache
hosts
no
utmp, wtmp, failedlogin File Format: ==================================== AIX: ---Purpose Describes formats for user and accounting information. Description The utmp file, the wtmp file, and the failedlogin file contain records with user and accounting information. When a user attempts to logs in, the login program writes entries in two files: The /etc/utmp file, which contains a record of users logged into the system. The /var/adm/wtmp file (if it exists), which contains connect-time accounting records. On an invalid login attempt, due to an incorrect login name or password, the login program makes an entry in: The /etc/security/failedlogin file, which contains a record of unsuccessful login attempts. The records in these files follow the utmp format, defined in the utmp.h header file. To convert a binary record in wtmp format to an ASCII record called dummy.file, enter: /usr/sbin/acct/fwtmp < /var/adm/wtmp > /etc/dummy.file The content of a binary wtmp file is redirected to a dummy ASCII file. failedlogin: Use the who command to read the contents of the /etc/security/failedlogin file:
# who /etc/security/failedlogin # who /etc/security/failedlogin > /tmp/failed_login.txt To clear the file use: # cp /dev/null /etc/security/failedlogin
Notes on the libc libary in AIX 5L: =================================== What is it? ----------Most unixes has a couple of important shared libraries. One of them is the libc.a lib on AIX. libc = C Libary glibc = GNU C library (on linux and open systems) It is an XCOFF shared library under AIX and hence a critical part of the running system. The standard C library, `libc.a', is automatically linked into your programs by the `gcc' control program. Or it is used by C/C++ compilers to create statically linked programs. It provides many of the functions that are normally associated with C programs For each function or variable that the library provides, the definition of that symbol will include information on which header files to include in your source to obtain prototypes and type definitions relevant to the use of that symbol. Note that many of the functions in `libm.a' (the math library) are defined in `math.h' but are not present in libc.a. Some are, which may get confusing, but the rule of thumb is this--the C library contains those functions that ANSI dictates must exist, so that you don't need the -lm if you only use ANSI functions. In contrast, `libm.a' contains more functions and supports additional functionality such as the matherr call-back and compliance to several alternative standards of behavior in case of FP errors. Version: -------On AIX, you can determine the version of the libc fileset on your machine as follows: # lslpp -l bos.rte.libc
Its gone, now what? ------------------Note: You might want to look at the "recsh" recovery shell command first. Other ways to recover: You can recover from this without rebooting or reinstalling, if you have another copy of libc.a available that is also named "libc.a". If you moved libc.a to a different directory, you're in luck -- do the following: export LIBPATH=/other/directory And your future commands will work. But if you renamed libc.a, this won't do it. If you have an NFS mounted directory somewhere, you can put libc.a on the that host, and point LIBPATH to that directory as shown above. Or.. If you have a good copy of from somewhere.. Copy the libc.a fix into place, e.g., a. b. c. d. e. f.
# # # # # #
cp -f your_dir/locale_format/lib/libc.a /usr/ccs/lib/ chown bin.bin /usr/ccs/lib/libc.a chmod 555 /usr/ccs/lib/libc.a ln -sf /usr/ccs/lib/libc.a /usr/lib/libs.a unset LIBPATH slibclean
Make sure that the new libraries will be picked up at the next reboot. Now Reboot. IBM's version on how to recover: -------------------------------Restore Access to an Unlinked or Deleted System Library When the existing libc.a library is not available, most operating system commands are not recognized. The most likely causes for this type of problem are the following: The link in /usr/lib no longer exists. The file in /usr/ccs/lib has been deleted. The following procedure describes how to restore access to the libc.a library. This procedure requires system downtime. If possible, schedule your downtime when it least impacts your workload to protect yourself from a possible loss of data or functionality.
The information in this how-to was tested using AIX� 5.3. If you are using a different version or level of AIX, the results you obtain might vary significantly. Restore a Deleted Symbolic Link Use the following procedure to restore a symbolic link from the /usr/lib/libc.a library to the /usr/ccs/lib/libc.a path: With root authority, set the LIBPATH environment variable to point to the /usr/ccs/lib directory by typing the following commands: # LIBPATH=/usr/ccs/lib:/usr/lib # export LIBPATH At this point, you should be able to execute system commands. To restore the links from the /usr/lib/libc.a library and the /lib directory to the /usr/lib directory, type the following commands: ln -s /usr/ccs/lib/libc.a /usr/lib/libc.a ln -s /usr/lib /lib At this point, commands should run as before. If you still do not have access to a shell, skip the rest of this procedure and continue with the next section, Restore a Deleted System Library File. Type the following command to unset the LIBPATH environment variable. unset LIBPATH
Symbol resolution failed for /usr/lib/libc_r.alibc_r.a: ======================================================= Note 1: ------libc_r.a is a standard re-entrant C library, which allows synchronization of the tasks at exit.
Note 2: ------thread: Q: Hi there I've just tried to install Informix 9.3 64-bit on AIX 52. It failed with the error shown below. Any suggestions as to what could be wrong? I tried to find information on the web as to what versions of Informix (if any) are
supported on AIX52, but could not find anything. I would be grateful for any advice in this matter. Disk Initializing Demo IBM Informix Dynamic Server exec(): 0509-036 Cannot load program /u01/app/informix-9.3-64/server/bin/oninit because of the following errors: 0509-130 Symbol resolution failed for /usr/lib/libc_r.a[aio_64.o] becau e: 0509-136 Symbol kaio_rdwr64 (number 0) is not exported from dependent module /unix. 0509-136 Symbol listio64 (number 1) is not exported from dependent module /unix. 0509-136 Symbol acancel64 (number 2) is not exported from dependent module /unix. 0509-136 Symbol iosuspend64 (number 3) is not exported from dependent module /unix. 0509-136 Symbol aio_nwait (number 4) is not exported from dependent module /unix. 0509-150 Dependent module libc_r.a(aio_64.o) could not be loaded. 0509-026 System error: Cannot run a file that does not have a valid for at. 0509-192 Examine .loader section symbols with the 'dump -Tv' command. Bundle Install program has finished A: Did you enable AIX aio? If not then run the following smit command. $ smit aio Choose "Change / Show Characteristics of Asynchronous I/O" Set the state to be configure at system restart to Available. Set state of fast path to Enable. Also check that you enabled 64-bit version of AIX run time. Note 3: ------Q: Suppose you get the error: Symbol resolution failed for /usr/lib/libc_r.a Examples: Error: Exec(): 0509-036 Cannot load program Article ID: 20180 Software: ArcGIS - ArcInfo 8.0.1, 8.0.2, 8.1 ArcView GIS 3.1, 3.2, 3.2a Platforms: AIX 4.3.2.0, 4.3.3.0
Error Message Executing some ArcInfo Workstation commands, or running ArcView GIS cause the following errors to occur: Exec(): 0509-036 Cannot load program ... because of the 0509-130 Symbol resolution failed for /usr/lib/libc_r.a(aio.o) because: 0509-136 Symbol kaio_rdwr (number 0) is not exported from dependant module /unix 0509-136 Symbol listio (number 1) is not exported from dependant module /unix 0509-136 Symbol acancel (number 2) is not exported from dependant module /unix 0509-136 Symbol iosuspend (number 3) is not exported from dependant module /unix 0509-136 Symbol aio_nwait (number 4) is not exported from dependant module /unix 0509-192 Examine .loader section symbols with the 'dump -Tv' command. root@n5110l13:/appl/emcdctm/dba/log#cat dmw_et.log Could not load program ./documentum: Symbol resolution failed for /usr/lib/libc_r.a(aio.o) because: Symbol kaio_rdwr (number 0) is not exported from dependent module /unix. Symbol listio (number 1) is not exported from dependent module /unix. Symbol acancel (number 2) is not exported from dependent module /unix. Symbol iosuspend (number 3) is not exported from dependent module /unix. Symbol aio_nwait (number 4) is not exported from dependent module /unix. Symbol aio_nwait64 (number 5) is not exported from dependent module /unix. Symbol aio_nwait_timeout (number 6) is not exported from dependent module /unix. Symbol aio_nwait_timeout64 (number 7) is not exported from dependent module /unix. System error: Error 0 A: Cause The AIX asynchronous I/O module has not been loaded. Solution or Workaround Load asynchronous I/O. You must do this as a ROOT user: Use SMITTY and navigate to Devices > Async I/O > Change/Show. Make the defined option available. Reboot the machine. or Enable AIO by running the following commands: /usr/sbin/chdev -l aio0 -a autoconfig=available /usr/sbin/mkdev -l aio0
KDB kernel debugger and kdb command: ==================================== AIX Only KDB kernel debugger and kdb command This document describes the KDB kernel debugger and kdb command. The KDB kernel debugger and the kdb command are the primary tools a developer uses for debugging device drivers, kernel extensions, and the kernel itself. Although they appear similar to the user, the KDB kernel debugger and the kdb command are two separate tools: -- KDB kernel debugger: The KDB kernel debugger is integrated into the kernel and allows full control of the system while a debugging session is in progress. The KDB kernel debugger allows for traditional debugging tasks such as setting breakpoints and single-stepping through code. -- kdb command: This command is implemented as an ordinary user-space program and is typically used for post-mortem analysis of a previously-crashed system by using a system dump file. The kdb command includes subcommands specific to the manipulation of system dumps. Both the KDB kernel debugger and kdb command allow the developer to display various structures normally found in the kernel's memory space. Both do the following: -Provide numerous subcommands to decode various data structures found throughout the kernel. -Print the data structures in a user-friendly format. -Perform debugging at the machine instruction level. Although this is less convenient than source level debugging, it allows the KDB kernel debugger and the kdb command to be used in the field where access to source code might not be possible. -Process the debugging information found in XCOFF objects. This allows the use of symbolic names for functions and global variables. slibclean: ========== AIX: Note 1: Removes any currently unused modules in kernel and library memory. Syntax # slibclean
Description The slibclean command unloads all object files with load and use counts of 0. It can also be used to remove object files that are no longer used from both the shared library region and in the shared library and kernel text regions by removing object files that are no longer required. Files /usr/sbin/slibclean Contains the slibclean command.
thread_getregs, thread_waitlock, sigprocmask: ============================================= Note 1: ------thread: Q: thread_waitlock Hello all Can someone please provide me with a link to where the above function is documented ?? I know its part of libc_r.a and is used for thread synchronization ... I need to get some details on the function as to what exactly it does since a program I'm trying to debug is getting a ENOTSUP error while calling this function ... Would really appreciate the help. A: thread_waitlock() Reply from Richard Joltes on 8/25/2003 5:48:00 PM This doesn't seem to be documented anywhere, but it appears this function is _not_ in libc(_r). I found this elsewhere: "...kernel symbols are defined by import lists found in /usr/lib. You'll need threads.exp and syscalls.exp. Look at the -bI option in the ld documentation." You'll find references to this function if you look through these two file so maybe that's your best option. Threads.exp even specifically says "the system calls listed below are not imported by libc.a." Note 2: ------thread:
APAR: IY17298 COMPID: 5765C3403 REL: 430 ABSTRACT: ASSERT IN THREAD_SETSTATE_FAST PROBLEM DESCRIPTION: Program termination due to an assert in thread_setstate_fast. PROBLEM SUMMARY: Assert in thread_setstate_fast PROBLEM CONCLUSION: Increase lock scope. Note 3: ------thread: Paul Pluzhnikov wrote: > "pankajtakawale" writes: > > Here is the snippet of truss output > ... > > sbrk(0x00000060)
Err#12 ENOMEM
> > Do i need to increase swap space or thread stack size? > Increasing swap might help, but I would not expect it. > You are running out of *heap* space. Check your limits, e.g. 'ulimit > -a' in *sh or 'limit' in *csh. Yes process was running out of heap space. In my local environment I decreased soft limit of data segment and ran app. truss showed 'sbrk faild with ENOMEM'. Now Im planning to run app in very heavy configuration such that 'unlimited data segment' too will be insufficient. And on same configuration I will make app large addr space model by setting env variable LDR_CNTRL (app shud run in large addr space model). And will update thread with results. Thanks for your valuable help Paul. Note 4: ------+ + + + + + + + + + +
On Linux, the interface exports a bunch of "#define __NR_foo 42" style definitions, so there is no implementation. On AIX, syscall numbers are not fixed ahead of time; in principle each process can have its own assignment of numbers to actual syscalls. As a result we have a bunch of global variables to store the number for each syscall, which are assigned to at system startup, and a bunch of #defines which map "__NR_foo" names to these global variables. Initially, when we don't know what a syscall's number is, it is set to __NR_AIX5_UNKNOWN.
+ Therefore, on AIX, this module provides a home for those variables. + + It also provides VG_(aix5_register_syscall) to assign numbers to + those variables. +*/ e.g. +Int VG_(aix5_NR__sigqueue) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR__sigsuspend) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR__sigaction) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_sigprocmask) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_siglocalmask) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_count_event_waiters) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_waitact) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_waitlock_local) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_waitlock) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_wait) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_unlock) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_twakeup_unlock) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_twakeup_event) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_twakeup) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_tsleep_event) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_tsleep_chkpnt) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_tsleep) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_post_many) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_post) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_ue_proc_unregister) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_ue_proc_register) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_kthread_ctl) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR__thread_setsched) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_threads_runnable) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_getregs) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_terminate_unlock) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_terminate_ack) = __NR_AIX5_UNKNOWN; +Int VG_(aix5_NR_thread_setstate_fast) = __NR_AIX5_UNKNOWN; etc....
skulker command: ================ AIX: The skulker command is a command file for periodically purging obsolete or unneeded files from file systems. Candidate files include files in the /tmp directory, files older than a specified age, a.out files, core files, or ed.hup files. The skulker command is normally invoked daily, often as part of an accounting procedure run by the cron command during off-peak periods. Modify the skulker command to suit local needs following the patterns shown in the distributed version. System users should be made aware of the criteria for automatic file removal.
The find command and the xargs command form a powerful combination for use in the skulker command. Most file selection criteria can be expressed conveniently with find expressions. The resulting file list can be segmented and inserted into rm commands using the xargs command to reduce the overhead that would result if each file were deleted with a separate command. Note Because the skulker command is run by a root user and its whole purpose is to remove files, it has the potential for unexpected results. Before installing a new skulker command, test any additions to its file removal criteria by running the additions manually using the xargs -p command. After you have verified that the new skulker command removes only the files you want removed, you can install it. To enable the skulker command, you should use the crontab -e command to remove the comment statement by deleting the # (pound sign) character from the beginning of the /usr/sbin/skulker line in the /var/spool/cron/crontabs/root file.
L1 cache, L2 cache, L3 cache and differences: ============================================= Note 1: ------Q: Question from cmos "What is L2 cache? What is L3 cache? What is the major difference between the two." A: Answer from LinksMaster "CPU Cache (the example CPU is a little old but the concepts are still the same) * The initial level of storage on a processor are the registers. The registers are where the actually processing input and output takes place. * L1 cache - Then the level 1 cache comes next. It is logically the closest high speed memory to the CPU core / registers. It usually runs at the full speed (meaning the same as the CPU core clockspeed). L1 often comes in size of 8kB, 16kB, 32kB, 64kB or 128kB. But, it is very high speed even though the amount is relatively small.
* L2 cache - The next level of cache is L2, or level 2. Nowadays L2 is larger than L1 and it often comes in 256kB, 512kB and 1,024MB amounts. L2 often runs at 1/4, 1/2 or full speed in relation to the CPU core clockspeed. * L3 cache - Level 3 cache is something of a luxury item. Often only high end workstations and servers need L3 cache. L3 has been both "on-die", meaning part of the CPU or "external" meaning mounted near the CPU on the motherboard. It comes in many sizes and speeds. Note 2: ------L2 cachhe, short for Level 2 cache, cache memory that is external to the microprocessor. In general, L2 cache memory, also called the secondary cache, resides on a separate chip from the microprocessor chip. Although, more and more microprocessors are including L2 caches into their architectures. As more and more processors begin to include L2 cache into their architectures, Level 3 cache is now the name for the extra cache built into motherboards between the microprocessor and the main memory. Quite simply, what was once L2 cache on motherboards now becomes L3 cache when used with microprocessors containing built-in L2 caches.
xcom: ===== Used for filetransfer between systems with many nice features like printing a report of the transfer, queuing of transfers, EBCIDIC - ASCII conversion, scheduling etc.. The command "xcom62" is used for SNA networks. The command "xcomtcp" is used for the tcpip networks. The xcom daemon is "xcomd" in /opt/xcom/bin Use: xcomd -c xcomd
to kill/stop to start the daemon.
logging and config of xcom events can be found in: /usr/spool/xcom -
xcom.glb has all conf. settings and is a superset of xcom.cnf After reconfig, stop and start the daemon atoe files are for ascii / ebcdic conversions xcomqm for maintaining queues
- xcom.trusted must be defined for each trusted transfer - xcomtool is for GUI sending of files is done with "xcomtcp -c[1234] other options" where -c1 means sending a file Example commands: xcomtcp -c1 -f /tmp/xcom.cnf LOCAL_FILE=/tmp/xcomtest.txt REMOTE_FILE=Q:\ REMOTE_SYSTEM=NLPA020515.patest.nl.eu.abnamro.com QUEUE=NO PROTOCOL=TCPIP PORT=8044 xcomtcp -c1 -f /tmp/xcom.cnf LOCAL_FILE=/tmp/xcomtest.txt REMOTE_FILE=c:\test.txt REMOTE_SYSTEM=NLPR020796.branches.nl.eu.abnamro.com QUEUE=NO PROTOCOL=TCPIP PORT=8044 xcomtcp -c1 -f /tmp/xcom.cnf LOCAL_FILE=/tmp/xcomtest.txt REMOTE_FILE=Q:\XCOM\DATA\IN\t.txt REMOTE_SYSTEM=NLPA020515.patest.nl.eu.abnamro.com QUEUE=NO PROTOCOL=TCPIP PORT=8044 xcomtcp -c1 -f /tmp/xcom.cnf LOCAL_FILE=/tmp/xcomtest.txt REMOTE_FILE=Q:\ REMOTE_SYSTEM=NLPA020515.patest.nl.eu.abnamro.com QUEUE=NO PROTOCOL=TCPIP PORT=8044 where "/tmp/xcom.cnf" contains parameters (e.g. userid, password etc..) not specified at the prompt.
vmcid: IBM minor code: E02 =========================== Note 1: ------Seems there is no port 32888 assign on this systeem ZD111L08 /etc/services #
32775-32895
Maybe this is the issue.. Note 2: -------
AIX: 0403-031 The fork function failed: ======================================== run "svmon -P" to see the top consumers. You might try using:
# Unassigned
1. increase the paging space chps -s number_of_PP's hd6 Or 2. increase the maxuproc might help if its too low: maxuproc: Values: Display: Change:
Specifies the maximum number of processes per user ID. Default: 40; Range: 1 to 131072 lsattr -E -l sys0 -a maxuproc chdev -l sys0 -a maxuproc=NewValue
3. Actually, you should increase RAM memory as a structural solution, or decrease the number of processes. AIX create Ramdisk: =================== Example: # # # # #
mkramdisk 40000 ls -l /dev | grep ram mkfs -V jfs /dev/ramdiskx mkdir /ramdiskx mount -V jfs -o nointegrity /dev/ramdiskx /ramdiskx
AIX 5.3 ping error: =================== thread: Q: Hi all, If a normal use trys to ping to my workstation then it gives the followin error "0821-067 ping: The socket creation call failed.: The file access permissions do not allow the specified action" And in my workstation if i login as non-root user then if I ping to some other system it gives the same error.. whereas it is not so with root user. Any suggestions what can be the problem? A: Hi, looks like problems in program file ping rights... in my AIX system i have the following for /usr/sbin/ping
# ls -l /usr/sbin/ping -r-sr-xr-x 1 root system 31598 Dec 17 2002 /usr/sbin/ping # 100kggoud A: Technote IBM Cannot ping as Non-root user Technote (FAQ) Problem When trying to ping as a user that is not root, the following error message was displayed: 0821-067 Ping: the socket creation call failed. the file access permissions do not allow the specified actions. Solution -------------------------------------------------------------------------------Environment AIX Version 5.x Change the setuid bit permissions for /usr/sbin/ping. Enter: chmod 4555 /usr/sbin/ping
AIX: 0403-006 Execute permission denied: ======================================== Note 1: ------thread Q: hello all,now,I want to exe a shell script,the result of command "ls -l",it's permission: -rwxr-x--x but i use the "./proname" to exe it,the result is: 0403-006 Execute permission denied WHY?? the permission is all eXecute!!! A: If permissions seems ok, then chcek this: Make sure there are no "empty" lines with an "~" below the last statement, like ~
because "~" cannot be executed.
SAM on HP-UX: ============= The easiest way to administer HP-UX is to use Sam. As root, simply type "sam"... easy, huh? If you're in text-mode, you'll get a curses-based window, and if you're in CDE / VUE, you will get a new window on your workspace... Simply navigate your way through you can do a lot of your administration via sam. Some example screens in textmode sam # sam .. .. Starting the terminal version of sam... To move around in sam: - use the "Tab" key to move between screen elements - use the arrow keys to move within screen elements - use "Ctrl-F" for context-sensitive help anywhere in sam On screens with a menubar at the top like this: -----------------------------------------------------|File View Options Actions Help| | ---- ---- ------- ------------------------------- ---| -
use use use use use
"Tab" to move from the list to the menubar the arrow keys to move around "Return" to pull down a menu or select a menu item "Tab" to move from the menubar to the list without selecting a menu item the spacebar to select an item in the list
On any screen, press "CTRL-K" for more information on how to use the keyboard. + === System Administration Manager (gavnh300) (1) + �File View Options Actions Help � � Press CTRL-K for keyboard help. � �SAM Areas � �------------------------------------------------------------------------------� � Source Area � �+---------------------------------------------------------------------------+ � �� SAM Accounts for Users and Groups -> ^ � �� SAM Auditing and Security -> � �� SAM Backup and Recovery -> � �� SAM Clusters -> � �� SAM Disks and File Systems -> � �� SAM Display -> �
�� SAM
Kernel Configuration
->
�
�� SAM Networking and Communications -> � �� SAM Performance Monitors -> � �� SAM Peripheral Devices -> � �� SAM Printers and Plotters -> � �� SAM Process Management -> � �� Other Resource Management -> � �� SAM Routine Tasks -> v � �+---------------------------------------------------------------------------+ � � � +------------------------------------------------------------------------------+ Choose "Accounts for Users and Groups" and the following screen shows: + === System Administration Manager (gavnh300) (1) + �File View Options Actions Help � � Press CTRL-K for keyboard help. � �SAM Areas:Accounts for Users and Groups � �------------------------------------------------------------------------------� � Source Area � �+---------------------------------------------------------------------------+ � �� ..(go up) ^ � �� SAM Groups � �� SAM Users � �� � �� � �� � �� � �� � �� � �� � �� � �� � �� � �� v � �+---------------------------------------------------------------------------+ � � Working... � +------------------------------------------------------------------------------+ + === Accounts for Users and Groups (gavnh300) (1) �File List View Options Actions � � Add... �Template In Use: None � User Templates -> �Filtering: Displaying � Task Customization... �-----------------------� ===================================== �Users � Modify... �-----------------------� Remove... � Login User ID � Modify Secondary Group Membership... � Name (UID) � Modify User's Password �+----------------------� Reset User's Password �� ru1160 6243 � ------------------------------------�� sa2064 6975 � Deactivate... �� sa2194 8172 � -------------------------------------
+ Help � � � � � � � �--------------� �f 314 selected� �--------------� �ce Of � �e Lo � �------------+ � �LDEV R. ^ � �RATOR I � � �LMAN S � �
�� sc3060 5318 � Modify Security Policies... �MAN KE � � �� sc4634 8140 � Set Authorized Login Times... �DONLY JH � � �� sc6228 7027 +---------------------------------------+LMAN P. � �� se1223 8170 SEL sysman SYSMAN VA � � �� sh0403 7735 SHARIF oper OPERATOR T. � � �� si1608 7479 Sinha support APPLMAN R � � �� si1624 7391 Sinha support APPLMAN A v � � + � � � +------------------------------------------------------------------------------+
AIX 5L vmstat output issues: ============================ Suppose you see output like this: [pl003][tdbaeduc][/dbms/tdbaeduc/educroca/admin/dump/bdump] vmstat -v 1572864 memory pages 1506463 lruable pages 36494 free pages 7 memory pools 336124 pinned pages 80.0 maxpin percentage 20.0 minperm percentage 80.0 maxperm percentage 43.4 numperm percentage 654671 file pages 0.0 compressed percentage 0 compressed pages 45.8 numclient percentage 80.0 maxclient percentage 690983 client pages 0 remote pageouts scheduled 0 pending disk I/Os blocked with no pbuf --> 8868259 paging space I/Os blocked with no psbuf --> 2740 filesystem I/Os blocked with no fsbuf --> 13175 client filesystem I/Os blocked with no fsbuf --> 319766 external pager filesystem I/Os blocked with no fsbuf What is the meaning, and interpretation, of the outputlines like "pending disk I/Os blocked with no pbuf" ? Note 1: ------http://www.circle4.com/jaqui/eserver/eserver-AugSep06-AIXPerformance.pdf .. .. The last five lines of the vmstat -v report are useful when you're looking for I/O problems. The first line is for disk I/Os that were blocked because there were no pbufs. Pbufs are pinned memory buffers used to hold I/O requests at the logical volumemanager layer. Prior to AIX v5.3, this was a systemwide parameter.
It's now tuneable on a volume-group basis using the lvmo command. The ioo parameter that controls the default number of pbufs to add when a disk is added to a volume groupis pv_min_pbuf, and it defaults to 512. This specifies the minimum number of pbufs per PV that the LVM uses, and it's a global value that applies to all VGs on the system. If you see the pbuf blocked I/Os field above increasing over time, you may want to use the lvmo -a command to find out which volume groups are having problems with pbufs and then slowly increase pbufs for that volume group using the lvmo command. A reasonable value could be 1024. Paging space I/Os blocked with no psbuf refers to the number of paging space I/O requests blocked because no psbuf was available. These are pinned memory buffers used to hold I/O requests at the virtual memory manager layer. If you see these increasing, then you need to either find out why the system is paging or increase the size of the page datasets. Filesystem I/Os blocked with no fsbufs refers to the number of filesystem I/O requests blocked because no fsbuf was available. Fsbufs are pinned memory buffers used to hold I/O requests in the filesystem layer. If this is constantly increasing, then it may be necessary to use ioo to increase numfsbufs so that more bufstructs are available. The default numfsbufs value is determined by the system and seems to normally default to 196. I regularly increase this to either 1,024 or 2,048. Client filesystem I/Os blocked with no fsbuf refers to the number of client filesystem I/O requests blocked because no fsbuf was available. Fsbufs are pinned memory buffers used to hold I/O requests in the filesystem layer. This includes NFS, VxFS (Veritas) and GPFS filesystems. Finally, ext pager filesystem I/Os blocked with no fsbuf refers to the number of external pager client filesystem I/O requests blocked because no fsbuf was available. JFS2 is an external pager client filesystem. If I see this growing, I typically set j2_nBufferPerPagerDevice=1024 Note 2: ------thread: Q: we have I/O issue on the AIX box for our Oracle DB the disks having the Database files are always 100% busy and the wa column in vmstat hits above 50 and the vmstat -v show the I/O's being blocked 2238141 pending disk I/Os blocked with no pbuf 13963233 paging space I/Os blocked with no psbuf 2740 filesystem I/Os blocked with no fsbuf 1423313 client filesystem I/Os blocked with no fsbuf
1128548 external pager filesystem I/Os blocked with no fsbuf What does these indicate, short of real mem or does some kernal parameters need to be adjusted? A: I'd up the number of fsbufs per filesystem. What are your current settings? ioo -L|egrep 'numfsbufs|j2_nBufferPerPagerDevice' numfsbufs is for jfs filesystems j2_nBuffer... is for jfs2 filesystems if I'm not mistaken. Note, if you change these values, you have to umount/mount the filesystems to take effect. I.e. you have to bring Oracle down. HTH, p5wizard p5wizard, Thanks, I dont have the access to it,i will get the SA to get me the output. Are these figures cummulative since the last reboot of the box. what a good setting for this dbinsight (TechnicalUser) 10 Mar 06 14:06 ioo -L |egrep 'numfsbufs|j2_nBufferPerPagerDevice' numfsbufs 512 196 512 1 j2_nBufferPerPagerDevice 512 512 512 0
2G-1 2G-1
M
The above are our settings, Are these the default settings? p5wizard (IS/IT--Management) 13 Mar 06 3:35 answers to your questions: yes, cumulative (so depends on how long the system's been running to interpret the values). no, already been increased for jfs yes, defaults for jfs2 1st value = current situation 2nd value = system default 3rd value = value for nextboot # ioo -L|head -3; ioo -L|egrep 'numfs|j2_nBuff' NAME CUR DEF BOOT MIN MAX UNIT TYPE DEPENDENCIES -------------------------------------------------------------------------------j2_nBufferPerPagerDevice 512 512 512 0 256K M
numfsbufs
400
196
400
1
2G-1
M
But as I said before, doesn't help to increase 'em unless you unmount/mount the filesystems. As your SA has upped the 'NEXTBOOT' values, I guess (s)he knows about that. Run "topas 2" for a few iterations, and post that screenful please. Also "vmo -L|egrep 'perm%|client%'" output please. You have a very high value: 13963233 paging space I/Os blocked with no psbuf On my large DB servers this is close to zero. Run "lsps -a" and post that output also please. I googled for "aix psbufs" and found an Oracle AIX performance Technical Brief, here's an excerpt: # vmstat �v | tail -5 (we only need last 5 lines) 0 pending disk I/Os blocked with no pbuf o for pbufs, increase pv_min_pbuf using ioo, 0 paging space I/Os blocked with no psbuf o for psbufs, stop paging or add more paging space, 8755 filesystem I/Os blocked with no fsbuf ?? JFS o for fsbufs, increase numfsbufs using ioo, o default is 196, recommended starting value is 568, 0 client filesystem I/Os blocked with no fsbuf (NFS/Veritas) o for client filesystem fsbufs, increase: � nfso�s nfs_v3_pdts and nfs_v3_vm_bufs 2365 external pager filesystem I/Os blocked with no fsbuf (JFS2) o for external pager fsbufs, increase: � j2_nBufferPerPagerDevice, default is 512, recommended value is 2048, � j2_dynamicBufferPreallocation using ioo. Note 3: ------thread: 4.2) File System Buffers. By default, the number of file system buffers is set to 196. For high I/O systems, this is typically too small. To see if you are blocking I/O due to not having enough file system buffers, run: vmstat -v. For JFS file systems, look at the "filesystem I/Os blocked with no fsbuf" line. For JFS2 file systems, look at the "client filesystem I/Os blocked with no fsbuf" line. If these values are more than a couple thousand, you may need to increase the respective parameters. For JFS file systems, you will need to change the numfsbufs parameter. For JFS2 file systems, change the j2_nBufferPerPagerDevice parameter. Changing this parameter does not require a reboot, but will only take effect when the file system is mounted, so you will have to unmount/mount the file system.
4.2) JFS Log Devices. Heavily used filesystems should ALWAYS have their own JFS log on a separate physical disk. All writes to a JFS (or JFS2) file system are written to the JFS log. By default, there is only one JFS log created for any volume group containing JFS file systems. This means that ALL writes to ALL the file systems in the volume group go to ONE PHYSICAL DISK!! (This is, unless, your underlying disk structure is striped or another form of RAID for performance.) Creating separate JFS logs on different physical disks is very important to getting the most out of the AIX I/O subsystem.
/usr/ccs/bin/shlap64: ===================== The /usr/ccs/bin/shlap64 process is the Shared Library Support Daemon. The muxatmd, snmpmibd and aixmibd are Simple Network Managaement Protocol (SNMP) daemons for AIX. All can be turned off by commenting out the entries that start them in /etc/rc.tcpip. shlap64 is part of the 64-bit environment and needs to be running if you are using a 64-bit kernel. The IBM.* programs are part of the Reliable Scalable Cluster Technology which IBM added to AIX v5 from their SP cluster systems. These programs provide additional system monitoring (and alerting if configured to do so). You should probably leave them running. /etc/ncs/glbd: ============== glbd Daemon Purpose Manages the global location broker database. Syntax /etc/ncs/glbd [ -create { -first [-family FamilyName] | -from HostName } ] [ -change_family FamilyName ] [ -listen FamilyList] [ -version ] Description The glbd daemon manages the global location broker (GLB) database. The GLB database, part of the Network Computing System (NCS), helps clients to clients to locate servers on a network or internet. The GLB database stores the locations (specifically, the network addresses and port numbers) of servers on which processes are running. The glbd daemon maintains this database and provides access to it.
There are two versions of the GLB daemon, glbd and nrglbd. RBAC: ===== Role Based Access Control AIX� has provided a limited RBAC implementation since AIX 4.2.1. Most environments require that different users manage different system administration duties. It is necessary to maintain separation of these duties so that no single system management user can accidentally or maliciously bypass system security. While traditional UNIX� system administration cannot achieve these goals, Role Based Access Control can. RBAC allows the creation of roles for system administration and the delegation of administrative tasks across a set of trusted system users. In AIX�, RBAC provides a mechanism through which the administrative functions typically reserved for the root user can be assigned to regular system users. Beginning with AIX 6.1, a new implementation of RBAC provides for a very fine granular mechanism to segment system administration tasks. Since these two RBAC implementations differ greatly in functionality, the following terms are used: -Legacy RBAC Mode The historic behavior of AIX roles that was introduced in AIX 4.2.1 -Enhanced RBAC Mode The new implementation introduced with AIX 6.1 Both modes of operation are supported. However, Enhanced RBAC Mode is the default on a newly installed AIX 6.1 system.
llbd: ===== llbd Daemon Purpose Manages the information in the local location broker database. Syntax llbd [-family FamilyName] [ -version] Description The llbd daemon is part of the Network Computing System (NCS). It manages the local location broker (LLB) database,
which stores information about NCS-based server programs running on the local host. A host must run the llbd daemon to support the location broker forwarding function or to allow remote access (for example, by the lb_admin tool) to the LLB database. In general, any host that runs an NCS-based server program should run an llbd daemon, and llbd should be running before any such servers are started. Additionally, any network or internet supporting NCS activity should have at least one host running a global location broker daemon (glbd). The llbd daemon is started in one of two ways: Through the System Resource Controller (the recommended method), by entering on the command line: startsrc -s llbd By a person with root user authority entering on the command line: /etc/ncs/llbd & TCP/IP must be configured and running on your system before you start the llbd daemon. (You should start the llbd daemon before starting the glbd or nrglbd daemon.)
tripwire: ========= Tripwire data integrity assurance software monitors the reliability of critical system files and directories by identifying changes made to them. Tripwire configuration options include the ability to receive alerts via email if particular files are altered and automated integrity checking via a cron job. Using Tripwire for intrusion detection and damage assessment helps you keep track of system changes. Because Tripwire can positively identify files that have been added, modified, or deleted, it can speed recovery from a break-in by keeping the number of files which must be restored to a minimum. Tripwire compares files and directories against a database of file locations, dates modified, and other data. The database contains baselines, which are snapshots of specified files and directories at a specific point in time. The contents of the baseline database should be generated before the system is at risk of intrusion. After creating the baseline database, Tripwire then compares the current system to the baseline and reports any modifications, additions, or deletions. While Tripwire is a valuable tool for auditing the security state of Red Hat Linux systems, Tripwire is not supported by Red Hat, Inc. Refer to the Tripwire project's website
(http://www.tripwire.org/) for more information about Tripwire. SA-Agent uctsp0: ================ CONTROL-SA is a client/server solution that enables you to manage security systems distributed across multiple platforms. CONTROL-SA synchronizes accounts and passwords across those systems. On AIX, you can find the binaries and files in /usr/lpp/uctsp0. On HP, you can find the binaries and files in /usr/local/uctsp0. To stop the agent: # su - uctsp0 -c stop-ctsa To start the agent: # su - uctsp0 -c start-ctsa EMC Documentum: =============== General: -------The following components are associated with the Content Server: - A database containing relationships that relate to stored content (on filesystems). This database thus contains metadata (and not content). - file storage of the actual content being managed. The file store and database constitue the Documentum Repository abstraction, called Docbase. - A set of key processes that implement the Documentum content management solution such as the Document Broker. - A set of housekeeping utilities, including a Web-based Admin tool. Client Connect: --------------Access to Documentum Docbases is controlled through the Documentum client file dmcl.ini. You need to understand the architecture of Content Server and docbroker and how DMCL connects. Content Server and docbroker are 2 separate processes which are started (usually but not necessarily) on the same machine. Since they are separate processes they listen on different ports. Docbroker usually listens on a well-known port 1489. Content Server will listen on the port you configure in the services file. When you issue a DMCL connect (which is what DAB does - it is a documentum client using DMCL) the DMCL first locates a docbroker. It asks the docbroker for a list of docbases it knows about. The
docbroker returns the names of the docbases and provides details of the Content Server(s) that service the docbase. This includes the host and port details. The DMCL then issues requests directly to the Content Server bypassing the docbroker. Thus you need both the docbroker and the Content Server port open.
BPS http Listener (Installation and Configuration) -------------------------------------------------What is BPS Business Process Services (BPS) provides the gateway to access Docbase for a non Documentum user. It allows HTTP, SMTP of JMS message to be stored directly in the Docbase. When an http, SMTP or JMS message is sent to BPS http listener Servlet URL, email address or JMS queue; the listener intercepts the message and processes it to a protocol neutral format. The message is then passed to the BPS message handler. The message handler opens a connection to the Docbase and stores the message as virtual document. The attachment gets stored as child nodes of the virtual document. How http Listener Works The http message listener is implemented as a Servlet. It gets installed as a part of BPS web application. The URL to access the http listener Servlet is http://:/bps/http/http or https://:/bps/http/http As you can see from the URL, the http listener can use both http and https protocol. However it should be kept in mind that application server uses two separate ports to communicate with http and https protocol. If we provide http protocol port number (say 8080) to construct the https URL, it will not work. This is a common error one can make while configuring BPS http listener. In the following pages we will step through the installation, configuration and testing of BPS http listener. Configuring the BPS Handlers BPS configuration for handlers are kept in default.xml file. It is be located at drive:\Documentum\config\bps 1) Navigate to The default.xml file and open it for edit using a ASCII editor like Notepad. 2) Configuring element of this file. In the element we have to provide the connection details to Docbase, such as Docbasename, username, password etc. A sample
element entry should look like this: zebra dmadmin mypassword 3) Configuring element. This element specifies the message handlers available to BPS message listeners. Many out of the box handlers are provided with BPS but all of them are disabled by surrounding them within XML comment tag Either enable some of them or point towards your own custom handler class like this �. �. com.documentum.bps.handlers.LinkToFolderService 4) Configuring element Listeners element turns on the SSL capabilities of Local and remote listeners. Set the flag true or false as per your requirements. For our http listener test, we would use non-ssl connection, so make sure the value for the element is �true�. 5) Save the default.xml. A complete default.xml file for our test setup will look something like this. Replace the bold letters with your own Docbase, user, password and connection names. You can have multiple connections defined for multiple docbases. ?xml version=�1.0? encoding=�UTF-8??>
mydocbase1 myname1 mypassword1 mydocbase2 myname2 mypassword2 com.documentum.bps.handlers.ErrorHandlerService com.documentum.bps.handlers.SubjectMessageFilter com.documentum.bps.handlers.LinkToFolderService true true Creating a Test html Page We would need a test html page to test the http listener. Create html page out of the code provided below. This simple page submits a form to http listener after populating BPS http listener parameters in the form parameters. BPS http listener and LinkToFolder handler test Connection name: File1 to upload: File2 to upload:
Create a file called test.html out of this code and save it in the bps root folder. Testing the Application Start the application server where BPS is deployed and then invoke the html page by typing the following URL in your browser http://:/bps/test.html A page should appear in your browser. If not then please check if your application server is running or if it has been installed properly Fill up the connection name such as myconnection1 and then select a file to upload and then hit submit. This will cause the html form to be submitted to the BPS http listener, which will pass the message to LinkToFolder message handler and the file will be stored in bpsinbound folder. Once message handler succeeded, it will present a success page. Locating the Saved Message in the Docbase We have configured the LinkToFolder handler to save the message to bpsinbound folder. If you browse to the bpsinbound folder, you will found a new virtual document has been created by the LinkToFolder handler. Expanding the root virtual document will show the attached file. Summary- BPS http Installation and Configuration BPS http listener can be installed by selecting proper option in the BPS installer. To run the http listener, you will require an application server like Tomcat. The handler is implemented as Servlet. Before using the listener and the message handlers, BPS default.xml file needs to be configured. Please follow the instruction provided in this Whitepaper.to configure the default.xml file. Once it is configured; the http listener is ready for test. Use the test.html file provided in this White Paper to test the http listener Example start and stop of Documentum processes: ----------------------------------------------TAKE NOTICE: First of all, on any documentum server, find the account of the software owner. Since there are serveral accounts, depending on the site, you must check this
before starting or stopping a Service. You can allways check for the correct owner by looking at the owner of the "/appl/emcdctm" directory Example: on ZD111L13 you check root@zd111l13:/appl#ls -al total 16 drwxr-xr-x 4 root staff drwxr-xr-x 24 root system drwxr-xr-x 13 emcdmeu emcdgeu drwxr-xr-x 3 root staff
256 4096 4096 256
Jul 13 15:43 . Aug 21 15:09 .. Aug 9 15:04 emcdctm Jun 29 15:35 oracle
Now you do a swich user to the owner. In the example it would be "su - emcdmeu" If you logon as the software owner (e.g."su - emcdmeu"), you have several environment variables available, like $DOCUMENTUM which points to "/appl/emcdctm". 1. Docbroker processes: ----------------------Start $DOCUMENTUM/dba/dm_launch_Docbroker Stop $DOCUMENTUM/dba/dm_stop_Docbroker the startup calls ./dmdocbroker -port 1489 $@ >> $tlogfile 2>&1 & (/product/5.3/bin/dmdocbroker) Logs: tail -f $DOCUMENTUM/dba/log/docbroker..1489.log * for example tail -f $DOCUMENTUM/dba/log/docbroker.ZD110L12.nl.eu.abnamro.com.1489.log 2. Content Server: -----------------Content servers have Docbrokers and a "Java Method Server" There is also a service for each repository that has been installed Start $DOCUMENTUM/dba/dm_launch_Docbroker $DOCUMENTUM/dba/dm_start_dmwpreu1 $DM_HOME/tomcat/bin/startup.sh $DM_HOME/tomcat/bin/shutdown.sh $DOCUMENTUM/dba/dm_shutdown_dmwpreu1 $DOCUMENTUM/dba/dm_stop_Docbroker Stop $DM_HOME/tomcat/bin/shutdown.sh $DOCUMENTUM/dba/dm_shutdown_dmw_eu
$DOCUMENTUM/dba/dm_stop_Docbroker Or if there are 2 filestores, like in ETNL: Start $DOCUMENTUM/dba/dm_launch_Docbroker $DOCUMENTUM/dba/dm_start_dmw_et $DOCUMENTUM/dba/dm_start_dmw_et3 $DM_HOME/tomcat/bin/startup.sh Stop $DM_HOME/tomcat/bin/shutdown.sh $DOCUMENTUM/dba/dm_shutdown_dmw_et $DOCUMENTUM/dba/dm_shutdown_dmw_et3 $DOCUMENTUM/dba/dm_stop_Docbroker Logs *Repository tail -f $DOCUMENTUM/dba/log/dmw_et.log *JMS tail -f $DM_HOME/tomcat/logs/catalina.out Or: 1) kill all processes that are being run by emcdm user. 2) Run the following commands as user emcdm: $DOCUMENTUM/dba/dm_launch_Docbroker $DOCUMENTUM/dba/dm_start_dmw_et $DM_HOME/tomcat/bin/startup.sh
3. BPS: ------Start # As user {NL} emcdm, or {EU} wasemceu cd $DOCUMENTUM/dfc/bps/inbound/bin ./start_jms_listener.sh Better is: nohup ./start_jms_listener.sh & Stop # As user {NL} emcdm, or {EU} wasemceu ps -ef | grep bps kill -9 4. Index Server: ---------------Indexer - server IX Index servers have 3 services: Docbroker, Index Server,
and Index Agent {per repository} Start $DOCUMENTUM/dba/dm_launch_Docbroker $DOCUMENTUM/fulltext/IndexServer/bin/startup.sh $DOCUMENTUM_SHARED/IndexAgents/IndexAgent1/startupIndexAgent.sh Stop $DOCUMENTUM_SHARED/IndexAgents/IndexAgent1/shutdownIndexAgent.sh $DOCUMENTUM/fulltext/IndexServer/bin/shutdown.sh $DOCUMENTUM/dba/dm_stop_Docbroker Logs tail -f $DOCUMENTUM/dfc/logs/IndexAgent1.log 5. Websphere: ------------example 1: Syntax if rc.appserver exists: su - wasemceu /etc/rc.appserver start ETM1DAE /etc/rc.appserver start ETM1DEU /etc/rc.appserver stop ETM1DEU /etc/rc.appserver stop ETM1DAN /etc/rc.appserver stop ETM1DNL /etc/rc.appserver start ETM1DAN /etc/rc.appserver start ETM1DNL example 2: Syntax if just using websphere scripts: START: /appl/was51/bin/startNode.sh /appl/was51/bin/startServer.sh server1 /appl/was51/bin/startServer.sh STM1DNL /appl/was51/bin/startServer.sh STM1DAN tail tail tail tail
-f -f -f -f
/beheer/log/was51/server1/SystemOut.log /beheer/log/was51/STM1DNL/SystemOut.log /beheer/log/was51/STM1DNL/SystemErr.log /beheer/log/was51/STM1DAN/SystemOut.log
STOP: /appl/was51/bin/stopServer.sh STM1DAN /appl/was51/bin/stopServer.sh STM1DNL /appl/was51/bin/stopServer.sh server1 /appl/was51/bin/stopNode.sh
Backup options EMC Documentum:
-----------------------------1 cold backup: -------------If you want to backup a docbase the Documentum recommended way is: 1) Stop the Content Server 2) Stop the database 3) Backup the database using standard database or OS tools as appropriate for your database 4) Backup the Content Store(s) using OS tools. Using is referred to as a full, cold backup. There are options for hot and/or incremental backups but it does get more complicated (and possibly expensive). The full,cold backup is the simplest option available. 2. Online Hot backup: --------------------2.1 CYA hot backup software 2.2 Platform Dynamics:
Recovery management for EMC Documentum
2.3 EMC NetWorker Module for Documentum
Catalina: ========= The Java Serlvet womb part of Apache Tomcat server. It lets Java Servlets handle HTTP requests. Catalina is the name of the Java class of Tomcat from version 4.0 Tomcat's servlet container was redesigned as Catalina in Tomcat version 4.x
XMWLM: ====== Note 1: ------xmwlm Command Purpose Provides recording of system performance or WLM metrics. Syntax xmwlm [ -d recording_dir ] [ -n recording_name ] [ -t trace_level ] [ -L ]
Description The xmwlm agent provides recording capability for a limited set of local system performance metrics. These include common CPU, memory, network, disk, and partition metrics typically displayed by the topas command. Daily recordings are stored in the /etc/perf/daily directory. The topasout command is used to output these recordings in raw ASCII or speadsheet format. The xmwlm agent can also be used to provide recording data from Workload Management (WLM). This is the default format used when xmwlm is run without any flags. Daily recordings are stored in the /etc/perf/wlm directory. The wlmmon command can be used to process WLM-related recordings. The xmwlm agent can be started from the command line, from a user script, or can be placed near the end of the /etc/inittab file. All recordings cover 24hour periods and are only retained for two days. #ps -ef | grep -i xmwlm root 266378 1 0
Aug 06
- 272:17 /usr/bin/xmwlm -L
Note 2: ------IY78009: XMWLM HIGH RESOURCE CONSUMPTION, TOPASOUT COUNTERS A fix is available Obtain fix for this APAR APAR status Closed as program error. Error description xmwlm daemon may consume well over 1% of CPU resources some disk counter values may be inaccurate in topasout output Local fix Problem summary xmwlm daemon may consume well over 1% of CPU resources some disk counter values may be inaccurate in topasout output Problem conclusion Reduce SPMI instrumentations internal polling frequency for filesystem metrics. Update topasout for certain counter data types. Temporary fix Comments APAR information APAR number IY78009 Reported component name AIX 5.3 Reported component ID 5765G0300 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER
Submitted date 2005-10-21 Closed date 2005-10-21 Last modified date 2005-11-17 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Publications Referenced Fix information Fixed component name AIX 5.3 Fixed component ID 5765G0300 Note 3: ------IY95912: XMWLM LOOPING IN SIGNAL HANDLERS INFINITELY Subscribe to this APAR By subscribing, you will receive periodic email alerting you to the status of the APAR, and a link to download the fix once it becomes available.
A specific fix for this item is not yet available electronically This record will be updated with a link to the fix if the APAR is new. For APARs older than 365 days, contact your support center.
APAR status Closed as program error. Error description High cpu consumption by xmwlm Local fix Problem summary High cpu consumption by xmwlm Problem conclusion Stop xmwlm from looking infinitely in signal handler and avoid xmwlm from crashing when it has to record more than 4096 metrics by recording only 4096 metrics at max. Temporary fix Comments APAR information APAR number IY95912 Reported component name AIX 5.3 Reported component ID 5765G0300 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER Submitted date 2007-03-11
Closed date 2007-03-11 Last modified date 2007-03-15 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: IY96091
Second superuser: ================= For safety reasons, you might want to have a second root user on your system. Note 1: -------- Creating a second root user Follow these steps to create a second root user: Create a user. Manually edit the user ID field and group ID field in the /etc/passwd file. Change the user ID to ID 0. For a typical user ID, for example, change the entry from: russ:!:206:1::/u/russ:/bin/ksh to russ:!:0:0::/u/russ:/bin/ksh This creates a user (in this case, russ) with identical permissions to root.
-- Creating special users with root authority Special users that have root authority but can only execute one command may also be created. For instance, to create a user that can only reboot the system, create a regular user called shutdown and modify the /etc/passwd command to change the user and group ID to 0. For example, in AIX 3.2: shutdown:!:0:0::/u/shutdown:/bin/ksh Change the initial program from /bin/ksh to /etc/shutdown -Fr: shutdown:!:0:0::/u/shutdown:/etc/shutdown -Fr For AIX 4, the /etc/passwd entry for the user called shutdown should be: shutdown:!:0:0::/u/shutdown:/usr/sbin/shutdown -Fr The shutdown command on AIX Version 4.1 is located in /usr/sbin. Now when user shutdown logs in, the system will shut down and reboot.
Universal Command: ================== UC facilitates jobscheduling from Mainframe to AIX and HP-UX systems. AIX: # lslpp -La 'UCmdP' HP: # swlist -l subproduct UCmd Tiger: ====== Tiger is a security tool that can be used as a security and intrusion detection system. It works at many platforms and is provided under the GPL license. So its free software. Its written entirely in shell language. 5FC2DD4B PING TO REMOTE HOST FAILED: ===================================== AIX ONLY: In errpt you might find: [pl101][tdbaprod][/home/tdbaprod] errpt IDENTIFIER TIMESTAMP T C RESOURCE_NAME 5FC2DD4B 0225151808 I H ent2 9F7B0FA6 0225151108 I H ent2 LABEL: IDENTIFIER:
ECH_PING_FAIL_BCKP 5FC2DD4B
Date/Time: Sequence Number: Machine Id: Node Id: Class: Type: Resource Name: Resource Class: Resource Type: Location:
Mon Feb 25 14:41:06 2008 2140 00CB85FF4C00 pl101 H INFO ent2 adapter ibm_ech
Description PING TO REMOTE HOST FAILED Probable Causes CABLE SWITCH ADAPTER
DESCRIPTION PING TO REMOTE HOST FAILED PING TO REMOTE HOST FAILED
Failure Causes CABLES AND CONNECTIONS Recommended Actions CHECK CABLE AND ITS CONNECTIONS IF ERROR PERSISTS, REPLACE ADAPTER CARD. Detail Data FAILING ADAPTER ent1 SWITCHING TO ADAPTER ent0 Unable to reach remote host through backup adapter: switching over to primary adapter -- thread 1: All our servers every three minutes logs this message: 9F7B0FA6
0602080605 I H ent2
PING TO REMOTE HOST FAILED
The details of the message says it can't ping the default gateway through backup adapter. Why does it try this? Why does it fail because if we pull the primary cable it switches to the backup adapter with no problems. Cheers -- thread 2: Hello: I've seen similar things happen when the switch is not on "port host" (meaning the port begins receiving and sending packets quickly, instead of running Spanning Tree Protocol before going in the FORWARDING state): in this case, the EtherChannel sends the ping packets, they are dropped because the switch is still initializing, and the cycle continues on and on. Still, 30 minutes sounds like a long time. You can try the following: - verify that the EtherChannel switch ports are set to "port host" (i.e., STP should be disabled) on the VIOS, set the num_retries to a higher value (default is 3) and/or set the retry_time to a higher value (default is 1) Does this ONLY happen when updating from FP74 to FP8, or every time the VIOS boots? Kind regards, -- thread 3:
Hi All, I am getting the following error consistently on one of my servers. when i do a entstat -d ent3 | grep "Active channel", it does come back with Active channel: primary channel. Could you please provide me with any suggestions or steps I can take to fix this error? entstat -d ent2 | grep "Active channel" Hi Just Etherchannel or Etherchannel with Backup Adapter connected to a failover Switch just in case everything fails ?? If so, please take a read of the following: http://publib.boulder.ibm.com/infocenter/clresctr/v xrx/index.jsp?topic=/com.ibm.cluster.rsct.doc/rsct _aix5l53/bl5adm05/bl5adm0559.html Hope this helps -- thread 4: A VIOS network failover test produces the above error messages, so in that case there is no real problem.
midaemon, scopeux, measureware: =============================== The scopeux data collector, the midaemon (measurement interface daemon), and the alarmgen (alarm generator) process, are all part of HP Openview Measureware software that can run on a node. A typical process list might show the following: zd57l08:/home/root>ps -ef | grep /usr/lpp/perf/bin/ root 176232 1 0 Dec 20 - 0:17 /usr/lpp/perf/bin/midaemon root 188536 1 0 Dec 20 - 0:00 /usr/lpp/perf/bin/ttd root 200830 254112 0 Dec 20 - 5:06 /usr/lpp/perf/bin/alarmgen -svr 254112 -t alarmgen /var/opt/perf/datafiles// root 204918 1 0 Dec 20 - 106:40 /usr/lpp/perf/bin/scopeux root 233644 1 0 Dec 20 - 0:07 /usr/lpp/perf/bin/llbd root 254112 266370 0 Dec 20 - 6:56 /usr/lpp/perf/bin/agdbserver -t alarmgen /var/opt/perf/datafiles/ root 266370 1 0 Dec 20 - 3:42 /usr/lpp/perf/bin/perflbd root 307362 266370 0 Dec 20 - 8:22 /usr/lpp/perf/bin/rep_server -t SCOPE /var/opt/perf/datafiles/logglob You can start or stop or view the status of the processes, by using the mwa command: oranh202:/home/se1223>mwa status MeasureWare scope status: WARNING: scopeux is not active (MWA data collector) MeasureWare background daemon status: (Should always be running when the system is up) Running ttd (Transaction Tracker daemon) pid 1493
MeasureWare Running Running Running
server status: alarmgen agdbserver perflbd
(alarm generator) pid 12547 (alarm database server) pid 12546 (location broker) pid 12075
The following data sources have running repository servers: PID DATA SOURCE Running rep_server 12521 SCOPE How does mwa start on boot? --------------------------There is an entry in "/etc/inittab":
[email protected]:/etc#cat inittab | grep mwa mwa:2:wait:/etc/rc.mwa start >/dev/console # Start MeasureWare Check on whether its running: oper@zd110l03:/home/oper$ ps -ef | grep /usr/lpp/ root 147480 1 0 May 15 - 0:10 /usr/lpp/perf/bin/midaemon root 151694 1 0 May 02 - 38:59 /usr/lpp/perf/bin/llbd root 229394 340068 0 May 15 - 7:30 /usr/lpp/perf/bin/rep_server -t SCOPE /var/opt/perf/datafiles/logglob root 258142 393340 0 Jul 18 - 9:04 /usr/lpp/mmfs/bin/aix64/mmfsd64 root 270588 372908 0 May 15 - 4:07 /usr/lpp/perf/bin/alarmgen -svr 372908 -t alarmgen /var/opt/perf/datafiles// root 315572 1 0 May 15 - 40:33 /usr/lpp/perf/bin/scopeux root 340068 1 0 May 15 - 4:45 /usr/lpp/perf/bin/perflbd root 352326 1 0 May 15 - 0:00 /usr/lpp/perf/bin/ttd root 372908 340068 0 May 15 - 6:19 /usr/lpp/perf/bin/agdbserver -t alarmgen /var/opt/perf/datafiles/ root 393340 1 0 Jul 18 - 0:00 /bin/ksh /usr/lpp/mmfs/bin/runmmfs uctsp0 434430 1 0 May 04 - 58:36 /usr/lpp/uctsp0/controlsa/exe/AIX-51/p_ctsce uctsp0 503814 434430 0 22:41:01 - 0:00 /usr/lpp/uctsp0/controlsa/exe/AIX-51/./p_ctscd 57671683 57671682 434430 uctsp0 536756 434430 0 22:41:01 - 0:00 /usr/lpp/uctsp0/controlsa/exe/AIX-51/./p_ctscs 57671681 60817408 434430 -- How to stop and start the agents: 1. Use the /etc/rc.mwa script, if its available on your system: root@zd110l13:/etc#rc.mwa stop Shutting down Measureware collection software Shutting down scopeux, pid(s) 192688 Waiting on 192688 (10 more tries) The Measureware collector, scopeux has been shut down successfully. Shutting down the MeasureWare server daemons Shutting down the alarmgen process.
This may take a while
depending upon how many monitoring systems have to be notified that MeasureWare Server is shutting down. Shutting down the perflbd process The perflbd process has terminated Shutting down the agdbserver process The agdbserver process has terminated Shutting down the rep_server processes The rep_server processes have terminated The MeasureWare Server has been shut down successfully root@zd110l13:/etc#rc.mwa start The MeasureWare scope collector is being started. The Transaction Tracking daemon /usr/lpp/perf/bin/ttd has been started. The performance collection daemon /usr/lpp/perf/bin/scopeux has been started. The MeasureWare server daemon "llbd" is being started. The MeasureWare server daemons are being started. The MeasureWare Location Broker daemon /usr/lpp/perf/bin/perflbd has been started. root@zd110l13:/etc# Notes about mwa: ---------------About MWA(MeasureWare Agent) Introduction: MeasureWare Agent software captures performance, resource, and transaction data from your HP 9000 server or workstation system. Using minimal system resources, the software continuously collects, logs, summarizes, and timestamps data,and detects alarm conditions on current and historical data across your system. You can analyze the data using spreadsheet programs, Hewlett-Packard analysis products such as PerfView, or third-party analysis products. Also, MeasureWare Agent provides data access to PerfView and sends alarm notifications to PerfView, HP OpenView, and IT/Operations. HP OpenView MeasureWare Agent for UNIX has been renamed to HP OpenView Performance Agent for UNIX.
MeasureWare Agent uses data source integration (DSI) technology to receive, alarm on, and log data from external data sources such as applications, databases, networks, and other operating systems. The comprehensive data logged and stored by MeasureWare Agent allows you to: � Characterize the workloads in the environment. � Analyze resource usage and load balance. � Perform trend analyses on historical data to isolate and identify bottlenecks. � Perform service-level management based on transaction response time. � Perform capacity planning. � Respond to alarm conditions. � Solve system management problems before they arise. Starting MWA Automatically The process of starting MeasureWare Agent automatically whenever the system reboots is controlled by the configuration file /etc/rc.config.d/mwa. This file defines two shell variables, MWA_START and MWA_START_COMMAND. The default /etc/rc.config.d/mwa configuration file shipped with this version of MeasureWare Agent resides in /opt/perf/newconfig/ and assigns the following values to these variables: MWA_START=1 MWA_START_COMMAND=�/opt/perf/bin/mwa start� When MeasureWare Agent is installed, the file is conditionally copied to /etc/rc.config.d/mwa and will not replace any existing /etc/rc.config.d/mwa configuration file that may have been customized by the user for a previous version of MeasureWare Agent. When the file is copied to /etc/rc.config.d/mwa, the variable MWA_START=1 causes MeasureWare Agent to automatically start when the system reboots. The variable MWA_START_COMMAND=�/opt/perf/bin/mwa start� causes all MeasureWare Agent processes to initiate when the system reboots. If you want MeasureWare Agent to start at system reboot using special options, modify the /etc/rc.config.d/mwa file by changing MWA_START_COMMAND from its default value of �/opt/perf/bin/mwa start� to the desired value. For example, to start up scopeux but not the servers, change the value to �/opt/perf/bin/mwa start scope�. To disable MeasureWare Agent startup when the system reboots, change the variable MWA_START=1 to MWA_START=0. MWA Command: SYNOPSIS mwa [action] [subsystem] [parms] DESCRIPTION mwa is a script that is MeasureWare Agent processes. ACTION
used
to
start,
stop,
and
re-initialize
-? such as start stop restart stopped status version
List all mwa options. If your shell interprets ? as a wildcard character, use an invalid option -xxx nstead of -?. Start all or part of MeasureWare Agent. (default) Stop all or part of MeasureWare Agent. Reinitialize all or part of MWA. This option causes some processes to be and restarted. List the status of all or part of MWA processes. List the version of the all or part of MWA files.
SUBSYSTEM all Perform the selected action on all MWA components. (default) scope Perform the selected action on the scopeux collector. The restart operation causes the scopeux collector to stop, then restart. This causes the parm and ttd.conf files to be re-read. server Perform the selected action on the MWA server components. This affects the data repositories as well as the alarm generation subsystem. The restart operation causes all repository server processes to terminate and restart. This causes the perflbd.rc and alarmdef files to be re-read. alarm Perform the selected action on the MWA server alarm component. Restart is the only valid option and causes the alarmdef file to be reprocessed. db
Perform the selected action on
the MWA server db component.
PARMS -midaemon Provide the midaemon with parameters to initiate it with other than default parameters. Example: phred01:/> mwa status MeasureWare scope status: WARNING: scopeux is not active (MWA data collector) MeasureWare background daemon status: (Should always be running when the system is up) Running ttd (Transaction Tracker daemon) pid 1900 MeasureWare Running Running Running
server status: alarmgen agdbserver perflbd
(alarm generator) pid 2816 (alarm database server) pid 2815 (location broker) pid 1945
The following data sources have running repository servers: PID DATA SOURCE Running rep_server 2810 SCOPE phred01:/> mwa stop NOTE:
Shutting down Measureware collection software.. The Transaction Tracker daemon, ttd will be left running. pid 1900 Shutting down the MeasureWare server daemons.. Shutting down the alarmgen process. This may take awhile depending upon how many monitoring systems have to be
notified that MeasureWare Server is shutting down. The alarmgen process has terminated Shutting down the perflbd process The perflbd process has terminated The agdbserver process terminated The rep_server processes have terminated The MeasureWare Server has been shut down successfully phred01:/> mwa start The Transaction Tracker daemon is being started. The Transaction Tracker daemon /opt/perf/bin/ttd, is already running. The MeasureWare scope collector is being started. The performance collection daemon /opt/perf/bin/scopeux has been started. The MeasureWare server daemons are being started. The MeasureWare Location Broker daemon /opt/perf/bin/perflbd has been started. phred01:/> mwa status MeasureWare scope status: Running scopeux Running midaemon
(MWA data collector) pid 12361 (measurement interface daemon) pid 1936
MeasureWare background daemon status: Running ttd (Transaction Tracker daemon) pid 1900 MeasureWare Running Running Running
server status: alarmgen agdbserver perflbd
(alarm generator) pid 12907 (alarm database server) pid 12906 (location broker) pid 12369
The following data sources have running repository servers: PID DATA SOURCE Running rep_server 12905 SCOPE References: HP OpenView Performance Agent for HP-UX 10.20 and 11 Installation & Configuration Guide man mwa(Command)
Thread 1 about scopeaux: -----------------------Subject: restart vrs. start scopeux mwa status reports scopeux not running. Manual states to use restart command to retain existing logs (status.scope).
But, I'm more concerned about the database collected prior to "mysterious" end of scopeux. Will restart (or start) of scope (scopeux) preserve existing data? Thanks. Vic. Once the data is written to the log files, it stays there when scopeux stops and starts. The data is deleted after the logfile reachs its size limit and starts to wrap. The oldest data is overwritten first. I just do a "mwa start scope" to restart scope. I usually don't do a "mwa restart" as sometimes one of the processes may not stop, usually perflbd. I do a "mwa stop", check everything "mwa status" then do a "mwa start". Sometimes when scopeux crashes, it was in the act of writing a record and only a partial record is written. This partial record will corrupt the database and scopeux will not start. In this case, the only way to start scopeux is to delete the database. It is a good idea to backup the databases frequently if the data is important to you. HTH Marty If you only want to work with the Scope Collector itself (I.E. All other MeasureWare processes are running) do the following: mwa start scope or mwa restart scope This will narrow down what part of the MeasureWare product you are working with. The status.scope file might help you figure out why scope stopped. To see what may have happened to the scope daemon, look in its status file /var/opt/perf/status.scope. You can also use "perfstat -t" to see the last few lines of all the OVPA status files. Since the "perfstat" command shows glance and OVPA (mwa) status, I recommend using perfstat instead of "mwa status" (also less to type!). Since I'm in a recommending mood, I also recommend AGAINST doing a "mwa start scope" (or restart scope). The reason is that its always better to restart the datacomm daemons when the underlying collector is restarted. Thus its better to just do a "mwa restart" or "mwa start" instead of restarting scope out from under rep_server and friends.
In any case, if perfstat shows everything running but scopeux, then first find out why scope died (by looking at status.scope) before doing any restarts. Thread 2 about scopeux: ----------------------Subject: HELP OVPA: midaemon and scopeux won't start Jamie Chui Jun 21, 2007 03:23:12 GMT I could not get midaemon and scopeux to start. When using glance, the following error messages appears and what does it mean? midaemon: Mon Jun 11 15:51:05 2007 mi_ki_init - only able to allocate 3 bufsets Not enough space. I am using HP-UX 11.11 with OVPA C.04.55.00. Measureware ran for 10 days, and during this period, it had the following error message and then finally one day it stopped running. **** /opt/perf/bin/scopeux : 06/15/07 13:35:01 **** WARNING: Measurement Buffers Lost see metric GBL_LOST_MI_TRACE_BUFFERS. (PE221-5 0) How can I troubleshoot and get it running again? It looks like your OS is not allocating enough buffer space. You will need to increase your kernel parameters pertaining to buffer space and regen the kernel. HTH Marty
Tivoli endpoint, lcfd process: ============================== Tivoli Management Framework is the software infrastructure for many Tivoli software products. Using Tivoli Management Framework and a combination of Tivoli Enterprise products, you can manage large distributed networks with multiple operating systems, various network services, diverse system tasks, and constantly changing nodes and users. Tivoli Management Framework provides management services that are used by the installed Tivoli Enterprise products.
Tivoli Management Framework provides centralized control of a distributed environment, which can include mainframes, UNIX(R) operating systems, or Microsoft Windows operating systems. Using Tivoli Enterprise products, a single system administrator can perform the following tasks for thousands of networked systems: -Manage user and group accounts -Deploy new or upgrade existing software -Inventory existing system configurations -Monitor the resources of systems either inside or outside the Tivoli environment -Manage Internet and intranet access and control -Manage third-party applications Tivoli Management Framework lets you securely delegate system administration tasks to other administrators, giving you control over which systems an administrator can manage and what tasks that administrator can perform. Tivoli Management Framework includes the base infrastructure and base set of services that its related products use to provide direct control over specific resources in a distributed computing environment. Tivoli Management Framework provides a simple, consistent interface to diverse operating systems, applications, and distributed services. >> Architecture overview: Using this three-tiered hierarchy, the amount of communication with the Tivoli server is reduced. Endpoints do not communicate with the Tivoli server, except during the initial login process. All endpoint communication goes through the gateway. In most cases, the gateway provides all the support an endpoint needs without requiring communication with the Tivoli server. In a smaller workgroup-size installation, you can create the gateway on the Tivoli server. The server can handle communication requirements when fewer computer systems are involved. This is not an acceptable option in large deployments. The Tivoli server in a large installation will be overloaded if it also serves as a gateway. Refer to Endpoints and gateways for more information about endpoint communication. -- Tivoli servers The Tivoli server includes the libraries, binaries, data files, and the graphical user interface (GUI) (the Tivoli desktop) needed to install and manage your Tivoli environment. The Tivoli server performs all authentication and verification necessary to ensure the security of Tivoli data. The following components comprise a Tivoli server:
- An object database, which maintains all object data for the entire Tivoli region. - An object dispatcher, which coordinates all communication with managed nodes and gateways. The object dispatcher process is the oserv, which is controlled by the oserv command. - An endpoint manager, which is responsible for managing all of the endpoints in the Tivoli region. When you install the Tivoli server on a UNIX operating system, the Tivoli desktop is automatically installed. When you install the Tivoli server on a Windows operating system, you must install Tivoli Desktop for Windows separately to use the Tivoli desktop. -- Managed nodes A managed node runs the same software that runs on a Tivoli server. Managed nodes maintain their own object databases that can be accessed by the Tivoli server. When managed nodes communicate directly with other managed nodes, they perform the same communication or security operations that are performed by the Tivoli server. The difference between a Tivoli server and a managed node is that the Tivoli server object database is global to the entire region including all managed nodes. In contrast, the managed node database is local to the particular managed node. To manage a computer system that hosts the managed node, install an endpoint on that managed node. -- Gateways A gateway controls communication with and operations on endpoints. Each gateway can support thousands of endpoints. A gateway can launch methods on an endpoint or run methods on behalf of the endpoint. A gateway is generally created on an existing managed node. This managed node provides access to the endpoint methods and provides the communication with the Tivoli server that the endpoints occasionally require. Refer to Endpoints and gateways for more information about gateways. -- Endpoints An endpoint provides the primary interface for system management. An endpoint is any system that runs the lcfd service (or daemon), which is configured using the lcfd command. Typically, an endpoint is installed on a computer system that is not used for daily management operations. Endpoints run a very small amount of software and do not maintain an object
database. The majority of systems in a Tivoli environment should be endpoints. The Tivoli desktop is not installed with the endpoint software. If you choose to run a desktop on an endpoint, you must install Tivoli Desktop for Windows or telnet to a UNIX managed node. Refer to Endpoints and gateways for more information about endpoints.
Note 1: ------thread: Q: Dear friends, When i run "lslpp -l" i have in a line : "Tivoli_Management_Agent.client.rte 3.7.1.0 COMMITTED Management Framework Endpoint Runtime" ". What's the purpose of this fileset ? Ps : I have Aix 5.3 thank's a lot. A: The purpose of Tivoli Management Agent Reply from nlx6976 on 3/6/2006 5:56:00 PM Its an agent that runs on your system as part of the Tivoli Distributed Monitoring. It reports various things about your sysem back to the Tivoli Enterprise Console - usually your help desk. The basic monitors include things like file system usage (e.g if a FS is more than 80% used the system gets flagged at the console), or monitoring log files. Basically you can configure it to monitor whatever you want. Note 2: ------Problem The AIX server comes preloaded with the Tivoli Endpoint software installed. How can you make this process autostart at bootup? Solution Create the /etc/inittab entry: mkitab "rctma1:2:wait:/etc/rc.tma1 > /dev/console 2>&1 # Tivoli Management Agent" Create the startup file "/etc/rc.tma1"
#!/bin/sh # # Start the Tivoli Management Agent # if [ -f /Tivoli/lcf/dat/1/lcfd.sh ]; then /Tivoli/lcf/dat/1/lcfd.sh start fi When the OS reboot the LCFD process will automatically start. Note 3: ------The lcfd.log file, found on each endpoint in the lcf/dat directory, contains logging messages for upcall methods, downcall methods, and the login activities of the endpoint. You also can view this log file from the http interface. In addition, lcfd.log can have different levels of debugging information written to it. To set the level of debugging, use the lcfd command with the -dlevel option, which sets the log_threshold option in the last.cfg file. Set the log_threshold at level 2 for problem determination, because level 3 often provides too much information. Of the three log files, the lcfd.log file is sometimes the most useful for debugging endpoint problems. However, remote access to the endpoint is necessary for one-to-one contact. Endpoint log messages have the following format: timestamp level app_name messageThe message elements are as follows: timestamp Displays the date and time that the message was logged. level Displays the logging level of the message. app_name Displays the name of the application that generated the message. message Displays the full message text. The content of message is provided by the application specified in app_name. The default limit of the log file is 1 megabyte, which you can adjust with the lcfd (or lcfd.sh) command with the -D log_size =max_size option. The valid range is 10240 through 10240000 bytes. When the maximum size is reached, the file reduces to a size of approximately 200 messages and continues to log. In addition to these three log files, the following files help troubleshoot endpoint problems located on the endpoint: last.cfg A text file that contains the endpoint and gateway login configuration information from the last time
the endpoint successfully logged in to its assigned gateway. Use this file to review the configuration settings for an endpoint. lcf.id A text file that contains a unique ID number to represent the endpoint. This file is uniquely generated if the TMEID.tag file does not exist. lcf.dat A binary file that contains the gateway login information. You cannot modify this information; however, you can view network configuration information from the http interface. Of these files, the last.cfg file can be useful in determining problems with an endpoint. The last.cfg file resides in the \dat subdirectory of the endpoint installation and also can be viewed from the http interface. This file contains configuration information for the endpoint. The following example shows the contents of a last.cfg file: lcfd_port=9495 lcfd_preferred_port=9495 gateway_port=9494 protocol=TCPIP log_threshold=1 start_timeout=120 run_timeout=120 lcfd_version=41100 logfile=C:\Program Files\Tivoli\lcf\dat\1\lcfd.log config_path=C:\Program Files\Tivoli\lcf\dat\1\last.cfg run_dir=C:\Program Files\Tivoli\lcf\dat\1 load_dir=C:\Program Files\Tivoli\lcf\bin\w32-ix86\mrt lib_dir=C:\Program Files\Tivoli\lcf\bin\w32-ix86\mrt cache_loc=C:\Program Files\Tivoli\lcf\dat\1\cache cache_index=C:\Program Files\Tivoli\lcf\dat\1\cache\Index.v5 cache_limit=20480000 log_queue_size=1024 log_size=1024000 udp_interval=300 udp_attempts=6 login_interval=1800 lcs.machine_name=andrew1 lcs.crypt_mode=196608 lcfd_alternate_port=9496 recvDataTimeout=2 recvDataNumAttempts=10 recvDataQMaxNum=50 login_timeout=300 login_attempts=3 When you change endpoint configuration with the lcfd command, the last.cfg file changes. Therefore, you should not modify the last.cfg file. If you require changes, use the lcfd command to make any changes. However, running the lcfd command requires stopping and restarting the endpoint. Another useful tool for endpoint problem determination is the output from the wtrace command.
The wtrace command is useful for tracking upcall and downcall method failures. To learn more about the wtrace command, see Troubleshooting the Tivoli environment. sample logfile "root@zd110l13:/beheer/Tivoli/lcf/dat/1/lcfd.log" Nov 15 09:14:13 1 engineUpdate Sending msg amRaAdd Nov 15 09:14:13 1 engineUpdate Sending msg amTmrRemove Nov 15 09:14:13 1 engineUpdate Sending msg amMpeRemove Nov 15 09:14:13 1 engineUpdate Sending msg amRaRemove Nov 15 09:14:13 1 engineUpdate Sending msg amTmrAdd Nov 15 09:14:13 1 engineUpdate Sending msg amMpeAdd Nov 15 09:14:13 1 engineUpdate Sending msg amRaAdd Nov 15 09:14:13 1 engineUpdate Sending msg amRaAdd Nov 15 09:14:13 1 engineUpdate Sending msg amRaAdd Nov 15 09:14:13 1 engineUpdate Sending msg amRaAdd Nov 15 09:14:13 1 engineUpdate Sending msg amRaAddTasks Nov 15 09:14:13 1 engineUpdate Sending msg amEndPush Nov 15 09:18:48 1 lcfd Spawning: /beheer/Tivoli/lcf/dat/1/cache/bin/aix4r1/TME/Tmw2k/tmw2k_ep, ses: 215c89e6 Nov 15 09:28:46 1 lcfd Spawning: /beheer/Tivoli/lcf/dat/1/cache/bin/aix4r1/TME/Tmw2k/tmw2k_ep, ses: 215c8a22 Nov 15 09:33:51 1 lcfd Spawning: /beheer/Tivoli/lcf/dat/1/cache/bin/aix4r1/TME/Tmw2k/tmw2k_ep, ses: 215c8a4e Nov 15 09:48:55 1 lcfd Spawning: /beheer/Tivoli/lcf/dat/1/cache/bin/aix4r1/TME/Tmw2k/tmw2k_ep, ses: 215c8ac6 Nov 15 10:03:58 1 lcfd Spawning: /beheer/Tivoli/lcf/dat/1/cache/bin/aix4r1/TME/Tmw2k/tmw2k_ep, ses: 215c8b5b Nov 15 10:19:02 1 lcfd Spawning: /beheer/Tivoli/lcf/dat/1/cache/bin/aix4r1/TME/Tmw2k/tmw2k_ep, ses: 215c8c4a Nov 15 10:34:05 1 lcfd Spawning: /beheer/Tivoli/lcf/dat/1/cache/bin/aix4r1/TME/Tmw2k/tmw2k_ep, ses: 215c8cb6 root@zd110l05:/#find . -name "*tecad*" -print ./tmp/.tivoli/.tecad_logfile.fifo.zd110l05.aix-default ./tmp/.tivoli/.tecad_logfile.lock.zd110l05.aix-default ./tmp/.tivoli/.tecad_logfile.fifo.zd110l05.aix-defaultlogsourcepipe ./etc/Tivoli/tecad ./etc/Tivoli/tecad.1011792 ./etc/Tivoli/tecad.1011792/bin/init.tecad_logfile ./etc/Tivoli/tec/tecad_logfile.cache ./etc/rc.tecad_logfile ./etc/rc.shutdown-pre-tecad_logfile ./etc/rc.tecad_logfile-pre-tecad_logfile ./etc/rc.tivoli_tecad_mqseries find: 0652-023 Cannot open file ./proc/278708. find: 0652-023 Cannot open file ./proc/315572. find: 0652-023 Cannot open file ./proc/442616. find: 0652-023 Cannot open file ./proc/475172. ./beheer/Tivoli/lcf/dat/1/cache/out-of-date/init.tecad_logfile ./beheer/Tivoli/lcf/dat/1/cache/out-of-date/tecad-remove-logfile.sh ./beheer/Tivoli/lcf/dat/1/cache/bin/aix4-r1/TME/TEC/adapters/bin/tecad_logfile.cfg ./beheer/Tivoli/lcf/dat/1/LCFNEW/CTQ/logs/trace_mqs_start_tecad__MQS_CC.Q3P0063__1 __p1052790.log
./beheer/Tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/bin/tecad_logfile ./beheer/Tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/bin/init.tecad_logfile ./beheer/Tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/bin/tecad-remove-logfile.sh ./beheer/Tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/aixdefault/etc/C/tecad_logfile.fmt ./beheer/Tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/aix-default/etc/tecad_logfile.err ./beheer/Tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/aixdefault/etc/tecad_logfile.conf ./beheer/Tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/aix-default/etc/tecad_logfile.cds ./beheer/Tivoli/lcf/bin/aix4-r1/TME/MQS/bin/tecad_mqseries.cfg ./beheer/Tivoli/lcf/bin/aix4-r1/TME/MQS/bin/tecad_mqseries.mqsc ./beheer/Tivoli/lcf/bin/aix4-r1/TME/MQS/bin/tecad_mqseries_nontme ./beheer/Tivoli/lcf/bin/aix4-r1/TME/MQS/bin/tecad_mqseries_tmegw ./beheer/Tivoli/lcf/bin/generic_unix/TME/MQS/sh/mqs_start_tecad.sh ./beheer/Tivoli/lcf/bin/generic_unix/TME/MQS/sh/mqs_stop_tecad.sh ./beheer/Tivoli/lcf/bin/generic_unix/TME/MQS/teccfg/tecad_mqseries.Q3P0063.cfg
dircmp: ======= Linux / Unix dircmp command About dircmp Lists files in both directories and indicates whether the files in the directories are the same and/or different. Syntax dircmp [-d] [-s] [-w n] directoryone directorytwo. -d Compare the contents of files with the same name in both directories and output a list telling what must be changed in the two files to bring them into agreement. The list format is described in diff(1). -s Does not tell you about the files that are the same. -w n Change the width of the output line to n characters. The default width is 72. directoryone The first directory for comparing. directorytwo The second directory for comparing. Examples dircmp dir1 dir2 - Compares the directory dir1 with the directory dir2. Below is an example of the output you may receive when typing this command. Feb 8 17:18 2001 Comparison of help issues Page 1 directory . same ./favicon.ico same ./logo.gif same ./question.gif
FLASHCOPY: ==========
Some notes about flashcopy implementations: Note 1: ======= What is FlashCopy? FlashCopy is a function designed to create an instant "copy" of some data. When an administrator issues a FlashCopy command that essentially says "make a copy of this data," SVC via FlashCopy immediately provides the appearance of having created a copy of the data, when in reality it creates the physical copy in the background before moving that copy to an alternative data-storage device, which can take some time depending on the size of the backup copy. However, it creates the appearance of having completed the copy instantaneously, so customers can have a backup copy available as soon as the command is issued, even though copying to a different storage medium takes place behind the scenes. "Because it operates very quickly in this way, FlashCopy allows customers to make a copy and immediately move on to other work without having to wait for the data to actually physically be copied from one place to another," says Saul. "In that regard, SVC FlashCopy is very similar to FlashCopy on the DS8000, for example, with the difference being SVC FlashCopy operates on most storage devices attached to the SVC, spanning many different disk systems."
Note 2: ======= FlashCopy FlashCopy is an IBM feature supported on ESS (Enterprise Storage Servers) that allows you to make nearly instantaneous Point in Time copies of entire logical volumes or data sets. The HDS (Hitachi Data Systems) implementation providing similar function is branded as ShadowImage. Using either implementation, the copies are immediately available for both read and write access. -- FlashCopy Version 1 The first implementation of FlashCopy, Version 1 allowed entire volumes to be instantaneously �copied� to another volume by using the facilities of the newer Enterprise Storage Subsystems (ESS). Version 1 of FlashCopy had its limitations however. Although the copy (or �flash� of a volume occurred instantaneously, the FlashCopy commands were issued sequentially and the ESS required a brief moment to establish the new pointers. Because of this minute processing delay, the data residing on two volumes
that were FlashCopied are not exactly time consistent. -- FlashCopy Version 2 FlashCopy Version 2 introduced the ability to flash individual data sets and more recently added support for �consistency groups�. FlashCopy consistency groups can be used to help create a consistent point-in-time copy across multiple volumes, and even across multiple ESSs, thus managing the consistency of dependent writes. FlashCopy consistency groups are used in a single-site scenario in order to create a time-consistent copy of data that can then be backed-up and sent offsite, or in a multi-site Global Mirror for ESS implementation to force time consistency at the remote site. The implementation of consistency groups is not limited to FlashCopy. Global Mirror for z/Series (formerly known as XRC or eXtended Remote Copy) also creates consistency groups to asynchronously mirror disk data from one site to another over any distance.
Note 3: ------http://www.ibm.com/developerworks/forums/thread.jspa?messageID=13967589 Q: Using target volume from FlashCopy on same LPAR as source volume going thru VIO server Posted: Jun 28, 2007 12:21:09 PM Reply Synopsis: DS4500 logical drive mapped to a p5 550 VIO server, then mapped to an AIX partition. Without interrupting the source drive, created a flashcopy of the drive and mapped it to the same VIO server, then again to the same partition. This caused duplicate VGID on the system. Had to varyoff and export the volume group to run recreatevg against the flashcopy hdisk and make a new volume group with it. This works fine the first time, however after I varyoff the vg and export it, then disable the flashcopy, and re-create it I cannot import or varyon the vg on the partition. importvg and recreatevg both say the hdisk belongs to a different vg so they don't work. The varyvg fails because the descriptors are not constitent. How do I create a flashcopyvg on this partition using virtual disk from the VIO so that the process is repeatable and thus scriptable without having to interrupt the source volume group everytime I do this. The intent is to be able run a backup process against the flashcopy then disable
it and do it again a few hours later and repeat it several times each day. We are using legacy vsam instead of a DB and need to keep the data accessible to our CICS system, while being able to capture point in time backups throughout the day. A: Did you rmdev the vpath and hdisks before recreating the flash copy? Then you will need to run recreatevg again, as restarting the flash copy will change the pvid back to the same as the source volume. Why not just attach the flash copy to another host? Then you won't need to run recreate vg and you could assign the flash copy to the original host if you need to recover the data.
============================== 2. NOTES ABOUT SHELL PROGRAMS: ============================== ------------------------------------------------------------NOTE 1: # sh dothat
(the dothat file contains commands)
# chmod 755 dothat (or use: chmod +x dothat # dothat (now it's executable) ------------------------------------------------------------NOTE 2: # now=`date` # echo $now
(variable is output of a command)`
This means that commands are read from the string between two ` `. Usage in a nested command goes like this: font=`grep font \`cat filelist\`` ------------------------------------------------------------NOTE 3: To extend the PATH variable, on most systems use a statement like the following example: $ export PATH=$PATH:$ORACLE_HOME/bin $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib PATH=.:/usr/bin:/$HOME/bin:/net/glrr/files1/bin export PATH ------------------------------------------------------------NOTE 4:
Positional parameters: program, function or shell argument 1 through 9 nth argument number of positional parameters every positional parameter decimal value returned by last executed cmd successful this will be 0 pid of shell pid of last backgrounded command
$0 $1 .. $9 ${n} $# $@, $* $? if the former was $$ $!
Examples of usage of $n parameter: ---------------------------------# dothis grapes apples pears $1=grapes, $2=apples, $3=pears # cat makelist sort +1 -2 people | tr -d "[0-9]" | pr -h Distribution | lp This will only work on that filename, that is people # cat makelist sort +1 -2 $1 | tr -d "[0-9]" | pr -h Distribution | lp This will work on ANY file given as an argument to makelist # makelist file1 # makelist file2 ------------------------------------------------------------NOTE 5: # echo "Hi there $LOGNAME" Hi there Albert # echo 'Hi there $LOGNAME' Hi there $LOGNAME # echo "You owe me \$$amount" | mail Single-quotes are literal quotes. Double-quotes can have their contents expanded ------------------------------------------------------------NOTE 6: How to set variables: -------------------- A variable name must begin with a letter and can contain letters, digits, and underscores,
but no special characters. - A variable is set with an assignment of NAME=value Be sure not to have any white space before or after the equals sign =. Double quotes are used when white space is present in the text string you are assigning to the variable. So here are a few examples: ME=bill BC="bill clinton" Now the shell can react and use the variable $ME and it substitutes the value for that variable. Local and environment variables: -------------------------------variables that you set are local to the current shell unless you mark them for excport. Variables marked for export are called environment variables, and will be made available to any command that the shell creates. The following command marks the variable BC for export: export BC You can list local variables by typing the set command. You can list the environment variables by using the env command. ------------------------------------------------------------NOTE 7: for file in list_of_values do sort +1 -2 $file | tr -d "[0-9]" | pr -h Distribution | lp done if test $# -eq 0 then echo "You must give a filename" exit 1 fi -eq=equal, -ne=not equal, -gt=greater than, -lt=less then, -ge=greater or equal, -le=less or equal ------------------------------------------------------------NOTE 8: UNIX$ for file in `ls /local/ssl/misc/*` > do > echo I found a config file $file > echo Its type is `/usr/bin/file $file` > done ------------------------------------------------------------NOTE 9:
If a script is to accept arguments then these can be referred to as ` $1 $2 $3..$9'. There is a logical limit of nine arguments to a Bourne script, but Bash handles the next arguments as `${10}'. `$0' is the name of the script itself. Here is a simple Bash script which prints out all its arguments. #!/bin/bash # # Print all arguments (version 1) # for arg in $* do echo Argument $arg done echo Total number of arguments was $# The `$*' symbol stands for the entire list of arguments and `$#' is the total number of arguments. ------------------------------------------------------------NOTE 10: Start and End of Command A command starts with the first word on a line or if it's the second command on a line with the first word after a";'. A command ends either at the end of the line or whith a ";". So one can put several commands onto one line: print -n "Name: "; read name; print "" One can continue commands over more than one line with a "\" immediately followed by a newline sign which is made be the return key: grep filename | sort -u | awk '{print $4}' | \ uniq -c >> /longpath/file ------------------------------------------------------------NOTE 11: Bash and the Bourne shell has an array of tests. They are written as follows. Notice that `test' is itself not a part of the shell, but is a program which works out conditions and provides a return code. See the manual page on `test' for more details. test on file chracteristics: test -f file test -d file test -r file
True if the file is a plain file True if the file is a directory True if the file is readable
test test test test test test
-w -x -h -s -g -u
file file file file file file
True True True True True True
if if if if if if
the file is writable the file is executable the file is a symbolic link the file contains something setgid bit is set setuid bit is set
string comparisons: test s1 = s2 test s1 != s2
True if strings s1 and s2 are equal True if strings s1 and s2 are unequal
numeric comparisons: test test test test test test
x x x x x x
-eq -ne -gt -lt -ge -le
y y y y y y
True True True True True True
if if if if if if
the integers x and y are numerically equal integers are not equal x is greater than y x is less than y x>=y x /dev/null && echo "Directory Found" The opposite of && is the ||. When two commands are separated by ||, the second command executes only if the first command returns a nonzero exit status (indicating failure). Example: ls -d /usr/foo || echo "No Directory Found" If the directory does not exist, the message is displayed. Loops WHILE ===== The basic loop is the 'while' loop; "while" something is true, keep looping. There are two ways to stop the loop. The obvious way is when the 'something' is no longer true. The other way is with a 'break' command.
keeplooping=1; while [[ $keeplooping -eq 1 ]] ; do read quitnow if [[ "$quitnow" = "yes" ]] ; then keeplooping=0 fi if [[ "$quitnow" = "q" ]] ; then break; fi done
UNTIL ===== The other kind of loop in ksh, is 'until'. The difference between them is that 'while' implies looping while something remains true. 'until', implies looping until something false, becomes true until [[ $stopnow -eq 1 ]] ; do echo just run this once stopnow=1; echo we should not be here again. done
FOR === A "for loop", is a "limited loop". It loops a specific number of times, to match a specific number of items. Once you start the loop, the number of times you will repeat is fixed. The basic syntax is for i in eat run jump play do echo See Albert $i done See See See See
Albert Albert Albert Albert
eat run jump play
for i in "eat run jump play" do echo See Albert $i done See Albert eat run jump play for var in one two three ; do echo $var
done Whatever name you put in place of 'var', will be updated by each value following "in". So the above loop will print out one two three But you can also have variables defining the item list. They will be checked ONLY ONCE, when you start the loop. list="one two three" for var in $list ; do echo $var # Note: Changing this does NOT affect the loop items list="nolist" done The two things to note are: It stills prints out "one" "two" "three" Do NOT quote "$list", if you want the 'for' command to use multiple items If you used "$list" in the 'for' line, it would print out a SINGLE LINE, "one two three" for i in 1 2 3 4 5 6 7 do cp x.txt $i done ------------------------------------------------------------NOTE 14: Arrays Arrays Yes, you CAN have arrays in ksh, unlike old bourne shell. The syntax is as follows: # This is an OPTIONAL way to quickly null out prior values set -A array # array[1]="one" array[2]="two" array[3]="three" three=3 print print print print
${array[1]} ${array[2]} ${array[3]} ${array[three]}
Briefly, an array contains a collection of values (elements) that may be accessed individually or as a group. Although newer versions of the Korn shell support more than one type of array, this tip will only apply
to indexed arrays. When assigning or accessing array elements, a subscript is used to indicate each element's position within the array. The subscript is enclosed by brackets after the array name: arrayname[subscript] The first element in an array uses a subscript of 0, and the last element position (subscript value) is dependent on what version of the Korn shell you are using. Review your system's Korn shell (ksh) man page to identify this value. In this first example, the colors red, green, and blue are assigned to the first three positions of an array named colors: $ colors[0]=RED $ colors[1]=GREEN $ colors[2]=BLUE Alternatively, you can perform the same assignments using a single command: $ set -A colors RED GREEN BLUE Adding a dollar sign and an opening brace to the front of the general syntax and a closing brace on the end allows you to access individual array elements: ${arrayname[subscript]} Using the array we defined above, let's access (print) each array element one by one: $ print ${colors[0]} RED $ print ${colors[1]} GREEN $ print ${colors[2]} BLUE $ If you access an array without specifying a subscript, 0 will be used: $ print ${colors[]} RED $ The while construct can be used to loop through each position in the array: $ $ > > > >
i=0 while [ $i -lt 3 ] do print ${colors[$i]} (( i=i+1 )) done
RED GREEN BLUE $ Notice that a variable (i) was used for the subscript value each time through the loop.
Special variables There are some "special" variables that ksh itself gives values to. Here are the ones I find interesting PWD - always the current directory RANDOM - a different number every time you access it $$ - the current process id (of the script, not the user's shell) PPID - the "parent process"s ID. (BUT NOT ALWAYS, FOR FUNCTIONS) $? - exit status of last command run by the script PS1 - your "prompt". "PS1='$PWD:> '" is interesting. $1 to $9 - arguments 1 to 9 passed to your script or function Tweaks with variables Both bourne shell and KSH have lots of strange little tweaks you can do with the ${} operator. The ones I like are below. To give a default value if and ONLY if a variable is not already set, use this construct: APP_DIR=${APP_DIR:-/usr/local/bin} (KSH only) You can also get funky, by running an actual command to generate the value. For example DATESTRING=${DATESTRING:-$(date)} (KSH only) To count the number of characters contained in a variable string, use ${#varname}.
echo num of chars in stringvar is ${#stringvar} ------------------------------------------------------------NOTE 15: Appending dates to files and such: Example 1: ---------# mv logfile logfile.`date`
# mv logfile logfile.`date + %Y.%m.%d` Example 2: ---------MS korn shell: # now=`date -u %d`;export now # echo $now 24 -----------------------------------------------------------NOTE 16: Examples Example 1: ---------#!/usr/bin/ksh # Monitor the SPL p550 server # By Albert # version 0.1 umask 022 date=`date +%d-%m-%y` time=`date +%H:%M`
[email protected] echo "$date $time" > /tmp/topper df >> /tmp/topper mailx -r
[email protected] -s "::: Disk info p550 :::" $emailers < /tmp/topper rm /tmp/topper exit 0
cat /export/home/fas/RSP/RSP.log | grep "ORA-01000" > /tmp/brokencursor.err mailx -r
[email protected] -s "::: Process info NLIHblabla-08 :::" $emailers < /tmp/topper 'mailx' to send someone an email Example 2: ---------#!/bin/ksh # Monitor rsp logfile # PATH=/usr/ucb:/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/etc:/usr/opt /SUNWmd/sbin export PATH
umask 022 date=`date +%d-%m-%y` time=`date +%H:%M`
[email protected],
[email protected] cat /export/home/fas/RSP/RSP.log | grep "ORA-01000" > /tmp/brokencursor.err if [ -s /tmp/brokencursor.err ] then # echo "$date $time" > /tmp/brokencursor.err mailx -r
[email protected] -s "::: Check on ORA-01000 :::" $emailers < /tmp/brokencursor.err else echo "all OK" >> /tmp/brokencursor.log fi /bin/rm /tmp/brokencursor.err exit 0
Example 3: Automatic startup of an application ---------------------------------------------#!/bin/ksh # name: spl # purpose: script that will start or stop the spl stuff. case "$1" in start ) echo echo -t start"'" su start"' ;; stop ) echo echo -t stop"'" su stop"' ;; * ) echo exit esac
"starting spl" "su - ccbsys -c '/prj/spl/SPLS3/bin/splenviron.sh -e SPLS3 -c "spl.sh ccbsys -c '/prj/spl/SPLS3/bin/splenviron.sh -e SPLS3 -c "spl.sh -t
"stopping spl" "su - ccbsys -c '/prj/spl/SPLS3/bin/splenviron.sh -e SPLS3 -c "spl.sh ccbsys -c '/prj/spl/SPLS3/bin/splenviron.sh -e SPLS3 -c "spl.sh -t
"Usage: $0 (start | stop)" 1
Example 4: scheduled cleanup of logs ------------------------------------
#!/usr/bin/ksh SAVEPERIOD=5 echo "/prj/spl/splapp/SPLQ3"| \ while read DIR do cd $(DIR) find . -type f -mtime +$(SAVEPERIOD) -exec rm {} \; done exit 0 Example 5: some testing examples -------------------------------Initialise() { export SPLcomplog=$SPLSYSTEMLOGS/initialSetup.sh.log if [ -f $SPLcomplog ] then rm -f $SPLcomplog export RSP=$? if [ $RSP -ne 0 ] then echo "ERROR - Cannot remove the old Log file $SPLcomplog " exitFunc $RSP fi fi touch $SPLcomplog export RSP=$? if [ $RSP -ne 0 ] then echo "ERROR - Cannot create Log file $SPLcomplog " exitFunc $RSP fi export TMP1=$SPLSYSTEMLOGS/initialSetup.sh.tmp } exitFunc() { export RSP=$1 Log "Exiting $SCRIPTNAME with return code $RSP" if [ -f $TMP1 ] then rm -f $TMP1 > /dev/null 2>&1 fi exit $RSP } testDBconnection() { Log "Testing Database connection parameters entered in configureEnv.sh" if [ `which db2|wc -w` -gt 1 ] then Log "ERROR : cannot find \"db2\" Program. This is a PATH prerequisit to the Install"
exitFunc 1 fi . cisconnect.sh > $TMP1 2>&1 export RSP=$? if [ $RSP -ne 0 ] then Log "ERROR : connecting to Database:" Log -f "$TMP1" Log "ERROR : Rerun configureEnv.sh and ensure database connection parameters are correct" Log "ERROR : Check DB2 Connect configuration to ensure connection is o.K." exitFunc $RSP fi } Other example: check_cron() { # check of commando door cron of met de hand wordt uitgevoerd # CRON_PID=`ps -ef | grep check_sudo | grep -v grep | awk '{print $3}'` if [[ `ps -p ${CRON_PID} | grep -v TIME | awk '{print $4}'` == "cron" ]] then CRON_RUN="yes" # Genereer een sleeptime nummer, voorkom daarmee dat alle clients tegelijk de Distroserver benaderen # random_sleeptime else CRON_RUN="no" SLEEPTIME="1" fi }
Example 6: ---------P550:/home/reserve/bin $ cat CheckAppl #!/usr/bin/ksh # # # variabelen initialisatie appl=/prj/etm/1.5.20 # # to start trace option execute set -x if [ $1 = d ] then set -x fi #set -x # # cleanscreen clear echo "Just a moment" #
for i in `cat /etc/cistab | sed -e 's/:/ /g'| awk '{ print $1 }'` do #aantal processen # initialisatie aantal_processen=0 aantal_jsl=0 aantal_jrepsvr=0 aantal_bbl=0 aantal_tuxfulladm=0 aantal_tuxfullall=0 # aantal_processen=`ps -ef|grep $i| grep -v grep | wc -l` if [ $aantal_processen = 0 ] then status=DOWN else status=UP # aantal JSL aantal_jsl=`ps -ef|grep $i | grep -i JSL | wc -l` # aantal JREPSVR aantal_jrepsvr=`ps -ef|grep $i | grep -i JREPSVR | wc -l` # aantal_BBL aantal_bbl=`ps -ef|grep $i | grep -i BBL | wc -l` # aantal_TUXFULLadm aantal_tuxfulladm=`ps -ef|grep $i | grep -i tuxfulladm | wc -l` # aantal_TUXFULLall aantal_tuxfullall=`ps -ef|grep $i | grep -i tuxfullall | wc -l` fi if [ $status = UP ] ; then echo "$i $status BBL($aantal_bbl) TUXFULLall($aantal_tuxfullall) TUXFULLadm($aantal_tuxfulladm) JSL( $aantal_jsl )( JREPSVR( $aantal_jrepsvr ) " else echo $i $status fi done | sort +1 # check logs echo echo "Check backup to rmt0" echo "--------------------" tail -2 /opt/back*/backup_to_rmt0.log echo echo "Check backup to rmt1" echo "--------------------" tail -7 /opt/backupscripts/backup_to_rmt1.log echo echo "Check backup from 520" echo "---------------------" ls -l /backups/520backups/oradb/conv.dmp ls -l /backups/520backups/splenvs/*tar* Example 7:
---------#!/bin/sh getinfo() { USER=$1 PASS=$2 DB=$3 CONN="${USER}/${PASS}@${DB}"
}
echo " set linesize 1000 set pagesize 1000 set trimspool on SELECT CIS_RELEASE_ID,':', CM_RELEASE_ID FROM CI_INSTALLATION; " | sqlplus -S $CONN | grep '[0-9a-zA_Z]'
if [ $# -gt 0 ] then DB="$1" else DB="$SPLENVIRON" fi if [ "x$DB" = x ] then echo "dbvers: no environment" exit 1 fi getinfo cisread cisread $DB | sed -e 1d -e 's/[ Example 8: ---------#!/usr/bin/sh . $HOME/.profile >/dev/null 2>&1 [ $# -ne 1 ] && exit 1 MARKER=/home/cissys/etc/marker-file if [ $1 = "setmarker" ] then /bin/touch $MARKER fi
exit 0
if [ $1 = "cleanup" ] then [ \! -f $MARKER ] && exit 1
]//g'
for DIR do
in `cut -d: -f4 /etc/cistab` /usr/bin/find $DIR \! -newer $MARKER -type f -exec rm -f {} \;
done fi
exit 0
if [ $1 = "runbatch" ] then for ETM in `cut -d: -f1 /etc/cistab` do DIR1=`grep $ETM /etc/cistab|cut -d: -f3` DIR2=`grep $ETM /etc/cistab|cut -d: -f4` $DIR1/bin/splenviron.sh -q -e $ETM -c cdxcronbatch.sh \ >>$DIR2/cdxcronbatch.out 2>&1 done exit 0 fi exit 1 Example 9: ---------date >> /opt/backupscripts/backupdatabases.log cd /backups/oradb if [ -f spltrain.dmp ] then echo "backup of spltrain is OK" >> /opt/backupscripts/backupdatabases.log else echo "error backup of spltrain " >> /opt/backupscripts/backupdatabases.log fi Example 10: ----------#!/usr/bin/ksh # target : print configuration #set -x DAY=`date +%Y%m%d` HOSTNAME=`hostname` LOG=/home/reserve/log/ListConfiguration/LsConf.$DAY.$HOSTNAME.P522 date >> $LOG echo "++++++++++++++++++++++++++++++++++++++++++++" >> $LOG echo "lsdev -P " >> $LOG lsdev -P >> $LOG echo "++++++++++++++++++++++++++++++++++++++++++++" >> $LOG echo "lsdev -C " >> $LOG lsdev -C >> $LOG echo "++++++++++++++++++++++++++++++++++++++++++++" >> $LOG
echo "lsconf">> $LOG lsconf >> $LOG echo "++++++++++++++++++++++++++++++++++++++++++++" >> $LOG for i in `lsdev -C | awk '{ print $1 }` do echo "lsdev -C -l $i" >> $LOG lsattr -E -l $i >> $LOG echo >> $LOG done echo "++++++++++++++++++++++++++++++++++++++++++++" >> $LOG for i in `lsvg` do lsvg -p $i lsvg -l $i done >> $LOG echo "++++++++++++++++++++++++++++++++++++++++++++" >> $LOG for i in `lspv | awk '{ print $1 }'` do lspv -l $i lspv -L $i lspv -M $i lspv -p $i done >>$LOG echo "++++++++++++++++++++++++++++++++++++++++++++" >> $LOG echo "/etc/passwd">> $LOG cat /etc/passwd >> $LOG echo "++++++++++++++++++++++++++++++++++++++++++++" >> $LOG echo "/etc/group" >> $LOG cat /etc/group >> $LOG Example 11: ----------Make dynamic Oracle exports from a shell script. You do not need to list exp statements per database, this will be extracted from som file, like /etc/oratab. #!/usr/bin/ksh DATE=`date +%Y%m%d` HOSTNAME=`hostname` ORACONF=/etc/rc.oratab set -x # MAKE SURE THE ENVIRONMENT IS OK ORACLE_BASE=/apps/oracle; export ORACLE_BASE ORACLE_HOME=/apps/oracle/product/9.2; export ORACLE_HOME LIBPATH=/apps/oracle/product/9.2/lib; export LIBPATH ORACLE_TERM=xterm;export ORACLE_TERM export ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data LD_LIBRARY_PATH=$ORACLE_HOME/lib; export LD_LIBRARY_PATH export TNS_ADMIN=/apps/oracle/product/9.2/network/admin export ORAENV_ASK=NO PATH=/usr/local/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java1 31/jre/bin;export PATH PATH=$ORACLE_HOME/bin:$PATH;export PATH
# SAVE THE FORMER BACKUPS: LETS KEEP 1 EXTRA DAY ONLINE # Lets copy the current file to another filesystem: cd /backups/oradb # Now lets save the current file on the same filesystem in 1dayago cd /backups/oradb/1dayago mv spl*dmp /backups/oradb/2dayago cd /backups/oradb mv spl*dmp /backups/oradb/1dayago # Now create a new export file in /backups/oradb ExpOracle() { set -x for i in `cat ${ORACONF} | grep -v \# | awk '{ print $1 }'` do SID_NAME=$i BOOT=`grep $SID_NAME $ORACONF | awk '{ print $2}'` if [ $BOOT = Y ] ; then su - oracle -c " ORACLE_SID=${SID_NAME} export ORACLE_SID cd /backups/oradb exp system/cygnusx1@$SID_NAME file=$SID_NAME.$HOSTNAME.$DATE.dmp full=y statistics=none EOF " fi sleep 5 if [ -f $SID_NAME.$HOSTNAME.$DATE.dmp ] then echo "backup of $SID_NAME is OK" >> /opt/backupscripts/backupdatabases.log else echo "error backup of $SID_NAME " >> /opt/backupscripts/backupdatabases.log fi done } ExpOracle Example 12: ----------Running sqlplus from a shell script. $ORACLE_HOME/bin/sqlplus -s "/ as sysdba" 1 set heading off feedback off whenever sqlerror exit select 'DB_NAME=' || name from v\$database; .. # possible other stuff exit EOF
Example 13: ----------Kill a paricular process, that runs from "/dir/dir/abc" : kill `ps -ef | grep /dir/dir/abc | grep -v grep | awk '(print $2)'` Example 14: ----------#!/usr/bin/ksh # # description: start and stop the Documentum Content Server environment from dmadmin account # called by: dmadmin # DOCBASE_NM1=dmw_et DOCBASE_NM2=dmw_et3 function log { echo $(date +"%Y/%m/%d %H.%M.%S %Z") 'documentum.sh:' ${@} } # See how we were called. case $1 in start) # Starting DocBroker cd $DOCUMENTUM/dba ./dm_launch_Docbroker ./dm_start_$DOCBASE_NM1 ./dm_start_$DOCBASE_NM2 # Starting Tomcat services cd $DM_HOME/tomcat/bin ./startup.sh ;; stop) # Stopping Tomcat services cd $DM_HOME/tomcat/bin ./shutdown.sh # Stopping DocBroker cd $DOCUMENTUM/dba ./dm_shutdown_$DOCBASE_NM1 ./dm_shutdown_$DOCBASE_NM2 ./dm_stop_Docbroker ;; clean_logs) # Call myself to stop stuff ${0} stop # Stopping Tomcat services
find $DOCUMENTUM/dba/log -type f -name "*" -exec rm -rf {} \; # Call myself to restart stuff ${0} start ;; clean_performance) # Call myself to stop stuff ${0} stop # Stopping Tomcat services find $DOCUMENTUM/dba/log -type d -name "perftest*" -exec rm -rf {} \; find $DOCUMENTUM/dba/log -type d -name "perfuser*" -exec rm -rf {} \; find $DOCUMENTUM/dba/log -type d -name "RefAppUser*" -exec rm -rf {} \; # Call myself to restart stuff ${0} start ;; kill) cd $DOCUMENTUM/dba ./dm_launch_Docbroker -k ;; *) echo "Usage: $0 {start|stop|kill|clean_logs|clean_performance}" exit 1 esac exit 0 Example 15: ----------# Check bij aanloggen of voor dit domein een dmgr of nodeagent draait WASUSR=`whoami` echo "" DMAOK=`ps -ef | grep $WASUSR | grep dmgr | grep -v grep` if [ ! "$DMAOK" = "" ]; then echo "Deployment Manager is running!" else echo "NOTE: Deployment Manager is NOT running!" fi echo "" WASOK=`ps -ef | grep $WASUSR | grep nodeagent | grep -v grep` if [ ! "$WASOK" = "" ]; then echo "Nodeagent is running!" else echo "NOTE: Nodeagent is NOT running!" fi echo "" if [ "$WASOK" = "" ] || [ "$DMAOK" = "" ]; then echo "The $WASUSR-menu can be used to start the Deployment manager or Nodeagent." echo "Type 'menu' on the command-prompt followed by ENTER to start the menu." echo "" fi
Example 16: ----------Example with input from user: echo read if [ if
"" CLEARMSG?"Press C or c to clear this message or any other key to keep it : " "${CLEARMSG}" = "C" ] || [ "${CLEARMSG}" = "c" ]; then [ -f ExtraMessage.txt ]; then rm ~/ExtraMessage.txt
fi fi
Example 17: ----------# Check arguments if [ ${#} != 3 ] then log "Usage: ${0} " exit 1 fi # if [ -z "$1" ] then echo "use : build.sh PROGNAME e.g. build.sh CLBDSYNC " exit 1 fi if [ "$OPSYS" = "AIX" ]||[ "$OPSYS" = "HP-UX" ]||[ "$OPSYS" = "Linux" ] then .... else ....
Example 18: ----------Read Input from User and from Files - Read in a Variable From a user we read with: read var. Then the users can type something in. One should first print something like: print -n "Enter your favorite haircolor: ";read var; print "". The -n suppresses the newline sign.
- Read into a File Line for Line To get each line of a file into a variable iteratively do: { while read myline;do # process $myline done } < filename - To catch the output of a pipeline each line at a time in a variable use: last | sort | { while read myline;do # commands done }
Example 19: ----------#!/bin/sh # **************************************************************************** # This script is used to start Tomcat # It calls the startup.sh script under $CATALINA_HOME/bin. # # **************************************************************************** #JAVA_OPTS="-Xms512m -Xmx512m -XX:NewSize=128m -XX:SurvivorRatio=8 -verbosegc" JAVA_OPTS="-Xms384m -Xmx384m" export JAVA_OPTS CATALINA_BASE=$SPLEBASE/tomcatBase export CATALINA_BASE if [ ! -d $CATALINA_HOME/bin ] then echo "Unable to find directory $CATALINA_HOME/bin" else $CATALINA_HOME/bin/startup.sh fi Example 20: ----------export export export export export export
SCRIPTNAME=$0 SPLQUITE=N SPLCOMMAND="" SPLENVIRON="" MYID=`id |cut -d'(' -f2|cut -d')' -f1` SPLSUBSHELL=ksh
# Current Platform and OS export OPSYS=`uname -s` case $OPSYS in SunOS) export OPSYSVER=`uname -r` # Supplied and Supported Tuxedo Version TUXVERS=tuxedo8.1 # Supplied and Supported Cobol Application Server
#
# #
#
SPLCOBDIR=/opt/SPLcobAS40sp2 Supplied and Supported Java Version AWK=nawk ;; AIX) export OPSYSVER=`oslevel | cut -c1-3` TUXVERS=tuxedo8.1 Supplied and Supported Cobol Application Server SPLCOBDIR=/opt/SPLcobAS40sp2 Supplied and Supported Java Version AWK=nawk ;; Linux) export OPSYSVER=`uname -r| cut -c1-3` TUXVERS=tuxedo8.1 Supplied and Supported Cobol Application Server SPLCOBDIR=/opt/SPLcobAS40sp2 AWK=awk SPLSUBSHELL=bash ;; HP-UX)
# # esac
export OPSYSVER=`uname -r|sed 's/^[A-Z]\.//'|cut -c1-2` TUXVERS=tuxedo8.1 Supplied and Supported Cobol Application Server SPLCOBDIR=/opt/SPLcobAS40sp2 Supplied and Supported Java Version AWK=awk ;;
Example 21: ----------Get a certain number of columns from df -k output: df -k |awk '{print $1,$2,$5,$8}' |grep -v "Filesystem" > /tmp/df.txt #!/usr/bin/ksh for i in `df -k |awk '{print $7}' |grep -v "Filesystem"'` do echo "Albert" done #!/usr/bin/ksh cd ~ rm -rf /root/alert.log echo "Important alerts in errorlog: " >> /root/alert.log errpt | grep -i STORAGE >> /root/alert.log errpt | grep -i QUORUM >> /root/alert.log errpt | grep -i ADAPTER >> /root/alert.log errpt | grep -i VOLUME >> /root/alert.log errpt | grep -i PHYSICAL >> /root/alert.log errpt | grep -i STALE >> /root/alert.log errpt | grep -i DISK >> /root/alert.log
errpt | grep -i LVM >> /root/alert.log errpt | grep -i LVD >> /root/alert.log errpt | grep -i UNABLE >> /root/alert.log errpt | grep -i USER >> /root/alert.log errpt | grep -i CORRUPT >> /root/alert.log cat /root/alert.log if [ `cat alert.log|wc -l` -eq 1 ] then echo "No critical errors found." fi echo " " echo "Filesystems that might need attention, e.g. %used:" df -k |awk '{print $4,$7}' |grep -v "Filesystem"|grep -v tmp cat /root/tmp.txt | sort -n | tail -3
> /root/tmp.txt
Example 22: ----------for sid in `grep -v "^#" /etc/oratab | sed -e 's/:.*$//'` do echo "/data/oracle/$sid/admin/bdump/alert_$sid.log:/beheer/log/history/oracle/$sid:cat: :::" >> /tmp/test done Notes: -----lsnrctl>set Log_status off mv Listener.log to listenerold.log lsnrctl>set Log_Status on % % % %
cd /u01/app/oracle/product/9.2.0/network/log lsnrctl set log_status off mv listener.log listener.old lsnrctl set log_status on
case $IN in start) for dbase in `grep -v "^#" /etc/oratab | sed -e 's/:.*$//'` do su - $dbase -c "/beheer/oracle/cluster/orapkg.sh start" done;; for dbase in `grep -v "^#" /etc/oratab | sed -e 's/:.*$//'` do echo $dbase done;; for sid in `grep -v "^#" /etc/oratab | sed -e 's/:.*$//'` do echo "/data/oracle/$sid/admin/bdump/alert_$sid.log:/beheer/log/history/oracle/$sid:cat:
:::" >> /tmp/test done
===================== 3. BOOT and Shutdown: ===================== 3.1 Shutdown systems: ===================== 3.1.1 Shutdown a Solaris system: ================================ Under Solaris, you need to use init or shutdown are normally best: they run the kill scripts halt or reboot do not run the kill scripts properly /usr/sbin/shutdown -i5 -g0 /usr/sbin/shutdown -i6 -g0 -y /usr/sbin/shutdown -i0 -g0 shutdown -i6
-- this let the system go to the powerdown state -- this let the system reboot -- shuts everything down, unmounts all fs
(is a reboot in Solaris8)
shutdown [-y no interactive confirmations] [-g grace period in seconds] [-i init state] [message] - If you say init 6, or shutdown -i6, the system reboots an restart into a runstate as defined as the default in the inittab file. - If you say init 0, the system cleanly shuts down, and you can power of the system If you say init 5, is equivalent to the poweroff command, and the system cleanly shuts down, and you can power of the system to achieve the desired effect. Be sure to read the man page for shutdown for your operating system. With no argument, shutdown will take the system into single user mode. - The /usr/sbin/reboot command: is used when you want to reboot. The system does not go through the shutdown scripts. Also, it usually sync's the filesystem. Thus, the following is a safe bet on all Unixes: sync;sync;sync;reboot - The /usr/sbin/halt command: syncs the filesystem and stops the processor. No shutdown scripts are fired up.
- The fastboot/fasthalt command: The fasthalt command halts the processor and creates a /fastboot file to tell the system to skip the fsck operation upon reboot - The sync command: completes pending filesystem writes to disk (in other words, the buffer cache is dumped to disk). Most Unix shutdown, reboot, and halt commands will do a sync. However, the reboot, fastboot, or halt commands will not go through the shutdown scripts. If you manually sync, it is customary to do it multiple times (as we saw before). This is partly Unix superstition and part fact. The first sync is supposed to schedule a sync, not actually perform it. The second and subsequent syncs force the sync. sync sync init 0 - Shutdown scripts: Like startup scripts, the system initialization directories (usually /etc/rcN.d) contains shutdown scripts which are fired up by init during an orderly shutdown (i.e. when either the init command is used to change the runlevel or when the shutdown command is used). The usual convention is to use the letter K in front of a number, followed by a service name, such as K56network. The number determines the order in which the scripts are fired up when the system transitions into a particular run level. 3.1.2 Shutdown an AIX system: ============================= You can use the init, shutdown and halt commands. The shutdown command stops the system in an orderly fashion. Bring the system from multi-user mode to maintenance mode, use # shutdown -m To restart the system, use # shutdown -r To gracefully shutdown the system, use # shutdown If you need a customized shutdown sequence, you can create a file called /etc/rc.shutdown. If this file exists, it is called by the shutdown command and is executed first. This can be usefull for example, if you need to close a database prior to a shutdown. If rc.shutdown fails (non zero return code value), the shutdown cycle is terminated.
Example rc.shutdown: -------------------#cat /etc/rc.shutdown #!/bin/ksh # stop Control-SA/Agent /etc/rc.ctsa stop /etc/rc.mwa stop /etc/rc.opc stop # Stop TSM dsmcad en scheduler /etc/rc.dsm stop # Stop TSCM client /opt/IBM/SCM/client/jacclient stop # /etc/rc.shutdown SHOULD always end with a # Stop db2 instances as last line /etc/rc.ihs stop /etc/rc.ihs stop des /etc/rc.appserver stop PRM1DES /etc/rc.nodeagent stop /etc/rc.dmgr stop # Stop db2 instances /etc/rc.db2_udb stop all /etc/rc.directoryserver stop #Stop the Tivoli Enterprise Console Logfile Adapter if [ -f /beheer/Tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/bin/init.tecad_logfile ]; then /beheer/Tivoli/lcf/bin/aix4-r1/TME/TEC/adapters/bin/init.tecad_logfile stop aix-default >/dev/null 2>&1 echo "Tivoli Enterprise Console Logfile Adapter stopped." fi exit 0
3.1.3 Shutdown a Linux system: ============================== Note 1: Redhat systems: To shut down Red Hat Linux, issue the shutdown command. You can read the shutdown man page for complete details, but the two most common uses are: /sbin/shutdown -h now /sbin/shutdown -r now You must run shutdown as root. After shutting everything down, the -h option will halt the machine,
and the -r option will reboot. Non-root users can use the reboot and halt commands to shutdown the system while in runlevels 1 through 5. However, not all Linux operating systems support this feature. If your computer does not power itself down, be careful not turn off the computer until you see a message indicating that the system is halted.
3.2 Booting: ============ 3.2.1 Generic description booting a unix system: ================================================ 1. Or some rom menu, or some command prompt, or automatic procedure, provides for finding or selecting initial bootstraps code on some device 2. kernel is loaded (unix, vmunix etc.. in /, or /boot, or /kernel, or some place else) 3. start init 4. run scripts SunOs: /vmunix Solaris8 = SunOs 5.8: /kernel/unix AIX: /unix
3.2.2 Bootprocedure Solaris: ============================ 1. Boot overview ---------------- Openboot PROM: After a dignostice fase, it shows either - the "ok" prompt or - via Openboot parameter "auto_boot" goes on with the bootprocedure. Thanks to the Openboot parameter "boot_device" the path to the bootblk is known. You can also use the "ok boot alias/physical_device_name" to boot from the specified device, like for example "ok boot disk3" You can also use options as "ok boot -a=interactive boot, -r=reconfiguration boot, -s=boot to single-user state, -v=verbose mode"
The command "ok boot disk5 kernel/unix -s", the PROM will look for the primary bootprogram bootblk on the alias disk5, which could be a physical device as /iommu/sbus/espdma@f,400000/esp@f,800000/sd@0,0 The primary startup command will then load "ufsboot". This will then load the kernel as specified. Thus, after the simple boot command, the boot process goes on in the following manner: -
bootblk (from the default boot-device) bootblk find ufsboot (plus filesystem drivers) ufsboot starts the kernel, its merges genunix and unix (mounts the root fs) kernel mounts other fs start sched (swapper) start /sbin/init init starts demons in rc scripts
You can also view the startup information via: $ more /var/adm/messages $ /usr/sbin/dmesg 2. Booting with Other system file: ---------------------------------1. login as root 2. create a backup copy of the /etc/system file cp /etc/system /etc/system.orig 3. Halt the system /usr/sbin/shutdown -y -g0 -i0 4. at the OK prompt, boot the system using the interactive option OK boot -a 5. You will be prompted to enter a filename for the kernel, and a default directory for modules. Enter a return for each of these questions. When prompted to use the default /etc/system file: Name of system file [etc/system]: enter the following: /etc/system.orig 3. More about init: init uses the /etc/inittab File When you boot the system or change run levels with the init or shutdown command, the init daemon starts processes by reading information from the /etc/inittab file. This file defines three important items for the init process: -The system's default run level
-What processes to start, monitor, and restart if they terminate -What actions to be taken when the system enters a new run level Each entry in the /etc/inittab file has the following fields: id:rstate:action:process in /etc we find the links: rc0 -> /sbin/rco rc1 -> /sbin/rc1 rc2 -> /sbin/rc2 rc3 -> /sbin/rc3 rc4 -> /sbin/rc4 rc5 -> /sbin/rc5 rc6 -> /sbin/rc6 in /sbin we find the scripts rc0 - rc6, rcS. These are not links, but true shell scripts. In /etc we find the links rc0 - rc6, rcS. In /etc we find the (true) directories /etc/rc#.d. So suppose the runlevel=3 1. init reads inittab Contents /etc/inittab \u@\h[\w]> more inittab ap::sysinit:/sbin/autopush -f /etc/iu.ap ap::sysinit:/sbin/soconfig -f /etc/sock2path fs::sysinit:/sbin/rcS >/dev/console 2/dev/console /dev/console 2/dev/console s0:0:wait:/sbin/rc0 >/dev/console 2/dev/console /dev/console 2/dev/console /dev/console 2/dev/console /dev/console 2/dev/console /dev/console 2/dev/console /dev/console 2/dev/console /dev/console 2/dev/console /dev/console 2/dev/console /dev/console 2/dev/console /dev/null 2>&1 if [ $9 = 'S' -o $9 = '1' ] then echo 'The system is ready.' fi 4. From /sbin/rc3 all K* and S* scripts in /etc/rc3.d will be run Oracle is installed on this host, so there should be a /etc/rc3.d/S99oracle or similar script. Now there indeed exists the S88dbora script. 5. There is an S88dbora script, so it will be called: Oracle S88dbora script in /etc/rc3.d Example: -------mt -f /dev/rm rewind tar -xvf /dev/rmt1.1 fielname mt -f /dev/rmt0.1 fsf 2 (voor drie) (daarna staat tapepointer op begin 4) fsf bsf \u@\h[\w]> more S88dbora #!/bin/sh # # Startup for Oracle Databases # ORACLE_HOME=/opt/oracle/product/8.0.6 ORACLE_OWNER=oracle if [ ! -f $ORACLE_HOME/bin/dbstart ] ;then echo "Oracle startup: cannot start" exit fi case "$1" in 'start') # Start the Oracle databases su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/dbstart" > /dev/null 2>&1
2>&1
su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/lsnrctl start" > /dev/null 2>&1 su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/lsnrctl dbsnmp_start" > /dev/null ;;
'stop') # Stop the Oracle databases su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/lsnrctl dbsnmp_stop" > /dev/null 2>&1 su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/lsnrctl stop" > /dev/null 2>&1 su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/dbshut" > /dev/null 2>&1 ;; *) esac
echo "Usage: $0 { start | stop }" ;;
Another example: ---------------more /etc/init.d/dbora nlih30207858-08:/etc/init.d $ more dbora # Set ORA_HOME to be equivalent to the ORACLE_HOME # from which you wish to execute dbstart and # dbshut # set ORA_OWNER to the user id of the owner of the # Oracle database in ORA_HOME ORA_HOME=/u01/app/oracle/product/9.2 ORA_OWNER=oraclown if [ ! -f $ORA_HOME/bin/dbstart -o ! -d $ORA_HOME ] then echo "Oracle startup: cannot start" exit fi case "$1" in 'start') # Start the Oracle databases and listener: su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl start" & su - $ORA_OWNER -c $ORA_HOME/bin/dbstart & ;; 'stop') # Stop the Oracle databases and listener: su - $ORA_OWNER -c $ORA_HOME/bin/lsnrctl stop & su - $ORA_OWNER -c $ORA_HOME/bin/dbshut & ;; esac 6. To start the database(s) en listener(s), the dbstart script is run: \u@\h[\w]> more dbstart : # # $Header: dbstart.sh.pp 1.1 95/02/22 14:37:29 rdhoopar Osd $ dbstart.sh.p p Copyr (c) 1991 Oracle #
################################### # # usage: dbstart # # This script is used to start ORACLE from /etc/rc(.local). # It should ONLY be executed as part of the system boot procedure. # ##################################### ORATAB=/var/opt/oracle/oratab trap 'exit' 1 2 3 case $ORACLE_TRACE in T) set -x ;; esac # Set path if path not set (if called from /etc/rc) case $PATH in "") PATH=/bin:/usr/bin:/etc export PATH ;; esac # # Loop for every entry in oratab file and and try to start # that ORACLE # cat $ORATAB | while read LINE do case $LINE in \#*) ;; #comment-line in oratab *) # Proceed only if third field is 'Y'. if [ "`echo $LINE | awk -F: '{print $3}' -`" = "Y" ] ; then ORACLE_SID=`echo $LINE | awk -F: '{print $1}' -` if [ "$ORACLE_SID" = '*' ] ; then ORACLE_SID="" fi # Called programs use same database ID export ORACLE_SID ORACLE_HOME=`echo $LINE | awk -F: '{print $2}' -` # Called scripts use same home directory export ORACLE_HOME # Put $ORACLE_HOME/bin into PATH and export. PATH=$ORACLE_HOME/bin:/bin:/usr/bin:/etc ; export PATH PFILE=${ORACLE_HOME}/dbs/init${ORACLE_SID}.ora #
Figure out if this is a V5, V6, or V7 database. Do we really need V5? if [ -f $ORACLE_HOME/bin/sqldba ] ; then VERSION=`$ORACLE_HOME/bin/sqldba command=exit | awk ' /SQL\*DBA: (Release|Version)/ {split($3, V, ".") ; print V[1]}'` else if test -f $ORACLE_HOME/bin/svrmgrl; then VERSION="7.3"
else VERSION="5"
fi fi if test
-f $ORACLE_HOME/dbs/sgadef${ORACLE_SID}.dbf -o \ -f $ORACLE_HOME/dbs/sgadef${ORACLE_SID}.ora
then STATUS="-1" else STATUS=1 fi case $STATUS in 1) if [ -f $PFILE ] ; then case $VERSION in 5) ior w pfile=$PFILE ;;
connect internal startup EOF
6)
sqldba command=startup ;;
7)
sqldba &1 # Enable 64-bit execs tunables:23456789:wait:/usr/sbin/tunrestore -R > /dev/console 2>&1 # Set tunables rc:23456789:wait:/etc/rc 2>&1 | alog -tboot > /dev/console # Multi-User checks fbcheck:23456789:wait:/usr/sbin/fbcheck 2>&1 | alog -tboot > /dev/console # run /etc/firstboot srcmstr:23456789:respawn:/usr/sbin/srcmstr # System Resource Controller rctcpip:23456789:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP daemons rcnfs:23456789:wait:/etc/rc.nfs > /dev/console 2>&1 # Start NFS Daemons cron:23456789:respawn:/usr/sbin/cron nimclient:2:once:/usr/sbin/nimclient -S running piobe:2:wait:/usr/lib/lpd/pio/etc/pioinit >/dev/null 2>&1 # pb cleanup qdaemon:23456789:wait:/usr/bin/startsrc -sqdaemon writesrv:23456789:wait:/usr/bin/startsrc -swritesrv uprintfd:23456789:respawn:/usr/sbin/uprintfd shdaemon:2:off:/usr/sbin/shdaemon >/dev/console 2>&1 # High availability daemon l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 l7:7:wait:/etc/rc.d/rc 7 l8:8:wait:/etc/rc.d/rc 8 l9:9:wait:/etc/rc.d/rc 9 logsymp:2:once:/usr/lib/ras/logsymptom # for system dumps itess:23456789:once:/usr/IMNSearch/bin/itess -start search >/dev/null 2>&1 diagd:2:once:/usr/lpp/diagnostics/bin/diagd >/dev/console 2>&1 httpdlite:23456789:once:/usr/IMNSearch/httpdlite/httpdlite -r /etc/IMNSearch/httpdlite/httpdlite.conf & >/dev/console 2>&1 ha_star:h2:once:/etc/rc.ha_star >/dev/console 2>&1 dt_nogb:2:wait:/etc/rc.dt cons:0123456789:respawn:/usr/sbin/getty /dev/console srv:2:wait:/usr/bin/startsrc -s sddsrv > /dev/null 2>&1 perfstat:2:once:/usr/lib/perf/libperfstat_updt_dictionary >/dev/console 2>&1 ctrmc:2:once:/usr/bin/startsrc -s ctrmc > /dev/console 2>&1 lsof:2:once:/usr/lpp/aix4pub/lsof/mklink monitor:2:once:/usr/lpp/aix4pub/monitor/mklink nmon:2:once:/usr/lpp/aix4pub/nmon/mklink ptxnameserv:2:respawn:/usr/java14/jre/bin/tnameserv -ORBInitialPort 2279 2>&1 >/dev/null # Start jtopasServer ptxfeed:2:respawn:/usr/perfagent/codebase/jtopasServer/feed 2>&1 >/dev/null # Start jtopasServer
ptxtrend:2:once:/usr/bin/xmtrend -f /etc/perf/jtopas.cf -d /etc/perf/Top -n jtopas 2>&1 >/dev/null # Start trend direct:2:once:/tmp/script_execute_after_reboot_pSeries 2>>/tmp/pSeries.050527_16:56.log fmc:2:respawn:/usr/opt/db2_08_01/bin/db2fmcd #DB2 Fault Monitor Coordinator smmonitor:2:wait:/usr/sbin/SMmonitor start > /dev/console 2>&1 # start SMmonitor daemon The inittab is reread by the init daemon every 60 secs. To add records into the inittab file, you should use the mkitab command. For example, to add an entry for tty4, enter the following command: # mkitab "tty4:2:respawn:/usr/sbin/getty /dev/tty4" Other observations: ------------------{dbserver2:root}/etc/rc.d -> cd /etc/rc.d {dbserver2:root}/etc/rc.d -> ls -al total 40 drwxr-xr-x 11 root system 4096 drwxr-xr-x 30 root system 12288 drwxr-xr-x 2 root system 256 -r-xr--r-1 root system 1586 drwxr-xr-x 2 root system 256 drwxr-xr-x 2 root system 256 drwxr-xr-x 2 root system 256 drwxr-xr-x 2 root system 256 drwxr-xr-x 2 root system 256 drwxr-xr-x 2 root system 256 drwxr-xr-x 2 root system 256 drwxr-xr-x 2 root system 256
Oct Aug May Sep May Oct Oct Oct Oct Oct Oct Oct
08 08 27 16 27 08 08 08 08 08 08 08
2002 11:41 16:56 2002 17:00 2002 2002 2002 2002 2002 2002 2002
. .. init.d rc rc2.d rc3.d rc4.d rc5.d rc6.d rc7.d rc8.d rc9.d
The bootlist command: --------------------Purpose Displays and alters the list of boot devices available to the system. Syntax bootlist [ { -m Mode } [ -r ] [ -o ] [ [ -i ] [ -V ] [ -F ]| [ [ -f File ] [ Device [ Attr=Value ... ] ... ] ] ] [ -v ] The bootlist command allows the user to display and alter the list of possible boot devices from which the system may be booted. When the system is booted, it will scan the devices in the list and attempt to boot from the first device it finds containing a boot image. The AIX "bootlist" command can be used to select the boot disk. This is useful if you want to test different AIX levels on the same system. For example, assume hdisk0 has AIX 4.2.1 installed and hdisk1 AIX 4.3.3 installed.
Use one of the following "bootlist" commands** to select which version will come up on the next reboot: bootlist -m normal hdisk0 bootlist -m normal hdisk1
# Reboots to AIX421 # Reboots to AIX433
The second disk can be installed from CD, a "mksysb" tape, or using AIX 4.3's "alt_disk_install" capability. Both CD and mksysb installs require downtime. The "alt_disk_install" allows you to install the second disk from a "mksysb" or clone your existing OS while the system is running ** Comment: In practice, I recommend the following "bootlist" syntax which specifies that if hdisk0 fails to boot, try booting from hdisk1, then tape, and finally CD ROM. bootlist -m normal hdisk0 hdisk1 rmt cd The bosboot command: -------------------Purpose Creates boot image. Syntax For General Use: bosboot -Action [ -d Device ] [ -Options ... ] To Create a Device Boot Image: bosboot -a [ -d Device ] [ -p Proto ] [ -k Kernel ] [ -I | -D ] [ -l LVdev ] [ -L] [ -M { Norm | Serv | Both } ] [ -T Type ] [ -b FileName ] [ -q ] Description The bosboot command creates the boot image that interfaces with the machine boot ROS (Read-Only Storage) EPROM (Erasable Programmable Read-Only Memory). The bosboot command creates a boot file (boot image) from a RAM (Random Access Memory) disk file system and a kernel. This boot image is transferred to a particular media that the ROS boot code recognizes. When the machine is powered on or rebooted, the ROS boot code loads the boot image from the media into memory. ROS then transfers control to the loaded images kernel. Examples - To make a disk bootable, or recreate the boot image, use: # bosboot -a -d /dev/hdiskn - To create a boot image on the default boot logical volume on the fixed disk from which the system is booted, enter: bosboot -a - To create a bootable image called /tmp/tape.bootimage for a tape device, enter: bosboot -ad /dev/rmt0 -b /tmp/tape.bootimage
- To copy a given tape boot image to a tape device, enter: bosboot -w /tmp/tape.bootimage -d rmt0 - To create a boot image file for an Ethernet boot, enter: bosboot -ad /dev/ent0 -M both - When you have migrated a disk like disk0 to disk1, and you need to make the second disk bootable, proceed as follows: bosboot -a -d /dev/DestinationDiskNumber
# bosboot -ad
/dev/hdiskxx
Then: bootlist -m normal DestinationDiskNumber Then: mkboot -c -d /dev/SourceDiskNumber
3.2.5 Bootprocedure Linux: ========================== Note 1: Redhat system --------------------1. on a x86 system, the BIOS loads. 2. BOS loads the MBR of the first (primary) disk Once loaded, the BIOS tests the system, looks for and checks peripherals and then locates a valid device with which to boot the system. Usually, it first checks any floppy drives and CDROM drives present for bootable media, then it looks to the system's hard drives. The order of the drives searched for booting can often be controlled with a setting in BIOS. Often, the first hard drive set to boot is the C drive or the master IDE device on the primary IDE bus. The BIOS loads whatever program is residing in the first sector of this device, called the Master Boot Record or MBR, into memory. The MBR is only 512 bytes in size and contains machine code instructions for booting the machine along with the partition table. Once found and loaded the BIOS passes control whatever program (the bootloader) is on the MBR. 3. bootloader in MBR Linux boot loaders for the x86 platform are broken into at least two stages. The first stage is a small machine code binary on the MBR. Its sole job is to locate the second stage boot loader and load the first part of it into memory. Under Red Hat Linux you can install one of two boot loaders: GRUB or LILO. GRUB is the default boot loader, but LILO is available for those who require it for their hardware setup or who prefer it.
> If you are using LILO under Red Hat Linux, the second stage boot loader uses information on the MBR to determine what boot options are available to the user. This means that any time a configuration change is made or you upgrade your kernel manually, you must run the /sbin/lilo -v -v command to write the appropriate information to the MBR. For details on doing this, see the Section called LILO in Chapter 4. > GRUB, on the other hand, can read ext2 partitions and therefore simply loads its configuration file � /boot/grub/grub.conf � when the second stage loader is called. Once the second stage boot loader is in memory, it presents the user with the Red Hat Linux initial, graphical screen showing the different operating systems or kernels it has been configured to boot. If you have only Red Hat Linux installed and have not changed anything in the /etc/lilo.conf or /boot/grub/grub.conf, you will only see one option for booting. If you have configured the boot loader to boot other operating systems, this screen gives you the opportunity to select it. Use the arrow keys to highlight the operating system and press [Enter]. If you do nothing, the boot loader will load the default selection. 4. Kernel Once the second stage boot loader has determined which kernel to boot, it locates the corresponding kernel binary in the /boot/ directory. The proper binary is the /boot/vmlinuz2.4.x-xx file that corresponds to the boot loader's settings. Next the boot loader places the appropriate initial RAM disk image, called an initrd, into memory. The initrd is used by the kernel to load any drivers not compiled into it that are necessary to boot the system. This is particularly important if you have SCSI hard drives or are using the ext3 file system [1]. When the kernel loads, it immediately initializes and configures the computer's memory. Next it configures the various hardware attached to the system, including all processors and I/O subsystems, as well as any storage devices. It then looks for the compressed initrd image in a predetermined location in memory, decompresses it, mounts it, and loads all necessary drivers. Next it initializes file system-related virtual devices, such as LVM or software RAID before unmounting the initrd disk image and freeing up all the memory it once occupied. After the kernel has initialized all the devices on the system, it creates a root device, mounts the root partition read-only, and frees unused memory.
At this point, with the kernel loaded into memory and operational. However, with no user applications to give the user the ability to provide meaningful input to the system, not much can be done with it. To set up the user environment, the kernel starts the /sbin/init command. 5. init The init program coordinates the rest of the boot process and configures the environment for the user. When the init command starts, it becomes the parent or grandparent of all of the processes that start up automatically on a Red Hat Linux system. First, it runs the /etc/rc.d/rc.sysinit script, which sets your environment path, starts swap, checks the file systems, and so on. Basically, rc.sysinit takes care of everything that your system needs to have done at system initialization. For example, most systems use a clock, so on them rc.sysinit reads the /etc/sysconfig/clock configuration file to initialize the clock. Another example is if you have special serial port processes which must be initialized, rc.sysinit will execute the /etc/rc.serial file. This is what init runs: /sbin/init
-> runs /etc/rc.d/rc.sysinit -> runs /etc/inittab -> inittab contains default runlevel: init runs all processes for that runlevel /etc/rc.d/rcN.d/ , -> runs /etc/rc.d/rc.local Below is an example listing for a runlevel 5, /etc/rc.d/rc5.d/ directory: K01pppoe -> ../init.d/pppoe K05innd -> ../init.d/innd K10ntpd -> ../init.d/ntpd K15httpd -> ../init.d/httpd K15mysqld -> ../init.d/mysqld K15pvmd -> ../init.d/pvmd K16rarpd -> ../init.d/rarpd K20bootparamd -> ../init.d/bootparamd K20nfs -> ../init.d/nfs .. .. K80nscd -> ../init.d/nscd K84ypserv -> ../init.d/ypserv K90ups -> ../init.d/ups K96irda -> ../init.d/irda S05kudzu -> ../init.d/kudzu S06reconfig -> ../init.d/reconfig S08ipchains -> ../init.d/ipchains S10network -> ../init.d/network S12syslog -> ../init.d/syslog .. etc..
As you can see, none of the scripts that actually start and stop the services are located in the /etc/rc.d/rc5.d/ directory. Rather, all of the files in /etc/rc.d/rc5.d/ are symbolic links pointing to scripts located in the /etc/rc.d/init.d/ directory. Symbolic links are used in each of the rc directories so that the runlevels can be reconfigured by creating, modifying, and deleting the symbolic links without affecting the actual scripts they reference. As usual, the K* scripts are kill/stop scripts, and the S* scripts are started in sequence by number. In runlevel 5, /etc/inittab runs a script called /etc/X11/prefdm. The prefdm script runs the preferred X display manager, gdm if you are running GNOME or kdm if you are running KDE, based on the contents of the /etc/sysconfig/desktop/ directory. The last thing the init program does is run any scripts located in /etc/rc.d/rc.local. At this point, the system is considered to be operating at runlevel 5. You can use this file to add additional commands necessary for your environment. For instance, you can start additional daemons or initialize a printer. - Differences in the Boot Process of Other Architectures Once the Red Hat Linux kernel loads and hands off the boot process to the init command, the same sequence of events occurs on every architecture. So the main difference between each architecture's boot process is in the application used to find and load the kernel. For example, the Alpha architecture uses the aboot boot loader, while the Itanium architecture uses the ELILO boot loader. - Runlevels SysV Init The SysV init is a standard process used by Red Hat Linux to control which software the init command launches or shuts off on a given runlevel. SysV init chosen because it is easier to use and more flexible than the traditional BSD style init process. The configuration files for SysV init are in the /etc/rc.d/ directory. Within this directory, are the rc, rc.local, and rc.sysinit scripts as well as the following directories: init.d rc0.d rc1.d rc2.d rc3.d rc4.d rc5.d
rc6.d The init.d directory contains the scripts used by the init command when controlling services. Each of the numbered directories represent the six default runlevels configured by default under Red Hat Linux. The default runlevel is listed in /etc/inittab. To find out the default runlevel for your system, look for the line similar to the one below near the top of /etc/inittab: id:3:initdefault: Generally, Red Hat Linux operates in runlevel 3 or runlevel 5 � both full multiuser modes. The following runlevels are defined in Red Hat Linux: 0 1 2 3 4 5 6
� � � � � � �
Halt Single-user mode Not used (user-definable) Full multi-user mode Not used (user-definable) Full multi-user mode (with an X-based login screen) Reboot
If you are using LILO, you can enter single-user mode by typing "linux single" at the LILO boot: prompt. If you are using GRUB as your boot loader, you can enter single-user mode using the following steps. - In the graphical GRUB boot loader screen, select the Red Hat Linux boot label and press [e] to edit it. - Arrow down to the kernel line and press [e] to edit it. - At the prompt, type single and press [Enter]. - You will be returned to the GRUB screen with the kernel information. Press the [b] key to boot the system into single user mode. In case of boot problems, like a corrupt /etc/inittab file, you might try the following: Boot by typing linux init=/bin/bash at the LILO boot: prompt. This places you at a shell prompt; note that no file systems other than the root file system are mounted, and the root file system is mounted in read-only mode. To mount it in read-write mode (to allow editing of a broken /etc/inittab, for example) do: mount -n /proc mount -o rw,remount / - Installing GRUB: Once the GRUB rpm package is installed, open a root shell prompt and run the command
/sbin/grub-install , where is the location GRUB Stage 1 boot loader should be installed. The following command installs GRUB to the MBR of the master IDE device on the primary IDE bus, alos known as the C drive: /sbin/grub-install /dev/hda - GRUB and bootpaths: In Linux entire harddisks are listed as devices without numbers, such as "/dev/hda" (IDE) or "/dev/sda" (SCSI). Partitions on a disk are referred to with a number such as "/dev/hda1". GRUB uses something different. Device Names in GRUB: The first hard drive of a system is called (hd0) by GRUB. The first partition on that drive is called (hd0,0), and the fifth partition on the second hard drive is called (hd1,4). In general, the naming convention for file systems when using GRUB breaks down in this way: (,) The parentheses and comma are very important to the device naming conventions. The refers to whether a hard disk (hd) or floppy disk (fd) is being specified. The is the number of the device according to the system's BIOS, starting with 0. The primary IDE hard drive is numbered 0, while the secondary IDE hard drive is numbered 1. The ordering is roughly equivalent to the way the Linux kernel arranges the devices by letters, where the a in hda relates to 0, the b in hdb relates to 1, and so on. File Names When typing commands to GRUB involving a file, such as a menu list to use when allowing the booting of multiple operating systems, it is necessary to include the file immediately after specifying the device and partition. A sample file specification to an absolute filename is organized as follows: (,)/path/to/file, for example, (hd0,0)/grub/grub.conf. - Example grub.conf: default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz # section to load linux title Red Hat Linux (2.4.18-5.47)
root (hd0,0) kernel /vmlinuz-2.4.18-5.47 ro root=/dev/sda2 initrd /initrd-2.4.18-5.47.img # section to load Windows 2000 title windows rootnoverify (hd0,0) chainloader +1 This file would tell GRUB to build a menu with Red Hat Linux as the default operating system, set to autoboot it after 10 seconds. Two sections are given, one for each operating system entry, with commands specific to this system's disk partition table. - Example lilo.conf: The file /etc/lilo.conf is used by lilo to determine which operating system or kernel to start, as well as to know where to install itself (for example, /dev/hda for the first MBR of the first IDE hard drive). A sample /etc/lilo.conf file looks like this (your /etc/lilo.conf may look a little different): boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 message=/boot/message lba32 default=linux image=/boot/vmlinuz-2.4.0-0.43.6 label=linux initrd=/boot/initrd-2.4.0-0.43.6.img read-only root=/dev/hda5 other=/dev/hda1 label=dos
- Creating a bootdiskette in Redhat: Change to the directory that contains the image file. That might be on the original CD of Redhat. then use the following command: # dd if=boot.img of=/dev/fd0 bs=1440k
3.2.6 Bootprocedure HP-UX 11.x: ===============================
3.2.6.1 Shutdown the system: ---------------------------Note 1: Shutdown HP-UX ---------------------System Shutdown To shut down HP-UX for power-off, you can do any of the following: # init 0 # shutdown -h -y now To shut down and reboot HP-UX: # reboot # shutdown -r -y now To shut down HP-UX to single-user mode: # init S # shutdown -y now # shutdown 0 The -h option to the shutdown command halts the system completely but will prompt you for a message to issue users. The -y option completes the shutdown without asking you any of the questions it would normally ask. Note 2: Shutdown HP-UX: ----------------------When HP-UX is running on an nPartition, you can shut down HP-UX using the shutdown command. On nPartitions you have the following options when shutting down HP-UX: To shut down HP-UX and reboot an nPartition: shutdown -r On nPartition-capable HP Integrity servers, the shutdown -r command is equivalent to the shutdown -R command. To shut down HP-UX and halt an nPartition: shutdown -h On nPartition-capable HP Integrity servers, the shutdown -h command is equivalent to the shutdown -R -H command. To perform a reboot for reconfig of an nPartition: shutdown -R To hold an nPartition at a shutdown for reconfig state: shutdown -R -H Note 3: Shutdown HP-UX: ----------------------Shutting down /sbin/shutdown -r -y now /sbin/shutdown -h -y now
Reboot Stop system
/sbin/shutdown -y now
Single user mode
Note 4: Shutdown HP-UX: ----------------------To reboot HP-UX use command # reboot To shutdown HP-UX in 120 seconds (2 minutes) use command # shutdown -hy 120 To shutdown to single user mode use command # shutdown -y 0 To shutdown down a V-Class server use command # cd / # shutdown When you are are at root prompt (from single user mode restart) type following command: # reboot -h
3.2.6.1 Booting HP-UX: ---------------------Note 1: ------PDC -> ISL -> hpux -> kernel -> init PDC HP-UX systems come with firmware installed called Processor Dependent Code. After the system is powered on or the processor is RESET, the PDC runs self-test operations and initializes the processor. PDC also identifies the console path so it can provide messages and accept input. PDC would then begin the "autoboot" process unless you interrupt it during the 10-second interval that is supplied. If you interrupt the "autoboot" process, you can issue a variety of commands. The interface to PDC commands is called the Boot Console Handler (BCH). This is sometimes a point of confusion; that is, are we issuing PDC commands or BCH commands? The commands are normally described as PDC commands, and the interface through which you execute them is the BCH. ISL The Initial System Loader is run after PDC. You would normally just run an "autoboot" sequence from ISL; however, you can run a number of commands from the ISL prompt. hpux The hpux utility manages loading the HP-UX kernel and gives control to the kernel.
ISL can have hpux run an "autoexecute" file, or commands can be given interactively. In most situations, you would just want to automatically boot the system; however, I cover some of the hpux commands you can execute. This is sometimes called the Secondary System Loader (SSL). Note 2: ------HP-UX Normal Boot The bootstrap process involves the execution of three software components: pdc isl hpux - pdc Automatic boot processes on various HP-UX systems follow similar general sequences. When power is applied to the HP-UX system processor, or the system Reset button is pressed, the firmware processor-dependent code (pdc) is executed to verify hardware and general system integrity. After checking the hardware, pdc gives the user the option to override the autoboot sequence by pressing the Esc key. A message resembling the following usually appears on the console. (c) Copyright. Hewlett-Packard Company. 1994. All rights reserved. PDC ROM rev. 130.0 32 MB of memory configured and tested. Selecting a system to boot. To stop selection process, press and hold the ESCAPE key... If no keyboard activity is detected, pdc commences the autoboot sequence by loading isl and transferring control to it. - isl The initial system loader (isl) implements the operating-system-independent portion of the bootstrap process. It is loaded and executed after self-test and initialization have completed successfully. Typically, when control is transferred to isl, an autoboot sequence takes place. An autoboot sequence allows a complete bootstrap operation to occur with no intervention from an operator. While an autoboot sequence occurs, isl finds and executes the autoexecute file which requests that hpux be run with appropriate arguments. Messages similar to the following are displayed by isl on the console:
Booting from: scsi.6 HP 2213A Hard booted. ISL Revision A.00.09 March 27, 1990 ISL booting hpux boot disk(;0)/stand/vmunix - hpux hpux, the secondary system loader, then announces the operation it is performing, in this case the boot operation, the device file from which the load image comes, and the TEXT size, DATA size, BSS size, and start address of the load image, as shown below, before control is passed to the image. Booting disk(scsi.6;0)/stand/vmunix 966616+397312+409688 start 0x6c50 Finally, the loaded image displays numerous configuration and status messages, and passes control to the init process. - Single-user Boot A single-user boot in HP-UX is sometimes referred to as an interactive boot or attended mode boot. Pressing the Escape key at the boot banner on an older Series 700 workstation halts the automatic boot sequence, puts you into attended mode, and displays the Boot Console User Interface main menu, a sample of which is below. Selecting a system to boot. To stop selection process, press and hold the ESCAPE key. Selection process stopped. Searching for Potential Boot Devices. To terminate search, press and hold the ESCAPE key. Device Selection Device Path Device Type ------------------------------------------------------------P0 scsi.6.0 QUANTUM PD210S P1 scsi.1.0 HP 2213A P2 lan.ffffff-ffffff.f.f hpfoobar b) s) a) x)
Boot from specified device Search for bootable devices Enter Boot Administration mode Exit and continue boot sequence Select from menu:
In this case the system automatically searches the SCSI, LAN, and EISA interfaces for all potential boot devices -devices for which boot I/O code (IODC) exists. The key to booting to single-user mode is first to boot to ISL using the b) option. The ISL is the program that actually controls the loading of
the operating system. To do this using the above as an example, you would type the following at the Select from menu: prompt: Select from menu: b p0 isl This tells the system to boot to the ISL using the SCSI drive at address 6 (since the device path of P0 is scsi.6.0). After displaying a few messages, the system then produces the ISL> prompt. Pressing the Escape key at the boot banner on newer Series 700 machines produces the Boot Administration Utility, as shown below. Command Description ----------------Auto [boot|search] [on|off] Display or set auto flag Boot [pri|alt|scsi.addr][isl] Boot from primary, alt or SCSI Boot lan[.lan_addr][install][isl] Boot from LAN Chassis [on|off] Enable chassis code Diagnostic [on|off] Enable/disable diag boot mode Fastboot [on|off] Display or set fast boot flag Help Display the command menu Information Display system information LanAddress Display LAN station addresses Monitor [type] Select monitor type Path [pri|alt] [lan.id|SCSI.addr] Change boot path Pim [hpmc|toc|lpmc] Display PIM info Search [ipl] [scsi|lan [install]] Display potential boot devices Secure [on|off] Display or set security mode ----------------------------------------------------------------BOOT_ADMIN> To display bootable devices with this menu you have to execute the Search command at the BOOT_ADMIN> prompt: BOOT_ADMIN> search Searching for potential boot device. This may take several minutes. To discontinue, press ESCAPE. Device Path -------------scsi.6.0 scsi.3.0 scsi.2.0
Device Type --------------HP C2247 HP HP35450A Toshiba CD-ROM
BOOT_ADMIN> To boot to ISL from the disk at device path scsi.6.0 type the following: BOOT_ADMIN>boot scsi.6.0 isl Once you get the ISL prompt you can run the hpux utility to boot the kernel to single-user mode:
ISL>hpux -is Note: the following can also be used; ISL>hpux -is -lq (;0)/stand/vmunix This essentially tells hpux to load the kernel (/stand/vmunix) into single-user mode (-is) off the SCSI disk drive containing the kernel. The -is option says to pass the string s to the init process (i), and the command init s puts the system in single-user mode. In fact, you will see something similar to the following after typing the above command: Boot : disk(scsi.6;0)/stand/vmunix 966616+397312+409688 start 0x6c50 Kernel Startup Messages Omitted INIT: Overriding default level with level 's' INIT: SINGLE USER MODE WARNING: YOU ARE SUPERUSER!! # - Startup Beginning with HP�UX 10 /etc/inittab calls /sbin/rc, which in turn calls execution scripts to start subsystems. This approach follows the OSF/1 industry standard and has been adopted by Sun, SGI, and other vendors. There are four components to this method of startup and shutdown: /sbin/rc, execution scripts, configuration variable scripts, and link files. /sbin/rc This script invokes execution scripts based on run levels. It is also known as the startup and shutdown sequencer script. Execution scripts These scripts start up and shut down various subsystems and are found in the /sbin/init.d directory. /sbin/rc invokes each execution script with one of four arguments, indicating the "mode": "start" Bring "start_msg" Report what "stop" Bring "stop_msg" Report what
the the the the
subsystem up start action will do subsystem down stop action will do
These scripts are designed never to be modified. Instead, they are customized by sourcing in configuration files found in the /etc/rc.config.d directory. These configuration files contain variables that you can set. For example, in the configuration file /etc/rc.config.d/netconf you can specify routing tables by setting variables like these:
ROUTE_DESTINATION[0]="default" ROUTE_GATEWAY[0]="gateway_address" ROUTE_COUNT[0]="1" The execution script /sbin/init.d/net sources these and other network-related variables when it runs upon system startup. More on configuration files is described below. Upon startup a checklist similar to the one below will appear based upon the exit value of each of the execution scripts. HP-UX Startup in progress ----------------------------------Mount file systems..............................[ OK ] Setting hostname................................[ OK ] Set privilege group.............................[ OK ] Display date...................................[FAIL]* Enable auxiliary swap space....................[ N/A ] Start syncer daemon.............................[ OK ] Configure LAN interfaces........................[ OK ] Start Software Distributor agent daemo..........[ OK ] The execution scripts have the following exit values: 0 Script exited without error. This causes the status OK to appear in the checklist. 1 Script encountered errors. This causes the status FAIL to appear in the checklist. 2 Script was skipped due to overriding control variables from /etc/rc.config.d files or for other reasons, and did not actually do anything. This causes the status N/A to appear in the checklist. 3 Script executed normally and requires an immediate system reboot for the changes to take effect. (NOTE: Reserved for key system components). Configuration variable scripts Configuration variable scripts are designed to customize the execution scripts. This goal here is to separate startup files from configuration files so that upgrading your system does not overwrite its configuration. These scripts are written for the POSIX shell (/usr/bin/sh or /sbin/sh), and not the Bourne shell, ksh, or csh. In some cases, these files must also be read, and possibly modified by other scripts or the SAM program. For this reason, each variable definition must appear on a separate line, in the syntax: variable=value No trailing comments may appear on a variable definition line. Comment statements must be on separate lines, with the "#" comment character in column 1. An example of the required syntax for configuration files is given below: # Cron configuration. See cron(1m) # # CRON: Set to 1 to start cron daemon # CRON=1
Both the execution scripts and the configuration files are named after the subsystem they control. For example, the /sbin/init.d/cron execution script controls the cron daemon, and it is customized by the /etc/rc.config.d/cron configuration variable script. Link Files These files control the order in which execution scripts run. The /sbin/rc#.d (where # is a run-level) directories are startup and shutdown sequencer directories. They contain only symbolic links to the execution scripts in /sbin/init.d that are executed by /sbin/rc on transition to a specific run level. For example, the /sbin/rc3.d directory contains symbolic links to scripts that are executed when entering run level 3. These directories contain two types of link files: start links and kill links. Start links have names beginning with the capital letter S and are invoked with the start argument at system boot time or on transition to a higher run level. Kill links have names beginning with the capital letter K and are invoked with the stop argument at system shutdown time, or when moving to a lower run level. Further, all link files in a sequencer directory are numbered to ensure a particular execution sequence. Each script has, as part of its name, a three-digit sequence number. This, in combination with the start and kill notation, provides all the information necessary to properly start up and shut down a system. The table below shows some samples from the run-level directories. (The sequence numbers shown are only for example and may not accurately represent your system.) /sbin/rc0.d /sbin/rc1.d /sbin/rc2.d /sbinrc3.d K480syncer S100hfsmount S340net S000nfs.server K800killall S320hostname S500inetd K900hfsmount S440savecore S540sendmail S500swapstart S610rbootd S520syncer S720lp S730cron K270cron K280lp K900nfs.server K390rbootd K460sendmail K500inetd K660net Because each script in /sbin/init.d performs both the startup and shutdown functions, each will have two links pointing towards the script from /sbin/rc*.d; one for the start action and one for the stop action. Run Levels and /sbin/rc In previous HP-UX releases, /etc/rc (now /sbin/rc) was run only once. Now it may
run several times during the execution of a system, sequencing the execution scripts when moving between run levels. However, only the subsystems configured for execution, through configuration variables in /etc/rc.config.d, are started or stopped when transitioning the run levels. /sbin/rc sequences the startup and shutdown scripts in the appropriate sequencer directories in lexicographical order. Upon transition from a lower to a higher run level, the start scripts for the new run level and all intermediate levels between the old and new level are executed. Upon transition from a higher to a lower run level, the kill scripts for the new run level and all intermediate levels between the old and new level are executed. When a system is booted to a particular run level, it will execute startup scripts for all run levels up to and including the specified level (except run level 0). For example, if booting to run level 4, /sbin/rc looks at the old run level (S) and the new run level (4) and executes all start scripts in states 1, 2, 3, and 4. Within each level, the start scripts are sorted lexicographically and executed in that order. Each level is sorted and executed separately to ensure that the lower level subsystems are started before the higher level subsystems. Consequently, when shutting down a system, the reverse takes place. The kill scripts are executed in lexicographical order starting at the highest run level and working down, as to stop the subsystems in the reverse order they were started. As mentioned earlier, the numbering is reversed from the startup order. Example If you want cron to start when entering run level 2, you would modify the configuration variable script /etc/rc.config.d/cron to read as follows: # cron config # # CRON=1 to start CRON=1 This would be necessary because the execution script, /sbin/init.d/cron contains the following: # cron startup # . /etc/rc/config if [ $CRON = 1 ] then /usr/sbin/cron fi cron will start at run level 2 because in /sbin/rc2.d a link exists from S730cron to /sbin/init.d/cron. /sbin/rc will invoke /sbin/init.d/cron with a start argument because the link name
starts with an S.
End Of File =========================================================================== 4. Most important and current AIX, SOLARIS, and Linux fixes: =========================================================================== 4.1 AIX: ======== 4.2 SOLARIS: ============ 4.3 Linux Redhat: =================
================= 5. Oracle en UNIX: ================= (Vanaf hier: Oude tekst. As from here, ignore all text, cause its too old. Its only interresting to Albert) 5.1 Installatie Oracle 8i: -------------------------5.1.1 Operating system dependencies: -----------------------------------Bepaal eerst voor de te gebruiken Oracle versie, welke OS settings en patches nodig zijn. Bijvoorbeeld, bij linux is glibc 2.1.3 nodig bij Oracle versie 8.1.7. Linux is erg kritisch m.b.t. de libraries in combinatie met Oracle. Ook moet er mogelijk shmmax (max size of shared memory segment) en dergelijke parameters worden aangepast. # # # #
sysctl -w kernel.shmmax=100000000 sysctl -w fs.file-max=65536 echo "kernel.shmmax = 100000000" >> /etc/sysctl.conf echo "kernel.shmmax = 2147483648" >> /etc/sysctl.conf
Opmerking: Het onderstaANDe is algemeen, maar is ook afgeleid van een Oracle 8.1.7 installatie op Linux Redhat 6.2
Als de 8.1.7 installatie gedaan wordt is ook nog de Java JDK 1.1.8 nodig. Deze kan gedownload worden van www.blackdown.org Download jdk-1.1.8_v3 jdk118_v3-glibc-2.1.3.tar.bz2 in /usr/local tar xvif jdk118_v3-glibc-2.1.3.tar.bz2 ln -s /usr/local/jdk118_v3 /usr/local/java 5.1.2 Omgevingsvariablelen: --------------------------Zorg er voor dat de juiste oracle variabelen zijn gezet. Op ieder platform zijn dat minimaal: ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE (root voor oracle software) ORACLE_HOME=$ORACLE_BASE/product/8.1.5; export ORACLE_HOME (bepaald de directory waarin de instance software zich bevind) ORACLE_SID=brdb; export ORACLE_SID (bepaald de naam van de huidige instance) ORACLE_TERM=xterm, vt100, ansi of wat ANDers; export ORACLE_TERM ORA_NLSxx=$ORACLE_HOME/ocommon/nls/admin/data; export ORA_NLS (bepaald de nls directory t.b.v. datafiles voor meerdere talen) NLS_LANG="Dutch_The NetherlANDs.WE8ISO8859P1"; export NLS_LANG Dit specificeert de language, territory en characterset t.b.v de client applicaties. LD_LIBRARY_PATH=/u01/app/oracle/product/8.1.7/lib; export LD_LIBRARY_PATH PATH=$ORACLE_HOME/bin:/bin:/user/bin:/usr/sbin:/bin; export PATH plaats deze variabelen in de oracle user profile file: .profile, of .bash_profile etc.. 5.1.3 OFA directory structuur: -----------------------------Hou je aan OFA. Een voorbeeld voor database PROD: /u01/app/oracle/product/8.1.6 /u01/app/oracle/admin/PROD /u01/app/oracle/admin/PROD/pfile /u01/app/oracle/admin/PROD/adhoc /u01/app/oracle/admin/PROD/bdump /u01/app/oracle/admin/PROD/udump /u01/app/oracle/admin/PROD/adump /u01/app/oracle/admin/PROD/cdump /u01/app/oracle/admin/PROD/create
/u02/oradata/PROD /u03/oradata/PROD /u04/oradata/PROD etc..
5.1.4 Users en groups: ---------------------Als je met OS verificatie wilt werken, moet in de init.ora gezet zijn: remote_login_passwordfile=none (passwordfile authentication via exlusive) Benodigde groups in UNIX: group dba. Deze moet voorkomen in de /etc/group file vaak is ook nog nodig de group oinstall groupadd dba groupadd oinstall groupadd oper Maak nu user oracle aan: adduser -g oinstall -G dba -d /home/oracle oracle 5.1.5 mount points en disks: ---------------------------maak de mount points: mkdir mkdir mkdir mkdir
/opt/u01 /opt/u02 /opt/u03 /opt/u04
dit moeten voor een produktie omgeving aparte schijven zijn Geef nu ownership van deze mount points aan user oracle en group oinstall chown chown chown chown
-R -R -R -R
oracle:oinstall oracle:oinstall oracle:oinstall oracle:oinstall
directories: drwxr-xr-x files : -rw-r----: -rw-r--r--
/opt/u01 /opt/u02 /opt/u03 /opt/u04 oracle oracle oracle
chmod 644 * chmod u+x filename chmod ug+x filename 5.1.6 test van user oracle: ---------------------------
dba dba dba
log in als user oracle en geef de commANDo's $groups $umask
laat de groups zien (oinstall, dba) laat 022 zien, zoniet zet dan de line umask 022 in het .profile
umask is de default mode van een file of directory wanneer deze aangemaakt wordt. rwxrwxrwx=777 rw-rw-rw-=666 rw-r--r--=644 welke correspondeert met umask 022 Verander nu het .profile of .bash_profile van de user oracle. Plaats de environment variabelen van 9.1 in het profile. log uit en in als user oracle, en test de environment: %env %echo $variablename 5.1.7 Oracle Installer bij 8.1.x op Linux: -----------------------------------------Log in als user oracle. Draai nu oracle installer: Linux: startx cd /usr/local/src/Oracle8iR3 ./runInstaller of Ga naar install/linux op de CD en run runIns.sh Nu volgt een grafische setup. Beantwoord de vragen. Het kan zijn dat de installer vraagt om scripts uit te voeren zoals: orainstRoot.sh en root.sh Om dit uit te voeren: open een nieuw window su root cd $ORACLE_HOME ./orainstRoot.sh
5.2 Automatische start oracle bij system boot: ---------------------------------------------5.2.1 oratab: ------------Inhoud ORATAB in /etc of /var/opt: Voorbeeld:
# $ORACLE_SID:$ORACLE_HOME:[N|Y] # ORCL:/u01/app/oracle/product/8.0.5:Y # De oracle scripts om de database te starten en te stoppen zijn: $ORACLE_HOME/bin/dbstart en dbshut, of startdb en stopdb of wat daarop lijkt. Deze kijken in ORATAB om te zien welke databases gestart moeten worden. 5.2.2 dbstart en dbshut: -----------------------Het script dbstart zal oratab lezen en ook tests doen en om de oracle versie te bepalen. Verder bestaat de kern uit: het starten van sqldba, svrmgrl of sqlplus vervolgens doen we een connect vervolgens geven we het startup commando. Voor dbshut geldt een overeenkomstig verhaal. 5.2.3 init, sysinit, rc: -----------------------Voor een automatische start, voeg nu de juiste entries toe in het /etc/rc2.d/S99dbstart (or equivalent) file: Tijdens het opstarten van Unix worden de scrips in de /etc/rc2.d uitgevoerd die beginnen met een 'S' en in alfabetische volgorde. De Oracle database processen zullen als (een van de) laatste processen worden gestart. Het bestAND S99oracle is gelinkt met deze directory. Inhoud S99oracle: su - oracle -c "/path/to/$ORACLE_HOME/bin/dbstart" su - oracle -c "/path/to/$ORACLE_HOME/bin/lsnrctl start" su - oracle -c "/path/tp/$ORACLE_HOME/bin/namesctl start" (optional)
# Start DB's # Start listener # Start OraNames
Het dbstart script is een standaard Oracle script. Het kijkt in oratab welke sid's op 'Y' staan, en zal deze databases starten. of customized via een customized startdb script: ORACLE_ADMIN=/opt/oracle/admin; export ORACLE_ADMIN su - oracle -c "$ORACLE_ADMIN/bin/startdb WPRD 1>$ORACLE_ADMIN/log/WPRD/startWPRD.$$ 2>&1"
su - oracle -c "$ORACLE_ADMIN/bin/startdb WTST 1>$ORACLE_ADMIN/log/WTST/startWTST.$$ 2>&1" su - oracle -c "$ORACLE_ADMIN/bin/startdb WCUR 1>$ORACLE_ADMIN/log/WCUR/startWCUR.$$ 2>&1"
5.3 Het stoppen van Oracle in unix: ----------------------------------Tijdens het down brengen van Unix (shutdown -i 0) worden de scrips in de directory /etc/rc2.d uitgevoerd die beginnen met een 'K' en in alfabetische volgorde. De Oracle database processen zijn een van de eerste processen die worden afgesloten. Het bestand K10oracle is gelinkt met de /etc/rc2.d/K10oracle # Configuration File: /opt/oracle/admin/bin/K10oracle ORACLE_ADMIN=/opt/oracle/admin; export ORACLE_ADMIN su - oracle -c "$ORACLE_ADMIN/bin/stopdb WPRD 1>$ORACLE_ADMIN/log/WPRD/stopWPRD.$$ 2>&1" su - oracle -c "$ORACLE_ADMIN/bin/stopdb WCUR 1>$ORACLE_ADMIN/log/WCUR/stopWCUR.$$ 2>&1" su - oracle -c "$ORACLE_ADMIN/bin/stopdb WTST 1>$ORACLE_ADMIN/log/WTST/stopWTST.$$ 2>&1" 5.4 startdb en stopdb: ---------------------Startdb [ORACLE_SID] -------------------Dit script is een onderdeel van het script S99Oracle. Dit script heeft 1 parameter, ORACLE_SID # Configuration File: /opt/oracle/admin/bin/startdb # Algemene omgeving zetten . $ORACLE_ADMIN/env/profile ORACLE_SID=$1 echo $ORACLE_SID # Omgeving zetten RDBMS . $ORACLE_ADMIN/env/$ORACLE_SID.env # Het starten van de database sqlplus /nolog /opt/oracle/admin/batches/log/batcheserroroutput.log 2>&1
# Configuration File: /opt/oracle/admin/batches/bin/batches.sh # Door de op de commandline ' BL_TRACE=T ; export BL_TRACE ' worden alle
commando's getoond. case $BL_TRACE in T) set -x ;; esac ORACLE_ADMIN=/opt/oracle/admin; export ORACLE_ADMIN ORACLE_HOME=/opt/oracle/product/8.1.6; export ORACLE_HOME ORACLE_SID=WCUR ; export ORACLE_SID su - oracle -c ". $ORACLE_ADMIN/env/profile ; . $ORACLE_ADMIN/env/$ORACLE_SID.env; cd $ORACLE_ADMIN/batches/bin; sqlplus /NOLOG @$ORACLE_ADMIN/batches/bin/Analyse_WILLOW2K.sql 1> $ORACLE_ADMIN/batches/log/batches$ORACLE_SID.`date +"%y%m%d"` 2>&1" ORACLE_SID=WCON ; export ORACLE_SID su - oracle -c ". $ORACLE_ADMIN/env/profile ; . $ORACLE_ADMIN/env/$ORACLE_SID.env; cd $ORACLE_ADMIN/batches/bin; sqlplus /NOLOG @$ORACLE_ADMIN/batches/bin/Analyse_WILLOW2K.sql 1> $ORACLE_ADMIN/batches/log/batches$ORACLE_SID.`date +"%y%m%d"` 2>&1"
=================== 6. Unix and Sybase: =================== 6.1 How can I start using Sybase? First you need to logon to any of the Solaris machines in the CISE department. Type the following command on the Solaris machine prompt: % source /local/etc/sybase.cshrc Then you will have to logon to Sybase using the following command. %sqsh (or isql) password:
6.2 Startup in UNIX How to start/stop ASE when CPU reboots -------------------------------------------------------------------------------Below is an example of the various files (on Irix) that are needed to start/stop an ASE. The information can easily be extended to any UNIX platform. The idea is to allow as much flexibility to the two classes of administrators who manage the machine:
The System Administrator The Database Administrator Any errors introduced by the DBA will not interfere with the System Administrator's job. With that in mind we have the system startup/shutdown file /etc/init.d/sybase invoking a script defined by the DBA: /usr/sybase/sys.config/{start,stop}.sybase /etc/init.d/sybase On some operating systems this file must be linked to a corresponding entry in /etc/rc.0 and /etc/rc.2 -- see rc0(1M) and rc2(1M) #!/bin/sh # last modified: 10/17/95, sr. # # Make symbolic links so this file will be called during system stop/start. # ln -s /etc/init.d/sybase /etc/rc0.d/K19sybase # ln -s /etc/init.d/sybase /etc/rc2.d/S99sybase # chkconfig -f sybase on # Sybase System-wide configuration files CONFIG=/usr/sybase/sys.config if $IS_ON verbose ; then ECHO=echo VERBOSE=-v else ECHO=: VERBOSE= fi
# For a verbose startup and shutdown # For a quiet startup and shutdown
case "$1" in 'start') if $IS_ON sybase; then if [ -x $CONFIG/start.sybase ]; then $ECHO "starting Sybase servers" /bin/su - sybase -c "$CONFIG/start.sybase $VERBOSE &" else fi fi ;; 'stop')
if $IS_ON sybase; then if [ -x $CONFIG/stop.sybase ]; then $ECHO "stopping Sybase servers" /bin/su - sybase -c "$CONFIG/stop.sybase $VERBOSE &" else fi fi ;;
*) echo "usage: $0 {start|stop}" ;; esac
/usr/sybase/sys.config/{start,stop}.sybase start.sybase #!/bin/sh -a # # Script to start sybase # # NOTE: different versions of sybase exist under /usr/sybase/{version} # # Determine if we need to spew our output if [ "$1" != "spew" ] ; then OUTPUT=">/dev/null 2>&1" else OUTPUT="" fi # 10.0.2 servers HOME=/usr/sybase/10.0.2 cd $HOME # Start the backup server eval install/startserver -f install/RUN_BU_KEPLER_1002_52_01 $OUTPUT # Start the dataservers # Wait two seconds between starts to minimize trauma to CPU server eval install/startserver -f install/RUN_FAC_WWOPR $OUTPUT sleep 2 eval install/startserver -f install/RUN_MAG_LOAD $OUTPUT exit 0 stop.sybase #!/bin/sh # # Script to stop sybase # # Determine if we need to spew our output if [ -z "$1" ] ; then OUTPUT=">/dev/null 2>&1" else OUTPUT="-v" fi eval killall -15 $OUTPUT dataserver backupserver sybmultbuf sleep 2 # if they didn't die, kill 'em now... eval killall -9 $OUTPUT dataserver backupserver sybmultbuf exit 0 If your platform doesn't support killall, it can easily be simulated as follows: #!/bin/sh # # Simple killall simulation... # $1 = signal # $2 = process_name # # # no error checking but assume first parameter is signal... # what ya want for free? :-) # kill -$1 `ps -ef | fgrep $2 | fgrep -v fgrep | awk '{ print $1 }'` (### thats nice ! )
======================= 7. INSTALLING SUNOS: ======================= Installing Sun Solaris 2.8 -------------------------------------------------------------------------------Contents Overview Using Serial Console Connection Starting the Installation Answering the Screen Prompts Post-Installation Tasks -------------------------------------------------------------------------------Overview This article documents installing the 2/02 release of Solaris 8 from CD-ROM. For the purpose of this example, I will be installing Solaris 8 on a Sun Blade 150 with the following configuration: Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard, OpenBoot 4.6 1,792 MB RAM Memory 40 GB IDE Western Digital Hard Drive - (/dev/dsk/c0t0d0) Built-in Ethernet - (eri0) CDROM - (/dev/dsk/c0t1d0) Installing Solaris 8 will require 2 CDs found in the Solaris media kit labeled SOLARIS 8 SOFTWARE - 1 of 2 / 2 of 2. Before starting the installation process, ensure that you have noted the following items: Determine the host name of the system you are installing Determine the language and locales you intend to use on the system If you intend to include the system in a network, gather the following information: Host IP address Subnet mask Type of name service (DNS, NIS, or NIS+, for example) Domain name Host name of server Host IP address of the name server Using Serial / Console Connection For a complete discussion of connecting to a Sun serial console from Linux, see my article "Using Serial Consoles - (Sun Sparcs)". For this particular installation, I will NOT be using a VGA monitor connected to the built-in frame-buffer (video card). The installation will be done using the serial port of the Sun Blade as a console.
A serial cable (null modem) will be connected from the serial port of a Linux machine to the serial port of the Sun Blade. Keep in mind that you will not be able to make use of the serial console of the Sun Blade if it was booted with the keyboard/mouse plugged in. In order to make use of the serial console, you will need to disconnect the keyboard/mouse and reboot the Sun server. On the Sun Blade 100/150, if the keyboard/mouse are plugged in during the boot phase, all console output will be redirected to the VGA console. From the Linux machine, you can use a program called minicom. Start it up with the command "minicom". Press "Ctrl-A Z" to get to the main menu. Press "o" to configure minicom. Go to "Serial port setup" and make sure that you are set to the correct "Serial Device" and that the speed on line E matches the speed of the serial console you are connecting to. (In most cases with Sun, this is 9600.) Here are the settings I made when using Serial A / COM1 port on the Linux machine: +-----------------------------------------------------------------------+ | A Serial Device : /dev/ttyS0 | | B - Lockfile Location : /var/lock | | C Callin Program : | | D - Callout Program : | | E Bps/Par/Bits : 9600 8N1 | | F - Hardware Flow Control : Yes | | G - Software Flow Control : No | | | | Change which setting? | +-----------------------------------------------------------------------+ After making all necessary changes, hit the ESC key to go back to the "configurations" menu. Now go to "Modem and dialing". Change the "Init string" to "~^M~". Save the settings (as dflt), and then restart Minicom. You should now see a console login prompt. [root@bertha1 root]# minicom Welcome to minicom 1.83.1 OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n Compiled on Aug 28 2001, 15:09:33. Press CTRL-A Z for help on special keys alex console login: root Password: Last login: Tue Nov 4 18:55:41 on console Nov 7 12:17:24 alex login: ROOT LOGIN /dev/console Sun Microsystems Inc. SunOS 5.8 Generic Patch # # init 0 INIT: New run level: 0 The system is coming down. Please wait. System services are now being stopped. Print services stopped.
October 2001
Nov 7 12:17:38 alex syslogd: going down on signal 15 The system is down. syncing file systems... done Program terminated ok Starting the Installation The installation process starts at the ok prompt. The previous section of this document provides the steps required to not only gain access to the console port of the Sun SPARC server, but also how to get the server to an ok prompt. If when logging you, the machine is already booted (you have console login like the following: "alex console login:") you will need to bring the machine to its EEPROM (ok prompt) by initiating init 0 like in the Using Serial / Console Connection section above. The first step in installing Solaris 8 it to boot the machine from Disk 1 of the SOLARIS 8 SOFTWARE CDs. You will need to get the machine to the ok prompt. You can do this by shutting the system down using init 0. Once at the ok prompt, type in boot cdrom. (Or in some cases, you can use reboot cdrom). From here, the installation program prompts you for system configuration information that is needed to complete the installation. NOTE: If you were performing a network installation, you would type: ok boot net. In almost all cases, you will be installing the Solaris 8 software on a new system where it will not be necessary to preserve any data already on the hard drive. Using this assumption, I will partition the single 40 GB IDE hard drive in the system. Answering the Screen Prompts Let's start the installation process! Put the SOLARIS 8 SOFTWARE (Disk 1 of 2) in the CDROM tray and boot to it: ok boot cdrom Resetting ... Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.6, 1792 MB memory installed, Serial #52928138. Ethernet address 0:3:ba:27:9e:8a, Host ID: 83279e8a. Rebooting with command: boot cdrom Boot device: /pci@1f,0/ide@d/cdrom@1,0:f File and args: SunOS Release 5.8 Version Generic_108528-13 64-bit Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved. The boot process may take several minutes to complete, but once done, you will start answering a series of prompts. The following section will walk you through many of the screen prompts from the installation.
The first three prompts are from the command line interface (CLI) and are used to specify the language, locale and terminal. Use English for both Language and Locale. As for a terminal setting, I commonly telnet to a Linux server (that is connected from the serial port of the Linux server to the serial port of the Sun machine). From the Linux server, I use "minicom" to connect from the Linux server to the Sun server. The best terminal for this type of installation is "DEC VT100": Language : English Locale : English What type of terminal are you using? : 3) DEC VT100 NOTE: You should be able to use a terminal type of "DEC VT100" or "X Terminal Emulator (xterms)". NOTE: Further installation through the terminal requires responses to the selections through ESC and function keys and space bar, which are mentioned on the installation screen. Many of the screens to follow will ask you about networking information. When asked if the system will be connected to a network, answer Yes. NOTE: Many of the screens should be easy to complete except for the "Names Services" section. In almost all cases, you will want to use DNS naming services, but if your machine is not currently configured within DNS, this section will fail and no information entered about Names Services will be stored and configured. If this is the case, you will need to select None under the Names Services section. The network configuration will then need to be completed after the installation process by updating certain network files on the local hard drive. This will be documented in the "Post Installation Procedures" of this document.
-------------------------------------------------------------------------------Screen 1 : The Solaris Installation Program This is the Solaris Installation Welcome screen. Hit ESC - F2 to continue Screen 2 : Identify This System This screen informs you about how you will need to identify the computer as it applies to network connectivity. Hit ESC - F2 to continue
Screen 3 : Network Connectivity Networked --------[X] Yes [ ] No Hit ESC - F2 to continue Screen 4 : DHCP Use DHCP -------[ ] Yes [X] No Hit ESC - F2 to continue Screen 5 : Host Name Host name: alex Hit ESC - F2 to continue Screen 6 : IP Address Host name: 192.168.1.102 Hit ESC - F2 to continue Screen 7 : Subnets System part of a subnet ----------------------[X] Yes [ ] No Hit ESC - F2 to continue Screen 8 : Netmask Netmask: 255.255.255.0 Hit ESC - F2 to continue Screen 9 : IPv6 Enable IPv6 ----------[ ] Yes [X] No Hit ESC - F2 to continue Screen 10 : Confirm Information This is a confirmation screen. Verify all data is correct.
Hit ESC - F2 to continue Screen 11 : Configure Security Policy Configure Kerberos Security --------------------------[ ] Yes [X] No Hit ESC - F2 to continue Screen 12 : Confirm Information This is a confirmation screen. Verify all data is correct. Hit ESC - F2 to continue Screen 13 : Name Service Name service -----------[ ] NIS+ [ ] NIS [X] DNS [ ] LDAP [ ] None Hit ESC - F2 to continue Screen 14 : Domain Name Host name: idevelopment.info Hit ESC - F2 to continue Screen 15 : DNS Server Addresses Server's IP address: 63.67.120.18 Server's IP address: 63.67.120.23 Server's IP address: Hit ESC - F2 to continue Screen 16 : DNS Search List Search domain: Search domain: Search domain: Search domain: Search domain: Search domain: Hit ESC - F2 to continue Screen 17 : Confirm Information
This is a confirmation screen. Verify all data is correct. Hit ESC - F2 to continue Screen 18 : Time Zone Regions ------[ ] Asia, Western [ ] Australia / New Zealand [ ] Canada [ ] Europe [ ] Mexico [ ] South America [X] United States [ ] other - offset from GMT [ ] other - specify time zone file Hit ESC - F2 to continue Screen 19 : Time Zone Time zones ---------[X] Eastern [ ] Central [ ] Mountain [ ] Pacific [ ] East-Indiana [ ] Arizona [ ] Michigan [ ] Samoa [ ] Alaska [ ] Aleutian [ ] Hawaii Hit ESC - F2 to continue Screen 20 : Date and Time Date and time: YYYY-MM-DD HH:MM Year (4 digits) :
Screen 21 : Confirm Information This is a confirmation screen. Verify all data is correct. Hit ESC - F2 to continue
Screen 22 : Solaris Interactive Installation This screen recognizes if a previous version of Solaris is installed and whether you would like to upgrade or not. Always select the install option (F4_Initial). Hit ESC - F4 to continue Screen 23 : Solaris Interactive Installation There are two ways to install your Solaris software: "Standard" or "Flash". Choose the "Standard" method (Esc-2_Standard). Hit ESC - F2 to continue Screen 24 : Time Zone Select the geographic regions for which support should be installed. -------------------------------------------------------------------> [ ] Asia > [ ] Eastern Europe > [ ] Middle East > [ ] Central America > [ ] South America > [ ] Northern Europe > [ ] Southern Europe > [ ] Central Europe V [/] North America [ ] Canada-English (ISO8859-1) [ ] Canada-French (ISO8859-1) [ ] French [ ] Mexico (ISO8859-1) [X] U.S.A. (en_US.ISO8859-1) [ ] Australasia > [ ] Western Europe > [ ] Northern Africa Hit ESC - F2 to continue Screen 25 : Select Software Select the Solaris software to install on the system. ----------------------------------------------------[ ] Entire Distribution plus OEM support 64-bit 1432.00 MB [X] Entire Distribution 64-bit ................. 1401.00 MB [ ] Developer System Support 64-bit ............ 1350.00 MB [ ] End User System Support 64-bit ............. 932.00 MB [ ] Core System Support 64-bit ................. 396.00 MB Hit ESC - F2 to continue Screen 26 : Select Disks You must select the disks for installing Solaris software. If there are several disks available, I always install the Solaris software on the boot disk c0t0d0.
---------------------------------------------------------Disk Device (Size) Available Space ============================================= [X] c0t0d0 (14592 MB) boot disk 14592 MB (F4 to edit) Total Selected: Suggested Minimum:
14592 MB 974 MB
-------------------------------------------------------------------------------I generally select ESC - F4 to edit the c0t0d0 disk to ensure that the root directory is going to be located on this disk. ---------------------------------------------------------On this screen you can select the disk for installing the root (/) file system of the Solaris software. Original Boot Device : c0t0d0 Disk ============================== [X] c0t0d0 (F4 to select boot device)
-------------------------------------------------------------------------------On this screen, I typically select ESC - F4 to select boot device to ensure the root file system will be located on slice zero, c0t0d0s0. ---------------------------------------------------------On this screen you can select the specific slice for the root (/) file system. If you choose Any of the Above, the Solaris installation program will choose a slice for you. Original Boot Device : c0t0d0s0 [X] c0t0d0s0 [ ] c0t0d0s1 [ ] c0t0d0s2 [ ] c0t0d0s3 [ ] c0t0d0s4 [ ] c0t0d0s5 [ ] c0t0d0s6 [ ] c0t0d0s7 [ ] Any of the Above Hit ESC - F2 to after selecting Disk Slice --------------------------------------------------------------------------------
Hit ESC - F2 to continue with your Boot Disk selection -------------------------------------------------------------------------------Screen 27 : Reconfigure EEPROM? Do you want to update the system's hardware (EEPROM) to always boot from c0t0d0? Hit ESC - F2 to Reconfigure EEPROM and Continue Screen 28 : Preserve Data? Do you want to preserve existing data? At least one of the disks you've selected for installing Solaris software has file systems or unnamed slices that you may want to save. Hit ESC - F2 to continue Screen 29 : Automatically Layout File Systems? Do you want to use auto-layout to automatically layout file systems? Manually laying out file systems requires advanced system administration skills. I typically perform an "Auto" File System Layout (F2_Auto Layout). Hit ESC - F2 to Perform Auto Layout. Screen 30 : Automatically Layout File Systems On this screen you must select all the file systems you want auto-layout to create, or accept the default file systems shown. File Systems for Auto-layout ======================================== [X] / [ ] /opt [ ] /usr [ ] /usr/openwin [ ] /var [X] swap Hit ESC - F2 to continue Screen 31 : File System and Disk Layout The summary below is your current file system and disk layout, based on the information you've supplied. NOTE: If you choose to customize, you should understand file systems, their intended purpose on the disk, and how changing them may affect the operation of the system.
File system/Mount point Disk/Slice Size ============================================================= / c0t0d0s0 1338 MB swap c0t0d0s1 296 MB overlap c0t0d0s2 38162 MB /export/home c0t0d0s7 36526 MB
-------------------------------------------------------------------------------I generally select ESC - F4 (F4_Customize) to edit the partitions for disk c0t0d0. If this is a workstation, I make only three partitions: / : I often get the sizes for the individual filesystems (/usr, /opt, and /var) incorrect. This is one reason I typically create only one partition as / that will be used for the entire system (minus swap space). In most cases, I will be installing addition disks for large applications like the Oracle RDBMS, Oracle Application Server, or other J2EE application servers. overlap : The overlap partition represents entire disk and is slice s2 of the disk. swap : The swap partition size depends on the size of RAM in the system. If you are not sure of its size, make it double the amount of RAM in your system. I typically like to make swap 1GB. -----------------------------------------------Boot Device: c0t0d0s0 ================================================= Slice Mount Point Size (MB) 0 / 37136 1 swap 1025 2 overlap 38162 3 0 4 0 5 0 6 0 7 0 ================================================= Capacity: 38162 MB Allocated: 38161 MB Rounding Error: 1 MB Free: 0 MB Hit ESC - F2 to continue -------------------------------------------------------------------------------This is what the File System and Disk Layout screen looks like now. File system/Mount point Disk/Slice Size ============================================================= / c0t0d0s0 37136 MB swap c0t0d0s1 1025 MB
overlap Hit ESC - F2 to continue
c0t0d0s2
38162 MB
Screen 32 : Mount Remote File Systems? Do you want to mount software from a remote file server? This may be necessary if you had to remove software because of disk space problems. Hit ESC - F2 to continue Screen 33 : Confirm Information This is a confirmation screen. Verify all data is correct. Hit ESC - F2 to continue Screen 34 : Reboot After Installation? After Solaris software is installed, the system must be rebooted. You can choose to have the system automatically reboot, or you can choose to manually reboot the system if you want to run scripts or do other customizations before the reboot. You can manually reboot a system by using the reboot(1M) command. [X] Auto Reboot [ ] Manual Reboot Hit ESC - F2 to Begin the Installation Screen 34 : Installation Progress Afterwards it starts configuring disk making partitions and installing software indicating the progress. Preparing system for Solaris install Configuring disk (c0t0d0) - Creating Solaris disk label (VTOC) Creating and checking UFS file systems - Creating / (c0t0d0s0) ================================================================== MBytes Installed: 392.08 MBytes Remaining: 428.09 Installing: JavaVM run time environment *************** | | |
|
|
|
0 20 40 60 80 100 After the installation is complete it customizes system files, devices, and logs.
The system then reboots or asks you to reboot depending upon the choice selected earlier in the Reboot After Installation? screen. Screen 36 : Create a root Password On this screen you can create a root password. A root password can contain any number of characters, but only the first eight characters in the password are significant. (For example, if you create `a1b2c3d4e5f6' as your root password, you can use `a1b2c3d4' to gain root access.) You will be prompted to type the root password twice; for security, the password will not be displayed on the screen as you type it. > If you do not want a root password, press RETURN twice. Root password: Enter Your root Password and Press Return to continue. Screen 37 : Solaris 8 Software 2 of 2 Please specify the media from which you will install Solaris 8 Software 2 of 2 (2/02 SPARC Platform Edition). Alternatively, choose the selection for "Skip" to skip this disc and go on to the next one. Media: 1. CD/DVD 2. Network File System 3. Skip Media [1]: 1 Screen 38 : Insert the CD/DVD for Solaris 8 Software 2 of 2 Please insert the CD/DVD for Solaris 8 Software 2 of 2 (2/02 SPARC Platform Edition). After you insert the disc, please press Enter. Enter S to skip this disc and go on to the next one. To select a different media, enter B to go Back. [] Screen 39 : Solaris 8 packages (part 2) After hitting in the previous screen, the installation will continue installing the Solaris software (part 2)
Reading Solaris 8 Software 2 of 2 (2/02 SPARC Platform Edition).... \ Launching installer for Solaris 8 Software 2 of 2 (2/02 SPARC Platform Edition). Please Wait... Installing Solaris 8 packages (part 2) |-1%--------------25%-----------------50%-----------------75%--------------100%| Installation details: 1.
Product Solaris 8 packages (part 2)
2.
Done
Result Installed
More Info Available
Enter the number corresponding to the desired selection for more information, or enter 2 to continue [2]:2 Post-Installation Tasks After successfully installing the Solaris operating platform software, there may be several tasks that need to be performed depending on your configuration. Networking: If you will be using networking database files for your TCP/IP networking configuration, several files will need to be manually created and/or modified. I provided a step-by-step document on how to manually configure TCP/IP networking files to manually enable TCP/IP networking using files: Configuring TCP/IP on Solaris - TCP/IP Configuration Files - (Quick Config Guide) Solaris 8 Patch Cluster: It is advisable to install the latest Sun Solaris Patch Cluster to ensure a stable operating environment. I provided a step-by-step document on how to download and install the latest Sun Solaris 8 Patch Cluster: Patching Sun Solaris 2.8
======================= 8. RAID Volumes on SUN: =======================
8.1 SCSI, DISKS AND RAID: ========================= 8.1.1 General -------------
SCSI HBA-----------SCSI ID 5----Lun 0 | |--Lun 1 | |-- .... | |--Lun 7 | |----SCSI ID 6----Lun 0 | |--... | |----SCSI ID 0----...
Primary CDROM drive Slave CDROM drive Slave CDROM drive Primary CDROM
Every SCSI Device can have 8 lun numbers from 0-7 A logical unit number (LUN) is a unique identifier used on a SCSI bus that enables it to differentiate between up to eight separate devices (each of which is a logical unit). Each LUN is a unique number that identifies a specific logical unit, which may be an disk. A SCSI (Small System Computer Interface) is a parallel interface, that can have up to eight devices all attached through a single cable; the cable and the host (computer) adapter make up the SCSI bus. The bus allows the interchange of information between devices independently of the host. In the SCSI program, each device is assigned a unique number, which is either a number between 0 and 7 for an 8-bit (narrow) bus, or between 8 and 16 for a 16-bit (wide) bus. The devices that request input/output (I/O) operations are initiators and the devices that perform these operations are targets. Each target has the capacity to connect up to eight additional devices through its own controller; these devices are the logical units, each of which is assigned a unique number for identification to the SCSI controller for command processing. Short for logical unit number, a unique identifier used on a SCSI bus to distinguish between devices that share the same bus. SCSI is a parallel interface that allows up to 16 devices to be connected along a single cable. The cable and the host adapter form the SCSI bus, and this operates independently of the rest of the computer. Each of the eight devices is given a unique address by the SCSI BIOS, ranging from 0 to 7 for an 8-bit bus or 0 to 15 for a 16-bit bus. Devices that request I/O processes are called initiators. Targets are devices that perform operations requested by initiators. Each target can accommodate up to eight other devices, known as logical units, and each is assigned an LUN. Commands that are sent to the SCSI controller identify devices based on their LUNs. So we might have a situation as: - Drive C: is standard, Drive D: is SCSI Target 0 LUN 0. - Drive C: is SCSI Target 0 LUN 0, Drive D:, if installed,is SCSI Target 0 LUN 1 or Target 1 LUN 0.
8.1.2 single-initiator ---------------------A single-initiator SCSI bus has only one node connected to it, and provides host isolation and better performance than a multi-initiator bus. Single-initiator buses ensure that each node is protected from disruptions due to the workload, initialization, or repair of the other nodes. When using a single- or dual-controller RAID array that has multiple host ports and provides simultaneous access to all the shared logical units from the host ports on the storage enclosure, the setup of the single-initiator SCSI buses to connect each cluster node to the RAID array is possible. If a logical unit can fail over from one controller to the other, the process must be transparent to the operating system. Note that some RAID controllers restrict a set of disks to a specific controller or port. In this case, single-initiator bus setups are not possible. To set up a single-initiator SCSI bus configuration, perform the following steps: Enable the onboard termination for each host bus adapter. Enable the termination for each RAID controller. Use the appropriate SCSI cable to connect each host bus adapter to the storage enclosure. Setting host bus adapter termination is done in the adapter BIOS utility during system boot. To set RAID controller termination, refer to the vendor documentation. --------SI SCSI bus -------------| T|--------------| HBA | |HBA | | ----------|T | | | | | ---------------------| | | | ------------------| T T | |Storage Enclosure| ------------------Recommended in Linux an Sun clusters. 8.1.3 Multi Initiator SCSI --------------------------
Multi Initiator SCSI configurations are configurations with two SCSI host adapter boards connect to a single SCSI bus like in the following example: ______________ ______________ | System 1 | SCSI ___________ ___________ SCSI | System 2 | |(SCSI Adapter)|--------|SCSI Device|--|SCSI Device|--------|(SCSI Adapter)| |______________| Bus |___________| |___________| Bus |______________|
--------SI SCSI bus | T|-------------------------------| | | |HBA | | | | | --------| ------------------| T | |Storage Enclosure| -------------------
-------------|T | | | |HBA | | | ---------------
Not recommended for Linux or Solaris clusters.
8.2 Installing an A1000 on Solaris8: ==================================== contributed by Jim Shumpert, edited by Doug Hughes Here is what you need to do to install An A1000 on Solaris8. The order is very particular. Much of this is by way of example. The particulars of your site will differ. Substitute the latest version of Raid Manager if there is a newer one available. Also, the exact firmware versions will change over time, so, do not take this too literally. -Install Solaris8 -Install required OS patches (If you have an Ultra60, install 106455-09 or better - firmware patch - before proceeding) - Install Raid Manager 6.22 (RM 6.22) or better. # pkgadd -d . SUNWosar SUNWosafw SUNWosamn SUNWosau See also section 6.2 (contributed by Greg Whalin) Check /etc/osa/mnf and make sure that your controller name does NOT contain any periods. Change them to a _ instead. The RM software does not have any clue how to deal with a period. This kept me screwed up for quite a while. /etc/osa >more mnf rebv-pegasu_001~1T94516518~ 0 1 2~~~0~3~~c1t0d0~~ Install patches 109571-02 (for Solaris8 FCS) and 108553-07 (or newer)
(for Solaris7/2.6 patch 108834-07 or newer) [ NOTE: 112125-01 and 112126-01 or better for RM 6.22.1] # patchadd 109571-02 # patchadd 108553-02 Boot -r # touch /reconfigure # reboot -- -r Upgrade the firmware on the A1000 /usr/lib/osa/bin/raidutil -c c1t0d0 -i LUNs found on c1t0d0. LUN 0 RAID 0 0 MB Vendor ID Symbios ProductID StorEDGE A1000 Product Revision 0205 Boot Level 02.05.01.00 Boot Level Date 12/02/97 Firmware Level 02.05.02.11 Firmware Date 04/09/98 raidutil succeeded! Find lowest number firmware upgrade that is still greater than the firmware that is installed on your A1000. For the above example, with patch 108553, upgrade to 2.05.06.32 (do this first, VERY IMPORTANT!) # cd /usr/lib/osa/fw # /usr/lib/osa/bin/fwutil 02050632.bwd c1t0d0 # /usr/lib/osa/bin/fwutil 02050632.apd c1t0d0 Upgrade to the each next higher firmware in succession until you get to the most recent version. It is recommend that you do the upgrades in order. For this example, Upgrade to 3.01.02.33/5 # /usr/lib/osa/bin/fwutil 03010233.bwd c1t0d0 # /usr/lib/osa/bin/fwutil 03010235.apd c1t0d0 Upgrade to 03.01.03.60 (or better) # /usr/lib/osa/bin/fwutil 03010304.bwd c1t0d0 # /usr/lib/osa/bin/fwutil 03010360.apd c1t0d0 Check that the array has the correct versions: # /usr/lib/osa/bin/raidutil -c c1t0d0 -i LUNs found on c1t0d0. LUN 0 RAID 0 0 MB Vendor ID ProductID Product Revision Boot Level Boot Level Date Firmware Level
Symbios StorEDGE A1000 0301 03.01.03.00 10/22/99 03.01.03.54
Firmware Date 03/30/00 raidutil succeeded! Check to make sure that the RAID is attached and looks good # /usr/lib/osa/bin/drivutil -i c1t0d0 Drive Information for satl-adb1_a_001 Location
Capacity (MB) [1,0] 17274 3BT0RHKA00 [2,0] 17274 3BT0QZM600 [1,1] 17274 3BT0QLRG00 [2,1] 17274 3BT0RHM400 [1,2] 17274 3BT0R9FZ00 [2,2] 17274 3BT0R9SZ00 [1,3] 17274 3BT0R9FY00 [2,3] 17274 3BT0QKVR00 [1,4] 17274 3BT0R79X00 [2,4] 17274 3BT0QX8500 [1,5] 17274 3BT0R9JS00 [2,5] 17274 3BT0RCY600
Status
Vendor
Optimal
Product Firmware ID Version SEAGATE ST318404LSUN18G 4207
Optimal
SEAGATE ST318404LSUN18G
4207
Optimal
SEAGATE ST318404LSUN18G
4207
Optimal
SEAGATE ST318404LSUN18G
4207
Optimal
SEAGATE ST318404LSUN18G
4207
Optimal
SEAGATE ST318404LSUN18G
4207
Optimal
SEAGATE ST318404LSUN18G
4207
Optimal
SEAGATE ST318404LSUN18G
4207
Optimal
SEAGATE ST318404LSUN18G
4207
Optimal
SEAGATE ST318404LSUN18G
4207
Optimal
SEAGATE ST318404LSUN18G
4207
Optimal
SEAGATE ST318404LSUN18G
4207
Serial Number
drivutil succeeded! Example: Create 1 large 10-disk RAID 5 configuration (LUN 0) of max size and then create 2 Hot Spare disks # /usr/lib/osa/bin/raidutil -c c1t0d0 -D 0 LUNs found on c1t0d0. LUN 0 RAID 0 0 MB Deleting LUN 0. Press Control C to abort. LUNs successfully deleted raidutil succeeded! # /usr/lib/osa/bin/raidutil -c c1t0d0 -l 5 -n 0 -s 0 -r fast -g 10,20,11,21,12,22,13,23,14,24 No existing LUNs were found on c1t0d0. Capacity available in drive group: 317669184 blocks
(155111 MB).
Creating LUN 0 Registering new logical unit 0 with system. Formatting logical unit 0 RAID 5 155111 MB LUNs found on c1t0d0. LUN 0 RAID 5 155111 MB LUNs successfully created raidutil succeeded! # /usr/lib/osa/bin/raidutil -c c1t0d0 -h 15,25 LUNs found on c1t0d0. LUN 0 RAID 5 155111 MB raidutil succeeded! Format new RAID by making only one slice 2 partition: # * * * * * * * * * * * * * * * * * * * * *
prtvtoc /dev/rdsk/c1t0d0s2 /dev/rdsk/c1t0d0s2 partition map Dimensions: 512 bytes/sector 75 sectors/track 64 tracks/cylinder 4800 sectors/cylinder 65535 cylinders 65533 accessible cylinders Flags: 1: unmountable 10: read-only Unallocated space: First Sector Last Sector Count Sector 0 314558400 314558399 Partition 2
Tag 5
Flags 01
First Sector Last Sector Count Sector 0 314558400 314558399
Mount Directory
Newfs new RAID # newfs /dev/dsk/c1t0d0s2 Mount the RAID up as /raid # mkdir /raid # echo "/dev/dsk/c1t0d0s2 /dev/rdsk/c1t0d0s2 /raid ufs 3 yes -" >> /etc/vfstab # mount /raid Check to make sure that the new array is available via "df -lk" # df -lk Filesystem /dev/md/dsk/d0
kbytes 2056211
used avail capacity 43031 1951494 3%
Mounted on /
/dev/md/dsk/d6 /proc fd mnttab /dev/md/dsk/d5 swap swap /dev/md/dsk/d7 /dev/dsk/c1t0d0s2
4131866 1133180 0 0 0 0 0 0 2056211 9092 1450208 8 1450208 8 8089425 182023 154872105
2957368 28% 0 0% 0 0% 0 0% 1985433 1% 1450200 1% 1450200 1% 7826508 3% 9 153323375
/usr /proc /dev/fd /etc/mnttab /var /var/run /tmp /export 1% /raid
6.2 Install problem A1000 ------------------------Hi. Thanks for your kind responses. There are a few reply but tons of out of office mail. And sorry for forgetting to state that A1000 is not brand new one but used one. After some researches I found this. here's my summary. Conclusion: If A1000 has previously defined LUNs and will be used to be array as new one, you have to be remove old LUNs before define new LUNs or your rm6 complains that cannot find raid modules. --if you can see more than 1 LUNs in boot prom via command "probe-scsi-all" you have to insert disk into slot as many as LUNs than reboot with boot -rs. Than you can see configured LUNs via /usr/lib/osa/bin/lad. and /usr/lib/osa/bin/raidutil -c c#t#d# -X to delete all old LUNs. Once you delete old LUNs you can boot normaly with just one disk and can find raid module. Again, Thanks for your help. --
6.3 Installing RM 6.22 on Solaris: ---------------------------------Raid Manager 6.22 and A1000 config -- Config and setup -- ---------------Firstly install the Raid manager 6.22 (6.221) software on the Solaris 8 system. # pkgadd -d . SUNWosar SUNWosafw SUNWosamn SUNWosau Defending upon your raid manager version and scsi/fibre card type you will need to patch the system. The following patches are recommended for Solaris 8. Solaris 8 & Raid manager 6.22 Solaris 8 & Raid manager 6.221 Ultra 60
108553-07108982-09111085-02 112125-01108982-09111085-02 106455-09
Fibre channel card
109571-02
It is probably worth giving the system a reconfigure reboot at this stage. -- Firmware -- -------The first thing to do is check the firmware of the A1000. This can be done with the raidutil command. ( I assume the A1000 is on controller 1. If not then change the controller as appropriate. # raidutil -c c1t0d0 -i If the returned values are less that those shown below you will have to upgrade the firmware using fwutil. Product Boot Level Boot Level Date Firmware Level Firmware Date
Revision 0301 03.01.03.04 07/06/00 03.01.03.60 06/30/00
To upgrade the firmware perform the following. # # # # # # #
cd /usr/lib/osa/fw fwutil 02050632.bwd c1t0d0 fwutil 02050632.apd c1t0d0 fwutil 03010233.bwd c1t0d0 fwutil 03010235.apd c1t0d0 fwutil 03010304.bwd c1t0d0 fwutil 03010360.apd c1t0d0
You can now re-perform the "raidutil -c c1todo -i" command again to verify the firmware changes. Clean up the array I am assuming that the array is free for full use by ourselves and intend to remove any old luns that might be lying around. # raidutil -c c1t0d0 -X The above command resets the array internals. We can now remove any old lun's. To do this run "raidutil -c c1t0d0 -i" and note any luns that are configured. To delete the luns perform the following command. # raidutil -c c1t0d0 -i LUNs found on c1t0d0. LUN 0 RAID 1 10 MB Vendor ID ProductID Product Revision Boot Level Boot Level Date Firmware Level
Symbios StorEDGE A1000 0301 03.01.03.04 07/06/00 03.01.03.60
Firmware Date 06/30/00 raidutil succeeded! # raidutil -c c1t0d0 -D 0 In the above example we are removing lun 0. number as appropriate.
repeat this command changing the lun
We can now give the array a name of our choice. (Do not use a .) # storutil -c c1t0d0 -n "dragon_array" Creating Lun's The disks are labelled on the front of the A1000 as controller number and disk number seperated by a comma eg. 1,0 1,2 and 2,0 etc, etc. We refer to the disks without using the comma. So the first disk on controller 1 is disk 10 and the 3rd disk on controller 2 is disk 23. we will use disks on both controllers when creating the mirrors. I am starting with the disks on each controller as viewed form the left. The next stage is to create the luns we require. In the below example I will configure a fully populated (12 disks) system which has 18Gb drives into the following sizes. Here we will use the raidutil command again. # raidutil -c controller -n lun_number -l disk_list LUN 0 two disks.
raid_type
-s
size
-g
Size 8617mb of a stripped/mirror configuration across half of the first # raidutil -c c1t0d0 -n 0 -l 1+0 -s 8617 -g 10,20
LUN 1 Size 8617mb of a stripped/mirror configuration across the second half of the first two disks. # raidutil -c c1t0d0 -n 1 -l 1+0 -s 8617 -g 10,20 LUN 2 two disks.
Size 8617mb of a stripped/mirror configuration across half of the next # raidutil -c c1t0d0 -n 2 -l 1+0 -s 8617 -g 11,21
LUN 3 Size 8617mb of a stripped/mirror configuration across the second half of the next two disks. # raidutil -c c1t0d0 -n 3 -l 1+0 -s 8617 -g 11,21 LUN 4 disks.
Size 34468mb of a stripped/mirror configuration across the next four
LUN 5 disks.
Size 17234mb of a stripped/mirror configuration across the next two
LUN 6
Size 17234mb of a non mirror configuration on the next disk. # raidutil -c c1t0d0 -n 6 -l 0 -s 34468 -g 15
# raidutil -c c1t0d0 -n 4 -l 1+0 -s 34468 -g 12,13,22,23
# raidutil -c c1t0d0 -n 5 -l 1+0 -s 34468 -g 14,24
This then leaves the disk 25 or disk 5 on the second controller free as a hot spare. to set up this disk as a hot spare run # raidutil -h 25 Finishing off
We are now ready to reboot the system performing a reconfigure. When this is done we can format, partition, newfs and mount the disks in the normal way. Other commands The following is a list of possibly useful raid manager commands rm6 (GUI interface) drivutil (drive / lun management) healtchk (helth check on a raid module lad (list array devices) logutil (log formatting program) nvutil (edit / modify NVSRAM) parityck (parity checker and repair) rdacutil (redundency controller for failed bits and load balancing) storutil (host and naming info)
7.3 Sun StorEdge D1000: ======================= Overview The Sun StorEdge D1000 is a disk tray with hot-pluggable - Power supplies - Fans - Disks (If SPARCstorage Volume Manager configured). A D1000 is disk array attached to the hostname is configured as a RAID5 metadevice. Disk Terminology Before you can effectively use the information in this section, you should be familiar with basic disk architecture. In particular, you should be familiar with the following terms: Track Cylinder Sector Disk controller Disk label Device drivers Disk Slices Files stored on a disk are contained in file systems. Each file system on a disk is assigned to a slice-a group of cylinders set aside for use by that file system. Each disk slice appears to the operating system (and to the system administrator) as though it were a separate disk drive. Slices are sometimes referred to as partitions. Each disk slice holds only one file system.
No file system can span multiple slices. On SPARC based systems, Solaris defines eight disk slices and assigns to each a conventional use. These slices are numbered 0 through 7. Slice File System Purpose 0 root Holds files and directories that make up the operating system. 1 swap Provides virtual memory, or swap space. Swap space is used when running programs are too large to fit in a computer's memory. The Solaris operating environment then "swaps" programs from memory to the disk and back as needed. 2 Refers to the entire disk, by convention. It is defined automatically by the format and the Solaris installation programs. The size of this slice should not be changed. 3 /export Holds alternative versions of the operating system. These alternative versions are required by client systems whose architectures differ from that of the server. Clients with the same architecture type as the server obtain executables from the /usr file system, usually slice 6. 4 /export/swap Provides virtual memory space for client systems. 5 /opt Holds application software added to a system. If a slice is not allocated for this file system during installation, the /opt directory is put in slice 0. 6 /usr Holds operating system commands-also known as executables- designed to be run by users. This slice also holds documentation, system programs (init and /tech/sun/commands/syslogd.html">syslogd, for example) and library routines. 7 /export/home Holds files created by users. Or.. something like this is also seen on a single disk system: / swap /export /var /opt /usr /u01
Slice 0, partition about 2G Slice 1, partition about 4G Slice 3, partition about 50G, maybe you link it to /u01 Slice 4, partition about 2G Slice 5, partition about 10G if you plan to install apps here Slice 6, partition about 2G Slice 7, partition optional, standard it's /home Depending on how you configure /export, size could be around 20G
Raw Data Slices The SunOS operating system stores the disk label in block 0, cylinder 0 of each disk. This means that using third-party database applications that create raw data slices must not start at block 0, cylinder 0, or the disk label will be overwritten and the data on the disk will be inaccessible. Do not use the following areas of the disk for raw data slices, which are sometimes created by third-party d atabase applications: Block 0, cylinder 0 Where the disk label is stored. Cylinder 0 Avoid for improved performance. Slice 2 Represents the entire disk.
Slice Arrangements on Multiple Disks Although a single disk that is large enough can hold all slices and their corresponding file systems, two or more disks are often used to hold a system's slices and file systems. A slice cannot be split between two or more disks. However, multiple swap slices on separate disks are allowed. For instance, a single disk might hold the root (/) file system, a swap area, and the /usr file system, while a separate disk is provided for the /export/home file system and other file systems containing user data. In a multiple disk arrangement, the disk containing the operating system software and swap space (that is, the disk holding the root (/) or /usr file systems or the slice for swap space) is called the system disk. Disks other than the system disk are called secondary disks or non-system disks. Locating a system's file systems on multiple disks allows you to modify file systems and slices on the secondary disks without having to shut down the system or reload operating system software. Having more than one disk also increases input-output (I/O) volume. By distributing disk load across multiple disks, you can avoid I/O bottlenecks.
Determining Which Slices to Use When you set up a disk's file systems, you choose not only the size of each slice, but also which slices to use. The system configuration requires the use of different slices. The table below lists these requirements. Slice Server 0 root 1 swap 2 3 /export 4 /export/swap 5 /opt 6 /usr 7 /export/home
The format Utility The format utility can be used to manipulate hard disk drives: Display slice information Divide a disk into slices Add a disk drive Reformat a disk drive Repair a disk drive Disk Labels A special area of every disk is set aside for storing information about the disk's controller, geometry, and slices. That information is called the disk's label. Another term used to described the disk label is the VTOC (Volume Table of Contents). To label a disk means to write slice information onto the disk. You
usually label a disk after changing its slices. If you fail to label a disk after creating slices, the slices will be unavailable because the operating system has no way of "knowing" about the slices. The partition table identifies a disk's slices, the slice boundaries (in cylinders), and total size of the slices. A disk's partition table can be displayed using the format utility. Partition flags and tags are assigned by convention and require no maintenance. The following partition table example is displayed from a 1.05-Gbyte disk using the format utility: Total disk cylinders available: 2036 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 300 148.15MB (301/0/0) 303408 1 swap wu 301 - 524 110.25MB (224/0/0) 225792 2 backup wm 0 - 2035 1002.09MB (2036/0/0) 2052288 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 usr wm 525 - 2035 743.70MB (1511/0/0) 1523088 7 unassigned wm 0 0 (0/0/0) 0 The partition table contains the following information: Column Name Description Part Partition or (slice number). Valid numbers are 0-7. Tag A numeric value that usually describes the file system mounted on this partition. 0=UNASSIGNED 1=BOOT 2=ROOT 3=SWAP 4=USR 5=BACKUP 7=VAR 8=HOME Flags wm Partition is writable and mountable. wu rm Partition is writable and unmountable. Default state of partitions dedicated for swap areas. The mount command does not check the "not mountable" flag. top>rm The partition is read only and mountable. Cylinders The starting and ending cylinder number for the slice. Size The slice size in Mbytes. Blocks The total number of cylinders and the total number of sectors per slice in the far right column. The following example displays a disk label using the prtvtoc command. # prtvtoc /dev/rdsk/c0t1d0s0 * /dev/rdsk/c0t1d0s0 partition map * * Dimensions: * 512 bytes/sector * 72 sectors/track
* 14 tracks/cylinder * 1008 sectors/cylinder * 2038 cylinders * 2036 accessible cylinders * * Flags: * 1: unmountable * 10: read-only * * First * Partition Tag Flags Sector 0 2 00 0 1 3 01 303408 2 5 00 0 6 4 00 529200
Sector Count 303408 225792 2052288 1523088
Last Sector 303407 529199 2052287 2052287
Mount Directory / /usr
The disk label includes the following information: Dimensions - Physical dimensions of the disk drive. Flags - Flags listed in the partition table section. Partition (or Slice) Table - Contains the following information: Column Name Description Partition Slice number Flags Partition flag. First Sector The first sector of the slice. Sector Count The total number of sectors in the slice. Last Sector The last sector number in the slice. Mount Directory The last mount point directory for the file system.
Dividing a Disk Into Slices The format utility is most often used by system administrators to divide a disk into slices. The steps are: Determining which slices are needed Determining the size of each slice Using the format utility to divide the disk into slices Labeling the disk with new slice information Creating the file system for each slice The easiest way to divide a disk into slices is to use the modify command from the partition menu. The modify command allows you to create slices by specifying the size of each slice in megabytes without having to keep track of starting cylinder boundaries. It also keeps tracks of any disk space remainder in the "free hog" slice.
Using the Free Hog Slice When you use the format utility to change the size of one or more disk slices, you designate a temporary slice that will expand and shrink to accommodate the resizing operations. This temporary slice donates, or "frees," space when you expand a slice, and
receives, or "hogs," the discarded space when you shrink a slice. For this reason, the donor slice is sometimes called the free hog. The donor slice exists only during installation or when you run the format utility. There is no permanent donor slice during day-to-day, normal operations.
How to Identify the Disks on a System Become superuser. Run the format utility. # format The format utility displays a list of disks that it recognizes under AVAILABLE DISK SELECTIONS. Here is sample format output: # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf785d11,0 1. c1t1d0 /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf78670e,0 2. c2t0d0 /pci@8,600000/scsi@1/sd@0,0 3. c2t1d0 /pci@8,600000/scsi@1/sd@1,0 4. c2t8d0 /pci@8,600000/scsi@1/sd@8,0 5. c2t9d0 /pci@8,600000/scsi@1/sd@9,0 The format output associates a disk's physical and local device name to the disk's marketing name which appears in angle brackets . This is an easy way to identify which local device names represent the disks connected to your system. The following example uses a wildcard to display the disks connected to a second controller. # format /dev/rdsk/c2* AVAILABLE DISK SELECTIONS: 0. /dev/rdsk/c2t0d0s0 /io-unit@f,e0200000/sbi@0,0/QLGC,isp@2,10000/sd@0,0 1. /dev/rdsk/c2t1d0s0 /io-unit@f,e0200000/sbi@0,0/QLGC,isp@2,10000/sd@1,0 2. /dev/rdsk/c2t2d0s0 /io-unit@f,e0200000/sbi@0,0/QLGC,isp@2,10000/sd@2,0 3. /dev/rdsk/c2t3d0s0 /io-unit@f,e0200000/sbi@0,0/QLGC,isp@2,10000/sd@3,0 4. /dev/rdsk/c2t5d0s0
/io-unit@f,e0200000/sbi@0,0/QLGC,isp@2,10000/sd@5,0 Specify disk (enter its number): The format output identifies that disk 2 (targets 0-5) are connected to the first SCSI host adapter (sbi@...), which is connected to the first SBus device (io-unit@).
-------------------------------------------------------------------------------Displaying Disk Slices You can use the format utility to check whether or not a disk has the appropriate disk slices. If you determine that a disk does not contain the slices you want to use, use the format utility to re-create them and label the disk. The format utility uses the term partition in place of slice.
Become superuser. Enter the format utility. Identify the disk for which you want to display slice information by selecting a disk listed under AVAILABLE DISK SELECTIONS. Specify disk (enter its number):1 Enter the partition menu by typing partition at the format> prompt. format> partition Display the slice information for the current disk drive by typing print at the partition> prompt. partition> print Exit the format utility by typing q at the partition> prompt and typing q at the format> prompt. partition> q format> q # Verify displayed slice information by identifying specific slice tags and slices. If the screen output shows that no slice sizes are assigned, the disk probably does not have slices.
Examples--Displaying Disk Slice Information The following example displays slice information for disk /dev/rdsk/c2t0d0s0 Total disk cylinders available: 24620 + 2 (reserved cylinders)
Part Tag 0 unassigned 1 unassigned 2 backup 3 unassigned 4 unassigned 5 unassigned 6 unassigned 7 unassigned
Flag wm wm wu wm wm wm wm wm
Cylinders 0 0 0 - 24619 0 0 0 0 - 24618 0
Size 0 0 33.92GB 0 0 0 33.91GB 0
Blocks (0/0/0) 0 (0/0/0) 0 (24620/0/0) 71127180 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (24619/0/0) 71124291 (0/0/0) 0
The following example displays slice information for disk /dev/rdsk/c2t8d0s0 Total disk cylinders available: 24620 + 2 (reserved cylinders) Part Tag 0 unassigned 1 unassigned 2 backup 3 unassigned 4 unassigned 5 unassigned 6 unassigned 7 unassigned
Flag wm wm wu wm wm wm wm wm
Cylinders 0 0 0 - 24619 0 0 0 0 - 24618 0
Size 0 0 33.92GB 0 0 0 33.91GB 0
Blocks (0/0/0) 0 (0/0/0) 0 (24620/0/0) 71127180 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (24619/0/0) 71124291 (0/0/0) 0
--------------------------------------------------------------------------------
Creating and Examining a Disk Label Labeling a disk is usually done during system installation or when you are creating new disk slices. You might need to relabel a disk if the disk label is corrupted (for example, from a power failure). The format utility will attempt to automatically configure any unlabeled SCSI disk. If format is able to automatically configure an unlabeled disk, it will display a message like the following: c1t0d0:configured with capacity of 404.65MB How to Label a Disk Become superuser. Enter the format utility. Enter the number of the disk that you want to label from the list displayed on your screen. Specify disk (enter its number):1
If the disk is unlabeled and was successfully configured, format will ask if you want to label the disk. Go to step 5 to label the disk. If the disk was labeled and you want to change the type, or format was not able to automatically configure the disk you must specify the disk type. Go to steps 6-7 to set the disk type and label the disk. Label the disk by typing y at the Label it now? prompt. Disk not labeled. Label it now? y The disk is now labeled. Go to step 10 to exit the format utility. Enter type at the format> prompt. format> type Format displays the Available Drive Types menu. Select a disk type from the list of possible disk types. Specify disk type (enter its number)[12]: 12 Label the disk. If the disk is not labeled, the following message is displayed. Disk not labeled. Label it now? y Otherwise you are prompted with this message: Ready to label disk, continue? y Use the verify command from the format main menu to verify the disk label. format> verify Exit the format utility by typing q at the format> prompt. partition> q format> q # Example-Labeling a Disk The following example automatically configures and labels a 1.05-Gbyte disk. # format c1t0d0: configured with capacity of 1002.09MB AVAILABLE DISK SELECTIONS: 0. c0t3d0 /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@1,0 1. c1t0d0 /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@1,0 Specify disk (enter its number): 1 Disk not labeled. Label it now? yes format> verify #
How to Examine a Disk Label Examine disk label information by using the prtvtoc(1M) command. See Chapter 28, Disk Management (Overview) for a detailed description of the disk label and the information displayed by the prtvtoc command. Become superuser. Display the disk label information by using the prtvtoc command. # prtvtoc /dev/rdsk/device-name
Automatically Configuring SCSI Disk Drives In Solaris 2.3 release and compatible versions, the format utility automatically configures SCSI disk drives even if that specific type of drive is not listed in the /etc/format.dat file. This feature enables you to format, slice, and label any disk driver compliant with SCSI-2 specification for disk device mode sense pages. The following steps are involved in configuring a SCSI drive using autoconfiguration: Shutting down the system Attaching the SCSI disk drive to the system Turning on the disk drive Performing a reconfiguration boot Using the format utility to automatically configure the SCSI disk drive After the reconfiguration boot, invoke the format utility. The format utility will attempt to configure the disk and, if successful, alert the user that the disk was configured. See How to Automatically Configure a SCSI Drive for step-by-step instructions on configuring a SCSI disk drive automatically. Here are the default slice rules that format uses to create the partition table. Disk Size Root File System Swap Slice 0 - 180 Mbytes 16 Mbytes 16 Mbytes 180 Mbytes - 280 Mbytes 16 Mbytes 32 Mbytes 280 Mbytes - 380 Mbytes 24 Mbytes 32 Mbytes 380 Mbytes - 600 Mbytes 32 Mbytes 32 Mbytes 600 Mbytes - 1.0 Gbytes 32 Mbytes 64 Mbytes 1.0 Gbytes - 2.0 Gbytes 64 Mbytes 128 Mbytes More than 2.0 Gbytes 128 Mbytes 128 Mbytes In all cases, slice 6 (for the /usr file system) gets the remainder of the space on the disk. Here's an example of a format-generated partition table for a 1.3-Gbyte SCSI disk drive.
Part 0 1 2 6
Tag root swap backup usr
Flag wm wu wu wm
Cylinders 0 96 97 - 289 0 - 1964 290 - 1964
Size 64.41MB 128.16MB 1.27GB 1.09GB
Blocks (97/0/0) (193/0/0) (1965/0/0) (1675/0/0)
How to Automatically Configure a SCSI Drive Become superuser. Create the /reconfigure file that will be read when the system is booted. # /tech/sun/commands/touch.html">touch /reconfigure Shut down the system. # /tech/sun/commands/shutdown.html">shutdown -i0 -g30 -y The ok or > prompt is displayed after the operating environment is shut down. Turn off power to the system and all external peripheral devices. Make sure the disk you are adding has a different target number than the other devices on the system. You will often find a small switch located at the back of the disk for this purpose. Connect the disk to the system and check the physical connections. Turn on the power to all external peripherals. Turn on the power to the system. The system will boot and display the login prompt. Login as superuser, invoke the format utility, and select the disk to be configured automatically. # format Searching for disks...done c1t0d0: configured with capacity of 1002.09MB AVAILABLE DISK SELECTIONS: 0. c0t1d0 /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@1,0 1. c0t3d0 /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@3,0 Specify disk (enter its number): 1 Reply yes to the prompt to label the disk. Replying y will cause the disk label to be generated and written to the disk by the autoconfiguration feature. Disk not labeled. Label it now? y Verify the disk label with the verify command.
format> verify Exit the format utility. format> q
--------------------------------------------------------------------------------
SPARC: How to Create Disk Slices and Label a Disk Become superuser. Start the format(1M) utility. # format A list of available disks is displayed. Enter the number of the disk that you want to repartition from the list displayed on your screen. Specify disk (enter its number): disk-number Go into the partition menu (which lets you set up the slices). format> partition Display the current partition (slice) table. partition> print Start the modification process. partition> modify Set the disk to all free hog. Choose base (enter number) [0]? 1 See Using the Free Hog Slice for more information about the free hog slice. Create a new partition table by answering y when prompted to continue. Do you wish to continue creating a new partition table based on above table[yes]? y Identify the free hog partition (slice) and the sizes of the slices when prompted. When adding a system disk, you must set up slices for: root (slice 0) and swap (slice 1) and/or /usr (slice 6) After you identify the slices, the new partition table is displayed. Make the displayed partition table the current partition table by answering y when asked. Okay to make this
the current partition table[yes]? y If you don't want the current partition table and you want to change it, answer no and go to Step 6 . Name the partition table. Enter table name (remember quotes): "partition-name" Label the disk with the new partition table when you have finished allocating slices on the new disk. Ready to label disk, continue? yes Quit the partition menu. partition> q Verify the disk label using the verify command. format> verify Quit the format menu. format> q SPARC: Example-Creating Disk Slices and Labeling a System Disk The following example uses the format utility to divide a 1-Gbyte disk into three slices: one for the root (/) file system, one for the swap area, and one for the /usr file system. # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t1d0 /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@1,0 1. c0t3d0 /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@3,0 Specify disk (enter its number): 0 selecting c0t1d0 [disk formatted] format> partition partition> print partition> modify Select partitioning base: 0. Current partition table (original) 1. All Free Hog Choose base (enter number) [0]? 1 Part Tag Flag Cylinders Size Blocks 0 root wm 0 0 (0/0/0) 0 1 swap wu 0 0 (0/0/0) 0 2 backup wu 0 - 2035 1002.09MB (2036/0/0) 2052288 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 usr wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 Do you wish to continue creating a new partition table based on above table[yes]? yes Free Hog partition[6]? 6 Enter size of partition `0' [0b, 0c, 0.00mb]: 200mb Enter size of partition `1' [0b, 0c, 0.00mb]: 200mb Enter size of partition `3' [0b, 0c, 0.00mb]: Enter size of partition `4' [0b, 0c, 0.00mb]: Enter size of partition `6' [0b, 0c, 0.00mb]: Enter size of partition `7' [0b, 0c, 0.00mb]: Part Tag Flag Cylinders Size 0 root wm 0 - 406 200.32MB 1 swap wu 407 - 813 200.32MB 2 backup wu 0 - 2035 1002.09MB 3 unassigned wm 0 0 4 unassigned wm 0 0 5 unassigned wm 0 0 6 usr wm 814 - 2035 601.45MB 7 unassigned wm 0 0 Okay to make this the current partition table[yes]? Enter table name (remember quotes): "disk0" Ready to label disk, continue? yes partition> quit format> verify format> quit
(0/0/0)
0
Blocks (407/0/0) 410256 (407/0/0) 410256 (2036/0/0) 2052288 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (1222/0/0) 1231776 (0/0/0) 0 yes
SPARC: Example-Creating Disk Slices and Labeling a Secondary Disk The following example uses the format utility to divide a 1-Gbyte disk into one slice for the /export/home file system. # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t1d0 /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@1,0 1. c0t3d0 /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@3,0 Specify disk (enter its number): 0 selecting c0t1d0 [disk formatted] format> partition partition> print partition> modify Select partitioning base: 0. Current partition table (original) 1. All Free Hog Choose base (enter number) [0]? 1 Part Tag Flag Cylinders Size Blocks 0 root wm 0 0 (0/0/0) 0 1 swap wu 0 0 (0/0/0) 0 2 backup wu 0 - 2035 1002.09MB (2036/0/0) 2052288 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 usr wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0 Do you wish to continue creating a new partition table based on above table[yes]? y Free Hog partition[6]? 7 Enter size of partition '0' [0b, 0c, 0.00mb, 0.00gb]: Enter size of partition '1' [0b, 0c, 0.00mb, 0.00gb]: Enter size of partition '3' [0b, 0c, 0.00mb, 0.00gb]: Enter size of partition '4' [0b, 0c, 0.00mb, 0.00gb]: Enter size of partition '5' [0b, 0c, 0.00mb, 0.00gb]: Enter size of partition '6' [0b, 0c, 0.00mb, 0.00gb]: Part Tag Flag Cylinders Size Blocks 0 root wm 0 0 (0/0/0) 0 1 swap wu 0 0 (0/0/0) 0 2 backup wu 0 - 2035 1002.09MB (2036/0/0) 2052288 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 usr wm 0 0 (0/0/0) 0 7 unassigned wm 0 - 2035 1002.09MB (2036/0/0) 2052288 Okay to make this the current partition table[yes]? yes Enter table name (remember quotes): "home" Ready to label disk, continue? y partition> q format> verify format> q #
SPARC: How to Create File Systems Become superuser. Create a file system for each slice with the newfs(1M) command. # newfs /dev/rdsk/cwtxdysz Verify the new file system by mounting it on an unused mount point. # mount /dev/dsk/cwtxdysz /mnt # ls lost+found
How to Stop All Processes Accessing a File System Become superuser. List all the processes that are accessing the file system, so you know which processes you are going to stop. # /tech/sun/commands/fuser.html">fuser -c [ -u ] mount-point Stop all processes accessing the file system. You should not stop a user's
processes without warning. # /tech/sun/commands/fuser.html">fuser -c -k mount-point A SIGKILL is sent to each process using the file system. Verify that there are no processes accessing the file system. # /tech/sun/commands/fuser.html">fuser -c mount-point
--------------------------------------------------------------------------------
Add Disk Follow the steps below to add a new external/internal disk: Bring the system down to the ok prompt. # init 0 Find an available target setting. This command will show what you currently have on your system. # probe-scsi If the disk is on another scsi controller (another card off of an sbus slot) # probe-scsi-all Attach the new disk with the correct target setting. Run probe-scsi again to make sure the system sees it. If it doesn't, the disk is either not connected properly, has a target conflict, or is defective. Resolve this issue before continuing. In this example, we'll say: T3 original internal drive T1 new/other internal drive where a duplicate copy of the OS will be placed. Perform a reconfiguration boot. # boot -rv rv -> reconfigure in verbose mode.
Run format and partition the disk. (Here's our example): # format Searching for disks...done AVAILABLE DISK SELECTIONS:
1. c0t1d0 /iommu@0,10000000/sbus@0,10001000/espdma@5,8400000/esp@5,8800000/sd@1,0 2. c0t3d0 /iommu@0,10000000/sbus@0,10001000/espdma@5,8400000/esp@5,8800000/sd@3,0 Specify disk (enter its number): 1 selecting c0t1d0 [disk formatted] FORMAT MENU: disk type partition current format repair label analyze defect backup verify save inquiry volname quit format> part
select a disk select (define) a disk type select (define) a partition table describe the current disk - format and analyze the disk - repair a defective sector - write label to the disk surface analysis - defect list management - search for backup labels - read and display labels save new disk/partition definitions show vendor, product and revision set 8-character volume name
PARTITION MENU: 0 - change `0' partition 1 - change `1' partition 2 - change `2' partition 3 - change `3' partition 4 - change `4' partition 5 - change `5' partition 6 - change `6' partition 7 - change `7' partition select - select a predefined modify - modify a predefined name - name the current table print - display the current label - write partition map quit
table partition table table and label to the disk
partition> print Current partition table (original): Total disk cylinders available: 2036 + 2 (reserved cylinders) Part Tag Flag 0 root wm 1 swap wu 2 backup 3 unassigned 4 var wm 5 unassigned 6 usr wm 7 unassigned
Cylinders Size Blocks 0 - 203 100.41MB (204/0/0) 205632 204 - 407 100.41MB (204/0/0) 205632 wm 0 - 2035 1002.09MB (2036/0/0) 2052288 wm 0 0 (0/0/0) 0 408 - 611 100.41MB (204/0/0) 205632 wm 612 - 1018 200.32MB (407/0/0) 410256 1019 - 2034 500.06MB (1016/0/0) 1024128 wm 0 0 (0/0/0) 0
partition> ****** Modify partitions to suit your needs ****** ****** Do NOT alter partition 2, backup !!! ****** In this example we'll go with the current displayed partition table listed: partition> 0 Part Tag 0 unassigned
Flag wm
Cylinders 0 - 162
Size Blocks 80.23MB (163/0/0) 164304
Enter partition id tag[unassigned]: Enter partition permission flags[wm]: Enter new starting cyl[0]: o `o' is not an integer. Enter new starting cyl[0]: 0 Enter partition size[164304b, 163c, 80.23mb, 0.08gb]: 100.41mb partition> pr Current partition table (unnamed): Total disk cylinders available: 2036 + 2 (reserved cylinders) Part 0 1 2 3 4 5 6 7
Tag unassigned unassigned backup unassigned unassigned unassigned unassigned unassigned
partition> 1 Part Tag 1 unassigned
wm wu wm wm wm wm wm
Flag Cylinders Size Blocks 0 - 203 100.41MB (204/0/0) 205632 163 - 423 128.46MB (261/0/0) 263088 wu 0 - 2035 1002.09MB (2036/0/0) 2052288 0 0 (0/0/0) 0 424 - 749 160.45MB (326/0/0) 328608 750 - 1109 177.19MB (360/0/0) 362880 1110 - 2035 455.77MB (926/0/0) 933408 0 0 (0/0/0) 0
Flag Cylinders wu 163 - 423
Size 128.46MB
Blocks (261/0/0) 263088
Enter partition id tag[unassigned]: Enter partition permission flags[wu]: Enter new starting cyl[163]: 204 Enter partition size[263088b, 261c, 128.46mb, 0.13gb]: 100.41mb partition> pr Current partition table (unnamed): Total disk cylinders available: 2036 + 2 (reserved cylinders) Part 0 1 2 3 4 5 6 7
Tag unassigned unassigned backup unassigned unassigned unassigned unassigned unassigned
partition> 4 Part Tag 4 unassigned
Flag Cylinders Size Blocks wm 0 - 203 100.41MB (204/0/0) 205632 wu 204 - 407 100.41MB (204/0/0) 205632 wu 0 - 2035 1002.09MB (2036/0/0) 2052288 wm 0 0 (0/0/0) 0 wm 424 - 749 160.45MB (326/0/0) 328608 wm 750 - 1109 177.19MB (360/0/0) 362880 wm 1110 - 2035 455.77MB (926/0/0) 933408 wm 0 0 (0/0/0) 0
Flag wm
Cylinders 424 - 749
Size 160.45MB
Blocks (326/0/0) 328608
Enter partition id tag[unassigned]: Enter partition permission flags[wm]: Enter new starting cyl[424]: 408 Enter partition size[328608b, 326c, 160.45mb, 0.16gb]: 100.41mb partition> pr Current partition table (unnamed): Total disk cylinders available: 2036 + 2 (reserved cylinders) Part 0 1 2 3 4 5 6 7
Tag unassigned unassigned backup unassigned unassigned unassigned unassigned unassigned
partition> 5 Part Tag 5 unassigned
Flag wm wu wm wm wm wm wm
Cylinders Size Blocks 0 - 203 100.41MB (204/0/0) 205632 204 - 407 100.41MB (204/0/0) 205632 wu 0 - 2035 1002.09MB (2036/0/0) 2052288 0 0 (0/0/0) 0 408 - 611 100.41MB (204/0/0) 205632 750 - 1109 177.19MB (360/0/0) 362880 1110 - 2035 455.77MB (926/0/0) 933408 0 0 (0/0/0) 0
Flag wm
Cylinders 750 - 1109
Size 177.19MB
Blocks (360/0/0) 362880
Enter partition id tag[unassigned]: Enter partition permission flags[wm]: Enter new starting cyl[750]: 612 Enter partition size[362880b, 360c, 177.19mb, 0.17gb]: 177mb partition> pr Current partition table (unnamed): Total disk cylinders available: 2036 + 2 (reserved cylinders) Part 0 1 2 3 4 5 6 7
Tag unassigned unassigned backup unassigned unassigned unassigned unassigned unassigned
partition> 6 Part Tag 6 unassigned
Flag wm wu wm wm wm wm wm
Cylinders Size Blocks 0 - 203 100.41MB (204/0/0) 205632 204 - 407 100.41MB (204/0/0) 205632 wu 0 - 2035 1002.09MB (2036/0/0) 2052288 0 0 (0/0/0) 0 408 - 611 100.41MB (204/0/0) 205632 612 - 971 177.19MB (360/0/0) 362880 1110 - 2035 455.77MB (926/0/0) 933408 0 0 (0/0/0) 0
Flag wm
Cylinders Size 1110 - 2035
455.77MB
Blocks (926/0/0)
933408
Enter partition id tag[unassigned]: Enter partition permission flags[wm]: Enter new starting cyl[1110]: 972 Enter partition size[933408b, 926c, 455.77mb, 0.45gb]: $ partition> pr Current partition table (unnamed): Total disk cylinders available: 2036 + 2 (reserved cylinders) Part 0
Tag unassigned
Flag wm
Cylinders 0 - 203
Size 100.41MB
Blocks (204/0/0) 205632
1 unassigned wu 204 - 407 100.41MB (204/0/0) 205632 2 backup wu 0 - 2035 1002.09MB (2036/0/0) 2052288
3 4 5 6 7
unassigned unassigned unassigned unassigned unassigned
wm wm wm wm wm
0 0 408 612 972 0 0
(0/0/0) 0 - 611 100.41MB (204/0/0) 205632 - 971 177.19MB (360/0/0) 362880 - 2035 523.69MB (1064/0/0) 1072512 (0/0/0) 0
partition> NOTE: You will know for certain that your partitioning is correct if you add all the cylinder values [the values enclosed in ( )], like so, 204+204+204+360+1064=2036 which is the same value for slice 2 or the whole disk (Tag = backup). Now label the disk. This is important as this is what saves the partition table in your VTOC (Virtual Table Of Contents). It's also always recommended to do the labeling part twice to be certain that the VTOC gets saved. partition> label partition> q format> q After partitioning c0t1d0 to be exactly the same as c0t3d0, be sure you label the disk so that VTOC gtes updated with the correct partition table. To recap, our scenario is: c0t3d0 (running Solaris 2.6) being copied to c0t1d0 (which will have the copied Solaris 2.6 slices/partitions) c0t3d0s0 / -> c0t1d0s0 / c0t3d0s4 /var -> c0t1d0s4 /var c0t3d0s5 /opt -> c0t1d0s5 /opt c0t3d0s6 /usr -> c0t1d0s6 /usr For each of the partitions that you wish to mount, run newfs to contruct a unix filesystem. So, newfs each partition. # # # #
newfs newfs newfs newfs
-v -v -v -v
/dev/rdsk/c0t1d0s0 /dev/rdsk/c0t1d0s4 /dev/rdsk/c0t1d0s5 /dev/rdsk/c0t1d0s6
To ensure that they are clean and mounted properly, run fsck on these mounted partitions: # # # #
fsck fsck fsck fsck
/dev/rdsk/c0t1d0s0 /dev/rdsk/c0t1d0s4 /dev/rdsk/c0t1d0s5 /dev/rdsk/c0t1d0s6
Make the mount points.
# /tech/sun/commands/mkdir.html">mkdir /mount_point Create mountpoints for each slice/partition, like so: # # # #
/tech/sun/commands/mkdir.html">mkdir /tech/sun/commands/mkdir.html">mkdir /tech/sun/commands/mkdir.html">mkdir /tech/sun/commands/mkdir.html">mkdir
/root2 /var2 /opt2 /usr2
Mount the new partitions. # mount /dev/dsk/c0t1d0sX /mount_point Mount each partition (of the new disk), like so: # # # #
mount mount mount mount
/dev/dsk/c0t1d0s0 /dev/dsk/c0t1d0s4 /dev/dsk/c0t1d0s5 /dev/dsk/c0t1d0s6
/root2 /var2 /opt2 /usr2
Now we /tech/sun/commands/ufsdump.html">ufsdump each slices/partitions: It is often difficult to copy from one disk to another disk. If you try to use dd, and the disks are of differing sizes, then you will undoubtedly run into trouble. Use this method to copy from disk to disk and you should not have any problems. Of course you're still on the old disk (that's where you booted from c0t3d0): # cd / (Just ensures that you are in the root's parent/top directory). # /tech/sun/commands/ufsdump.html">ufsdump 0f - /dev/rdsk/c0t3d0s0 /tech/sun/commands/ufsrestore.html">ufsrestore rf -) # /tech/sun/commands/ufsdump.html">ufsdump 0f - /dev/rdsk/c0t3d0s4 /tech/sun/commands/ufsrestore.html">ufsrestore rf -) # /tech/sun/commands/ufsdump.html">ufsdump 0f - /dev/rdsk/c0t3d0s5 /tech/sun/commands/ufsrestore.html">ufsrestore rf -) # /tech/sun/commands/ufsdump.html">ufsdump 0f - /dev/rdsk/c0t3d0s6 /tech/sun/commands/ufsrestore.html">ufsrestore rf -)
| (cd /root2; | (cd /var2; | (cd /opt2; | (cd /usr2;
The gotcha here is that you can't really specify the directory name as /tech/sun/commands/ufsdump.html">ufsdump will interpret it as not being a block or character device. To illustrate this error: # cd /usr # /tech/sun/commands/ufsdump.html">ufsdump 0f - /usr | (cd /usr2; /tech/sun/commands/ufsrestore.html">ufsrestore xf - ) DUMP: Writing 32 Kilobyte records DUMP: Date of this level 0 dump: Wed Dec 10 17:33:42 1997 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rdsk/c0t3d0s0 (tmpdns:/usr) to standard output DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Estimated 317202 blocks (154.88MB) DUMP: Dumping (Pass III) [directories]
DUMP: Broken pipe DUMP: The ENTIRE dump is aborted If you want to use the directory names to simplify your command line, use the tar command instead of /tech/sun/commands/ufsdump.html">ufsdump as follows: Example: # cd /usr # tar cvfp - . | (cd /usr2; tar xvfp - ) OPTIONAL (This may be redundant BUT ensures that the copied files are once again clean and consistent). Checking the integrity of a filesystem is always highly recommended even if it becomes redundant in nature. Now, check and run fsck on the new partition/slices: # # # #
fsck fsck fsck fsck
/dev/rdsk/c0t1d0s0 /dev/rdsk/c0t1d0s4 /dev/rdsk/c0t1d0s5 /dev/rdsk/c0t1d0s6
Edit your /mount_point/etc/vfstab file to have this disk bootup from the correct disk/devices c0t1d0 as opposed to c0t3d0. # cd /root2 # vi /root2/etc/vfstab Change c0tXd0sX devices to reflect the new disk! #device device mount FS fsck mount mount #to mount to fsck point type pass at boot options # #/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes fd - /dev/fd fd - no /proc - /proc proc - no /dev/dsk/c0t1d0s1 - - swap - no /dev/dsk/c0t1d0s0 /dev/rdsk/c0t1d0s0 / ufs 1 no /dev/dsk/c0t1d0s6 /dev/rdsk/c0t1d0s6 /usr ufs 1 no /dev/dsk/c0t1d0s4 /dev/rdsk/c0t1d0s4 /var ufs 1 no /dev/dsk/c0t1d0s5 /dev/rdsk/c0t1d0s5 /opt ufs 2 yes swap - /tmp tmpfs - yes :wq! Now you must run /tech/sun/commands/installboot.html">installboot to load a new bootblk on that disk. Not loading a bootblk will leave this disk in an unbootable state as the boot strap program is contained within the bootblk, and this in turn is what loads the boot file called ufsboot after interfacing with the OBP (Open Boot PROM). You can do this from your current booted disk or you may choose to boot off from cdrom via ok> boot cdrom -sw (single-user mode, writeable mode off of cdrom's mini-root). If you choose to get bootblk from your current disk the location of the bootblk in Solaris 2.5 or higher is under:
/usr/platform/`uname -i`/lib/fs/ufs/bootblk # /usr/sbin/installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk \ /dev/rdsk/c0t1d0s0 If you choose to get bootblk from your cdrom image: ok> boot cdrom -sw # /tech/sun/commands/installboot.html">installboot /cdrom/solaris_2_5_sparc/s0/export/exec/sparc.Solaris_2.5 \ /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0txd0s0 ANOTHER SPARC EXAMPLE: To install a ufs bootblock on slice 0 of target 0 on con- troller 1, of the platform where the command is being run, use: example# /tech/sun/commands/installboot.html">installboot /usr/platform/`uname -i` /lib/fs/ufs/bootblk \ /dev/rdsk/c1t0d0s0 Now create an alias for the other disk (this may be existent if it's off of the onboard/first scsi controller). ok> probe-scsi T3 original boot disk T1 new disk with copied slices Verify via devalias command to see current /tech/sun/commands/aliases.html">aliases: disk1 is for sd@1,0 which is scsi id/target 1 ok> devalias ok> setenv boot-device disk1 ok> boot -rv You do not necessarily need to do a reconfiguration boot as devices had already been created. This parameter will only be run if you attached new devices to your system. By default this will always boot from the new disk. If you want to boot from the old disk you can manually tell it to boot to that alias, like so: ok> boot disk or ok> boot disk3 (This will boot off from any Target 3/scsi id 3 internal disk). Also see INFODOC #'s 14046, 11855, 11854 for setting different boot devalias'es.
NOTE: If the new disk encounters a problem on booting, most likely cause would be inappropriate /tech/sun/commands/devlinks.html">devlinks so, the course of action to take here is the /etc/path_to_inst, /dev, /devices fix: The following is a solution to solve problems with /dev, /devices, and/or /etc/path-to_inst. This routine extracts the defaults (with links intact) from the Solaris 2.x CD-ROM. ok> boot cdrom -sw # mount /dev/dsk/c0t1d0s0 /a ** This step assumes your boot disk is c0t1d0s0 # cd /tmp/dev # tar cvfp - . | (cd /a/dev; tar xvfp - ) # cd /tmp/devices # tar cvfp - . | (cd /a/devices; tar xvfp - ) # cd /tmp/root/etc # /tech/sun/commands/cp.html">cp path_to_inst /a/etc/path_to_inst # /tech/sun/commands/reboot.html">reboot -- -rv If you plan to move this new disk you copied the OS on, you MUST ensure that it will be moved to a similar architecture and machine type as hardware address paths are usually different from one machine to another. Each hardware platform has a hardware device tree which must match the device tree information saved during installation in /devices and the /dev directories. Another reason is that a kernel from one architecture cannot boot on a machine of a different architecture. Customers often overlook these architecture differences (Sun 4/4c/4m/4d/4u). A boot drive moved from a SPARCstation 2 (sun4c architecture) cannot boot on a SPARCstation 5 (sun4m architecture). For more details on why you can't move Solaris 2.X boot disk between machines please see INFODOC 13911 and 13920. Also ensure that you have the correct /tech/sun/commands/hostname.html">hostname, IP address and vfstab entries for this new drive if you plan to move it to another machine.
Add a New Disk II In this example, the Sun StorEdge D1000 tray is connected to a UDWIS host adapter corresponding to controller c2 and a drive was added to slot 4 on the tray. The new drive appears as /dev/dsk/c2t4d0s[0-7] and /dev/rdsk/c2t4d0s[0-7]. Add the new device: # drvconfig (or devfsadm) # disks Verify the new disk has been created: # ls -l /dev/dsk/c1t4d0s* The new disk drive is now available for use as a block or character device. Refer to sd for more info.
7.4 bare-metal restore procedure. ================================= SUMMARY: Help troubleshooting bare-metal restore procedure. Thank you: Anand Chouthai Roy Erickson With help from contributors I identified two things wrong w/ the procedure I was implementing: 1. I needed to update /dev,/devices, and /etc/path_to_inst so that the replacement FC drive w/ a new WWN was correctly recognized as the root disk (this was on a Sun 280R). 2. After fixing that it helped me uncover the "lockup". It was because I didn't add the "-H" option to bprestore which indicates that to rename the hardlink targets as well as the normal source files (I thought bprestore had an AI module that figured all that out ;-). After making these two changes I was able to get the system back to a sane state. Below are the updated scripts. The first one is the revised script I am using to do the actual bare metal restore. The second is a script I use to build a recovery image. Certain packages and tarballs are needed which aren't included but the general idea is there. -The only quirk I have observed is that /var/run doesn't get mounted as swap (the system creates a normal directory). mount: mount-point /var/run does not exist. Not sure about this one but for now I will live w/ it. Thanks again Sun Managers! Kevin Counts -Script #1: #!/bin/sh #-----------------------------------------------------------------------# $Id: recover-egate2.sh,v 1.7 2004/03/01 19:36:06 countskm Exp $ #-----------------------------------------------------------------------# Custom script to restore egate2 (run from jumpstart recovery image). #-------------------------------------------------------------------------
#------------------------------------------------------------------------# Create pre-defined vtoc for 36GB FC Drive #------------------------------------------------------------------------/usr/sbin/fmthard -s - /dev/rdsk/c1t0d0s2
"ses" "ses" "ses" "ses" "ses" "ses" "ses" "ses"
- Logical Device names. The "Logical device names" are used with most Solaris file system commands to refer to devices. Logical device files in the /dev directory are symbolically linked to physical device files in the /devices directory. Logical device names are used to access disk devices in the following circumstances: - adding a new disk to the system and partitioning the disk - moving a disk from one system to another - accessing or mounting a file system residing on a local disk - backing up a local file system - repairing a file system Logical devices are organized in subdirs under the /dev directory by their device types /dev/dsk block interface to disk devices /dev/rdsk raw or character interface to disk devices /dev/rmt tape devices /dev/term serial line devices etc.. Logical device files have a major and minor number that indicate device drivers, hardware addresses, and other characteristics. Furthermore, a device filename must follow a specific naming convention. A logical device name for a disk drive has the following format: /dev/[r]dsk/cxtxdxsx where cx refers to the SCSI controller number, tx to the SCSI bus target number, dx to the disk number (always 0 except on storage arrays) and sx to the slice or partition number. /dev/ls -al .. lrwxrwxrwx lrwxrwxrwx lrwxrwxrwx lrwxrwxrwx
1 1 1 1
root root root root
root root root root
13 13 13 13
Aug Aug Aug Aug
10 10 10 10
2004 2004 2004 2004
rsd1a rsd1b rsd1c rsd1d
-> -> -> ->
rdsk/c1t1d0s0 rdsk/c1t1d0s1 rdsk/c1t1d0s2 rdsk/c1t1d0s3
lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root ../devices/pseudo/rsm@0:rsm lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root other ../devices/pseudo/rts@0:rts drwxr-xr-x 2 root sys lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root ..
13 13 13 13 13 13 13 13 13 13 13 13 27
Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug
10 10 10 10 10 10 10 10 10 10 10 10 10
2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004
rsd1e -> rsd1f -> rsd1g -> rsd1h -> rsd3a -> rsd3b -> rsd3c -> rsd3d -> rsd3e -> rsd3f -> rsd3g -> rsd3h -> rsm ->
13 7 7 7 7 27
Aug Aug Aug Aug Aug Aug
10 10 10 10 10 10
2004 2004 2004 2004 2004 2004
rsr0 -> rdsk/c0t0d0s2 rst12 -> rmt/0lb rst20 -> rmt/0mb rst28 -> rmt/0hb rst36 -> rmt/0cb rts ->
512 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12
Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug
10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004
sad sd1a sd1b sd1c sd1d sd1e sd1f sd1g sd1h sd3a sd3b sd3c sd3d sd3e sd3f sd3g sd3h
/dev>cd dsk /dev/dsk>ls -al total 58 drwxr-xr-x 2 root sys 512 Aug drwxr-xr-x 14 root sys 4096 Oct lrwxrwxrwx 1 root root 42 Aug ../../devices/pci@1e,600000/ide@d/sd@0,0:a lrwxrwxrwx 1 root root 42 Aug ../../devices/pci@1e,600000/ide@d/sd@0,0:b lrwxrwxrwx 1 root root 42 Aug ../../devices/pci@1e,600000/ide@d/sd@0,0:c lrwxrwxrwx 1 root root 42 Aug ../../devices/pci@1e,600000/ide@d/sd@0,0:d lrwxrwxrwx 1 root root 42 Aug ../../devices/pci@1e,600000/ide@d/sd@0,0:e lrwxrwxrwx 1 root root 42 Aug ../../devices/pci@1e,600000/ide@d/sd@0,0:f lrwxrwxrwx 1 root root 42 Aug
-> -> -> -> -> -> -> -> -> -> -> -> -> -> -> ->
rdsk/c1t1d0s4 rdsk/c1t1d0s5 rdsk/c1t1d0s6 rdsk/c1t1d0s7 rdsk/c1t0d0s0 rdsk/c1t0d0s1 rdsk/c1t0d0s2 rdsk/c1t0d0s3 rdsk/c1t0d0s4 rdsk/c1t0d0s5 rdsk/c1t0d0s6 rdsk/c1t0d0s7
dsk/c1t1d0s0 dsk/c1t1d0s1 dsk/c1t1d0s2 dsk/c1t1d0s3 dsk/c1t1d0s4 dsk/c1t1d0s5 dsk/c1t1d0s6 dsk/c1t1d0s7 dsk/c1t0d0s0 dsk/c1t0d0s1 dsk/c1t0d0s2 dsk/c1t0d0s3 dsk/c1t0d0s4 dsk/c1t0d0s5 dsk/c1t0d0s6 dsk/c1t0d0s7
10 2004 . 4 14:15 .. 10 2004 c0t0d0s0 -> 10
2004 c0t0d0s1 ->
10
2004 c0t0d0s2 ->
10
2004 c0t0d0s3 ->
10
2004 c0t0d0s4 ->
10
2004 c0t0d0s5 ->
10
2004 c0t0d0s6 ->
../../devices/pci@1e,600000/ide@d/sd@0,0:g lrwxrwxrwx 1 root root 42 Aug ../../devices/pci@1e,600000/ide@d/sd@0,0:h lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@0,0:a lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@0,0:b lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@0,0:c lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@0,0:d lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@0,0:e lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@0,0:f lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@0,0:g lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@0,0:h lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@1,0:a lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@1,0:b lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@1,0:c lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@1,0:d lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@1,0:e lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@1,0:f lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@1,0:g lrwxrwxrwx 1 root root 43 Aug ../../devices/pci@1c,600000/scsi@2/sd@1,0:h
10
2004 c0t0d0s7 ->
10
2004 c1t0d0s0 ->
10
2004 c1t0d0s1 ->
10
2004 c1t0d0s2 ->
10
2004 c1t0d0s3 ->
10
2004 c1t0d0s4 ->
10
2004 c1t0d0s5 ->
10
2004 c1t0d0s6 ->
10
2004 c1t0d0s7 ->
10
2004 c1t1d0s0 ->
10
2004 c1t1d0s1 ->
10
2004 c1t1d0s2 ->
10
2004 c1t1d0s3 ->
10
2004 c1t1d0s4 ->
10
2004 c1t1d0s5 ->
10
2004 c1t1d0s6 ->
10
2004 c1t1d0s7 ->
/dev/dsk>cd .. /dev>cd rdsk /dev/rdsk>ls -al total 58 drwxr-xr-x 2 root sys 512 Aug 10 2004 . drwxr-xr-x 14 root sys 4096 Oct 4 14:15 .. lrwxrwxrwx 1 root root 46 Aug 10 2004 c0t0d0s0 -> ../../devices/pci@1e,600000/ide@d/sd@0,0:a,raw lrwxrwxrwx 1 root root 46 Aug 10 2004 c0t0d0s1 -> ../../devices/pci@1e,600000/ide@d/sd@0,0:b,raw lrwxrwxrwx 1 root root 46 Aug 10 2004 c0t0d0s2 -> ../../devices/pci@1e,600000/ide@d/sd@0,0:c,raw lrwxrwxrwx 1 root root 46 Aug 10 2004 c0t0d0s3 -> ../../devices/pci@1e,600000/ide@d/sd@0,0:d,raw lrwxrwxrwx 1 root root 46 Aug 10 2004 c0t0d0s4 -> ../../devices/pci@1e,600000/ide@d/sd@0,0:e,raw lrwxrwxrwx 1 root root 46 Aug 10 2004 c0t0d0s5 -> ../../devices/pci@1e,600000/ide@d/sd@0,0:f,raw lrwxrwxrwx 1 root root 46 Aug 10 2004 c0t0d0s6 -> ../../devices/pci@1e,600000/ide@d/sd@0,0:g,raw lrwxrwxrwx 1 root root 46 Aug 10 2004 c0t0d0s7 -> ../../devices/pci@1e,600000/ide@d/sd@0,0:h,raw
lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@0,0:a,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@0,0:b,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@0,0:c,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@0,0:d,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@0,0:e,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@0,0:f,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@0,0:g,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@0,0:h,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@1,0:a,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@1,0:b,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@1,0:c,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@1,0:d,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@1,0:e,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@1,0:f,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@1,0:g,raw lrwxrwxrwx 1 root root 47 Aug 10 ../../devices/pci@1c,600000/scsi@2/sd@1,0:h,raw
2004 c1t0d0s0 -> 2004 c1t0d0s1 -> 2004 c1t0d0s2 -> 2004 c1t0d0s3 -> 2004 c1t0d0s4 -> 2004 c1t0d0s5 -> 2004 c1t0d0s6 -> 2004 c1t0d0s7 -> 2004 c1t1d0s0 -> 2004 c1t1d0s1 -> 2004 c1t1d0s2 -> 2004 c1t1d0s3 -> 2004 c1t1d0s4 -> 2004 c1t1d0s5 -> 2004 c1t1d0s6 -> 2004 c1t1d0s7 ->
# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 /pci@1c,600000/scsi@2/sd@0,0 1. c1t1d0 /pci@1c,600000/scsi@2/sd@1,0 Specify disk (enter its number): # * * * * * * * * * * * *
prtvtoc /dev/rdsk/c1t0d0s2 /dev/rdsk/c1t0d0s2 partition map Dimensions: 512 bytes/sector 424 sectors/track 24 tracks/cylinder 10176 sectors/cylinder 14089 cylinders 14087 accessible cylinders Flags: 1: unmountable
* 10: read-only * * * Partition Tag 0 2 1 3 2 5 3 7 4 0 5 0 6 8 7 0 # * * * * * * * * * * * * * * * *
First Sector Last Flags Sector Count Sector 00 9514560 8191680 17706239 01 0 8395200 8395199 00 0 143349312 143349311 00 8466432 1048128 9514559 00 51266688 33560448 84827135 00 17706240 33560448 51266687 00 84827136 58522176 143349311 00 8395200 71232 8466431
Mount Directory
prtvtoc /dev/rdsk/c1t1d0s2 /dev/rdsk/c1t1d0s2 partition map Dimensions: 512 bytes/sector 424 sectors/track 24 tracks/cylinder 10176 sectors/cylinder 14089 cylinders 14087 accessible cylinders Flags: 1: unmountable 10: read-only Partition 0 1 2 3 4 5 6 7
Tag 2 3 5 7 0 0 8 0
First Sector Last Flags Sector Count Sector 00 9514560 8191680 17706239 01 0 8395200 8395199 00 0 143349312 143349311 00 8466432 1048128 9514559 00 51266688 33560448 84827135 00 17706240 33560448 51266687 00 84827136 58522176 143349311 00 8395200 71232 8466431
Mount Directory
#
Intel's x86 processors and their clones are little endian. Sun's SPARC,Motorola's 68K, and the PowerPC families are all big endian. Contents on AIX /dev: --------------------# ls -al .. .. crw------crw-rw-rwcrw-rw-rwcrw-rw-rw-
1 1 1 1
root root root root
system system system system
17, 22, 22, 22,
0 0 1 2
Aug May May May
08 27 27 27
12:00 17:45 17:45 17:45
tty0 ttyp0 ttyp1 ttyp2
.. .. brw-rw---brw-rw---brw-rw---brw-rw---brw-rw---brw-rw---brw------brw------brw------brw------brw------brw------brw------brw------.. ..
1 1 1 1 1 1 1 1 1 1 1 1 1 1
root root root root root root root root root root root root root root
system system system system system system system system system system system system system system
10, 10, 10, 10, 10, 10, 16, 16, 16, 16, 16, 16, 16, 16,
7 4 1 2 3 6 7 2 10 12 5 20 21 22
May Jun Aug May May May May May May May May May May May
27 27 08 27 27 27 27 27 27 27 27 27 27 27
17:46 15:51 11:41 17:46 17:46 17:46 17:44 17:44 18:23 18:23 17:44 18:23 18:23 18:23
hd3 hd4 hd5 hd6 hd8 hd9var hdisk0 hdisk1 hdisk10 hdisk11 hdisk2 hdisk20 hdisk21 hdisk22
The 'c' implies that the device is a character device, as opposed to a block device (b prefix) or ordinary file. RAID codes: =========== RAID ERROR CODE DESCRIPTIONS This document describes the various error codes returned by the Series 3 RAID controllers. On detection of an error condition, the controller will return a status of Check Condition on the command that had the error. The host should respond with a Request Sense command. On receipt of the Request Sense, the controller will return sense data, which includes the Sense Key, FRU Code, and ASC/ASCQ information, indicating the reason for the error condition. SENSE KEYS The possible Sense Keys returned by the RAID controller in the sense data, on receipt of a Request Sense command are shown below. The Sense Key is returned in byte 2 (zero-referenced) of the Request Sense data. The Sense Key may be thought of as a summary code for the error. More detailed information about the error is provided by the FRU and ASC/ASCQ codes described in the next sections. (0x00)-No Sense The controller has no errors to report at this time. (0x01)-Recovered Error The controller detected the error, but was able to recover from it. (0x02)-Not Ready The controller is in the process of finishing initialization, and will not allow hosts access to user data until it is ready.
(0x03)-Media Error A drive attached to the controller detected a media error on itself. (0x04)-Hardware Error This Sense Key is typically returned by the controller on most unrecoverable errors. (0x05)-Illegal Request A command was issued to the controller that is not allowed (for example, access to a non-existent logical unit). (0x06)-Unit Attention The controller is informing the host of an action it took to remedy an exception condition (for example, the controller marked a drive Failed, because the drive could no longer be accessed). (0x0B)-Aborted Command The controller could not finish the requested operation. However, in the typical scenario, it will have taken some action to ensure that the error condition would not occur again. Therefore, the next time this same command is received, the same error condition should not occur. (0x0E)-Miscompare A failed Verify operation, or a Verify with Parity Check operation failure will return a Sense Key of Miscompare. FIELD REPLACEABLE UNITS (FRU) CODE DEFINITIONS Each time an error is detected, the controller will put the Field Replaceable Unit (FRU) code of the failed component in the sense data (byte 14 (zero-referenced) in the sense data for the first error and bytes 26-33 (zero-referenced) for additional errors). To provide meaningful information for troubleshooting, the FRU codes have been grouped. The defined FRU groups are listed below. FRU Code 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09-0x0F 0x10-0xFF
Description Host Channel Group Controller Drive Interface Group Controller Buffer Group Controller ASIC Group Controller Other Group Subsystem Group Not Used Sub-enclosure Group Reserved Drive Groups
(0x01)-Host Channel Group This group consists of the host SCSI bus, its SCSI interface chip, and all initiators and other targets connected to the bus. (0x02)-Controller Drive Interface Group This group consists of the SCSI interface chips on the controller which connect to the drive buses. (0x03)-Controller Buffer Group This group consists of the controller logic used to implement the on-board data buffer.
(0x04)-Controller Array ASIC This group consists of the ASICs on the controller associated with the RAID functions. (0x05)-Controller Other Group This group consists of all controller-related hardware not associated with another group. (0x06)-Subsystem Group This group consists of subsystem components that are monitored by the RAID controller, such as power supplies, fans, thermal sensors, and AC power monitors. (0x08)-Sub-Enclosure Group This group consists of the devices such as power supplies, environmental monitor, and other subsystem components in the sub-enclosure. (0x10-0xFF)-Drive Group This group consists of a drive (embedded controller, drive electronics, and Head Disk Assembly), its power supply, and the SCSI cable that connects it to the controller; or supporting sub-enclosure environmental electronics. An FRU code denoting a drive contains the channel number (1-relative) in the upper nibble, and the drive's SCSI ID in the lower nibble. For example, a drive on the third channel, SCSI ID 2 would be denoted by an FRU code of 0x32. ADDITIONAL SENSE CODES AND QUALIFIERS This section lists the Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ) values returned by the RAID controller in the sense data. The ASC and ASCQ provide detailed information about the specific error. SCSI-2 defined codes are used whenever possible. Array specific error codes are used when necessary, and are assigned SCSI-2 vendor unique codes 0x80 to 0xFF. The most probable Sense Keys (listed below for reference) returned for each error are also listed in the table. Sense Keys of 6 in parentheses indicate that 6 (Unit Attention) would be the nominal Sense Key reported; however, the actual value would be that set in the "Sense Key for Vendor-unique Conditions" field in the User-configurable options of the NVSRAM. ASCs and ASCQs are normally returned in bytes 12 and 13 (zero-referenced) of the sense data. On multiple errors (defined as errors that occurred on the same command, not necessarily as errors that occurred simultaneously), there may be additional ASCs and ASCQs in the ASC/ASCQ stack, which are bytes 22-25 (zeroreferenced) of the sense data. In most cases, the first error detected is stored in bytes 12 and 13 of the sense data; subsequent errors are stored in the ASC/ASCQ stack. The following section lists all possible ASC/ASCQ combinations returned by the controller. ASC ASCQ Sense Key 00 00 0 No Additional Sense Information The controller has no errors to report for the requesting host and addressed logical unit combination. ASC 04
ASCQ 01
Sense Key 2
Logical Unit In Process Of Becoming Ready The controller is executing its initialization functions on the addressed logical unit. This includes drive spin-up and validation of the drive and logical unit configuration information. This error is normally returned on commands following the initial Inquiry command after a power-up/reset. ASC ASCQ Sense Key 04 02 2 Logical Unit Not Ready, Initializing Command Required The controller is configured to wait for a Start/Stop Unit command before spinning up the drives, but the command has not yet been received. ASC ASCQ Sense Key 04 04 2 Logical Unit Not Ready, Format In Progress The controller previously received a Format Unit command from an initiator, and is executing that command on this logical unit. Other commands cannot be sent to this logical unit until the Format Unit completes. ASC ASCQ Sense Key 04 81 02 Firmware Versions Incompatible The versions of firmware on the redundant controllers are incompatible/inconsistent. This is probably because you replaced a failed controller with a new controller that does not have the same version of firmware. Controllers with an incompatible version of firmware may cause unexpected results. Therefore, you must download new firmware as soon as possible. Use the Recovery Guru/Health Check in the Recovery Application to obtain instructions on how to download firmware to make the versions consistent. ASC ASCQ Sense Key 04 A1 2 Quiescence Is In Progress or Has Been Achieved ASC ASCQ Sense Key 0C 00 4,(6) Unrecoverable Write Error If this error is reported during normal operation, the controller has detected an error on a write operation to a drive, but was unable to recover from the error. The drive that failed the write operation will be marked Failed. If this error is reported just after a power loss has occurred, it indicates that the controller has detected that its batteries have been discharged. > If the power loss was for a reasonably long time, wait for the controller's batteries to be recharged. > If the power loss was for a very short time, the controller's cache holdup battery logic has failed. > If the controller has on-board batteries (such as a 3601 RAID controller), replace the controller. > If the controller has off-board batteries, check the battery hardware to ensure that there is no malfunction. ASC 0C
ASCQ 01
Sense Key 1
Write Error Recovered With Auto Reallocation The controller recovered a write operation to a drive. Auto reallocation may or may not have been used but this is the only standard ASC/ASCQ that tells the initiator that no further actions are required by the driver. The host need not take any action. ASC ASCQ Sense Key 0C 80 4,(6) Unrecovered Write Error Due To Possible Battery Discharge And Alternate Controller Failure If this error is reported during normal operation, it indicates that the controller had to synchronize and/or purge its cache due to configuration changes (such as logical unit deletion, addition or replacement), or if requested to do so by the host system, and the cache synchronization or purge failed for some reason. The user should restore any data that would have been lost. This error is also reported in the following situations at power-up: > The controller noted that it had dirty data in cache, and attempted to flush it to disk, but the flush operation failed. The dirty data will be lost. The user should restore any data that would have been lost. > If the controller had been in write-back caching mode with caching without batteries disabled and mirroring DISABLED: > The controller has detected that the batteries are either not physically present now, or they have fully discharged. Dirty user data in this controller's cache has been lost and the user must restore the dirty data. > If the controller has its own on-board batteries, the user should replace the controller with a good one, or if that is impossible, turn off writeback caching until the controller can be replaced. > If the controller has off-board batteries, the user should replace the batteries in the battery pack and ensure that the battery hardware is functioning normally. > If the controllers had been in write-back caching mode with caching without batteries disabled and mirroring ENABLED: > The controller has detected that its batteries, as well as those of the alternate controller are not functioning. Dirty user data in the cache has been lost and the user must restore the dirty data. The user must replace the controllers' batteries. > The controller has detected that it was newly swapped into this subsystem, and that it had dirty data in cache. The dirty data cannot be flushed to disk because it has been removed from its original subsystem. The user should ignore the error, since no data loss has occurred on this subsystem. > The controller has detected that its batteries are not functioning, and it had dirty cached data, and the alternate controller has been replaced by another controller (and therefore the mirrored copy of the cached data has been lost). Dirty user data in this controller's cache may have been lost and the user must restore the dirty data. The user must replace the controller's batteries. If possible, the user should swap-in the original alternate controller, so that the dirty data in that controller's cache may be reclaimed and flushed to disk. ASC ASCQ Sense Key 0C 81 4,(6) Deferred Unrecoverable Error Due To Memory Failure Recovery from a Data Cache error was unsuccessful. User data may have been lost. ASC
ASCQ
Sense Key
11 00 3 Unrecovered Read Error An unrecovered read operation to a drive occurred and the controller has no redundancy to recover the error. The error probably occurred in RAID 0 or Degraded RAID levels 1, 3, or 5. ASC ASCQ Sense Key 11 8A 3 Miscorrected Data Error - Due To Failed Drive Read A media error has occurred on a read operation during interrupted write processing. ASC ASCQ Sense Key 18 02 1 Recovered Data - Data Auto Reallocated The controller recovered a read operation to a drive. Auto reallocation may or may not have been used but this is the only standard ASC/ASCQ that tells the initiator that no further actions are required by the driver. The host need not take any action. ASC ASCQ Sense Key 1A 00 5 Parameter List Length Error A command was received by the controller that contained a parameter list and the list length in the CDB was less than the length necessary to transfer the data for the command. ASC ASCQ Sense Key 20 00 5 Invalid Command Operation Code The controller received a command from the initiator that it does not support. ASC ASCQ Sense Key 21 00 5 Logical Block Address Out Of Range The controller received a command that requested an operation at a logical block address beyond the capacity of the logical unit. This error could be in response to a request with an illegal starting address or a request that started at a valid logical block address and the number of blocks requested extended beyond the logical unit capacity. The user should check the capacity of the logical unit, and retry the command after correcting it. ASC ASCQ Sense Key 24 00 5 Invalid Field In CDB The controller received a command from the host with an unsupported value in one of the fields in the command block. ASC ASCQ Sense Key 25 00 5 Logical Unit Not Supported The addressed logical unit is currently not configured. An Add Logical Unit operation to the Logical Array Mode Page must be executed to define and configure the logical unit before it is accessible. ASC ASCQ Sense Key 26 00 5 Invalid Field In Parameter List
The controller received a command with a parameter list that contained an error. This error is typically returned on a Mode Select if: > an attempt was made to issue the Mode Select to a non-supported mode page. > an attempt was made to change a changeable mode page field with a Mode Select to an unsupported value. > an attempt was made to reconstruct a drive that is not part of any logical unit. The typical scenario in this case is the deletion of a Degraded logical unit, leaving the Failed drive marked Failed. > a Mode Select was issued to the Logical Array Page (page 2B) for a non-supported action (the "Action To Take" field was not set to a value 0x80-0x88). ASC ASCQ Sense Key 28 00 6 Not Ready To Ready Transition The controller has completed its initialization operations on the logical unit and it is now ready for access. This Unit Attention is used to notify hosts that the controller is ready to allow access to logical units. This notification is particularly useful if a host has exhausted its retry count soon after reset or power up. ASC ASCQ Sense Key 29 00 6 Power On, Reset, Or Bus Device Reset Occurred The controller has detected one of the above conditions. ASC ASCQ Sense Key 29 04 6 Device Internal Reset The controller has reset itself due to an internal error condition. progress have been lost.
Commands in
ASC ASCQ Sense Key 29 81 (6) Default Configuration Has Been Created The controller has completed the process of creating a default logical unit. There is now an accessible logical unit that did not exist previously. The host should execute its device scan to find the new logical unit. ASC ASCQ Sense Key 29 82 (6) Controller Firmware Synchronized The controller firmware was successfully synchronized with the replacement controller. ASC ASCQ Sense Key 2A 01 6 Mode Parameters Changed The controller received a request from another initiator to change the mode parameters for the addressed logical unit. This Check Condition is to notify the current initiator that the change occurred. This error may also be reported if the Mode Select parameters changed because of a cache synchronization error during the processing of the mode recent Mode Select request. The host should execute its device scan to determine the changes on the logical unit. ASC ASCQ Sense Key 2A 02 6 Log Parameters Changed
The controller received a request from another initiator to change the log parameters for the addressed logical unit. This Check Condition notifies the current initiator that the change occurred. The host should be aware that the other host may have cleared log parameters, such as the controller's performance statistics or its AEN log. ASC ASCQ Sense Key 2F 00 6 Commands Cleared By Another Initiator The controller received a Clear Queue message from another initiator. This Check Condition is to notify the current initiator that the controller cleared the current initiator's commands if it had any outstanding commands. If the host had outstanding commands, it should retry them. ASC ASCQ Sense Key 31 01 1,4 Format Command Failed A Format Unit command issued to a drive returned an unrecoverable error. The drive will be identified in the FRU code of the sense data. The user should replace the drive. ASC ASCQ Sense Key 32 00 4 Out Of Alternates A Re-assign Blocks command to a drive failed. The drive will be identified in the FRU code of the sense data. The user should replace the drive. ASC ASCQ Sense Key 3F 01 (6) Drive Microcode Changed The controller successfully downloaded new microcode to the specified drive, as requested by the host. This Unit Attention is used to notify the host that the Download Drive Microcode function completed successfully. ASC ASCQ Sense Key 3F 0E 6 Reported LUNs data has changed Previously LUN data reported via a Report LUNs command has changed(due to LUN creation/deletion or controller hot swap) ASC ASCQ Sense Key 3F 80 (6) Drive Failed Due To Write Failure The drive failed a write command to it. The user should replace the drive. ASC ASCQ Sense Key 3F 82 (6) Drive Failed Due To Format/Restore Failure The (previously-failed) drive was marked Failed due to either: (1) the drive failing a Format Unit command issued to it, or (2) the reconstruction on the drive failing due to the controller being unable to restore it (for example, an error occurring on another drive required for reconstruction). If the drive was marked Failed prior to reconstruction starting on it, the user should replace it. If the drive was Failed after reconstruction had begun, the drive was marked Failed because the controller could not reconstruct it. The user should format the entire logical unit, and then restore data from the last good tape backup. ASC
ASCQ
Sense Key
3F 83 (6) Drive Encountered Error During Reconstruction An error occurred in a read operation on this drive while attempting to reconstruct data for a (different) replaced drive. The replaced drive will be marked Failed, but this drive will not. The user should replace this drive, then format the entire logical unit, and restore data from the last good tape backup. ASC ASCQ Sense Key 3F 85 (6) Drive Failed Due To No Response The drive failed a Read Capacity or Read command at Start Of Day. The controller was unable to read the RAID subsystem configuration information stored on it. The user should replace the drive. ASC ASCQ Sense Key 3F 86 (6) Drive Failed Due To Format Failure The drive failed either a Format Unit command, or a Write operation (issued when a logical unit was formatted). The user should replace the drive. ASC ASCQ Sense Key 3F 87 (6) Drive User-Failed Via Mode Select The drive was manually failed by the user.
The user should replace the drive.
ASC ASCQ Sense Key 3F 89 (6) Wrong Drive Removed/Replaced The user hot-removed a non-Failed drive. If the controller has not marked the drive Failed yet, the user should re-insert the drive as soon as possible. If the drive has been marked Failed, the user should replace it. ASC ASCQ Sense Key 3F 8B (6) Drive Capacity Less Than Minimum The drive is not large enough to support all the logical units that must be reconstructed on it. The user should replace the drive with a larger capacity drive. ASC ASCQ Sense Key 3F 8C (6) Drive Has Wrong Block Size The drive's block size does not match that of the other drives in the logical unit. The user should either: (1) issue a Mode Select command to the controller directing it to first format, and then reconstruct the drive, or (2) replace this drive with another drive pre-formatted to the block size used by all of the other drives in the logical unit. ASC ASCQ Sense Key 3F 8D (6) Drive Failed - Controller Storage Failure The controller was unable to access or store internal RAID subsystem configuration information on the drive. The user should replace the drive. ASC ASCQ Sense Key 3F 8E (6) Drive Failed - Reconstruction Failure A drive failed due to a reconstruction failure at Start of Day (SOD).
ASC ASCQ Sense Key 3F 98 (6) Drive Marked Offline Due To Internal Recovery Procedure An error has occurred during interrupted write processing causing the LUN to transition to the Dead state. Drives in the drive group that did not experience the read error will transition to the Offline state (0x0B) and log this error. ASC ASCQ Sense Key 3F BD (6) Drive Has Incorrect Critical Parameters Set The controller was unable to query the drive for its current critical mode page settings, or was unable to change these to the correct setting. Currently, this indicates the Qerr bit is set incorrectly on the drive specified in the FRU field of the Request Sense data. ASC ASCQ Sense Key 3F C3 (6) Channel Failure The controller failed a channel, and will not access drives on this channel any more. The FRU Group Qualifier (byte 26) in the sense data will indicate the 1relative channel number of the failed channel. This condition is typically caused by a drive ignoring SCSI protocol on one of the controller's destination channels. The controller typically fails a channel if it issued a reset on a channel, and it continued to see drives ignore the SCSI Bus Reset on this channel. ASC ASCQ Sense Key 3F C7 (6) Non-Media Component Failure (1) A subsystem component other than a drive or controller has failed (for example, fan, power supply, battery) or (2) An over-temperature condition has occurred (some RAID modules contain a temperature sensor). The fans, power supplies, and battery are usually located in the controller module tray. The FRU codes will indicate the faulty component. The user should replace the component indicated. ASC ASCQ Sense Key 3F C8 (6) AC Power Fail The Uninterruptible Power Source (UPS) has indicated that AC power is no longer present and the UPS has switched to standby power. While there is no immediate cause for concern, users should save their work frequently, in case the battery is suddenly depleted. ASC ASCQ Sense Key 3F C9 (6) Standby Power Depletion Imminent The Uninterruptible Power Source (UPS) has indicated that its standby power source is nearing depletion. The host should take actions to stop IO activity to the controller. Normally, the controller will change from a write-back caching mode to a write-through mode. The user should not change again to write-back mode until full AC power has been restored. ASC ASCQ Sense Key 3F CA (6) Standby Power Source Not At Full Capacity The Uninterruptible Power Source (UPS) has indicated that its standby power source is not at full capacity. To prevent loss of data in the event of the failure of
AC power, the user should not activate write-back caching mode until full UPS power has been restored. ASC ASCQ Sense Key 3F CB (6) AC Power Has Been Restored The Uninterruptible Power Source (UPS) has indicated that AC power is now being used to supply power to the controller. ASC ASCQ Sense Key 3F D0 (6) Write-Back Cache Battery Discharged The controller has detected that its battery is no longer charged. If a power failure were to occur, any dirty user data in cache will be lost. To prevent the loss of any user data, the user should either: (1) replace this controller with another, or (2) turn off write-back cache. ASC ASCQ Sense Key 3F D1 (6) Write-Back Cache Battery Charged The controller has detected that its battery is now fully charged, and will be capable of holding up the cache contents in the event of a power failure. The user may switch to write-back mode, if desired. ASC ASCQ Sense Key 3F D8 (6) Battery Reached Expiration The controller has failed the battery because the battery has reached its expirations date. You should replace the battery as soon as possible. ASC ASCQ Sense Key 3F D9 (6) Battery Near Expiration The controller has detected that the battery is nearing its expiration date. You should replace the battery as soon as possible. ASC ASCQ Sense Key 3F E0 (6) Logical Unit Failure The controller has placed the logical unit in a "Dead" state. User data and/or parity can no longer be maintained to ensure availability. The most likely cause is the failure of a single drive in non-redundant configurations or a second drive in a configuration protected by one drive. The data on the logical unit is no longer accessible. ASC ASCQ Sense Key 3F EB (6) LUN Marked Dead Due To Media Error Failure An error has occurred during interrupted write processing during Start of Day causing the LUN to transition to the Dead state. ASC ASCQ Sense Key 40 NN 4,(6) Diagnostic Failure On Component NN (0x80 - 0xFF) The controller has detected the failure of an internal controller component. This failure may have been detected during operation as well as during an on-board diagnostic routine. The values of NN supported in this release are listed as follows:
> 80 - Processor RAM > 81 - RAID buffer > 82 - NVSRAM > 83 - RAID Parity Assist (RPA) chip > 84 - Battery-backed NVSRAM or clock failure > 91 - Diagnostic self test failed non-data transfer components test most likely controller cache holdup battery discharge) > 92 - Diagnostic self test failed data transfer components test > 93 - Diagnostic self test failed drive Read/Write Buffer data turnaround test > 94 - Diagnostic self test failed drive Inquiry access test > 95 - Diagnostic self test failed drive Read/Write data turnaround test > 96 - Diagnostic self test failed drive self test In a dual controller environment, (hold in reset) (unless the error case the user should wait for the environments, the user should not replaced.
the user should place this controller offline indicates controller battery failure, in which batteries to recharge). In single controller use this subsystem until the controller has been
ASC ASCQ Sense Key 43 00 4 Message Error The controller attempted to send a message to the host, but the host responded with a Reject message. ASC ASCQ Sense Key 44 00 4,B Internal Target Failure The controller has detected a hardware or software condition that does not allow the requested command to be completed. If the Sense Key is 0x04 indicating a Hardware Failure, the controller has detected what it believes is a fatal hardware or software failure and it is unlikely that just a retry of the command would be successful. If the Sense Key is 0x0B indicating an Aborted Command, the controller has detected what it believes is a temporary software failure that is likely to be recovered if retried. ASC ASCQ Sense Key 45 00 4 Selection Time-out On A Destination Bus A drive did not respond to selection within a selection time-out period. Possible reasons for this error include drive failure, channel failure, or the possibility of an incomplete hot-swap holding the whole channel in reset. ASC ASCQ Sense Key 47 00 1,B SCSI Parity Error The controller detected a parity error on the host SCSI bus or one of the drive SCSI buses. ASC ASCQ Sense Key 48 00 1,B Initiator Detected Error Message Received The controller received an Initiator Detected Error Message from the host during the operation. ASC ASCQ Sense Key 49 00 B Invalid Message Error
The controller received a message from the host that is not supported or was out of context when received. ASC ASCQ Sense Key 49 80 B Drive Reported Reservation Conflict A drive returned a status of Reservation Conflict. ASC ASCQ Sense Key 4B 00 1,4 Data Phase Error The controller encountered an error while transferring data to/from the initiator or to/from one of the drives. ASC ASCQ Sense Key 4E 00 B Overlapped Commands Attempted The controller received a tagged command while it had an untagged command pending from the same initiator, or it received an untagged command while it had a tagged command(s) pending from the same initiator. ASC ASCQ Sense Key 5D 80 6 Drive Reported PFA (Predicted Failure Analysis) Condition Policies for drive-predicted failure notifications vary depending on such factors as performance and availability requirements, RAID level, and use of Hot Spare drives. If you intend to replace the drive in advance of failure, you MUST first fix any components that have a Failed status. Failure to do so may result in data loss. If the drive is contained in a RAID 0 LUN, back up your data BEFORE failing the drive. Fail the indicated drive using Options>>Manual Recovery>>Drives>>Fail in the Recovery Application (its fault LED will turn ON). Then replace it with a spare drive of adequate capacity. For RAID 0 LUNs, you must re-format the affected LUNs and restore data from your back up. For all other RAID levels, the data on the drive will be reconstructed upon replacing the drive. Contact your Customer Support Representative if you have questions. ASC ASCQ Sense Key 5D 90 6 Controller Reported PFA (Predicted Failure Analysis) Condition This ASC/ASCQ only applies to SCSI drive side buses. It is only returned when the feature is enabled in the NVSRAM options. Specifically, byte 35 bit 3 must be set to 1 to enable this feature. When enabled, the controller reports this as an AEN. For a given bus, if the controller detects 5 bus errors or 3 timeout errors within 40 seconds, this AEN is posted. The period is measured beginning with the first bus error or timeout. At the end of the 40 seconds, if the required number of errors has not occurred, the counters are cleared. Any further events will start a new period. The bus errors include: 1> Unexpected bus phase error 2> Unexpected disconnect 3> Bus parity error 4> Bad transfer 5> Unexpected message 6> Bad message Timeout errors are counted in the general count of 5 bus errors, but they can also
trigger this condition if 3 timeout errors are seen during the period. Timeout errors include: 1> Timeouts 2> Drive reported ASC/ASCQ 15 01 mechanical positioning error When this AEN is reported, the user should replace the cable. If that fails to resolve the problem, they should examine the host error log to see if a single component (a drive or an ESM) seems to be causing the problem. If so, it should be replaced. If not, replace the controller. ASC ASCQ Sense Key 80 02 4 Bad ASC Code detected by Error/Event Logger ASC ASCQ Sense Key 80 03 4 Error Occurred During Data Transfer From SRM Host ASC ASCQ Sense Key 84 00 4 Operation Cannot Be Completed With LUN In Its Current State The requested command or Mode Select operation is not allowed with the logical unit in the state indicated in byte 76 of the sense data. Typically, the controller will return this error if: > A Repair Parity, Write And Verify With Parity Check, or Reassign Blocks command was issued to the logical unit, but the logical unit is either in the Degraded or Reconstructing state. > A Test Unit Ready was issued to a Dead logical unit, and the NVSRAM option that directs the controller to return a Good status in this case has not been enabled. > A user data access command (Read or Write) was issued to a Dead logical unit. > The user attempted to replace a logical unit, but the logical unit is currently in the Reconstructing state. > The user attempted to add a logical unit, but the specified logical unit already exists. > The user attempted to check available capacity for logical unit addition, but no logical unit exists on the specified set of drives. > The user attempted to delete, modify, replace or format a non-existent logical unit. ASC ASCQ Sense Key 84 06 4 Logical Unit Awaiting Format A Mode Select has successfully completed to create a logical unit, but the logical unit has not been formatted. ASC ASCQ Sense Key 85 01 4 Drive IO Request Aborted IO issued to failed or missing drive due to recently failed removed drive. This error can occur as a result of IOs in progress at the time of a failed or removed
drive. ASC ASCQ Sense Key 87 00 4 Microcode Download Error The controller detected an error while downloading microcode and storing it in non-volatile memory. ASC ASCQ Sense Key 87 08 4 Microcode Download Error Incompatible board type for the code downloaded. ASC ASCQ Sense Key 87 0E 6 Controller Configuration Definition Inconsistent with Alternate Controller ASC ASCQ Sense Key 88 0A (6) Subsystem Monitor NVSRAM Values Configured Incorrectly The controller detected an error in the configuration of the Subsystem Fault region of the NVSRAM. This error means that the controller either cannot turn on or turn off the desired Fault LEDs. ASC ASCQ Sense Key 8A 00 5 Illegal Command For Drive Access The initiator attempted to pass a command through to a drive that is not allowed. The command could have been sent in pass-through mode or by attempting to download drive microcode. ASC ASCQ Sense Key 8A 01 5 Illegal Command For The Current RAID Level The controller received a command that cannot be executed on the logical unit due to its RAID level configuration. Examples are parity verify or repair operations on a RAID 0 logical unit. The user should check the command being attempted, and ensure that it is being issued to a logical unit configured to an appropriate RAID level. ASC ASCQ Sense Key 8A 10 5 Cannot Perform Modification - Non-standard Segment Size/Insufficient Resources Could not perform the modification because either (1) some or all of the LUNs in the group have non-standard segment sizes or (2) the RAID controller doesn't have sufficient resources to perform it. For Cause #1: Check the segment sizes of the LUNs by using Module Profile>>LUNs. The standard segment sizes (in blocks) are: 16, 32, 64, 128, 256, and 512. If some of the LUNs in the group have non-standard segment sizes, the only way to complete the modification operation is to back up the data, delete these LUNs, and recreate them with the desired RAID level, number of drives, and segment size. For Cause #2: If the LUNs in the group have standard segment sizes, use Options>>Modify Group/LUN>>Segment Size in Configuration and attempt to select a smaller size and retry the modification operation. If the modification operation fails again, the
only way to complete the modification operation is to back up the data, delete these LUNs, and recreate them with the desired RAID level, number of drives, and segment size. ASC ASCQ Sense Key 8B 02 B,(6) Quiescence Is In Progress Or Has Been Achieved The addressed logical unit has been quiescent. Redundant controller mode changes or logical unit ownership transfers will be, or already are in progress. ASC ASCQ Sense Key 8B 03 B Quiescence Could Not Be Achieved Within The Quiescence Timeout Period It was not possible to make the requested logical units quiescent within the specified period. The make-quiescent attempt has been aborted, and controller mode changes, or logical unit ownership transfers will not be attempted. ASC ASCQ Sense Key 8B 04 5 Quiescence Is Not Allowed It is not possible to make the requested logical units quiescent at this time, probably because another initiator has already requested quiescence in anticipation of a redundant controller mode change, or a logical unit ownership transfer. ASC ASCQ Sense Key 8E 01 E,(6) A Parity/Data Mismatch Was Detected The controller detected inconsistent parity/data during a parity verification. ASC ASCQ Sense Key 91 00 5 General Mode Select Error An error was encountered while processing a Mode Select command. returned for the following reasons:
This error could
> An invalid "Action To Take" value was set in the Mode Select page. > An attempt was made to clear all drive and logical unit configurations by issuing a "CLEAR" to the Redundant Controller Mode Page, but the Mode Select was sent to the controller with the lower drive-side SCSI ID. > The controller could not save configuration information to the drives when a logical unit was added or replaced. The user should verify that the drives' hardware is functioning correctly, or replace the drive listed in the FRU code. > The controller could not spin up a drive that the user manually added via the "Add Drive" operation via a Mode Select to the Physical Array Page. The user should verify that the drive's hardware is functioning correctly, or replace the drive. > The controller could not mark a failed drive Optimal, if the user wished to do so via a Mode Select to the Physical Array Page. > The user attempted to mark failed an Optimal drive in an already-Dead LUN. > The user attempted to mark a failed drive as Replaced, but the controller could not access the failed drive. The user should verify that the drive's hardware is
functioning correctly, or replace the drive. > The user attempted to mark a failed drive as Replaced in a logical unit that is either Dead or formatting. The user should bring the logical unit to the appropriate state before attempting the operation again. > The user requested the controller to initiate a parity scan on all logical units, but the controller is the Passive controller. The user should retry the operation via the Active controller. > The user requested an operation that caused the controller to synchronize and purge its cache (such as logical unit addition, deletion, or replacement, a transfer of ownership of the logical unit from one controller to another, or a change in the redundant controller mode of operation), but either the synchronize or the purge of the cache failed. ASC ASCQ Sense Key 91 03 5 Illegal Operation For Current Drive State A drive operation was requested through a Mode Select that cannot be executed due to the state of the drive. This error could be returned for the following reasons: > The user attempted to mark a non-existent drive as Optimal, Failed, Non-existent or Replaced, or assign or deassign the non-existent drive as Global Hot Spare. > The user attempted to operate on a drive on a non-supported channel or SCSI ID. For example, attempting to "Add a Drive" to channel 7 on a 5-channel RAID controller. > The user attempted to add or replace a logical unit on a drive that is neither in an Optimal (but not Global Hot Spare) nor Spare state. > The user attempted to reassign blocks on a non-existent drive. > The user attempted to format a logical unit which has missing drives in it. > The user attempted to format a logical unit which exists on a set of drives that have SubLUNs on them. > The user attempted to mark a reconstructing drive (status of Replaced) as Optimal. > The user attempted to mark a non-failed drive as Replaced. > The user attempted to delete a drive, but the drive was not marked unassigned (it belongs to a logical unit). > The user attempted to revive a logical unit that (1) is not currently marked Dead, (2) has missing drives in it, (3) has drives in it that are marked Wrong Drive Replaced, or (4) has multiple drives that are marked Failed, but not all of the failed drives are on the same channel. > The user attempted to download drive firmware to a drive that is not owned by this controller, or the drive is either Non-existent or has been removed. > The user attempted to mark a failed drive as Replaced, but the drive's capacity is too small to support the logical units configured on the drive group.
> The user attempted to mark a drive as Replace, Format And Reconstruct that is neither in the Failed or Replaced states. ASC ASCQ Sense Key 91 09 5 Illegal Operation With Multiple SubLUNs Defined An operation was requested that cannot be executed when multiple SubLUNs are defined on the drive. This error could be returned for the following reasons: > The user attempted to add or replace a SubLUN on a drive group which is configured with logical units configured to a different RAID level. > The user attempted to add or replace a SubLUN on a drive group which its drives are not in the same sequence as that for the other SubLUNs on them. > The user attempted to let one controller take over the ownership of certain SubLUNs, but all SubLUNs on the affected drive group were not transferred. ASC ASCQ Sense Key 91 33 5 Illegal Operation For Controller State The requested Mode Select operation could not be completed due to the current state of the controller. This error could be returned for the following reasons: > The user attempted to fail or unfail the alternate controller, but the current controller is in the Passive mode of operation. > The user attempted to switch from Active-Passive mode of operation to ActiveActive mode, but this is a single controller system. > The user attempted to direct this controller to fail the alternate controller, but the alternate controller still owns some of the configured logical units. ASC ASCQ Sense Key 91 36 5 Command Lock Violation The controller received a Write Buffer Download Microcode, Send Diagnostic, or Mode Select command, but only one such command is allowed at a time and there was another such command active. ASC ASCQ Sense Key 91 3B 6 Improper LUN Definition for Auto-LUN Transfer mode - ALT is disabled Controller will operate in normal redundant controller mode without performing Auto-LUN transfers. ASC ASCQ Sense Key 91 50 5 Illegal Operation For Drive Group State An operation was requested that cannot be executed because of the current state of the drive group (such as a modification operation being performed). ASC ASCQ Sense Key 91 51 5 Cannot Perform Modification - Insufficient Reserved Capacity A modification operation (RAID level, segment size, capacity expansion, or defragmentation) could not be performed because there is insufficient capacity
reserved on each drive for internal configuration purposes. If you want to complete this modification, the only solution is to back up the data on the drive group's LUNs, delete the LUNs, and recreate them with the desired RAID level, number of drives, and segment size. NOTE: There may be a decrease in drive group capacity when recreating the LUNs (about 38 MB per drive), since this drive group was originally created with pre2.05 controller firmware and release 3.X controller firmware requires more reserved capacity per drive for internal configuration purposes. ASC ASCQ Sense Key 91 53 5 Illegal Reconfiguration Request - Legacy Constraint Command could not be completed due to Legacy configuration or definition constraints. ASC ASCQ Sense Key 94 01 5 Invalid Request Due To Current LUN Ownership The operation is not allowed because the controller does not own the logical unit. The user should change the logical unit's owner, or attempt the operation from the owning controller. ASC ASCQ Sense Key 95 01 4 Extended Drive Insertion/Removal Signal The controller has detected that the drive insertion/removal signal is permanently active. The user should ensure that the drives on the affected channel are properly seated. ASC ASCQ Sense Key 95 02 (6) Controller Removal/Replacement Detected The controller detected the activation of the signal(s) used to indicate that the alternate controller has been removed or replaced. ASC ASCQ Sense Key 98 01 (6) Multiple Drive Trays With Same ID The controller has determined that there are multiple drive trays with the same ID selected. The user should ensure that each drive tray has a unique ID setting. ASC ASCQ Sense Key A0 00 (6) Write-Back Cache (With Mirroring) Could Not Be Enabled The user requested the controller to enable write-back cache, but the controller was unable to do so because: > A battery was charging after a power cycle. If the RAID Module was power cycled, the user should wait approximately 12 to 15 minutes. The caching should be enabled again. > Mirroring was requested, but this controller cannot do so because: (1) its batteries are not operational, and the cache-without-batteries (CWOB) feature is disabled, or (2) its batteries are not present, and the CWOB feature is disabled, or (3) the alternate controller's batteries are either not present or not operational,
and the CWOB feature is disabled. The user should replace this controller with another one, or should turn off write-back caching. > The controller was mirroring data, and the Force Write Through on Two Minute Warning bit (FWT) is set, and it has now detected a two minute warning from the UPS. It will now transition to write-through mode until full AC power has been restored. The user should not re-enable write-back caching until full AC power is restored. > Mirroring was requested, but the alternate controller is not ready to mirror. The user should ensure that the alternate controller is present in the RAID Module and that it is functional. > The controller was mirroring data, and now detects that the mirrors are out of synchronization, because: (1) a mirror operation failed, or (2) the alternate controller was removed. The user should ensure that the alternate controller is present in the RAID Module and that it is functional. ASC ASCQ Sense Key A1 00 (6) Write-Back Cache (With Mirroring) Could Not Be Enabled - Cache Size Mismatch The controller will not allow mirroring to be enabled if the alternate controller's cache size is different. The user must ensure that both controllers in the subsystem have the same cache size. ASC ASCQ Sense Key A4 00 (6) Global Hot Spare Drive Smaller Than At Least One Drive In The Subsystem A drive designated as Global Hot Spare does not have the capacity to cover all of the drives in the RAID subsystem. The user should attempt to ensure that the Global Hot Spare drive has a capacity as large as the largest capacity drive in the RAID subsystem. Note that the Global Hot Spare drive will still be used to cover any smaller capacity drives. ASC ASCQ Sense Key A6 00 (6) Recovered Processor Memory Failure The controller has detected and corrected a recoverable error in processor memory. ASC ASCQ Sense Key A7 00 (6) Recovered Data Buffer Memory Error The controller has detected and corrected a recoverable error in the data buffer memory. Sense bytes 34-36 will contain the count of errors encountered and recovered. ASC ASCQ Sense Key C0 00 4,(6) The Inter-controller Communications Channel Has Failed The controller has detected the failure of the communications link between the redundant controllers. A switch to Active-Active mode of operation will not be allowed. ASC D0
ASCQ 06
Sense Key 4
Drive IO Time-Out The controller destination IO timer expired while waiting for a drive command to complete. This error is possible if the drive's power was suddenly turned off, or if there is an extended reset on the channel due to an incomplete drive removal/insertion. The user should check that the drive is still powered up. If there was a drive removal/insertion on this channel a few seconds ago, the user should ensure that the drive is completely seated in the subsystem. ASC ASCQ Sense Key D1 0A 4 Drive Reported Busy Status A drive returned a Busy status in response to a command. ASC ASCQ Sense Key E0 XX 4 Destination Channel Error If XX = 00 - 07, it indicates the Sense Key returned by the drive after a Check Condition status. If XX = 10, it indicates that a bus level error occurred. If the same error continues to be returned, the user should replace the drive.
========================= 8. Current machines 2005: ========================= 8.1 AIX machines: ================= 1. eServer p5 family: --------------------p5-510 p5-520 p5-550 p5-570
dimensions Express 19" 2U Express 19" 4U or deskside Express 19" 4U or deskside Express 19" rack
p5-510 p5-520 * p5-550 p5-570 p5-575 p5-590 p5-595
cpu 1 or 2 1 or 2 1,2,4 2,4,8
Ghz 1.5 1.5 1.5 1.5
dimensions 19" 2U 19" 4U or deskside 19" 4U or deskside 19" rack
cpu 1 or 2 2 1,2 or 4 2,4,8,12,16
Ghz Max mem GB 1.65 32 1.65 32 1.5 or 1.65 64 1.65 or 1.90 128
dimensions 24" frame 24" frame 24" frame
cpu 8 8 to 32 16 to 64
Ghz Max mem GB 1.90 256 1.65 256 1.65 or 1.90 256 / 512
More info on the 550: --------------------5 hotplug PCI slots, 1 embedded Ultra 320 SCSI dual channel controller,
Max mem GB 32 32 64 128
1 10/100/1000 Mbps integrated dual port Ethernet controller, 2 service processor communications port, 2 USB 2 ports, 2 HMC ports, 2 RIO ports = Remote IO ports, e.g. for connecting the system to an external drawer 2 System Power Control Network SPCN ports 1 or 2 hotswap capable 4-diskbays. 4x146 or 8x 146 GB Ultra320 scsi disks SPCN interface: System Power Control Network is a microprocessor based operating system that controls all aspects of the IBM power network, including power on/off, sequencing, fru isolation, battery testing etc.. So SPCN is used for power control RIO interface: for connecting the system to external drawer. SPC interface: Service Processor Communications port. Can be used to connect a terminal. 8.2 former pSeries: =================== - pSeries 655 (Rack-mount) Easy-to-manage 4- or 8-way ultra-dense cluster-optimized server for HPC and BI. Processor 64-bit POWER4+ Clock rates (Min/Max) 1.50GHz / 1.70GHz System memory (Std/Max) 4GB / 64GB Internal storage (Std/Max) 72.8GB / 2.6TB Performance (rPerf range)*** 15.22 to 21.87 - pSeries 670 (Rack-mount) The 4- to 16-way p670 is packed with the same Capacity on Demand (CoD) capabilities and innovative technology as the flagship p690. Processor POWER4+ Clock rates (Min/Max) 1.50GHz System memory (Std/Max) 4GB / 256GB Internal storage (Std/Max) 72.8GB / 7.0TB Performance (rPerf range)*** 13.66 to 46.79 - pSeries 690 8- to 32-way enterprise-class AIX 5L/Linux server Processor 64-bit POWER4+ Clock rates (Min/Max) 1.50GHz / 1.90GHz System memory (Std/Max) 8GB / 1TB Internal storage (Std/Max) 72.8GB / 18.7TB Performance (rPerf range)*** 27.11 to 104.17
8.3 Recent Sun machines: ======================== Sun Fire High-End: -----------------Sun Fire High-end Servers Sun's flagship servers powered by the new UltraSPARC IV+ processors work with the Solaris Operating System to offer a stellar enterprise consolidation platform for customers: over five times greater performance, doubled memory capacity and significantly increased I/O performance over previous generation systems. Compatible with multiple platforms and CPU speeds, the Solaris 10 OS allows customers to quickly and easily take advantage of the latest server technology and the industry's only true technology systems investment protection. Sun Fire E20K High-end computing, affordability, and scalability: The Sun Fire E20K server gives you 36 UltraSPARC IV+ processors and 72 simultaneous threads, with mainframe class reliability and security. Later, scale it up to the full Sun Fire E25K capacities. Scales up to 36 UltraSPARC IV+ processors with 72 threads, over 5x faster performance over UltraSPARC III processor-based servers Doubled memory capacity with 2GB DIMMs: 576 GB memory Unique Uniboard technology to provision up to 9 CPU/Memory Uniboards on the fly Easily upgraded up to 72 processors with 144 threads and over 1TB memory High-bandwidth PCI-X support for I/O intensive applications Mix and match UltraSPARC III, IV and IV+ processors in the same system Dynamic System Domains and Solaris Containers Predictive Self-Healing/Automatic System Recovery Solaris Security Toolkit Capacity on Demand 2.0 to add resources only when needed Solaris 9 9/05 and Solaris 10 3/05 HW1 Sun Fire E25K Scales up to 72 UltraSPARC IV+ processors with 144 threads, over 5x faster performance compared to UltraSPARC III processor-based servers Doubled memory capacity with 2GB DIMMs: over 1TB memory Unique Uniboard technology to provision up to 18 CPU/Memory Uniboards on the fly High-bandwidth PCI-X support for I/O intensive applications Mix and match UltraSPARC III, IV and IV+ processors in the same system Dynamic System Domains and Solaris Containers Predictive Self-Healing/Automatic System Recovery Solaris Security Toolkit Capacity on Demand 2.0 to add resources only when needed Solaris 9 9/05 and Solaris 10 3/05 HW1
Sun Fire Mid-Range: ------------------Sun Fire Midrange Servers Designed for compute density backed by enterprise-class features, Sun's midrange servers deliver high performance and protect your IT investments over time. Sun has enhanced the industry's leading 64-bit server line with the UltraSPARC IV+ processor, offering up to five times the performance of previous UltraSPARC III systems. Yet you retain Sun's migration-enabling unbroken binary application compatibility with the Solaris OS. Sun Fire V490 Scales up to four processors, eight simultaneous compute threads Sun Fire V890 Scales up to eight processors, 16 simultaneous compute threads Sun Fire E2900 Scales up to 12 processors, 24 simultaneous compute threads Sun Fire E4900 Scales up to 12 processors, 24 simultaneous compute threads Sun Fire E6900 Scales up to 24 processors, 48 simultaneous compute threads Sun Fire Low-End: ----------------V125 V215 V245 V445 V210 V240 etc.. Sun Fire x64 Servers: --------------------These servers can run many operating system, including Solaris OS, Linux, Windows or VMware. These are the Sun Blade machines. 8.4 Recent HP Servers: ====================== � HP ProLiant servers � HP ProLiant DL � HP ProLiant ML
� HP ProLiant BL blades � � � � �
HP Integrity servers Entry-class Mid-range Superdome (high-end) HP Integrity BL blades
� � � � �
HP Integrity NonStop servers HP 9000 servers HP AlphaServer systems Telco and carrier-grade servers HP e3000 servers
HP servers running HP-UX 11i : � HP 9000 servers PA-RISC powered servers � HP Integrity servers Industry standard Itanium� 2 based servers � HP Telco servers For the telecom and service provider industries
======================================= 9. Most important pSeries LED Codes: ======================================= MCA LED codes: -------------Booting BIST Booting POST LED 200: key LED 299: BLV
phase: leds 100-195, defining hardware status phase: leds 200-2E7, during finding BLV in secure position will be loaded
PCI systems an pSeries LED codes: --------------------------------reduced ODM from BLV copied into RAMFS: OK=510, NOT OK=LED 548: LED 511: bootinfo -b is called to determine the last bootdevice ipl_varyon of rootvg: OK=517,ELSE 551,552,554,556: LED 555,557: mount /dev/hd4 on temporary mountpoint /mnt LED 518: mount /usr, /var LED 553: syncvg rootvg, or inittab problem LED 549 LED 581: tcp/ip is being configured, and there is some problem
Last phases in the boot is where cfgcon is called, to configure the console. cfgcon LED codes include: C31: Console not yet configured. C32: Console is an LFT terminal C33: Console is a TTY C34: Console is a file on disk C99: Could not detect a console device LED 551: ipl_varyon of rootvg 201 223-229 551,555,557 552,554,556 553
: : : : :
Damaged boot image Invalid boot list Corrupted filesystem, corrupted JFS log Superblock corrupted, corrupted customized ODM database Corrupted /etc/inittab file
Firmware that leads to LED code: -------------------------------LED Code 888 right after boot: software problem 102, OR, hardware or software problem 103 rc.boot LED codes: -----------------rc.boot1 init restbase cfgmgr -f bootinfo -b end rc.boot 1
success=F05 error=c06 copies bootimage ODM -> RAM fs ODM: success=510 error=548 configuration all base devices needed to access rootvg LED=511
PCI / RS6000 LED Codes: ======================== ============= 1. Built-In Self-Test (BIST) Indicators -----------------------------------100 101 102 103 104 105 106 111 112 113
BIST completed successfully; control was passed to IPL ROS. BIST started following reset. BIST started, following the system unit's power-on reset. BIST could not determine the system model number. Equipment conflict; BIST could not find the CBA. BIST could not read from the OCS EPROM. BIST failed: CBA not found OCS stopped; BIST detected a module error. A checkstop occurred during BIST; checkstop results could not be logged out. Three checkstops have occurred.
120 121 122 123 124 125 126 127 130 140 142 143 144 151 152 153 154 160 161 162 163 164 165 166 170 180 182 185 186 187 195 199 888
BIST starting a CRC check on the 8752 EPROM. BIST detected a bad CRC in the first 32K bytes of the OCS EPROM. BIST started a CRC check on the first 32K bytes of the OCS EPROM. BIST detected a bad CRC on the OCS area of NVRAM. BIST started a CRC check on the OCS area of NVRAM. BIST detected a bad CRC on the time-of-day area of NVRAM. BIST started a CRC check on the time-of-day area of NVRAM. BIST detected a bad CRC on the 8752 EPROM. BIST presence test started. Running BIST. (Box Manufacturing Mode Only) Box manufacturing mode operation. Invalid memory configuration. Manufacturing test failure. BIST started AIPGM test code. BIST started DCLST test code. BIST started ACLST test code. BIST started AST test code. Bad EPOW Signal/Power status signal. BIST being conducted on BUMP I/O. BIST being conducted on JTAG. BIST being conducted on Direct I/O. BIST being conducted on CPU. BIST being conducted on DCB and Memory. BIST being conducted on Interrupts. BIST being conducted on Multi-Processors. Logout in progress. BIST COP bus not responding. A checkstop condition occurred during the BIST. System logic-generated checkstop (Model 250 only). Graphics-generated checkstop (Model 250). Checkstop logout complete Generic SCSI backplane BIST did not start.
Power-On Self-Test (POST) Indicators -----------------------------------200 201 202 203 204 205 206 207 208 209 20c 210 211 212 213 214 215 216 217 218 219
IPL attempted with keylock in the Secure position. IPL ROM test failed or checkstop occurred (irrecoverable). Unexpected machine check interrupt. Unexpected data storage interrupt. Unexpected instruction storage interrupt. Unexpected external interrupt. Unexpected alignment interrupt. Unexpected program interrupt. Unexpected floating point unavailable interrupt. Unexpected SVC interrupt. L2 cache POST error. (The display shows a solid 20c for 5 seconds.) Unexpected SVC interrupt. IPL ROM CRC comparison error (irrecoverable). RAM POST memory configuration error or no memory found (irrecoverable). RAM POST failure (irrecoverable). Power status register failed (irrecoverable). A low voltage condition is present (irrecoverable). IPL ROM code being uncompressed into memory. End of boot list encountered. RAM POST is looking for good memory. RAM POST bit map is being generated.
21c L2 cache is not detected. (The display shows a solid 21c for 2 seconds.) 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 operator panel 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. 224 Attempting a Normal mode IPL from 9333 subsystem device specified in NVRAM IPL Devices List. 225 Attempting a Normal mode IPL from 7012 DBA disk-attached devices specified in NVRAM IPL Devices List. 226 Attempting a Normal mode IPL from Ethernet specified in NVRAM IPL Devices List. 227 Attempting a Normal mode IPL from Token-Ring specified in NVRAM IPL Devices 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 entries in the Devices List. 22c Attempting a normal mode IPL from FDDI specified in NVRAM IPL device list. 230 Attempting a Normal mode IPL from adapter feature ROM specified in IPL ROM Device List. 231 Attempting a Normal mode IPL from Ethernet specified in IPL ROM Device 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 IPL from 9333 subsystem device specified in IPL ROM Device List. 235 Attempting a Normal mode IPL from 7012 DBA disk-attached devices specified in IPL ROM Default Device List. 236 Attempting a Normal mode IPL from Ethernet specified in IPL ROM Default Device List. 237 Attempting a Normal mode IPL from Token-Ring specified in IPL ROM Default Device List. 238 Attempting a Normal mode IPL from Token-Ring specified by the operator. 239 System failed to IPL 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 IPL from adapter feature ROM. 241 Attempting a normal boot from devices specified in the NVRAM boot list. 242 Attempting a Service mode IPL from Standard I/O planar-attached devices specified in the NVRAM IPL Devices List. 243 Attempting a Service mode IPL from SCSI-attached devices specified in the NVRAM IPL Devices List. 244 Attempting a Service mode IPL from 9333 subsystem device specified in the NVRAM IPL Devices List. 245 Attempting a Service mode IPL from 7012 DBA disk-attached devices specified in the NVRAM IPL Devices List. 246 Attempting a Service mode IPL from Ethernet specified in the NVRAM IPL Devices List. 247 Attempting a Service mode IPL from Token-Ring specified in the NVRAM Device
List. 248 Attempting a Service mode IPL from NVRAM expansion code. 249 Attempting a Service mode IPL from the NVRAM IPL Devices List; cannot IPL from any of the listed devices, or there are no 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 IPL from adapter feature ROM specified in the IPL ROM Device List. 251 Attempting a Service mode IPL from Ethernet specified in the IPL ROM Default Device List. 252 Attempting a Service mode IPL from Standard I/O planar-attached devices specified in the ROM Default Device List. 253 Attempting a Service mode IPL from SCSI-attached devices specified in the IPL ROM Default Device List. 254 Attempting a Service mode IPL from 9333 subsystem device specified in the IPL ROM Devices List. 255 Attempting a Service mode IPL from 7012 DBA disk-attached devices specified in IPL ROM Default Device List. 256 Attempting a Service mode IPL from Ethernet specified in the IPL ROM Devices List. 257 Attempting a Service mode IPL from Token-Ring specified in the IPL ROM Devices List. 258 Attempting a Service mode IPL from Token-Ring specified by the operator. 259 Attempting a Service mode IPL from FDDI specified by the operator. 25c Attempting a service mode IPL from FDDI specified in IPL ROM device list. 260 Information is being displayed on the display console. 261 No supported local system display adapter was found. 262 Keyboard not detected as being connected to the system's keyboard port. 263 Attempting a Normal mode IPL from adapter feature ROM specified in the NVRAM Device List. 269 Stalled state - the system is unable to IPL. 270 Low Cost Ethernet Adapter (LCE) POST executing 271 Mouse and Mouse port POST. 272 Tablet Port POST. 276 10/100Mbps MCA Ethernet Adapter POST executing 277 Auto Token-Ring LANstreamer MC 32 Adapter. 278 Video ROM scan POST. 279 FDDI POST. 280 3com Ethernet POST. 281 Keyboard POST executing. 282 Parallel port POST executing. 283 Serial port POST executing. 284 POWER Gt1 graphics adapter POST executing. 285 POWER Gt3 graphics adapter POST executing. 286 Token-Ring adapter POST executing. 287 Ethernet adapter POST executing. 288 Adapter card slots being queried. 289 POWER GT0 Display Adapter POST. 290 IOCC POST error (irrecoverable). 291 Standard I/O POST running. 292 SCSI POST running. 293 7012 DBA disk POST running. 294 IOCC bad TCW memory module 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). 298 Attempting a software IPL.
299 IPL ROM passed control to the loaded program code. 301 Flash Utility ROM test failed or checkstop occurred (irrecoverable 302 Flash Utility ROM: User prompt, move the key to the service position in order to perform an optional Flash Update. LED 3�2 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 then LED 3�3 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 3�2 will only appear if the key switch is 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 3�3 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 media device. 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 (irrecoverable). 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 Update successful and complete. Configuration Program Indicators -------------------------------500 501 502 503 504 505 506 507 508 510 511 512 513 516 517 518 520 521
Querying Standard I/O slot. Querying card in Slot 1. Querying card in Slot 2. Querying card in Slot 3. Querying card in Slot 4. Querying card in Slot 5. Querying card in Slot 6. Querying card in Slot 7. Querying card in Slot 8. Starting device configuration. Device configuration completed. Restoring device configuration files from media. Restoring basic operating system installation files from media. Contacting server during network boot. Mounting client remote file system during network IPL. Remote mount of the root and /usr file systems failed during network boot. Bus configuration running. /etc/init invoked cfgmgr with invalid options; /etc/init has been corrupted or
incor-rectly 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 object in the ODM database ( irrecoverable error). 527 The configuration manager was invoked with the 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 name 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 the PdAt object class (irrecoverable error). 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 acquire database lock (irrecoverable error). 535 HIPPI diagnostics interface driver being configured. 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 method. 539 The configuration method has terminated, and control has returned to the configura-tion manager. 551 IPL vary-on is running. 552 IPL varyon failed. 553 IPL phase 1 is complete. 554 The boot device could not be opened or read, or unable to define NFS swap device during network boot. 555 An ODM error occurred when trying to varyon the rootvg, or unable to create an NFS swap device during network boot. 556 Logical Volume Manager encountered error during IPL vary-on. 557 The root filesystem will not mount. 558 There is not enough memory to continue the system IPL. 559 Less than 2 M bytes 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. 575 A 9570 disk-array driver is 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 a 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/rc.boot 602 Configuring network parent devices. 603 /usr/lib/methods/defsys, /usr/lib/methods/cfgsys, or /usr/lib/methods/cfgbus failed. 604 Configuring physical network boot device. 605 Configuration of 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 attempt(s) to retrieve the client_info file are occurring. 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 file system failed. 612 Accessing remote files; unconfiguring network boot device. 614 Configuring local paging devices. 615 Configuration of a local paging device failed. 616 Converting from diskless 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 being configured 668 25MB ATM MCA Adapter being configured
680 POWER GXT800M Graphics Adapter 689 4.5GB Ultra SCSI Single Ended Disk Drive being configured 690 9.1GB Ultra SCSI Single Ended Disk Drive being configured 694 Eicon ISDN DIVA MCA Adapter for PowerPC Systems 700 Progress indicator. A 1.1 GB 8-bit SCSI disk drive being identified or configured. 701 Progress indicator. A 1.1 GB 16-bit SCSI disk drive is being identified or configured. 702 Progress indicator. A 1.1 GB 16-bit differential SCSI disk drive is being identified or configured. 703 Progress indicator. A 2.2 GB 8-bit SCSI disk drive is being identified or configured. 704 Progress indicator. A 2.2 GB 16-bit SCSI disk drive is being identified or configured. 705 The configuration method for the 2.2 GB 16-bit differential SCSI disk drive is being run. If an irrecoverable error occurs, the system halts. 706 Progress indicator. A 4.5 GB 16-bit SCSI disk drive is being identified or configured. 707 Progress indicator. A 4.5 GB 16-bit differential SCSI disk drive is being identified or configured. 708 Progress indicator. A L2 cache is being identified or configured. 710 POWER GXT150M graphics adapter being identified 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. 717 TP Ethernet Adapter being configured. 718 GXT500 Graphics Adapter being configured. 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 CD-ROM being identified or configured. 724 Unknown tape drive being identified or configured. 725 Unknown display adapter being identified or configured. 726 Unknown input device being identified or configured. 727 Unknown async device being identified or configured. 728 Parallel printer being identified or configured. 729 Unknown parallel device being identified or configured. 730 Unknown diskette drive being identified or configured. 731 PTY being identified or configured. 732 Unknown SCSI initiator type being configured. 733 7GB 8mm tape drive being configured. 734 4x SCSI-2 640MB CD-ROM Drive 741 1080MB SCSI Disk Drive 745 16GB 4mm Tape Auto Loader 748 MCA keyboard/mouse adapter being configured. 749 7331 Model 205 Tape Library 754 1.1GB 16-bit SCSI disk drive being configured. 755 2.2GB 16-bit SCSI disk drive being configured. 756 4.5GB 16-bit SCSI disk drive being configured. 757 External 13GB 1.5M/s 1/4 inch tape being configured. 772 4.5GB SCSI F/W Disk Drive
773 9.1GB SCSI F/W Disk Drive 774 9.1GB External SCSI Disk Drive 77c Progress indicator. A 1.0 GB 16-bit SCSI disk drive being identified or configured. 783 4mm DDS-2 Tape Autoloader 789 2.6GB External Optical Drive 794 10/100MB Ethernet PX MC Adapter 797 Turboways 155 UTP/STP ATM Adapter being identified or configured. 798 Video streamer adapter being identified or configured. 800 Turboways 155 MMF ATM Adapter being identified or configured. 803 7336 Tape Library Robotics being configured 804 8x Speed SCSI-2 CD ROM drive being configured 807 SCSI Device Enclosure being configured 808 System Interface Full (SIF) configuration process 80c SSA 4-Port Adapter being identified or configured. 811 Processor complex being identified or configured. 812 Memory being identified or configured. 813 Battery for time-of-day, NVRAM, and so on being identified or configured, or system I/O control logic being identified or configured. 814 NVRAM being identified or configured. 815 Floating-point processor test 816 Operator panel logic being identified or configured. 817 Time-of-day logic being identified or configured. 819 Graphics input device adapter being identified or configured. 821 Standard keyboard adapter being identified or configured. 823 Standard mouse adapter being identified or configured. 824 Standard tablet adapter being identified or configured. 825 Standard speaker adapter being identified or configured. 826 Serial Port 1 adapter being identified or configured. 827 Parallel port adapter being identified or configured. 828 Standard diskette adapter being identified or configured. 831 3151 adapter being identified or configured, or Serial Port 2 being identified or con-figured. 834 64-port async controller being identified or configured. 835 16-port async concentrator being identified or configured. 836 128-port async controller being identified or configured. 837 16-port remote async node being identified or configured. 838 Network Terminal Accelerator Adapter being identified or configured. 839 7318 Serial Communications Server being configured. 841 8-port async adapter (EIA-232) being identified or configured. 842 8-port async adapter (EIA-422A) being identified or configured. 843 8-port async adapter (MIL-STD 188) being identified or configured. 844 7135 RAIDiant Array disk drive subsystem controller being identified or configured. 845 7135 RAIDiant Array disk drive subsystem drawer being identified or configured. 846 RAIDiant Array SCSI 1.3GB Disk Drive 847 16-port serial adapter (EIA-232) being identified or configured. 848 16-port serial adapter (EIA-422) being identified or configured. 849 X.25 Interface Co-Processor/2 adapter being identified or configured. 850 Token-Ring network adapter being identified or configured. 851 T1/J1 Portmaster adapter being identified or configured. 852 Ethernet adapter being identified or configured. 854 3270 Host Connection Program/6000 connection being identified or configured. 855 Portmaster Adapter/A being identified or configured. 857 FSLA adapter being identified or configured. 858 5085/5086/5088 adapter being identified or configured.
859 FDDI adapter being identified or configured. 85c Progress indicator. Token-Ring High-Performance LAN adapter is being identified or configured. 861 Optical adapter being identified or configured. 862 Block Multiplexer Channel Adapter being identified or configured. 865 ESCON Channel Adapter or emulator being identified or configured. 866 SCSI adapter being identified or configured. 867 Async expansion adapter being identified or configured. 868 SCSI adapter being identified or configured. 869 SCSI adapter being identified or configured. 870 Serial disk drive adapter being identified or configured. 871 Graphics subsystem adapter being identified or configured. 872 Grayscale graphics adapter being identified or configured. 874 Color graphics adapter being identified or configured. 875 Vendor generic communication adapter being configured. 876 8-bit color graphics processor being identified or configured. 877 POWER Gt3/POWER Gt4 being identified or configured. 878 POWER Gt4 graphics processor card being configured. 879 24-bit color graphics card, MEV2 880 POWER Gt1 adapter being identified or configured. 887 Integrated Ethernet adapter being identified or configured. 889 SCSI adapter being identified or configured. 890 SCSI-2 Differential Fast/Wide and Single-Ended Fast/Wide Adapter/A. 891 Vendor SCSI adapter being identified or configured. 892 Vendor display adapter being identified or configured. 893 Vendor LAN adapter being identified or configured. 894 Vendor async/communications adapter being identified or configured. 895 Vendor IEEE 488 adapter being identified or configured. 896 Vendor VME bus adapter being identified or configured. 897 S/370 Channel Emulator adapter being identified or configured. 898 POWER Gt1x graphics adapter being identified or configured. 899 3490 attached tape drive being identified or configured. 89c Progress indicator. A multimedia SCSI CD-ROM is being identified or configured. 901 Vendor SCSI device being identified or configured. 902 Vendor display device being identified or configured. 903 Vendor async device being identified or configured. 904 Vendor parallel device being identified or configured. 905 Vendor other device being identified or configured. 908 POWER GXT1000 Graphics subsystem being identified or configured. 910 1/4GB Fibre Channel/266 Standard Adapter being identified or configured. 911 Fibre Channel/1063 Adapter Short Wave 912 2.0GB SCSI-2 differential disk drive being identified or configured. 913 1.0GB differential disk drive being identified or configured. 914 5GB 8 mm differential tape drive being identified or configured. 915 4GB 4 mm tape drive being identified or configured. 916 Non-SCSI vendor tape adapter being identified or configured. 917 Progress indicator. 2.0GB 16-bit differential SCSI disk drive is being identified or configured. 918 Progress indicator. 2GB 16-bit single-ended SCSI disk drive is being identified or configured. 920 Bridge Box being identified or configured. 921 101 keyboard being identified or configured. 922 102 keyboard being identified or configured. 923 Kanji keyboard being identified or configured.
924 Two-button mouse being identified or configured. 925 Three-button mouse being identified or configured. 926 5083 tablet being identified or configured. 927 5083 tablet being identified or configured. 928 Standard speaker being identified or configured. 929 Dials being identified or configured. 930 Lighted program function keys (LPFK) being identified or configured. 931 IP router being identified or configured. 933 Async planar being identified or configured. 934 Async expansion drawer being identified or configured. 935 3.5-inch diskette drive being identified or configured. 936 5.25-inch diskette drive being identified or configured. 937 An HIPPI adapter is being configured. 942 POWER GXT 100 graphics adapter being identified or configured. 943 Progress indicator. 3480 and 3490 control units attached to a System/370 Channel Emulator/A adapter are being identified or configured. 944 100MB ATM adapter being identified or configured 945 1.0GB SCSI differential disk drive being identified or configured. 946 Serial port 3 adapter is being identified or configured. 947 Progress indicator. A 730MB SCSI disk drive is being configured. 948 Portable disk drive being identified or configured. 949 Unknown direct bus-attach device being identified or configured. 950 Missing SCSI device being identified or configured. 951 670MB SCSI disk drive being identified or configured. 952 355MB SCSI disk drive being identified or configured. 953 320MB SCSI disk drive being identified or configured. 954 400MB SCSI disk drive being identified or configured. 955 857MB SCSI disk drive being identified or configured. 956 670MB SCSI disk drive electronics card being identified or configured. 957 120MB DBA disk drive being identified or configured. 958 160 MB DBA disk drive being identified or configured. 959 160MB SCSI disk drive being identified or configured. 960 1.37GB SCSI disk drive being identified or configured. 964 Internal 20GB 8mm tape drive identified or configured. 968 1.0GB SCSI disk drive being identified or configured. 970 Half-inch, 9-track tape drive being identified or configured. 971 150MB 1/4-inch tape drive being identified or configured. 972 2.3GB 8 mm SCSI tape drive being identified or configured. 973 Other SCSI tape drive being identified or configured. 974 CD-ROM drive being identified or configured. 975 Progress indicator. An optical disk drive is being identified or configured. 977 M-Audio Capture and Playback Adapter being identified or configured. 981 540MB SCSI-2 single-ended disk drive being identified or configured. 984 1GB 8-bit disk drive being identified or configured. 985 M-Video Capture Adapter being identified or configured. 986 2.4GB SCSI disk drive being identified or configured. 987 Progress indicator. Enhanced SCSI CD-ROM drive is being identified or configured. 989 200MB SCSI disk drive being identified or configured. 990 2.0GB SCSI-2 single-ended disk drive being identified or configured. 991 525MB 1/4-inch cartridge tape drive being identified or configured. 994 5GB 8 mm tape drive being identified or configured. 995 1.2GB 1/4 inch cartridge tape drive being identified or configured. 996 Progress indicator. Single-port, multi-protocol communications adapter is being identified or configured. 997 FDDI adapter being identified or configured.
998 2.0GB4 mm tape drive being identified or configured. 999 7137 or 3514 Disk Array Subsystem being configured. D81 T2 Ethernet Adapter being configured. Diagnostic Load Progress Indicators ----------------------------------Note: When a lowercase c is listed, it displays in the lower half of the sevensegment character position. c00 AIX Install/Maintenance loaded successfully. c01 Insert the first diagnostic diskette. c02 Diskettes inserted out of sequence. c03 The wrong diskette is in diskette drive. c04 The loading stopped with a nonrecoverable error. c05 A diskette error occurred. c06 The rc.boot configuration shell script is unable to determine type of boot. c07 Insert the next diagnostic diskette. c08 RAM file system started incorrectly. c09 The diskette drive is reading or writing a diskette. c20 An unexpected halt occurred, and the system is configured to enter the kernel debug program instead of entering a system 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 file system during the network boot. c29 The 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 then to Service. The diagnostic programs 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 being restored. c41 Could not determine the boot type or device. c42 Extracting data files from diskette. c43 Cannot access the boot/install tape. c44 Initializing 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 root volume group on target disks. c51 No paging devices 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 additional packages. c55 Could not remove the specified logical volume in a preservation installation. c56 Running user-defined customization. c57 Failure to restore BOS. c58 Displaying 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. c62 Loading platform dependent debug files c63 Loading platform dependent data files c64 Failed to load platform dependent data files c70 Problem Mounting diagnostic CDROM disc c99 Diagnostics have completed. This code is only used when there is no console.
============= 2. 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 0c4 The dump There is not this problem
is inhibit did not complete. A partial dump was written to the dump device. enough space on the dump deviceto contain the entire dump. To prevent 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 101 102 103 104 105 106 111 112 113 120 121 122 123 124
BIST completed successfully. Control was passed to IPL ROS. BIST started following RESET BIST started following Power-on Reset BIST could not determine the system model number. Equipment conflict. BIST could not find the CBA. BIST could not read the OCS EPROM. BIST detected a module error. OCS stopped. BIST detected a module error. A checkstop occured during BIST. BIST checkstop count is greater than 1. BIST starting a CRC check on the 8752 EPROM. BIST detected a bad CRC in the first 32K of the OCS EPROM. BIST started a CRC check on the first 32K of the OCS EPROM. BIST detected a bad CRC on the OCS area of NVRAM. BIST started a CRC check on the OCS area of NVRAM.
125 126 127 130 140 142 143 144 151 152 153 154 160 161 162 163 164 165 166 170 180 182 185 186 187 195 888
BIST detected a bad CRC on the time-of-day area of NVRAM. BIST started a CRC check on the time-of-day area of the NVRAM. BIST detected a bad CRC on the 8752 EPROM. BIST presence test started. BIST failed: procedure error BIST failed: procedure error Invalid memory configuration. BIST failed; procedure error. BIST started AIPGM test code. BIST started DCLST test code. BIST started ACLST test code. BIST started AST test code. Bad EPOW Signal/Power status signal BIST being conducted on BUMP I/O BIST being conducted on JTAG BIST being conducted on Direct I/O BIST being conducted on CPU BIST being conducted on DCB and Memory BIST being conducted on interrupts BIST being conducted on 'Multi-Processor BIST logout failed. BIST COP bus not responding A checkstop condition occured during the BIST System logic-generated checkstop (Model 250 only) Graphics-generated checkstop (Model 250) BIST logout completed. 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 threedigit 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 553 554 555 556 557 558 559 570 571 572 573 574 576 577 578 579 580 581 582 583
IPL Varyon failed. IPL phase 1 is complete. Unable to define NFS swap device during network boot Unable to define NFS swap device during network boot Logical Volume Manager encountered error during IPL varyon. The root filesystem will not mount. There is not enough memory to continue the IPL. Less than 2MB of good memory are available to load the AIX kernel. Virtual SCSI devices being configured. HIPPI common function device driver being configured. HIPPI IPI-3 master transport driver being configured. HIPPI IPI-3 slave transport driver being configured. HIPPI IPI-3 transport services user interface device driver being configured. Generic async device driver being configured. Generic SCSI device driver being configured. Generic commo device driver being configured. Device driver being configured for a generic device. HIPPI TCPIP network interface driver being configured. Configuring TCP/IP. Configuring token ring data link control. 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
=========================================== 10. Diskless machines, NFS Implementations: =========================================== Setting Setting Setting Setting Setting Setting Setting Setting Setting Setting Setting Setting
up up up up up up up up up up up up
nfs, nfs, nfs, nfs, nfs, nfs, nfs, nfs, nfs, nfs, nfs, nfs,
NetBSD OpenBSD FreeBSD Mac OS X and Darwin Linux SunOS Solaris NEWS-OS NEXTSTEP HP-UX 7 (couldn't get it to work) HP-UX 9 HP-UX 10 and later
-------------------------------------------------------------------------------NetBSD and OpenBSD If you have built your own kernel, you need to make sure you have the following in your config file: options NFSSERVER The GENERIC kernel distributed with NetBSD has this compiled in. # mkdir -p /export/client/root/dev
# mkdir /export/client/usr # mkdir /export/client/home # touch /export/client/swap # cd /export/client/root # tar -xvpzf /export/client/NetBSD-release/binary/sets/kern.tgz # mknod /export/client/root/dev/console c 0 0 Add the following lines to /etc/exports: #/etc/exports /export/client/root -maproot=root:wheel /export/client/swap -maproot=root:wheel /export/client/usr -maproot=nobody:nobody /export/client/home -maproot=nobody:nobody
client.test.net client.test.net client.test.net client.test.net
# ps -aux | grep mountd If mountd is running, then kill -HUP that process to force it to reread /etc/exports. Otherwise, you'll need to start it: # /usr/sbin/mountd # ps -aux | grep nfsd If the nfsdaemons are not running, then you need to start them: # /usr/sbin/nfsd -tun 4 If the server isn't running the NFS daemons, the client will print: le(0,0,0,0): Unknown error: code -1 boot: Unknown error: code -1 If the server is running NFS, but isn't exporting the root directory to the client, the client will print: boot: no such file or directory If everything is working properly, you will see a few numbers and a spinning cursor on the client. This means you have succeeded! At this point, your client isn't bootable. If you let it continue, it will panic when attempting to start init. Continue on to setting up the client filesystem -------------------------------------------------------------------------------FreeBSD The setup for FreeBSD 4.x is similar to NetBSD, but mountd needs different options and /etc/exports has a different format. # mkdir -p /export/client/root/dev # mkdir /export/client/usr # mkdir /export/client/home # touch /export/client/swap # cd /export/client/root # tar [--numeric-owner] -xvpzf /export/client/NetBSD-release/binary/sets/kern.tgz
# mknod /export/client/root/dev/console c 0 0 Add the following line to /etc/exports (see the FreeBSD Handbook, Section 17.4 on NFS): #/etc/exports /export/client/root /export/client/swap -maproot=root:wheel client.test.net FreeBSD is unable to export multiple directories within a filesystem (such as /export) to a client unless all of the directories are listed on a single line in /etc/exports. You will also need to make sure the your client's /home and /usr are stored in /export/client/root. FreeBSD is unable to set different properties for exported directories, defeating the point of exporting those directories separately (and without -maproot=root:wheel). # ps -aux | grep mountd If mountd is running, then kill that process. You need it to be running with the -r option for the swap file to be mountable, and the -2 option is to force it to use NFS V2. # /sbin/mountd -2r # ps -aux | grep nfsd If the nfsdaemons are not running, then you need to start them: # /sbin/nfsd -tun 4 If the server isn't running the NFS daemons, the client will print: le(0,0,0,0): Unknown error: code -1 boot: Unknown error: code -1 If the server is running NFS, but isn't exporting the root directory to the client, the client will print: boot: no such file or directory If everything is working properly, you will see a few numbers and a spinning cursor on the client. This means you have succeeded! At this point, your client isn't bootable. If you let it continue, it will panic when attempting to start init. Continue on to setting up the client filesystem -------------------------------------------------------------------------------Mac OS X and Darwin This setup for Mac OS X and Darwin use the NetInfo system. There are ways to use typical BSD-style configuration files, but most systems are by default configured to use NetInfo. Here, we describe how to set up a default install of Mac OS X/Darwin (i.e. in its own local NetInfo domain). Read your netinfo(5) man page for more information. # mkdir -p /export/client/root/dev # mkdir /export/client/usr # mkdir /export/client/home # touch /export/client/swap
# cd /export/client/root # tar -xvpzf /export/client/NetBSD-release/binary/sets/kern.tgz # mknod /export/client/root/dev/console c 0 0 Modify the NetInfo database to export your shares. Note that you must escape the forward slashes in the path to your export twice. Once for the shell, and once for the NetInfo parser (since it uses forward slashes to delimit NetInfo properties). Just to add to the confusion, the NetInfo property we're adding to is called /exports. # nicl . -create /exports/\\/export\\/client\\/root opts maproot=root:wheel # nicl . -create /exports/\\/export\\/client\\/root clients 192.168.0.10 # nicl . -create /exports/\\/export\\/client\\/swap opts maproot=root:wheel # nicl . -create /exports/\\/export\\/client\\/swap clients 192.168.0.10 # nicl . -create /exports/\\/export\\/client\\/usr opts maproot=nobody:nobody # nicl . -create /exports/\\/export\\/client\\/usr clients 192.168.0.10 # nicl . -create /exports/\\/export\\/client\\/home opts maproot=nobody:nobody # nicl . -create /exports/\\/export\\/client\\/home clients 192.168.0.10 To later add another client for the same export, you would append to that property (as opposed to the initial create): # nicl . -append /exports/\\/export\\/client\\/root clients 192.168.0.12 To verify that everything looks good, read it back: # nicl . -read /exports/\\/export\\/client\\/root name: /export/client/root opts: maproot=root:wheel clients: 192.168.0.10 192.168.0.12 # ps -aux | grep portmap If the portmap is not running, then you need to start it: # /usr/sbin/portmap # ps -aux | grep nfsd If the nfsdaemons are not running, then you need to start them: # /sbin/nfsd -t -u -n 6 # ps -aux | grep mountd If mountd is running, then kill -HUP that process to force it to reread the NetInfo database. If it's not running, then you need to start it: # /usr/sbin/mountd Your system will always start the NFS daemons after reboots if the NetInfo /exports property is present. To remove all exports and prevent your system from starting NFS in the future, run: # nicl . -delete /exports If the server isn't running the NFS daemons, the client will print: le(0,0,0,0): Unknown error: code -1 boot: Unknown error: code -1 If the server is running NFS, but isn't exporting the root directory to the client, the client will print: boot: no such file or directory If everything is working properly, you will see a few numbers and a spinning cursor on the client. This means you have succeeded! At this point, your client isn't bootable. If you let it continue, it will panic when attempting to start
init. Continue on to setting up the client filesystem -------------------------------------------------------------------------------Linux # mkdir -p /export/client/root/dev # mkdir /export/client/usr # mkdir /export/client/home # touch /export/client/swap # cd /export/client/root # tar [--numeric-owner] -xvpzf /export/client/NetBSD-release/binary/sets/kern.tgz # mknod /export/client/root/dev/console c 0 0 Add the following lines to /etc/exports: #/etc/exports /export/client/root client.test.net(rw,no_root_squash) /export/client/swap client.test.net(rw,no_root_squash) /export/client/usr client.test.net(rw,root_squash) /export/client/home client.test.net(rw,root_squash) # ps aux | grep mountd If mountd is running, then kill -HUP that process. This will force it to reread the /etc/exports file. If it's not already running, then you need to: # /sbin/rpc.mountd [--no-nfs-version 3] You may need to add the --no-nfs-version 3 if you're having problems. See below. # ps aux | grep nfsd If the nfsdaemons are running, then you need to restart them so that they reread the /etc/exports file. If they're not already running, then you need to: # /sbin/rpc.nfsd If the server isn't running the NFS daemons, the client will print: le(0,0,0,0): Unknown error: code -1 boot: Unknown error: code -1 If the server is running NFS, but isn't exporting the root directory to the client, the client will print: boot: no such file or directory If everything is working properly, you will see a few numbers and a spinning cursor on the client. This means you have succeeded! At this point, your client isn't bootable. If you let it continue, it will panic when attempting to start init. Kernel NFS Problem: Most versions of linux only implement NFS2, in which case NetBSD will try NFS3 and then automatically fall back. Some versions (notably RedHat 6.0) will incorrectly answer both NFS2 and NFS3 mount requests, then ignore any attempt to access the filesystem using NFS3. This causes untold pain and hassle. The workaround is to kill mountd and start it with options preventing NFS3 problems (i.e., rpc.mountd --no-nfs-version 3).
Continue on to setting up the client filesystem -------------------------------------------------------------------------------SunOS # mkdir -p /export/client/root/dev # mkdir /export/client/usr # mkdir /export/client/home # touch /export/client/swap # cd /export/client/root # tar [--numeric-owner] -xvpzf /export/client/NetBSD-release/binary/sets/kern.tgz # mknod /export/client/root/dev/console c 0 0 Create (or add to) your /etc/exports file: #/etc/exports /export/client/root -root=client /export/client/swap -root=client /export/client/usr /export/client/home # rm -f /etc/xtab;touch /etc/xtab # exportfs -a # ps aux | grep nfsd If nfsd not already running, then run: # nfsd 8 & # ps aux | grep mountd If mountd is not already running, then run: # rpc.mountd -n & If the server isn't running the NFS daemons, the client will print: le(0,0,0,0): Unknown error: code -1 boot: Unknown error: code -1 If the server is running NFS, but isn't exporting the root directory to the client, the client will print: boot: no such file or directory If everything is working properly, you will see a few numbers and a spinning cursor on the client. This means you have succeeded! At this point, your client isn't bootable. If you let it continue, it will panic when attempting to start init. Continue on to setting up the client filesystem -------------------------------------------------------------------------------Solaris # mkdir -p /export/client/root/dev
# mkdir /export/client/usr # mkdir /export/client/home # touch /export/client/swap # cd /export/client/root # tar [--numeric-owner] -xvpzf /export/client/NetBSD-release/binary/sets/kern.tgz # mknod /export/client/root/dev/console c 0 0 Add the following lines to /etc/dfs/dfstab: share -F nfs -o root=client /export/client/root share -F nfs -o root=client /export/client/swap share -F nfs -o rw=client /export/client/usr share -F nfs -o rw=client /export/client/home Be certain to use names, if you use numeric IP addresses, Solaris will deny access without any error messages. # /usr/bin/ps -ef | grep nfs If the nfs daemons are running, then you merely need to run: # shareall Normally, you'd need to run unshareall;shareall, but you've only added entries, not deleted anything. If the nfs daemons aren't running, then you will need to run: # /etc/init.d/nfs.server start If the server isn't running the NFS daemons, the client will print: le(0,0,0,0): Unknown error: code -1 boot: Unknown error: code -1 If the server is running NFS, but isn't exporting the root directory to the client, the client will print: boot: no such file or directory If everything is working properly, you will see a few numbers and a spinning cursor on the client. This means you have succeeded! At this point, your client isn't bootable. If you let it continue, it will panic when attempting to start init. Continue on to setting up the client filesystem -------------------------------------------------------------------------------NEWS-OS # mkdir -p /export/client/root/dev # mkdir /export/client/usr # mkdir /export/client/home # touch /export/client/swap # cd /export/client/root # tar [--numeric-owner] -xvpzf /export/client/NetBSD-release/binary/sets/kern.tgz
# mknod /export/client/root/dev/console c 0 0 Create (or add to) your /etc/exports file: #/etc/exports /export/client/root -root=client /export/client/swap -root=client /export/client/usr /export/client/home # rm -f /etc/xtab;touch /etc/xtab # /usr/etc/exportfs -av # ps -aux | grep nfsd If nfsd not already running, then run: # /etc/nfsd 4 & If the server isn't running the NFS daemons, the client will print: le(0,0,0,0): Unknown error: code -1 boot: Unknown error: code -1 If the server is running NFS, but isn't exporting the root directory to the client, the client will print: boot: no such file or directory If everything is working properly, you will see a few numbers and a spinning cursor on the client. This means you have succeeded! At this point, your client isn't bootable. If you let it continue, it will panic when attempting to start init. Continue on to setting up the client filesystem -------------------------------------------------------------------------------NEXTSTEP Note, NEXTSTEP doesn't support exporting a file. This means that swap will have to be a file on your root (nfs) filesystem, and not its own nfs mounted file. Keep this in mind in later steps involving swap. You may also wish to keep with NEXTSTEP convention and place all of your client files in /private/export/client instead of /export/client. # mkdir -p /export/client/root/dev # mkdir /export/client/usr # mkdir /export/client/home # touch /export/client/root/swap # cd /export/client/root # tar [--numeric-owner] -xvpzf /export/client/NetBSD-release/binary/sets/kern.tgz # mknod /export/client/root/dev/console c 0 0 Launch /NextAdmin/NFSManager.app Click on the "Export From ..." menu item
Select your NetInfo Domain (probably /) and click OK. Click on the top Add button to pick your Directory Name Type in your client's name under "Root Access" and click that "Add" button. Click OK. If your client doesn't have a DNS or /etc/hosts entry, NEXTSTEP will not serve correctly. Click the "Quit" menu item. For reference, here is a snapshot of what the NFSManager Exported Directories window should look like. If the server isn't running the NFS daemons, the client will print: le(0,0,0,0): Unknown error: code -1 boot: Unknown error: code -1 If the server is running NFS, but isn't exporting the root directory to the client, the client will print: boot: no such file or directory If everything is working properly, you will see a few numbers and a spinning cursor on the client. This means you have succeeded! At this point, your client isn't bootable. If you let it continue, it will panic when attempting to start init. Continue on to setting up the client filesystem -------------------------------------------------------------------------------HP-UX 7 I couldn't get the HP-UX 7 rpc.mountd to start. Here's what I tried, if you think it might work for you. Let us know what we're doing wrong. I don't think HP-UX 7's NFS server allows for restricting root read/write access. # mkdir -p /export/client/root/dev # mkdir /export/client/usr # mkdir /export/client/home # touch /export/client/swap # cd /export/client/root # tar [--numeric-owner] -xvpzf /export/client/NetBSD-release/binary/sets/kern.tgz # mknod /export/client/root/dev/console c 0 0 Add the following lines to /etc/exports: #/etc/exports /export/client/root client.test.net /export/client/swap client.test.net /export/client/usr client.test.net /export/client/home client.test.net
# ps -ef | grep nfsd If they're not running, then run: # /etc/nfsd 4 Make sure the rpc.mountd in /etc/inetd.conf is uncommented If the server isn't running the NFS daemons, the client will print: le(0,0,0,0): Unknown error: code -1 boot: Unknown error: code -1 If the server is running NFS, but isn't exporting the root directory to the client, the client will print: boot: no such file or directory If everything is working properly, you will see a few numbers and a spinning cursor on the client. This means you have succeeded! At this point, your client isn't bootable. If you let it continue, it will panic when attempting to start init. Continue on to setting up the client filesystem -------------------------------------------------------------------------------HP-UX 9 # mkdir -p /export/client/root/dev # mkdir /export/client/usr # mkdir /export/client/home # touch /export/client/swap # cd /export/client/root # tar [--numeric-owner] -xvpzf /export/client/NetBSD-release/binary/sets/kern.tgz # mknod /export/client/root/dev/console c 0 0 Open sam and make sure that the kernel has NFS support compiled in. Kernel Configuration -> Subsystems, NFS/9000 This will require a reboot if it's not. Add the following lines to /etc/exports: #/etc/exports /export/client/root -root=client.test.net /export/client/swap -root=client.test.net /export/client/usr -access=client.test.net /export/client/home -access=client.test.net # ps -ef | grep mountd If mountd is not already running, then run: # /usr/etc/rpc.mountd # ps -ef | grep nfsd If nfsd isn't already running, then run: # /etc/nfsd 4 # /usr/etc/exportfs -a If the server isn't running the NFS daemons, the client will print:
le(0,0,0,0): Unknown error: code -1 boot: Unknown error: code -1 If the server is running NFS, but isn't exporting the root directory to the client, the client will print: boot: no such file or directory If everything is working properly, you will see a few numbers and a spinning cursor on the client. This means you have succeeded! At this point, your client isn't bootable. If you let it continue, it will panic when attempting to start init. Continue on to setting up the client filesystem -------------------------------------------------------------------------------HP-UX 10 # mkdir -p /export/client/root/dev # mkdir /export/client/usr # mkdir /export/client/home # touch /export/client/swap # cd /export/client/root # tar [--numeric-owner] -xvpzf /export/client/NetBSD-release/binary/sets/kern.tgz # mknod /export/client/root/dev/console c 0 0 Edit /etc/rc.config.d/nfsconf and make sure that: NFS_SERVER=1 START_MOUNTD=1 If those are not set, then you will need to run: # /sbin/init.d/nfs.server start Add the following lines to /etc/exports: #/etc/exports /export/client/root -root=client.test.net /export/client/swap -root=client.test.net /export/client/usr -access=client.test.net /export/client/home -access=client.test.net # /usr/sbin/exportfs -a If the server isn't running the NFS daemons, the client will print: le(0,0,0,0): Unknown error: code -1 boot: Unknown error: code -1 If the server is running NFS, but isn't exporting the root directory to the client, the client will print: boot: no such file or directory If everything is working properly, you will see a few numbers and a spinning cursor on the client. This means you have succeeded! At this point, your client isn't bootable. If you let it continue, it will panic when attempting to start init. Continue on to setting up the client filesystem
####################################################################### SUN SOLARIS EXAMS: ================== SUN: Certification Paths -
Java Technology Solaris Operating System Directory Server Custom Certification
1. SOLARIS: =========== Sun offers the following Solaris OS professional certifications: 1. 10 2. 10 3.
Sun Certified System Administrator for the Solaris Operating System - Solaris OS now available! Sun Certified Network Administrator for the Solaris Operating System - Solaris OS now available! Sun Certified Security Administrator for the Solaris Operating System
We will look at the exams of the first certification: Solaris 10 OS Part I - Sun Certified System Administrator for the Solaris 10 Operating System (CX-310-200) - New! Part II - Sun Certified System Administrator for the Solaris 10 Operating System (CX-310-202) - New! Upgrade - Sun Certified System Administrator for the Solaris 10 Operating System (CX-310-203) - New! Solaris 9 OS Part I - Sun Certified System Administrator for the Solaris 9 Operating System (CX-310-014) Part II - Sun Certified System Administrator for the Solaris 9 Operating System (CX-310-015) Upgrade - Sun Certified System Administrator for the Solaris 9 Operating System (CX-310-016)
Solaris 10: Exam CX-310-200 --------------------------Exam Objectives Section 1: Install Software --------------------------------------------------------------------------------Explain the Solaris 10 OS installation and upgrade options for CD / DVD,
including how to provide Minimal Installations for SPARC, x64, and x86-based systems. -Perform an OS installation from CD / DVD for SPARC, x64, and x86- based systems. Section 2: Manage File Systems --------------------------------------------------------------------------------Explain the Solaris 10 OS directory hierarchy, including root subdirectories, file components, and file types, and create and remove hard and symbolic links. -Explain disk architecture including the UFS file system capabilities and naming conventions for devices for SPARC, x64, and x86-based systems. -Use the prtconf and format commands to list devices, explain critical issues of the /etc/path_to_inst file and reconfigure devices by performing a reconfiguration boot or using the devfsadm command for SPARC, x64, and x86-based systems. -Given a scenario, partition a disk correctly using the appropriate files, commands, and options, and manage disk labels using SMI and EFI labels as they relate to disk sets. -Explain the Solaris 10 OS file system, including disk-based, distributed, devfs, and memory file systems related to SMF, and create a new UFS file system using options for 1Tbyte file systems. -Given a scenario, check and resolve Solaris 10 OS file system inconsistencies using fsck, and monitor file system usage using the command line (df, du, and quot commands). -Perform mounts and unmounts on a Solaris 10 OS file system, and use volume management to access mounted diskettes and CD-ROMs, restrict access, troubleshoot volume management problems, and explain access methods without volume management. -Perform Solaris 10 OS package administration using command-line interface commands and manage software patches for the Solaris OS, including preparing for patch administration, and installing and removing patches using the patchadd and patchrm commands. Section 3: Perform System Boot and Shutdown Procedures for SPARC, x64, and x86based systems. --------------------------------------------------------------------------------Given a scenario, explain boot PROM fundamentals, including OpenBoot Architecture Standard, boot PROM, NVRAM, POST, Abort Sequence, and displaying POST to serial port for SPARC. -Given a scenario, explain the BIOS settings for booting, abort sequence, and displaying POST, including BIOS configuration for x64 and x86-based system. -Execute basic boot PROM commands for a SPARC system. -Use the Xorg configuration files or kdmconfig utility to configure the keyboard, display, and mouse devices for an x64 and x86 based system. -Perform system boot and shutdown procedures, including identifying the system's boot device, creating and
removing custom device aliases, viewing and changing NVRAM parameters, and interrupting an unresponsive system. -Explain the Service Management Facility and the phases of the boot process. -Use SMF or legacy commands and scripts to control both the boot and shutdown procedures. Section 4:Perform User and Security Administration --------------------------------------------------------------------------------Explain and perform Solaris 10 OS user administration, and manage user accounts and initialization files. -Monitor system access by using appropriate commands. -Perform system security by switching users on a system, and by becoming root and monitoring su attempts. -Control system security through restricting ftp access and using /etc/hosts.equiv and $HOME/ .rhosts files, and SSH fundamentals. -Restrict access to data in files through the use of group membership, ownership, and special file permissions. Section 5: Manage Network Printers and System Processes --------------------------------------------------------------------------------Configure and administer Solaris 10 OSprint services, including client and server configuration, starting and stopping the LP print service, specifying a destination printer, and using the LP print service. -Control system processes by viewing the processes, clearing frozen processes, and scheduling automatic one-time and recurring execution of commands using the command line. Section 6: Perform System Backups and Restores --------------------------------------------------------------------------------Given a scenario, develop a strategy for scheduled backups, and backup an unmounted file system using the appropriate commands. -Perform Solaris 10 OS file system restores using the appropriate commands, including restoring a regular file system, the /usr file system, the /(root) file system, and performing interactive and incremental restores for SPARC, x64, and x86 based systems. -Backup a mounted file system by creating a UFS snapshot and performing a backup of the snapshot file. -Restore data from a UFS snapshot and delete the UFS snapshot.
Solaris 9: Exam CX-310-014 Exam Objectives Manage File Systems
--------------------------------------------------------------------------------Describe the purpose, features, and functions of root subdirectories, file components, file types, and hard links in the Solaris OS directory hierarchy. -Explain how to create and remove hard links in a Solaris OS directory. -Describe the basic architecture of a local disk and the naming conventions for disk devices as used in the Solaris OS. -Explain when and how to list devices, reconfigure devices, perform disk partitioning, and relabel a disk in a Solaris OS using the appropriate files, commands, options, and menus or tables or both. -Describe the purpose, features, and functions of disk-based, distributed, and pseudo file systems in a Solaris OS, and explain the differences among these file system types. -Explain when and how to create a new ufs file system using the newfs command, check the file system using fsck, resolve file system inconsistencies, and monitor file system usage using associated commands. -Explain the purpose and function of the vfstab file in mounting ufs file systems, and the function of the mnttab file in tracking current mounts. -Explain how to perform mounts and unmounts, and either access or restrict access to mounted diskettes and CD-ROMs. Install Software --------------------------------------------------------------------------------Explain how to install the Solaris OS from CD/DVD, including installation and upgrade options, hardware requirements, Solaris OS software components (software packages, clusters, and groups). -Explain the purpose of the the /var/sadm/install/contents file, and how to administer packages (how to display, add, check, and remove a package, and add a package into the spool directory) using the command-line interface. -Explain how to obtain, install, and remove patches, and patch clusters using either the command-line interface or the Solaris Management Console. Perform System Boot Procedures --------------------------------------------------------------------------------Explain how to execute boot PROM commands to: -Identify the systems boot PROM version -Boot the system; access detailed information -List, change and restore default NVRAM parameters -Display devices connected to the bus -Identify the systems boot device -Create and remove custom device aliases -View and change NVRAM parameters from the shell -Interrupt a hung system
-Given a scenario involving a hung system, troubleshoot problems and deduce resolutions. -Explain how to perform a system boot, control boot processes, and complete a system shutdown, using associated directories, scripts, and commands. Perform User and Security Administration --------------------------------------------------------------------------------Identify the main components of a user account, identify the system files that store account information, and explain what information is stored in each file. -Explain how to manage user accounts, and describe system-wide initialization files. -Identify the procedures and commands, variables, or permissions to monitor and control system access, switch users on a system, and restrict access to data in files. Manage Network Printers and System Processes --------------------------------------------------------------------------------Describe the purpose, features, and functionality of printer fundamentals, including print management tools, printer configuration types, Solaris LP print service, LP print service directory structure, and the Solaris OS printing process. -Explain how to configure printer classes, set the default printer, change the default printer class, remove a printers configuration, start the LP print service, and stop the LP print service using the appropriate commands. -Given a scenario, identify the appropriate commands to specify a destination printer, accept and reject print jobs, enable and disable printers, and move print jobs. -Explain how to view system processes, clear hung processes, schedule an automatic one-time execution of a command, and the automatic recurring execution of a command. Perform System Backups and Restores --------------------------------------------------------------------------------Given a backup requirement, develop a backup strategy that includes scheduled backups, number of tapes required, naming conventions, command protocols, and backup frequency/levels. -Explain how to perform incremental, full, and remote backups to tape for an unmounted file system using the ufsdump command or explain how to backup a mounted file system using ufs snapshot. -Explain how to perform ufs file system restores and special case recoveries. -- END OF SOLARIS EXAMS ################################################################################## ##########
IBM AIX EXAMS: ============== 1. TEST 232 (expired on november 2005) -------------------------------------Test 232 IBM V5.2
Certified Specialist - pSeries Administration and Support for AIX 5L
Note: Test 222: eServer p5 and pSeries Administration and Support AIX 5L V5.3, released on September 1, 2005, replaces Test 232: pSeries Administration and Support for AIX 5L V5.2, which will be withdrawn on November 30, 2005. The certification validates the ability to plan, install, configure, support, troubleshoot, and determine problems and take appropriate remedial actions for the pSeries Administration and Support for AIX 5L V5.2. The AIX 5L System Administrator manages and supports endusers and the day-to-day operation of AIX 5L in an IBM pSeries environment. 1 exam. Approximate # of questions: 90 Duration in minutes: 120 Format: MULTIPLE CHOICE. Required Passing Score: 60% 2. Test 222 ----------Test 222: pSeries Administration and Support for AIX 5L V5.2 The certification validates the ability to plan, install, configure, support, troubleshoot, and determine problems and take appropriate remedial actions for the p5 and pSeries Administration and Support for AIX 5L V5.3. The AIX 5L V5.3 System Administrator manages and supports end-users and the day-to-day operation of AIX 5L V5.3 in an IBM p5 and pSeries environment. To attain the IBM Certified Specialist - p5 and pSeries Administration and Support for AIX 5L V5.3 certification, candidates must pass 1 test. Note: Test 222 replaces Test 232. You are strongly encouraged to take Test 222. Test 232 will be permanently withdrawn November 30, 2005. 1 exam Approximate # of questions: 94 Duration in minutes: 120 Format: Multiple choice. Required Passing Score: 67%
2. Test 237: -----------Test 237: pSeries HACMP for AIX 5L
4. IBM Certified Systems Expert - p5 and pSeries Enterprise Technical Support AIX 5L V5.3 ----------------------------------------------------------------------------------------TEST 222+ 180 Both Test 180 and Test 222 are required for IBM Certified Systems Expert p5 and pSeries Enterprise Technical Support AIX 5L V5.3 Either Test 197 or Test 232 may be combined with Test 222 or Test 180 respectively, but the V5.2 level will be indicated on this certification, until the corresponding V5.3 tests are earned. 4. Other tests: --------------Test 190: AIX Basic Operations V5 Approximate # of questions: 67 Duration in minutes: 75 Format: multiple-choice Seems an easy test, just commands and shell etc.. Test 180: p5 and pSeries Enterprise Technical Support AIX 5L V5.3 Seems a difficult test, lpar etc..
----------------------------------------------------------------------------------------
TEST 222 objectives: -------------------Section 1 - Planning Determine device needs (e.g., communication adapters, disk controllers, HBAs, tape drives, CD-ROM drives, etc.) Determine the AIX OS level compatibility Determine redundancy requirements for levels of availability (e.g., multiple I/O controllers, multiple communication controllers, multiple processors, multiple
power supplies, RAID-level protection, dynamic CPU deallocation, dead gateway detection) Select appropriate IBM resources for system planning Describe LPAR and dLPAR features and benefits Determine disk requirements Section 2 - AIX Installation and Updates Install AIX from Media using CDROM or DVD or tape Describe the NIM installation process and configuration Identify why install hangs or fails Identify installation LED codes Describe the purpose of Trusted Computing Base (TCB) Describe the Alt Disk installation process and its advantages Describe the process to clone a system from a mksysb Describe the differences between migration, preservation, and new and complete overwrite installation Install software updates (e.g., PTFs) Describe the options available for adding and removing filesets (e.g., commit, apply, remove, reject) Describe the AIX installation packaging Given an operating system or application requirement, select the appropriate AIX installation method Manage filesets (eg: bffcreate and inutoc) Identify the operating system maintenance level and installed filesets Verify integrity of OS (e.g., lppchk and its flags) Describe the differences between installp and rpm Section 3 - Boot Process Describe the boot process (cfgmgr, file system mounts, application startup, rootvg varyon, BIST, POST, boot sector load, login enablement) Describe the use of the /etc/inittab Describe LED codes (121, 223, 229, 551, 552, 553, 581, OC31, OC32) Describe how to recover from a hung boot process Describe run levels 0 through 9 Describe the use of the following rc.* files (rc.net, rc.tcpip, rc.boot, rc., rc.local) Show, modify and reset bootlist Section 4 - Configuration Describe the function of the ODM and the locations of its files Query ODM Describe the function of smit Describe the process to run a Linux application under AIX Configure the network using the following: TCP/IP, /etc/hosts, hostname, ifconfig, chdev, route, /etc/resolv.conf, etc/netsvc.conf, no, /etc/ntpd.conf Configure Ethernet adapter (speed, duplex, virtual ethernet) Use NFS to import/export file systems (e.g., /etc/exports, biod, nfsd) Configure, list and modify paging space Determine/modify existing device configuration Reconfigure system to move from 32-bit to 64-bit and vice versa Check for possible exposure in system access files (e.g., /etc/hosts.equiv, .rhosts, .netrc, .forward) Section 5 - Storage and LVM<
Describe the relationship between physical and logical volumes and volume groups Describe the relationship between logical volumes and filesystems Describe the differences between JFS vs. JFS2 Manage volume groups (varyonvg, varoffvg, mkvg, importvg, exportvg, lsvg) Manage logical volumes Manage filesystems (mount, fsck, chfs, mkfs, defragfs) Describe the relationship between physical partition size and physical disk size List the attributes of volume groups, logical volumes, and filesystems that cannot be changed Migrate data from one physical volume to another Section 6 - Monitoring and Tuning Monitor root mail for error messages Monitor file systems growth to prevent a full file system Monitor the error log for hardware and software errors Use and interpret output from vmstat and sar to determine performance problems Use /etc/tunables for customization of system parameters Given system performance problems, select the appropriate tool(s) (e.g., vmstat, iostat, topas, netstat, sar, /proc) Use and interpret output from netstat and iostat to determine performance problems Use and interpret the output of /proc commands for problem determination Configure and monitor syslog for error conditions Describe the system commands that document current system configuration Use the Resource System Controller (RSCT) to set up resource and system monitoring Describe the advantages of using Workload Manager (WLM) for system resource allocation Describe Partition LoadManager features Describe how to determine and recover from a full file system Section 7 - Problem Determination and Resolution Given a system problem, determine which tool (e.g., errpt, diag, netstat, ifconfig, ping, filemon, traceroute) is appropriate for problem determination Monitor, interpret and manage the error log using errpt and/or errclear Identify reasons to monitor the root user's mail Identify when to use PerfPMRs Manage a support call with IBM (e.g., open, severity levels, escalation, closing) Determine how to size and configure dump devices Describe hot plug processes for replacing devices Given user problems, determine appropriate actions (e.g., usrck, grpck, file permissions, resetting failed login attempts, user limits) Given a hardware related problem, identify the probable cause Given failed disk situations, describe the procedures for replacing the bad disk Access rootvg in maintenance mode Use alog to examine boot messages to locate startup problems Troubleshoot system hangs when trying to start desktop Troubleshoot error unable to open display Section 8 - Backup and Recovery / Disaster Recovery Describe methods of backing up and restoring the operating system (e.g., mksysb) Describe methods of managing / positioning tape backup media for backup and restore purposes
Describe methods of backing up and restoring data and data structures (savevg and restvg, backup and restore, tar, cpio, pax, mkcd, gzip and gunzip) Describe methods to list / verify contents of backup media Describe methods of selectively altering / excluding data during backup and restore process Identify the elements of disaster recovery plans based on business needs Describe the differences between full, differential, and incremental backups and their effect on backup and restore windows Section 9 - Daily Management Add / delete / alter userids and passwords Alter default user profiles and limits (i.e., command shell profiles and /etc/security) Describe methods to monitor and manage processes (e.g., ps, kill, nice, fuser, topas, svmon) Identify and correct errors in shell script examples Define AIX file and directory permissions (e.g., user, group, other) and ownership Define and/or modify file permissions and ownership (e.g., chmod, chown, chgrp) Describe differences between foreground and background processes Describe how to check and alter priority of a process Describe the differences between local and global variables and how to set, unset and show them Describe how to enable System V printing Manage the print queuing subsystem Edit a file using vi Describe methods to read / create / delete / configure email Describe use of metacharacters and wildcards within the shell Describe how to redirect stdin, stdout, and stderr Use cron to schedule tasks Control system processes using System Resource Controller (SRC) ------------################################################################################## ########## Linux EXAMS: ============ 1. Redhat: ---------- Red Hat Certified Technician (RHCT) Now in its fourth year, Red Hat Certified Technician is the fastest-growing credential in all of Linux. RHCT is the best first step in establishing Linux credentials and is an ideal initial certification for those transitioning from non-UNIX�/ Linux environments. - Red Hat Certified Engineer (RHCE) Red Hat Certified Engineer began in 1999 and has been earned by more than 20,000 Linux experts. Called the crown jewel of Linux certifications, independent surveys have ranked the RHCE program #1 in all of IT.
- Red Hat Certified Security Specialist (RHCSS) An RHCSS has RHCE security knowledge plus specialized skills in Red Hat Enterprise Linux, Red Hat Directory Server and SELinux to meet the security requirements of today's enterprise environments. Additional specialization in Identity Management is also available. RHCSS is Red Hat's newest certification, and the only one of its kind. - Red Hat Certified Architect (RHCA) RHCEs who seek advanced training can enroll in Enterprise Architect courses and prove their competency with Red Hat Certified Architect (RHCA) certification. RHCA is the capstone certification to Red Hat Certified Technician (RHCT) and Red Hat Certified Engineer (RHCE), the most acclaimed certifications in the Linux space. RHCA also encapsulates many of the security-related competencies taught in the RHCSS program. Note 1: Under Red Hat Enterprise Linux 4, the certification exam consists of two parts conducted in a single day. The exam is performance-based, meaning that candidates must perform tasks on a live system, rather than answering questions about how one might perform those tasks. Note 2: Red Hat inc. Heeft het meeste bekendheid gekregen met de Red Hat Linux distributie. Inmiddels is deze bekendheid in de markt uitgebreid met de dienst 'Certificatie'. Er zijn twee niveaus: Red Hat Certified Technician en Red Hat Certified Engineer. Beide examens bevatten, in tegenstelling tot de andere examens, een uitgebreide praktijkcomponent en worden daardoor als een stuk zwaarder e
