Thursday, June 26, 2014

NTP Sync. Problem

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

Sunday, December 2, 2012

Installing and configuring the storage agent (AIX)

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 Storage Manager server on the same system.
To install and configure the storage agent:
  1. Log in as the root user.
  2. Insert the storage agent CD into the selected drive. For example: /dev/cd0.
  3. From your desktop, access SMIT and make selections according to the level of your AIX® operating system:
    1. Enter smit install_update &
    2. Select:
      Install Software
        Install Software
  4. On the next window, select the device that you are using for the installation. You can enter the drive name in the window or click List to access the device list. If you click List, select the CD drive that you are using for the installation.
  5. Click OK.
  6. Locate the line Software to Install. Before proceeding, review the software listed in the table.
    Table 1. Package and fileset names for AIX 5.3 ML6 SP2
    Package and fileset names Description
    tivoli.tsm.StorageAgent Storage agent common functions, sample dsmsta.opt file
    tivoli.tsm.gsksa.rte Encryption and Secure Socket Layer (SSL) capabilities in the storage agent
    tivoli.tsm.devices SCSI-runtime device support
    tivoli.tsm.devices.msg.xx_XX SMIT windows
    tivoli.tsm.server.msg.xx_XX.server Message catalog and online help
    The variable xx_XX represents the country code for the language contents of the package.
    • To install all components in the table, continue at step 8.
    • To selectively install components, click List for the latest available software packages and select the components that you need. Required components are the storage agent and the message package to be used by the storage agent. The Tivoli Storage Manager device driver is only required if you are using a SCSI device that is not covered by an IBM® SCSI device driver. For a list of devices supported by the Tivoli Storage Manager SCSI device driver, refer to the Tivoli Storage Manager product support Web site.
  7. Click OK.
  8. Check the default settings for the options on this window.
  9. Click OK. SMIT responds:
    ARE YOU SURE?...
  10. Click OK. This installation can take several minutes.
  11. After the installation is complete, click Done , remove the CD, and exit SMIT.
  12. Ensure that the DEVCONFIG option is specified in the storage agent options file (dsmsta.opt). For example, for a device configuration file named devconfig.out located at /usr/tivoli/tsm/StorageAgent/bin, edit the dsmsta.opt file and enter the following line: DEVCONFIG devconfig.out
  13. Use the information that you collected in the configuration-information work sheets to issue the DSMSTA SETSTORAGESERVER command. For example:
    dsmsta setstorageserver myname=storagnt mypassword=fun4me
    servername=tsmsrver serverpassword=not4u lladdress=1502
    The HLADDRESS must match the TCPSERVERADDRESS located in the dsm.sys file on the Tivoli Storage Manager client. When configuring the storage agent using the DSMSTA SETSTORAGESERVER command, use addresses that correspond to the communications method used by the backup-archive client. The backup-archive client supports either IPv4 (COMMMETHOD TCPIP) or IPv6 (COMMMETHOD V6TCPIP), but not both at the same time. The command generates the following lines in the device configuration file for the storage agent:
    set staname storagnt
    set stapassword xxxxxxx
    set stahladdress
    define server tsmsrver serverpassword=xxxxxxxxxxx lladdress=1502
    The passwords (shown as xxxxxxxxxxx) are encrypted in the file.
    The command also generates the following line in the dsmsta.opt file: SERVERNAME tsmsrver
The default installation directory is /opt/tivoli/tsm/StorageAgent/bin.

Create/rebuild a new .Xauthority file

<div dir="ltr" style="text-align: left;" trbidi="on">
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 file, enter the following

xauth list

Friday, February 17, 2012

Xmanger does not work

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"
to test run xclock

Monday, August 22, 2011

Recover root password

Resetting an unknown root password

The following procedure describes how to recover access to root privileges when the system's root password is unavailable or unknown.

The following procedure requires some 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 scenario was tested using specific versions of AIX®. The results you obtain might vary significantly depending on your version and level of AIX.

Insert the product media for the same version and level as the current installation into the appropriate drive.
Power on the machine.
When the screen of icons appears, or when you hear a double beep, press the F1 key repeatedly until the System Management Services menu appears.
Select Multiboot.
Select Install From.
Select the device that holds the product media and then select Install.
Select the AIX version icon.
Define your current system as the system console by pressing the F1 key and then press Enter.
Select the number of your preferred language and press Enter.
Choose Start Maintenance Mode for System Recovery by typing 3 and press Enter.
Select Access a Root Volume Group. A message displays explaining that you will not be able to return to the Installation menus without rebooting if you change the root volume group at this point.
Type 0 and press Enter.
Type the number of the appropriate volume group from the list and press Enter.
Select Access this Volume Group and start a shell by typing 1 and press Enter.
At the # (number sign) prompt, type the passwd command at the command line prompt to reset the root password. For example:

# passwd
Changing password for "root"
root's New password:
Enter the new password again:

To write everything from the buffer to the hard disk and reboot the system, type the following:


Monday, August 8, 2011

Resolve ISC Admin Center password expiration


The administrator logs in to the ISC (Integrated Solution Console), but when they try to access a TSM Server from the Admin Center (AC), it fails saying the TSM administrator password has expired and to reset it from the service property notebook. When the ISC administrator tries to reset the password from the Administration Center (AC) service property notebook it also fails, saying that the administrator password has expired.
Resolving the problem

To reset the TSM administrator password in AC for a TSM server, delete and recreate the TSM server connection within Admin Center, which will allow you to enter and use the current TSM administrator password.

1. Delete the server connection. From ISC -> TSM -> Server Maintenance, select the drop down action:

Remove Server Connection

2. Update the TSM administrator password from the TSM administration command line (dsmadmc):

update admin

3. Recreate the TSM server connection within AC. From ISC -> TSM -> Server Maintenance, select the drop down action:

Add Server Connection
Enter the updated password and a connection will be established.

making sure that the boxis checked to Unlock the Health Monitor

Wednesday, April 20, 2011


when i trying increase file systems i get that error
0516-404 allocp: This system cannot fulfill the allocation request.
There are not enough free partitions or not enough physical volumes
to keep strictness and satisfy allocation requests. The command
should be retried with different allocation characteristics.
this due to at rootvg there exist mirror and containing two disks
hdisk0 & hdisk1 when i execute the lspv hdisk0 & lspv hdisk1
i found that there exist space of one and not the other
to solve that decrease one of file system from the disk have not free space