Hello Everybody …
Sometimes for performance recommendations or redundancy solutions, you will need to change some parameters on fibre card, like fc_err_recov & dyntrk
TEST_SERVER#lsattr -El fscsi0
attach none How this adapter is CONNECTED False
dyntrk yes Dynamic Tracking of FC Devices True+
fc_err_recov delayed FC Fabric Event Error RECOVERY Policy True+
scsi_id Adapter SCSI ID False
sw_fc_class 3 FC Class for Fabric True
<a href="http://how-2-know.com/main/?p=2155#more-2155" class="continue-reading-link"> Continue reading <span class="meta-nav">→ </span></a>
AIX, card, chdef, chdev, class, device, efscsi, fibre, iocb, network, odm, subclass, type
The following lines are a for loop script to display disks info @ AIX System (Disk Name, Disk Unique ID, Disk Size in MB) and of course you can customize the data by add more columns:
If your work on AIX System (or any other UNIX/Linux Distribution), may be you face the following Message when you try to access SFTP:
Couldn't canonicalise: Permission denied
after many troubleshooting :
– user can access SSH without any problem.
– user can’t access SFTP
– you can switch on this user normally.
Sometimes when you try to mount file system (NFS) you will get the following Error:
#mount -o rw server1:/dir /bk
mount: 1831-008 giving up on:
vmount: Operation not permitted.
Configure DNS on AIX
To configure DNS on an AIX server:
Add the DNS server(s) to the /etc/resolv.conf configuration file:
IBM AIX has a 3 Edition (Standard, Express, Enterprise) and you can check the installed edition on you server by the following command:
and you can check the difference between each edition from the following Link:
Use the following command to rename a device:
# rendev -l hdisk4 -n hdisk53
where the ‘hdisk4’ is your device and ‘hdisk53’ is the new name.
HINT: The device must be free
Here are the commands related to error demon in AIX
To stop logging run the below command
To get rid of that log.
# rm /var/adm/ras/errlog
To restart the daemon, thus creating a new error log
Information about which PPs that are stale and which PVs are missing within a VG. The LVM and SCSI driver reserves somewhere between 7-10% of the available disk space for LVM maps, etc.
Information about all the LVs and PVs within a VG. The first 64K of a PV is reserved for this area – defined in <sys/bootrecord.h>.
The VGDA consists of
BOOTRECORD: – first 512 bytes. Allows the Read Only System (ROS) to boot system
BAD BLK DIRECTORY – found in <sys/bddir.h>
LVM RECORD – found in <lvmrec.h>