Unix System Administrator

The scenarios is as follows: Machine A : We need to take an mksysb image on a tape. The tape should be bootable. The machine does not have access to a tape drive. Machine B: Does have access to a tape drive and is connected to machine A via LAN. Procedure: A bootable tape as a result of mksysb contains 4 records (set of data). BOS Boot Image - contains a copy of the system's kernel and device drivers needed to boot from the tape. mkinsttape Image ./image.data - holds the information needed to recreate the root volume group and its logical volumes and file systems. ./bosinst.data - contains the customizable install procedures and dictates how the BOS install program will behave. This file allows for the non-interactive installs. Dummy "Table of Content" used to make mksysb tapes have the same number of files as BOS install tapes. Steps: (our working directory on both servers will be /opt) Machine A: Create a bootable image on machine A: Code: bosb...

To restore a mksysb without mirroring. the following procedure can be used NOTE: Access to another AIX system and an AIX formatted diskette is required to perform this procedure.  All references to the tape device in the next section are as rmt0. On another AIX system, place the mksysb tape in the tape drive. Change the block size of the tape drive to 512 by running: chdev -l rmt0 -a block_size=512   Create a temporary directory in /tmp called newdata .   mkdir /tmp/newdata Change to the /tmp/newdata directory. Enter:   cd /tmp/newdata    Make sure that the tape is rewound. Enter: tctl -f /dev/rmt0 rewind    Restore the image.data file from the second image of the mksysb tape. Enter: restore -s2 -xqvf /dev/rmt0.1 ./image.data    Edit the /tmp/newdata/image.data file and make c...

Creating a mksysb without mirroring If the ability to retrun the mksysb is available, the following procedure will allow you to create a mksysb without preserving mirroring.  To create a new image.data file, run the following command:  mkszfile  Change into the / directory and vi the image.data file. Enter: cd / vi image.data  The following examples show an lv_data stanza of an image.data file. The first example is with mirroring, while the second example shows the edited version without mirroring. The lines that need changes are marked by --> and are boldfaced. In the second example, the changes are made to those lines.        To view and edit the file,enter:  vi image.data Example 1     lv_data:                 VOLUME_GROUP= rootvg                 LV_SOURCE_DISK_LIST= hdisk0 ...

ntpdate[331858]: the NTP socket is in use, exiting  Stop ntp daemon :> stopsrc -s xntpd Try to update again:> ntpdate pool.ntp.org Start ntp daemon :> startsrc -s xntpd

The storage agent must be installed on a client system that has connections to storage resources on the SAN. Before beginning this procedure: Verify that your system meets the hardware and software requirements. Be sure that you have the information recorded in the configuration-information work sheets. Close all existing Tivoli® Storage Manager products prior to installing the storage agent. Installation will stop if an active Tivoli Storage Manager process is detected. If this occurs, close all active Tivoli Storage Manager products and retry installing the storage agent. The storage agent honors the Tivoli Storage Manager server environment variables DSMSERV_CONFIG. The instructions in this section are shown using the Software Management and Installation Tool (SMIT). You can also use the Install and Update Software Manager (installm). To reduce workload and processing time and to optimize LAN-free performance, do not install the storage agent and the Tivoli Storag...

This document describes the procedure for rebuilding a /$HOME/.Xauthority file. The information in this document applies to AIX 5.1 and higher. If you get an MIT magic cookie error when trying to gain remote access the CDE or Xdm, you may be able to solve the problem by rebuilding the .Xauthority file in the home directory of the user trying to log in. Follow these steps to create a /$HOME/.Xauthority file. Log in as user and confirm that you are in the user's home directory. Rename the existing .Xauthority file by running the following command mv .Xauthority old.Xauthority Generate a new .Xauthority file by running the following command: xauth generate :0 . trusted At the command line, create a new magic-cookie key by entering the following: randomkey=`/usr/bin/ksh -c 'echo $(( $RANDOM * $RANDOM * 2 ))'` Add a new entry for another server by running the following command: xauth add ${HOST}:0 . $randomkey To view a listing of the .Xauthority ...

when i was trying to login by Xmanger give the following error usr/bin/X11/xauth: 1356-361 Timeout in locking authority file /home/user-name/.Xauthority the solution log to the server by command line and run the following command $ xauth -b "Attempting to break locks on authority file /.Xauthority Using authority file /.Xauthority" exit to test run xclock