Unix System Administrator

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

Problem(Abstract) 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 wit

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

In AIX 5.2 and 5.3(pre TL7), there has been a 8 character password limitation when using the one-way hash function crypt(). AIX 5.3 TL7 and AIX 6.1 introduce Loadable Password Algorithm (LPA). Each supported password encryption algorithm is implemented as a LPA load module that is loaded at runtime when the algorithm is needed. The supported LPAs, and its attributes, are defined in system configuration file /etc/security/pwdalg.cfg. ---------------------------------------------------------------------------------- the different algorithms are MD5---------------->255 SHA1--------------->255 SHA265------------->255 SHA512------------->255 Blowfish----------->72 -------------------------------------------------------------------------------- NOTE: Without the pwd_algorithm entry in /etc/security/login, the default value is "crypt" which is the legacy crypt() function. ---------------------------------------------------------------------------------

AIX infocenter http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic= IBM AIX OS: Everything about AIX http://aix.lap.hu/ Taking mksysb image of an installed AIX system using NIM http://markelov.org/wiki/index.php/Taking_mksysb_image_of_an_installed_AIX_system_using_NIM AIX errors codes http://publib.boulder.ibm.com/infocenter/ts7680/serv/index.jsp?topic=%2Fcom.ibm.storage.3958.service.doc%2Fts7740_exxxprogcodes_2nwwoq.html

echo %errorlevel% to pass command line error if %errorlevel% neq 0 goto label

• /var/adm/wtmp &• /etc/security/failedlogin there exist two wayes 1- cat /dev/null > /var/adm/wtmp 2- > /etc/security/failedlogin • /var/adm/sulog • /var/spool/*/* 1. stopsrc -s qdaemon 2. rm /var/spool/lpd/qdir/* 3. rm /var/spool/lpd/stat/* 4. rm /var/spool/qdaemon/* 5. startsrc -s qdaemon • $HOME/smit.log • $HOME/smit.script • $HOME/websm.log • $HOME/websm.script This command will print the number of blocks used by each directory and file in the root. find . -type d -exec du -s {} \; You can search for "large" files by cd'ing to a suspect directory ( or even starting at /, if you must), and typing find . -size +5000 -print will print the names of all files over 5,000 blocks (2,560,000) bytes. This may find many, many files, so you might want to refine it with larger numbers. You might also want to sort it: find / -size +2000 -exec ls -s{} \; | sort -nr | more to print all files that change in current directory at last 24 hours f

to creat alias by a user vi /$HOME/.profile and set a value of variable  ENV="$HOME/.kshrc" then edit at .kshrc file alias alias_name= 'commands_to_execute' ex: alias tsmstart = ' cd /usr/tivoli/tsm/server/bin; nohup ./rc.admserv & '

To open a new term at background dtterm -name term_name &

http://www.tsmguide.co.cc/ http://lazysystemadmin.blogspot.com

dsmserve.opt   contains all server details. dsmserv.dsk     contains location of the DB & LOG volumes devconfig.out   all the information about the devices which used in TSM volhist.out        all the sequential access volumes details which used in the TSM server

viosbr command Purpose      Performs the operations for backing up the virtual and logical configuration, listing the configuration,      and restoring the configuration of the Virtual I/O Server.      The viosbr command can be run only by the padmin user. $ viosbr -backup -file /tmp/ v ios_ conf ig_b kp $ viosbr -view -list   v ios_ conf ig_b kp.tar.gz to switch from user padmin to root use command oem_setup_env

Network fundamentals free course form Juniper follow this link http://www.juniper.net/us/en/training/elearning/net_fun.html

If you receive one of the following errors from the problem may be a corrupted superblock: fsck or mount commands, the fsck: Not an AIX3 file system fsck: Not an AIXV3 file system fsck: Not an AIX4 file system fsck: Not an AIXV4 file system fsck: Not a recognized file system type mount: invalid argument The problem can be resolved by restoring the backup of the superblock over the primary superblock using one of the following commands: dd count=1 bs=4k skip=31 seek=1 if=/dev/lv00 of=/dev/lv00 Once the restoration process is completed, check the integrity of the file system